écran bleu sur windows 7
Madkey14
Messages postés
3
Date d'inscription
Statut
Membre
Dernière intervention
-
Madkey14 Messages postés 3 Date d'inscription Statut Membre Dernière intervention -
Madkey14 Messages postés 3 Date d'inscription Statut Membre Dernière intervention -
Bonjour,
depuis quelques jours , j ai des écrans bleu à répétition, j ai fais un test avec Whocrashed, voici le rapport, merci.
On Sun 24/06/2018 07:31:05 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\062418-20404-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x55A87)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002EB2A87, 0xFFFFF880009A9748, 0xFFFFF880009A8FB0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 system thread 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 Sun 24/06/2018 07:31:05 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!ltrGetNextRange+0x334)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF80002EB2A87, 0xFFFFF880009A9748, 0xFFFFF880009A8FB0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 24/06/2018 07:11:33 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\062418-18439-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xA48A0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002EAF1F5, 0xFFFFF880080D2590, 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 Sat 23/06/2018 22:16:09 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\062318-27518-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xA48A0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002FE4057, 0xFFFFF88008B8D810, 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 Sat 23/06/2018 21:32:34 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\062318-30654-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xA4870)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 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 might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
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 23/06/2018 21:26:53 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\062318-29811-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xA48A0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002FE737D, 0xFFFFF88008633D30, 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 Sat 23/06/2018 19:32:33 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\062318-33930-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xA48A0)
Bugcheck code: 0x34 (0x50853, 0xFFFFF880031AA5C8, 0xFFFFF880031A9E30, 0xFFFFF80002FE08F0)
Error: CACHE_MANAGER
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 problem occurred in the file system's cache manager.
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 23/06/2018 16:38:12 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\062318-34429-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002F7153A, 0xFFFFF8800798AFA0, 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.
depuis quelques jours , j ai des écrans bleu à répétition, j ai fais un test avec Whocrashed, voici le rapport, merci.
On Sun 24/06/2018 07:31:05 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\062418-20404-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x55A87)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002EB2A87, 0xFFFFF880009A9748, 0xFFFFF880009A8FB0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 system thread 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 Sun 24/06/2018 07:31:05 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!ltrGetNextRange+0x334)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF80002EB2A87, 0xFFFFF880009A9748, 0xFFFFF880009A8FB0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 24/06/2018 07:11:33 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\062418-18439-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xA48A0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002EAF1F5, 0xFFFFF880080D2590, 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 Sat 23/06/2018 22:16:09 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\062318-27518-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xA48A0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002FE4057, 0xFFFFF88008B8D810, 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 Sat 23/06/2018 21:32:34 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\062318-30654-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xA4870)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 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 might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
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 23/06/2018 21:26:53 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\062318-29811-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xA48A0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002FE737D, 0xFFFFF88008633D30, 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 Sat 23/06/2018 19:32:33 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\062318-33930-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xA48A0)
Bugcheck code: 0x34 (0x50853, 0xFFFFF880031AA5C8, 0xFFFFF880031A9E30, 0xFFFFF80002FE08F0)
Error: CACHE_MANAGER
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 problem occurred in the file system's cache manager.
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 23/06/2018 16:38:12 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\062318-34429-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002F7153A, 0xFFFFF8800798AFA0, 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.
A voir également:
- écran bleu sur windows 7
- Supprimer rond bleu whatsapp - Guide
- Photofiltre 7 - Télécharger - Retouche d'image
- Clé windows 7 - Guide
- Double ecran - Guide
- Retourner ecran windows - Guide
2 réponses
Salut,
Plus d'infos sur le fichier :
https://www.commentcamarche.net/contents/915-ntoskrnl-ntoskrnl-exe
Soit ton Windows est endommagé soit ton disque dur.
Tu devrais faire une analyse en mode sans echec et avec la recherche des cluster défectueux (ça risque de prendre un certains moment selon la taille de ton disque dur :
https://www.commentcamarche.net/informatique/windows/171-verifier-et-reparer-un-disque-dur-avec-chkdsk-sous-windows/
Plus d'infos sur le fichier :
https://www.commentcamarche.net/contents/915-ntoskrnl-ntoskrnl-exe
Soit ton Windows est endommagé soit ton disque dur.
Tu devrais faire une analyse en mode sans echec et avec la recherche des cluster défectueux (ça risque de prendre un certains moment selon la taille de ton disque dur :
https://www.commentcamarche.net/informatique/windows/171-verifier-et-reparer-un-disque-dur-avec-chkdsk-sous-windows/
Salut Aranud87, merci pour tes infos, par contre le mode sans echec ne fonctionne pas sur l'ordi.
Je fais bien f8 et mode sans echec, le pc reboot et lance un genre d analyse sur fond noir qui dure quelques secondes mais une fois fini, le pc reboot de nouveau en mode normal.
J ai test crystaldiskinfo et l état de mes disques durs sont corrects, sachant que j ai formater l'ordi hier soir.
Dans le gestionnaire de périphériques, j'ai un contrôleur de bus USB avec un point d'exclamation et un périphérique inconnu avec un point d exclamation.
Je dois envoyer en réparation le pc ou on peut encore trouver une solution à mon problème ? merci.
Je fais bien f8 et mode sans echec, le pc reboot et lance un genre d analyse sur fond noir qui dure quelques secondes mais une fois fini, le pc reboot de nouveau en mode normal.
J ai test crystaldiskinfo et l état de mes disques durs sont corrects, sachant que j ai formater l'ordi hier soir.
Dans le gestionnaire de périphériques, j'ai un contrôleur de bus USB avec un point d'exclamation et un périphérique inconnu avec un point d exclamation.
Je dois envoyer en réparation le pc ou on peut encore trouver une solution à mon problème ? merci.