Gros crash PC avec BSOD

[GixxerGSXR]

Bonjour, depuis quelques temps et de plus en plus régulièrement, j'ai des crashs avec écrans bleus (BSOD).

ma config : I7 3770K 3,5Ghz / 16 Go Ram Corsair / CG Geforce GTX680 2Go / Win7 64 bits pro.

Je soupçonne un soucis avec une des barettes RAM,

Je lance un check Ram avec memtest, mais dans le doute, je vous joint rapport whocrashed,

apparemment il s'agit de ntoskrnl.exe

Que faire ?

Help !

 

 

 

 

ntoskrnl.exe

 

System Information (local)

--------------------------------------------------------------------------------

 

computer name: STEFI7-3770K

windows version: Windows 7 Service Pack 1, 6.1, build: 7601

windows dir: C:\Windows

CPU: GenuineIntel Intel® Core i7-3770K CPU @ 3.50GHz Intel586, level: 6

8 logical processors, active mask: 255

RAM: 17132875776 total

VM: 2147352576, free: 1913053184

 

 

 

 

--------------------------------------------------------------------------------

Crash Dump Analysis

--------------------------------------------------------------------------------

 

Crash dump directory: C:\Windows\Minidump

 

Crash dumps are enabled on your computer.

 

On Thu 11/10/2012 17:24:16 GMT your computer crashed

crash dump file: C:\Windows\Minidump\101112-10686-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)

Bugcheck code: 0x1A (0x41790, 0xFFFFFA800C072930, 0xFFFF, 0x0)

Error: MEMORY_MANAGEMENT

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 severe memory management error occurred.

This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

 

 

On Thu 11/10/2012 17:24:16 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: 0x1A (0x41790, 0xFFFFFA800C072930, 0xFFFF, 0x0)

Error: MEMORY_MANAGEMENT

Bug check description: This indicates that a severe memory management error occurred.

This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

 

 

On Wed 10/10/2012 19:45:01 GMT your computer crashed

crash dump file: C:\Windows\Minidump\101012-9126-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)

Bugcheck code: 0x50 (0xFFFFD6000313A615, 0x8, 0xFFFFD6000313A615, 0x7)

Error: PAGE_FAULT_IN_NONPAGED_AREA

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 invalid system memory has been referenced.

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 Wed 10/10/2012 15:22:53 GMT your computer crashed

crash dump file: C:\Windows\Minidump\101012-9219-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)

Bugcheck code: 0x1A (0x41790, 0xFFFFFA800C072960, 0xFFFF, 0x0)

Error: MEMORY_MANAGEMENT

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 severe memory management error occurred.

This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

 

 

On Mon 17/09/2012 07:39:46 GMT your computer crashed

crash dump file: C:\Windows\Minidump\091712-9048-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)

Bugcheck code: 0x19 (0x3, 0xFFFFF8A0049CD070, 0xFFFF58A0049CD070, 0xFFFFF8A0049CD070)

Error: BAD_POOL_HEADER

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 pool header is corrupt.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

 

 

 

--------------------------------------------------------------------------------

Conclusion

--------------------------------------------------------------------------------

 

5 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.

[GixxerGSXR]

les dates de whocrashed sont bidons...

[GixxerGSXR]

çà pourrait venir du SSD 256 Go M4, il y a un update du firmware :

 

Mon lien

Modifié le 15 juin 2013 par Tonton
Suppression citation inutile. Utiliser le bouton "AJOUTER UNE REPONSE" et non "REPONDRE" :-)

[ab-web]

bonjour

 

mettre a jour le firmware

 

faire un controle de disque :

dans exécuter >>taper cmd dans la zone de recherche clic droit sur l'icone cmd >exécuter en tant qu'administrateur

dans l'invite de commande >> tape chkdsk /f /r

 

refait la maneuvre invite de commande , et tape sfc /scannow pour vérifier les fichiers système .

 

le controle de la mémoire est a faire car il est assez probable qu'il y ai un souci de ce côté .

[GixxerGSXR]

Mémoire vérifiée avec Memtest et pas de problême, par contre l'update firmware a semble t'il bien fonctionné, pas de BSOD depuis...

[leminou]

Bonjour à vous deux

 

memoire vérifiée avec Memtest et pas de problême

Vu les BS, cela métonne. Tu as fais les tests en boutant sur le CD de Memtest86 ? et laissé suffisamment longtemps ?

[GixxerGSXR]

bonjour tous, mise à jour firmware m4 effectuée et... plus un seul plantage !!!

mise a jour indispensable !!

[ab-web]

bonjour

 

bonne nouvelle

 

alors je pense que tu peu passer en résolu

aller sur le premier message puis comme ci dessous

 

Redimensionnée à 83% (453 x 188) - Cliquez pour agrandir