Bonjour,
J'ai des écrans bleus à répétition depuis quelques temps. En fait ça fait suite à une modification du PC : remplacement de vieilles barrettes par des neuves, ainsi que deux cartes graphiques neuves.
Le PC était sous Vista, je me suis dit il supporte pas tous ces changements hop je vais passer sous win7+ssd c'est l'occasion... et ça ne change rien.... d'autant plus que j'ai eu des écrans bleus pendant les updates donc je suis bon pour tout formatter et reinstall quand le problème sera résolu pour éviter d'avoir un win7 à moitié vérolé dès le départ.
J'ai fait une analyse WMD et ça me rapporte un problème hardware... Ce sont ces barrettes :
http://www.materiel.net/barrette-m [...] 20785.html
La carte mère c'est ça, je ne pense pas m'être dans le modèle de barrettes?
http://fr.asus.com/Motherboards/AM [...] LI_Deluxe/
Je pense donc remettre les vieilles barrettes pour voir si ça vient bien des barrettes...
D'autres pistes ou tests à me conseiller? 
Edit : ceci afin de bétonner mon analyse puisque ça va sentir le SAV chez le VPC chez qui j'ai commandé les barrettes. 
Voici le rapport de mes derniers plantages sous Whocrashed :
On Mon 09/07/2012 17:42:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070912-34484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800028FCA1A, 0x1, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 a kernel-mode program generated an exception which the error handler did not catch.
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 which cannot be identified at this time.
On Mon 09/07/2012 17:42:49 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: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800028FCA1A, 0x1, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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 which cannot be identified at this time.
On Mon 09/07/2012 17:38:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070912-14343-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002B74B96, 0xFFFFF880026E7160, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 which cannot be identified at this time.
On Mon 09/07/2012 17:25:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070912-15390-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x5A88)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF880062AD428, 0xFFFFF880062ACC80, 0xFFFFF80002878F40)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
Message édité par damtoul le 10-07-2012 à 10:27:24
---------------
Plouf plouf!
