A voir également:
- Blue Scren
- Blue griffon - Télécharger - HTML
- Blue iris - Télécharger - Divers Utilitaires
- Blue stack - Télécharger - Émulation & Virtualisation
- Blue screen - Guide
- Raccourci scren - Guide
7 réponses
Installe Whocrashed et poste le rapport ici.
https://www.commentcamarche.net/telecharger/utilitaires/23795-whocrashed-free-home-edition/
https://www.commentcamarche.net/telecharger/utilitaires/23795-whocrashed-free-home-edition/
Voici :
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Fri 22/11/2013 13:06:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112213-19234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x78A8A)
Bugcheck code: 0x1000009F (0x4, 0x258, 0xFFFFFA80042E9B50, 0xFFFFF8000483D3D0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 22/11/2013 13:06:14 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: 0x9F (0x4, 0x258, 0xFFFFFA80042E9B50, 0xFFFFF8000483D3D0)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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 Thu 21/11/2013 19:13:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112113-63898-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x78A8A)
Bugcheck code: 0x1000009F (0x4, 0x258, 0xFFFFFA8004305660, 0xFFFFF8000483D3D0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 21/11/2013 12:17:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112113-56831-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x78A8A)
Bugcheck code: 0x1000009F (0x4, 0x258, 0xFFFFFA80042E7B50, 0xFFFFF80000B9C3D0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 18/11/2013 22:27:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111813-61339-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000337A41F, 0xFFFFF8800C9B5750, 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 18/11/2013 09:53:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111813-23088-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x78A8A)
Bugcheck code: 0x1000009F (0x4, 0x258, 0xFFFFFA80042E7040, 0xFFFFF80000B9C3D0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 13/11/2013 20:16:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111313-67064-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x78A8A)
Bugcheck code: 0x1000009F (0x4, 0x258, 0xFFFFFA80042E9660, 0xFFFFF800048433D0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 08/11/2013 06:46:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\110813-26785-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000331B41F, 0xFFFFF8800B702750, 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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
8 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Fri 22/11/2013 13:06:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112213-19234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x78A8A)
Bugcheck code: 0x1000009F (0x4, 0x258, 0xFFFFFA80042E9B50, 0xFFFFF8000483D3D0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 22/11/2013 13:06:14 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: 0x9F (0x4, 0x258, 0xFFFFFA80042E9B50, 0xFFFFF8000483D3D0)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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 Thu 21/11/2013 19:13:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112113-63898-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x78A8A)
Bugcheck code: 0x1000009F (0x4, 0x258, 0xFFFFFA8004305660, 0xFFFFF8000483D3D0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 21/11/2013 12:17:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112113-56831-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x78A8A)
Bugcheck code: 0x1000009F (0x4, 0x258, 0xFFFFFA80042E7B50, 0xFFFFF80000B9C3D0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 18/11/2013 22:27:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111813-61339-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000337A41F, 0xFFFFF8800C9B5750, 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 18/11/2013 09:53:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111813-23088-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x78A8A)
Bugcheck code: 0x1000009F (0x4, 0x258, 0xFFFFFA80042E7040, 0xFFFFF80000B9C3D0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 13/11/2013 20:16:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111313-67064-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x78A8A)
Bugcheck code: 0x1000009F (0x4, 0x258, 0xFFFFFA80042E9660, 0xFFFFF800048433D0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 08/11/2013 06:46:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\110813-26785-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000331B41F, 0xFFFFF8800B702750, 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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
8 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
Bonjour,
J'ai un HP pavillon G7.
Il a planté y a 2 ou 3 mois, je n'avais plus d'internet, ça ne venait pas de mon fournisseur mais des pilotes a priori. HP me demandait 289€ pour réparer, j'ai envoyé chez un petit réparateur qui m'a pris 20€ .... mais c'est depuis que j'ai ce blue screen, il me semble.
J'ai un HP pavillon G7.
Il a planté y a 2 ou 3 mois, je n'avais plus d'internet, ça ne venait pas de mon fournisseur mais des pilotes a priori. HP me demandait 289€ pour réparer, j'ai envoyé chez un petit réparateur qui m'a pris 20€ .... mais c'est depuis que j'ai ce blue screen, il me semble.
Vous n’avez pas trouvé la réponse que vous recherchez ?
Posez votre question
mince, ça fait longtemps... donc une restauration systeme ne va pas etre evidente.
Parlez en a votre "petit réparateur" car il faut connaitre pour résoudre ce type de soucis.
En effet, un blue screen peut venir de beaucoups de choses. Il n'est pas evident de poser le diognostique.
J'en ai été moi meme victime cette semaine:
https://forums.commentcamarche.net/forum/affich-29132092-bsod-whochashed#p29151138
Parlez en a votre "petit réparateur" car il faut connaitre pour résoudre ce type de soucis.
En effet, un blue screen peut venir de beaucoups de choses. Il n'est pas evident de poser le diognostique.
J'en ai été moi meme victime cette semaine:
https://forums.commentcamarche.net/forum/affich-29132092-bsod-whochashed#p29151138
Bon je vais essayé de voir, mais comme je m'absente quelques jours ce sera fin de semaine prochaine.
Je vous tiens au courant
merci
Je vous tiens au courant
merci
