Bonjour
Depuis que j'ai monté ma config (voir plus loin) je subi l'apparition  aléatoire d'écran bleu dont je n'ai meme pas le temps de traduire les inscriptions vu que je suis nul en anglais.
Quelle procédure pour déterminer d'ou viens le probléme ?
est-ce plutot matériel ou de windows ?
Merci.
 
 
1 x Boîtier PC Moyen Tour Lian-Li PC-B25S
 1 x Alimentation Full modulaire Seasonic - 80+ Gold - 850W  
 1 x Carte mère ASUS P8Z68-DELUXE-B3 - Chipset Intel Z68 - Socket 1155
 2 x Mémoire Kit de 2 Barrettes DDR3 PC3-12800 - 2 x 2 Go (4 Go) 1600 MHz - CAS 8 - CMX4GX3M2A1600C8  
 1 x Processeur INTEL Core i5 2500K - 3.3 GHz - Socket LGA1155  
 1 x Ventilateur Noctua NH-U12P SE2 - Socket Intel 1156/1366/775 et AMD AM3/AM2+/AM2
1 x Disque Mémoire SSD M4 -SATA III – 2’’5 – 128 go - CT128M4SSD2
1 x-WD Black disque dur interne 1To(1000 go)7200 tours/min.interface SATA III 6Gbs/s mémoire cache  64 Mo- format 3.5
1 x -ASUS GTX570 / Carte graphique NVIDIA Geforce GTX 570 direct CU II-GPU cadencé à 742 Mhz-mémoire 1280 Go-PCI express 2
1 x Pack Clavier Souris sans fil - Wireless Desktop MK710

c’est bin dommage car les infos de l’écran bleu sont primordiales
essaye de lancer whocrashed pour voir si tu as des dump exploitables,
sinon change les options de redémarrage en cas d'incident

salut,  
je met le rapport de whocrashed si cela peut aider:
Crash dump directory: C:\Windows\Minidump
 
Crash dumps are enabled on your computer.
 
 
On Fri 19/10/2012 14:22:12 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x109 (0xA3A039D8A04866B3, 0xB3B7465EF2C53609, 0xFFFFF800034AEE80, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
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. Likely the culprit is another driver on your system which cannot be identified.  
 
 
 
On Fri 19/10/2012 09:50:26 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x19 (0x3, 0xFFFFFA8006C952E0, 0xFFFFFA8006C952E0, 0xFFFF7A8006C952E0)
Error: BAD_POOL_HEADER
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. Likely the culprit is another driver on your system which cannot be identified.  
 
 
 
Conclusion  
 
 
2 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.  
 
 
Merci
 
 
en voila d'autre;
On Sat 27/10/2012 04:19:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102712-21777-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)  
Bugcheck code: 0xA (0xFFFFFA808A934090, 0x2, 0x0, 0xFFFFF800034EBCEF)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.  
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.  
 
 
 
On Sat 27/10/2012 04:19:51 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)  
Bugcheck code: 0xA (0xFFFFFA808A934090, 0x2, 0x0, 0xFFFFF800034EBCEF)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.  
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.