Bonjour,
 
Je rencontre depuis l'assemblage de mon nouveau matériel des BSOD fréquents faisant référence à ntoskrnl.exe ainsi que watchdog.sys
 
Ma configuration est la suivante :
 
Carte mère ASUS P7P55D LE
 
Processeur Intel i5 750 Lynnfield 2.66GHz
 
Carte graphique ATI Radeon HD5850 1Go DDR5
 
Alimentation Advance 650W
 
Mémoire vive OCZ 2x2Go 1600MHz (OCZ3G1600VL4GK)
 
Disque dur Hitachi 500Go SATA II 7500t/min
 
Boitier Antec Three Hundred (2x140mm ventilateurs + 3x120mm ventilateurs)
 
Windows Seven Professionnel 64 bits officiel licence MSDN
 
Voici le résultat de Whocrashed :
 
--------------------------------------------------------------------------------
Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
 
 
On Thu 01/04/2010 01:12:45 your computer crashed
 
This was likely caused by the following module: ntoskrnl.exe
 
Bugcheck code: 0x1A (0x3452, 0x7FEFE62C000, 0xFFFFF70001081CF8, 0x0)
 
Error: MEMORY_MANAGEMENT
 
Dump file: C:\Windows\Minidump\040110-22167-01.dmp
 
file path: C:\Windows\system32\ntoskrnl.exe
 
product: Microsoft® Windows® Operating System
 
company: Microsoft Corporation
 
description: NT Kernel & System
 
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.  
 
 
 
 
 
 
 
On Wed 31/03/2010 19:52:54 your computer crashed
 
This was likely caused by the following module: ntoskrnl.exe
 
Bugcheck code: 0xA (0xFFFFF68000132F08, 0x0, 0x0, 0xFFFFF80002A90AE2)
 
Error: IRQL_NOT_LESS_OR_EQUAL
 
Dump file: C:\Windows\Minidump\033110-29952-01.dmp
 
file path: C:\Windows\system32\ntoskrnl.exe
 
product: Microsoft® Windows® Operating System
 
company: Microsoft Corporation
 
description: NT Kernel & System
 
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.  
 
 
 
 
 
 
 
On Wed 31/03/2010 18:36:57 your computer crashed
 
This was likely caused by the following module: ntoskrnl.exe
 
Bugcheck code: 0x18 (0x0, 0xFFFFFA80044117F0, 0x2, 0xFFFFFA80054437BF)
 
Error: REFERENCE_BY_POINTER
 
Dump file: C:\Windows\Minidump\033110-21106-01.dmp
 
file path: C:\Windows\system32\ntoskrnl.exe
 
product: Microsoft® Windows® Operating System
 
company: Microsoft Corporation
 
description: NT Kernel & System
 
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.  
 
 
 
 
 
 
 
On Wed 31/03/2010 16:58:22 your computer crashed
 
This was likely caused by the following module: watchdog.sys
 
Bugcheck code: 0x10E (0x23, 0x1, 0x20000000, 0x0)
 
Error: VIDEO_MEMORY_MANAGEMENT_INTERNAL
 
Dump file: C:\Windows\Minidump\033110-16364-01.dmp
 
file path: C:\Windows\system32\drivers\watchdog.sys
 
product: Microsoft® Windows® Operating System
 
company: Microsoft Corporation
 
description: Watchdog Driver
 
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.  
 
 
 
 
 
 
 
On Wed 31/03/2010 03:46:04 your computer crashed
 
This was likely caused by the following module: ntoskrnl.exe
 
Bugcheck code: 0xFC (0xFFFFF8800889D490, 0x80000000671E3963, 0xFFFFF8800889CF10, 0x2)
 
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
 
Dump file: C:\Windows\Minidump\033110-17612-01.dmp
 
file path: C:\Windows\system32\ntoskrnl.exe
 
product: Microsoft® Windows® Operating System
 
company: Microsoft Corporation
 
description: NT Kernel & System
 
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.  
 
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
 
5 crash dumps have been found and analyzed. Note that it's not always possible to state with certainty whether a reported driver is really responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.  
 
--------------------------------------------------------------------------------
 
Pouvez-vous m'aider à éclaircir cette analyse ??? Je lance un memtest dès ce soir et je vous dirais le résultat...  
Merci.
En attente d'une réponse de votre part.
Cordialement,
Baptiste.

En effet, memtest me semble une étape obligatoire ; sinon, as-tu défini les timings de ta ram dans ton BIOS ?

Tout est en auto dans le BIOS.
J'ai testé les différents timings qu'il me propose mais j'ai préféré laisser sur auto.
Je suis encore au boulot, je fais un memtest dès mon arrivée à la maison et je vous tiens au courant.
 
Une question me turlupine tout de même, un de mes jeux (BFBC2 ou Metro2033 je ne sais plus lequel) m'a demandé l'installation de Nvidia PhysX, ma question est donc:
Nvidia PhysX et mon ATI HD5850 ne seraient-ils pas en conflits malgré le fait qu'apparemment PhysX n'influerait que sur le proc ???
 
Merci pour la réponse.

Vérifies avec CPU-Z que les timings appliqués en auto par le BIOS correspondent à ceux conseillés par le constructeur de ta RAM, si ils sont trop poussés tes soucis peuvent venir de là.