écran bleu/ ordi bloqué
Résolu
biba31
Messages postés
221
Date d'inscription
Statut
Membre
Dernière intervention
-
biba31 Messages postés 221 Date d'inscription Statut Membre Dernière intervention -
biba31 Messages postés 221 Date d'inscription Statut Membre Dernière intervention -
Bonjour,
J'ai depuis quelques semaines des soucis avec mon PC HP Compaq:
-quelques minutes après le démarrage il se bloque avant même que je touche à la souris : l'écran reste figé et ni la souris ni le clavier ne fonctionnent, avec parfois des rayures noires et roses sur l'écran.
Dc je n'ai qu'à l'éteindre par le bouton de l'unité centrale. En redémarrant, des fois ça marche et d'autres non : l'unité centrale se met en marche mais l'écran est toujours en veille.
-Parois aussi après le démarrage, l'écran se met en veille tout seul et ne rallume pas.
-Parois aussi ça donne un écran bleu. Le dernier message que j'ai pu retenir était "DRIVER_IRQL_NOT_LESS_OR EQUAL"
J'ai besoin de votre aide et merci beaucoup d'avance.
J'ai depuis quelques semaines des soucis avec mon PC HP Compaq:
-quelques minutes après le démarrage il se bloque avant même que je touche à la souris : l'écran reste figé et ni la souris ni le clavier ne fonctionnent, avec parfois des rayures noires et roses sur l'écran.
Dc je n'ai qu'à l'éteindre par le bouton de l'unité centrale. En redémarrant, des fois ça marche et d'autres non : l'unité centrale se met en marche mais l'écran est toujours en veille.
-Parois aussi après le démarrage, l'écran se met en veille tout seul et ne rallume pas.
-Parois aussi ça donne un écran bleu. Le dernier message que j'ai pu retenir était "DRIVER_IRQL_NOT_LESS_OR EQUAL"
J'ai besoin de votre aide et merci beaucoup d'avance.
A voir également:
- écran bleu/ ordi bloqué
- Supprimer rond bleu whatsapp - Guide
- Ordi qui rame - Guide
- Double ecran - Guide
- Ecran bleu ordi - Guide
- Code puk bloqué - Guide
4 réponses
bonjour
va dans C:\Windows\minidump
et poste le fichier .dmp ou les fichier dmp
sinon utilise
whocrashed
https://www.commentcamarche.net/telecharger/utilitaires/23795-whocrashed-free-home-edition/#q=whocrashed&cur=1&url=%2F
analyse et poste le rapport
merçi
va dans C:\Windows\minidump
et poste le fichier .dmp ou les fichier dmp
sinon utilise
whocrashed
https://www.commentcamarche.net/telecharger/utilitaires/23795-whocrashed-free-home-edition/#q=whocrashed&cur=1&url=%2F
analyse et poste le rapport
merçi
2ème solution
tapote F8 au demarrage dans les option avancée choisit invite de commande
entrée
tu doi avoir la fe^tre
C:\Windows\system32
si ce n'est pas le cas tape cd C:\Windows\System32
ensuite tape la commande
start verifier.exe
suivant suivant il va te demander de rebbot
PS: verifier desactive les pilote defectueux comme cela tu peut demarrer et acceder au dossier minidump pour une analyse
si tu ne peut pas demarrer tu as juste a tapoter F8 et demarrer avec la derniere bonne config ou en mode sans echec
donc pour analyser minidump tu as le choix entre
whocrashed
Nirsoft
&
windbg
tapote F8 au demarrage dans les option avancée choisit invite de commande
entrée
tu doi avoir la fe^tre
C:\Windows\system32
si ce n'est pas le cas tape cd C:\Windows\System32
ensuite tape la commande
start verifier.exe
suivant suivant il va te demander de rebbot
PS: verifier desactive les pilote defectueux comme cela tu peut demarrer et acceder au dossier minidump pour une analyse
si tu ne peut pas demarrer tu as juste a tapoter F8 et demarrer avec la derniere bonne config ou en mode sans echec
donc pour analyser minidump tu as le choix entre
whocrashed
Nirsoft
&
windbg
1--> controle tes pilote
2-->lance une analyse antivirus minutieuse " complete "( netbt.sys)
3-->ton pc chauffe nettoie le .ntkrnlpa.exe
4-->manque de memoire (RAM) win32k.sys
quelle est ta config
dans demarrer tape
dxdiag
et poste une capture ecran ou enregistre les information sur le bureau et poste les ici.
2-->lance une analyse antivirus minutieuse " complete "( netbt.sys)
3-->ton pc chauffe nettoie le .ntkrnlpa.exe
4-->manque de memoire (RAM) win32k.sys
quelle est ta config
dans demarrer tape
dxdiag
et poste une capture ecran ou enregistre les information sur le bureau et poste les ici.
merci beaucoup mais je ne sais pas quel logiciel on utilise pour ouvrir un fichier dmp.
whocrashed
ou
nirsoft
http://launcher.nirsoft.net/download.html
pour nirsoft une fois installer click sur
nirlauncher ( lance le programme)
puis
all utilities
bluescreenview
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 09/11/2013 20:54:10 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFFFFF88D71131)
Bugcheck code: 0xD1 (0xC, 0x2, 0x0, 0xFFFFFFFF88D71131)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error.
Google query: DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Sat 09/11/2013 20:49:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\110913-21169-01.dmp
This was probably caused by the following module: netbt.sys (netbt+0x3080)
Bugcheck code: 0xC5 (0xAE8DF78, 0x2, 0x1, 0xFFFFFFFF83167476)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\Windows\system32\drivers\netbt.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: MBT Transport driver
Bug check description: This indicates that the system attempted to access invalid memory at a process IRQL that was too high.
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 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 04/11/2013 23:08:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\110513-16192-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDCB3C)
Bugcheck code: 0x18 (0x0, 0xFFFFFFFF84550AE8, 0x3, 0xFFFFFFFFC07F4FC0)
Error: REFERENCE_BY_POINTER
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the reference count of an object is illegal for the current state of the object.
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 Sat 26/10/2013 12:08:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102613-13681-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x896A5)
Bugcheck code: 0x1A (0x41287, 0x20206F55, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\win32k.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 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 Wed 23/10/2013 18:38:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102313-19546-01.dmp
This was probably caused by the following module: ataport.sys (ataport+0xA09D)
Bugcheck code: 0xD1 (0x38, 0x2, 0x0, 0xFFFFFFFF88BD409D)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ataport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ATAPI Driver Extension
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 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 Wed 23/10/2013 18:35:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102313-25942-01.dmp
This was probably caused by the following module: Unknown (0xFFFFFFFF82E91ABB)
Bugcheck code: 0xD1 (0x3, 0x2, 0x1, 0xFFFFFFFF88BEB05B)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error.
Google query: DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Sun 20/10/2013 15:19:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102013-25490-01.dmp
This was probably caused by the following module: Unknown (0xFFFFFFFF82F57232)
Bugcheck code: 0x19 (0x3, 0xFFFFFFFF82F6CA20, 0xFFFFFFFF86BE92D8, 0xFFFFFFFF82F6CA20)
Error: BAD_POOL_HEADER
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.
A third party driver was identified as the probable root cause of this system error.
Google query: BAD_POOL_HEADER
On Sun 20/10/2013 15:17:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102013-19921-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x120996)
Bugcheck code: 0x19 (0x3, 0xFFFFFFFFAFFA4948, 0xDC0A802, 0xFFFFFFFFE8C46902)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntkrnlpa.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 Sun 20/10/2013 14:08:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102013-20264-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x20DF4)
Bugcheck code: 0x19 (0x3, 0xFFFFFFFF85EA82E8, 0xFFFFFFFF87CBCA70, 0xFFFFFFFF85EA82E8)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Gestionnaire de filtres de système de fichiers Microsoft
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 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 Sat 19/10/2013 15:08:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101913-21075-01.dmp
This was probably caused by the following module: Unknown (0xFFFFFFFF82F30B3C)
Bugcheck code: 0xFE (0x6, 0xFFFFFFFF87FC7AE0, 0x43787254, 0x0)
Error: BUGCODE_USB_DRIVER
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
A third party driver was identified as the probable root cause of this system error.
Google query: BUGCODE_USB_DRIVER
On Fri 18/10/2013 17:02:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101813-20092-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xCA9B)
Bugcheck code: 0xC5 (0x4, 0x2, 0x0, 0xFFFFFFFF82F7487B)
Error: DRIVER_CORRUPTED_EXPOOL
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 that the system attempted to access invalid memory at a process IRQL that was too high.
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 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 Sun 13/10/2013 16:46:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101313-17581-01.dmp
This was probably caused by the following module: Unknown (0xFFFFFFFF82F247FF)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82F247FF, 0xFFFFFFFF96ECB6EC, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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.
A third party driver was identified as the probable root cause of this system error.
Google query: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Mon 12/08/2013 16:03:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081213-12979-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x3D810)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFF88677500, 0xFFFFFFFF88677550, 0x80A0009)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\win32k.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 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
--------------------------------------------------------------------------------
13 crash dumps have been found and analyzed.
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.
On Sat 09/11/2013 20:54:10 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFFFFF88D71131)
Bugcheck code: 0xD1 (0xC, 0x2, 0x0, 0xFFFFFFFF88D71131)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error.
Google query: DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Sat 09/11/2013 20:49:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\110913-21169-01.dmp
This was probably caused by the following module: netbt.sys (netbt+0x3080)
Bugcheck code: 0xC5 (0xAE8DF78, 0x2, 0x1, 0xFFFFFFFF83167476)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\Windows\system32\drivers\netbt.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: MBT Transport driver
Bug check description: This indicates that the system attempted to access invalid memory at a process IRQL that was too high.
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 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 04/11/2013 23:08:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\110513-16192-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDCB3C)
Bugcheck code: 0x18 (0x0, 0xFFFFFFFF84550AE8, 0x3, 0xFFFFFFFFC07F4FC0)
Error: REFERENCE_BY_POINTER
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the reference count of an object is illegal for the current state of the object.
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 Sat 26/10/2013 12:08:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102613-13681-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x896A5)
Bugcheck code: 0x1A (0x41287, 0x20206F55, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\win32k.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 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 Wed 23/10/2013 18:38:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102313-19546-01.dmp
This was probably caused by the following module: ataport.sys (ataport+0xA09D)
Bugcheck code: 0xD1 (0x38, 0x2, 0x0, 0xFFFFFFFF88BD409D)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ataport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ATAPI Driver Extension
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 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 Wed 23/10/2013 18:35:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102313-25942-01.dmp
This was probably caused by the following module: Unknown (0xFFFFFFFF82E91ABB)
Bugcheck code: 0xD1 (0x3, 0x2, 0x1, 0xFFFFFFFF88BEB05B)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error.
Google query: DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Sun 20/10/2013 15:19:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102013-25490-01.dmp
This was probably caused by the following module: Unknown (0xFFFFFFFF82F57232)
Bugcheck code: 0x19 (0x3, 0xFFFFFFFF82F6CA20, 0xFFFFFFFF86BE92D8, 0xFFFFFFFF82F6CA20)
Error: BAD_POOL_HEADER
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.
A third party driver was identified as the probable root cause of this system error.
Google query: BAD_POOL_HEADER
On Sun 20/10/2013 15:17:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102013-19921-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x120996)
Bugcheck code: 0x19 (0x3, 0xFFFFFFFFAFFA4948, 0xDC0A802, 0xFFFFFFFFE8C46902)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntkrnlpa.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 Sun 20/10/2013 14:08:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102013-20264-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x20DF4)
Bugcheck code: 0x19 (0x3, 0xFFFFFFFF85EA82E8, 0xFFFFFFFF87CBCA70, 0xFFFFFFFF85EA82E8)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Gestionnaire de filtres de système de fichiers Microsoft
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 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 Sat 19/10/2013 15:08:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101913-21075-01.dmp
This was probably caused by the following module: Unknown (0xFFFFFFFF82F30B3C)
Bugcheck code: 0xFE (0x6, 0xFFFFFFFF87FC7AE0, 0x43787254, 0x0)
Error: BUGCODE_USB_DRIVER
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
A third party driver was identified as the probable root cause of this system error.
Google query: BUGCODE_USB_DRIVER
On Fri 18/10/2013 17:02:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101813-20092-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xCA9B)
Bugcheck code: 0xC5 (0x4, 0x2, 0x0, 0xFFFFFFFF82F7487B)
Error: DRIVER_CORRUPTED_EXPOOL
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 that the system attempted to access invalid memory at a process IRQL that was too high.
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 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 Sun 13/10/2013 16:46:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101313-17581-01.dmp
This was probably caused by the following module: Unknown (0xFFFFFFFF82F247FF)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82F247FF, 0xFFFFFFFF96ECB6EC, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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.
A third party driver was identified as the probable root cause of this system error.
Google query: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Mon 12/08/2013 16:03:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081213-12979-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x3D810)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFF88677500, 0xFFFFFFFF88677550, 0x80A0009)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\win32k.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 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.