Chalut chalut !
J'ai très régulièrement ce blue screen, surtout au démarrage :
Je ne sais pas du tout à quoi correspondent les code d'erreur.
Disque dur ? Ram ? Périphérique ?
Inscrivez-vous gratuitement
pour pouvoir participer, suivre les réponses en temps réel, voter pour les messages, poser vos propres questions et recevoir la newsletter
Blue screen récurrent
Chalut chalut !
J'ai très régulièrement ce blue screen, surtout au démarrage :
Je ne sais pas du tout à quoi correspondent les code d'erreur.
Disque dur ? Ram ? Périphérique ?
Bonjour,
Tout d'abord, il me faudrait plus de précisions : Quel OS as-tu ?
c'est un PC de bureau ou portable ? De toute façon ce BSOD (Blue Screen Of Dead) est très souvent lié à une défaillance de disque dur. Je te conseille donc d'en essayer un autre...
Bonjour
Problème de mémoire RAM soit une barrette HS soit un problème avec une application qui plante en mémoire.
Faire un test avec une seule barrette l'une puis l'autre.
Crotte, j'ai 6 barrettes ...Envoyé par JML19
Je vais essayer cela et je verrais si ça change quelque chose.
Je crois qui a moyen de sortir les dump de windows et de les faire analyser par la suite avec un utilitaire ... Je vais chercher et je te reviens un de mes collegue l'avait fait
Merci, je vais voir ce que ça va donner, car j'ai tester ma RAM et ça ne change rien
Salut
Essaie avec le logiciel WhoCrashed
@+
Bestall666
Bonjour
Essais une mise à jour du pilote chipset carte mère et du pilote SATA AHCI.
Je viens de faire une analyse avec Whocrashed :
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 29/10/2012 20:21:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102912-18720-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x5F68)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF880037E8848, 0xFFFFF880037E80B0, 0xFFFFF880012E4E19)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
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 that cannot be identified at this time.
On Mon 29/10/2012 20:21:43 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x5F68)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF880037E8848, 0xFFFFF880037E80B0, 0xFFFFF880012E4E19)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
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 that cannot be identified at this time.
On Mon 29/10/2012 20:18:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102912-18049-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8007BB5B30, 0xFFFFFA8007BB5E10, 0xFFFFF80002FD1D50)
Error: CRITICAL_OBJECT_TERMINATION
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 process or thread crucial to system operation has unexpectedly exited or been terminated.
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 Mon 29/10/2012 14:25:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102912-18486-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002C8E161, 0xFFFFF88007D26010, 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 that cannot be identified at this time.
On Mon 29/10/2012 14:20:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102912-19250-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x5F68)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF880087B6848, 0xFFFFF880087B60B0, 0xFFFFF880012ADE19)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
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 that cannot be identified at this time.
On Mon 29/10/2012 14:16:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102912-19094-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002F4F3CF, 0xFFFFF88003BD6770, 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 that cannot be identified at this time.
On Mon 29/10/2012 14:02:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102912-39234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x19 (0x3, 0xFFFFFA8005177210, 0xFFFF7A8005177210, 0xFFFFFA8005177210)
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.
On Mon 29/10/2012 13:54:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102912-38641-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x19 (0x3, 0xFFFFFA8005178090, 0xFFFF7A8005178090, 0xFFFFFA8005178090)
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.
On Mon 29/10/2012 13:46:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102912-27534-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x50 (0xFFFFF6BB7DA0FFD8, 0x0, 0xFFFFF80002D76407, 0x5)
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 Mon 29/10/2012 13:42:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102912-27986-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002DED41D, 0xFFFFF880029C3DA0, 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 that cannot be identified at this time.
On Mon 29/10/2012 13:40:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102912-28438-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002C9FEE3)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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 29/10/2012 13:38:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102912-30357-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800030E033E, 0x0, 0xFFFFFFFFFFFFFFFF)
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 that cannot be identified at this time.
On Mon 29/10/2012 13:36:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102912-28220-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002F3ECBE, 0xFFFFF88007A70040, 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 that cannot be identified at this time.
On Mon 29/10/2012 13:34:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102912-28672-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x5F68)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF880037EF3F8, 0xFFFFF880037EEC60, 0xFFFFF880012C0C46)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
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 that cannot be identified at this time.
On Mon 29/10/2012 13:32:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102912-30248-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x5F68)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88006E73848, 0xFFFFF88006E730B0, 0xFFFFF880012B0E19)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
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 that cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
21 crash dumps have been found and analyzed. Only 15 are included in this report. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.
Moi pas tout comprendre
Moi je lancerais un scan de disk avec Hiren Boot CD, pour vérifié si ton disque a des bad sector!
Ca semble être ca selon moi ton problème et ca rend ton KERNEL de windows instable.
pour les dump, une corde de plus à tes compétences
mais ya une chose qui me chicotte un peu (that the Intel CPU generated a trap and the kernel failed to catch this trap)
a tu vraiment les bons driver de ton PC? tu peu aller juste vérifier sur ma-config.com c'est pas 100% parfait mais ca donne une bonne idée
Sur maconfig.com, il me trouve juste des drivers plus récent. Mais le soucis c'est que certain me font "freezer" mon ordi lorsque je les met à jour. Donc je n'ai installé que ceux qui étaient fourni avec le PC.
Je suis en train de télécharger Hiren Boot CD
EDIT: Euh ... Que dois-je faire exactement avec Hiren Boot ? Car je ne comprends pas, tout est en anglais
UP !
Sur la ligne Read Error Rate j'ai 117 Current, 99 Worst, 6 Threshold.
Je ne sais pas trop si ça peux m'aider ...
Avec hiren tu va pouvoir faire plusieurs chose sur ton pc je l'utilise souvent depuis que je connais l'existence. Il faudra que ti la grave sur cd et que tu redemarre ton pc avec , comme si tu installais windows et apres tu va avoir un menu avec plein d'applications pour verifier ton pc.
Je te reviens avec une liste d'application utile dans ton cas
-Envoyé iPhone-
Bonjour,
Est-ce que tu as SMART activé sur ton BIOS? Si oui, et si le disque dur est défectueux, cette option devrait te signaler des erreurs.
Autrement, tu devrais essayer avec CrystalDiskInfo. Un petit utilitaire qui vérifie la santé de ton disque dur.
J'ai utilisé CrystalDiskInfo. Voici ce que ça donne :
Bonsoir
Fais des tests avec HD Tune, ton disque n'est pas au mieux de sa forme.
Voici ce que donne le scan :
Si le disque est sur la fin de vie, autant que je le change. Surtout que c'est un PC que je vais vendre prochainement
Si tu a un autre disque dur, fait un clone de ton disque, hiren boot cd a l'utilitaire pour le faire 'GHOST ou CLONEZILLA' pendant une semaine tu pourrais voir si le pc va mieu et de 2 tu va avoir un backup si ya problem eventuellement
-Envoyer iPhone-
Bonjour
Niveau test HD Tune il fonctionne bien.
Oula, l'un me dit qu'il fonctionne bien, l'autre me dit que non ... Je doit croire qui ?
Vous avez un bloqueur de publicités installé.
Le Club Developpez.com n'affiche que des publicités IT, discrètes et non intrusives.
Afin que nous puissions continuer à vous fournir gratuitement du contenu de qualité, merci de nous soutenir en désactivant votre bloqueur de publicités sur Developpez.com.
Répondre avec citation
Partager