A voir également:
- Bluescreen
- Bluescreen - Guide
- Bluescreen code 101 - Forum Windows 10
- BlueScreen !! ✓ - Forum Windows
- BlueScreen - Forum Windows 7
- BlueScreen ✓ - Forum Windows
3 réponses
hisaeh
Messages postés
2642
Date d'inscription
samedi 10 mars 2007
Statut
Membre
Dernière intervention
23 août 2019
572
24 oct. 2012 à 09:26
24 oct. 2012 à 09:26
Bonjour,
Tu peux utiliser Whocrashed pour en savoir peut etre un peu plus sur la cause.
https://www.commentcamarche.net/telecharger/utilitaires/23795-whocrashed-free-home-edition/
Tu peux utiliser Whocrashed pour en savoir peut etre un peu plus sur la cause.
https://www.commentcamarche.net/telecharger/utilitaires/23795-whocrashed-free-home-edition/
Merci beaucoup hisaeh de votre réponse et excusez la lenteur de la mienne.
J'ai utilisé Whocrashed comme vous me l'avez conseillé. Voici le rapport d'analyse :
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 28/10/2012 12:48:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102812-38111-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002FB426C, 0xFFFFF8800A24BA90, 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 Sun 28/10/2012 12:48:39 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: 0x3B (0xC0000005, 0xFFFFF80002FB426C, 0xFFFFF8800A24BA90, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 Wed 24/10/2012 06:52:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102412-27643-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000300D26C, 0xFFFFF8800AC9AA90, 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 Fri 19/10/2012 20:05:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101912-28984-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002FB726C, 0xFFFFF8800A2F7A90, 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 Tue 10/04/2012 07:36:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041012-28142-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD10)
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 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 Fri 24/02/2012 10:14:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022412-30420-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC10)
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 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.
Que dois-je faire ?
Merci d'avance de vos réponses.
J'ai utilisé Whocrashed comme vous me l'avez conseillé. Voici le rapport d'analyse :
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 28/10/2012 12:48:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102812-38111-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002FB426C, 0xFFFFF8800A24BA90, 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 Sun 28/10/2012 12:48:39 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: 0x3B (0xC0000005, 0xFFFFF80002FB426C, 0xFFFFF8800A24BA90, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 Wed 24/10/2012 06:52:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102412-27643-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000300D26C, 0xFFFFF8800AC9AA90, 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 Fri 19/10/2012 20:05:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101912-28984-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002FB726C, 0xFFFFF8800A2F7A90, 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 Tue 10/04/2012 07:36:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041012-28142-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD10)
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 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 Fri 24/02/2012 10:14:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022412-30420-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC10)
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 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.
Que dois-je faire ?
Merci d'avance de vos réponses.
