A voir également:
- Blue screen(hal.dll,ntoskrnl.exe),erreur dans les pilotes
- Blue screen windows 10 - Guide
- Erreur 0x80070643 - Accueil - Windows
- Tous les pilotes - Télécharger - Pilotes & Matériel
- Screen whatsapp - Accueil - Messagerie instantanée
- Apowersoft screen recorder - Télécharger - Capture d'écran
1 réponse
Bonjour ,
Sa plante toujours, nouveau whocrashed en espérant que quelqu'un passe par la..
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Fri 16/08/2013 09:32:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081613-40607-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4ADE7C)
Bugcheck code: 0x124 (0x0, 0xFFFFFA800B5D34F8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
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 a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
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 16/08/2013 09:26:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081613-23914-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B50)
Bugcheck code: 0xC (0x0, 0x0, 0x0, 0x0)
Error: MAXIMUM_WAIT_OBJECTS_EXCEEDED
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 the current thread exceeded the permitted number of wait objects.
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 16/08/2013 09:25:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081613-45786-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x1A (0x5003, 0xFFFFF781C0000000, 0xF41F, 0xF4210001E83F)
Error: MEMORY_MANAGEMENT
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 16/08/2013 09:21:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081613-46675-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x19 (0x3, 0xFFFFF80003415FA0, 0xFFFFF80003415FB0, 0xFFFFF80003415FA0)
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 Thu 15/08/2013 21:11:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081513-58110-01.dmp
This was probably caused by the following module: bhdrvx64.sys (BHDrvx64+0xAB51C)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF880044FE51C, 0xFFFFF88003B937A0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\ProgramData\Norton\{0C55C096-0F1D-4F28-AAA2-85EF591126E7}\NAV_20.3.1.22\Definitions\BASHDefs\20130715.001\BHDrvx64.sys
product: BASH
company: Symantec Corporation
description: BASH Driver
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: bhdrvx64.sys (BASH Driver, Symantec Corporation).
Google query: Symantec Corporation SYSTEM_SERVICE_EXCEPTION
On Thu 15/08/2013 01:56:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081513-52931-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x1A654C)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\tcpip.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote TCP/IP
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 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.
Sa plante toujours, nouveau whocrashed en espérant que quelqu'un passe par la..
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Fri 16/08/2013 09:32:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081613-40607-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4ADE7C)
Bugcheck code: 0x124 (0x0, 0xFFFFFA800B5D34F8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
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 a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
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 16/08/2013 09:26:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081613-23914-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B50)
Bugcheck code: 0xC (0x0, 0x0, 0x0, 0x0)
Error: MAXIMUM_WAIT_OBJECTS_EXCEEDED
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 the current thread exceeded the permitted number of wait objects.
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 16/08/2013 09:25:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081613-45786-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x1A (0x5003, 0xFFFFF781C0000000, 0xF41F, 0xF4210001E83F)
Error: MEMORY_MANAGEMENT
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 16/08/2013 09:21:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081613-46675-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x19 (0x3, 0xFFFFF80003415FA0, 0xFFFFF80003415FB0, 0xFFFFF80003415FA0)
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 Thu 15/08/2013 21:11:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081513-58110-01.dmp
This was probably caused by the following module: bhdrvx64.sys (BHDrvx64+0xAB51C)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF880044FE51C, 0xFFFFF88003B937A0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\ProgramData\Norton\{0C55C096-0F1D-4F28-AAA2-85EF591126E7}\NAV_20.3.1.22\Definitions\BASHDefs\20130715.001\BHDrvx64.sys
product: BASH
company: Symantec Corporation
description: BASH Driver
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: bhdrvx64.sys (BASH Driver, Symantec Corporation).
Google query: Symantec Corporation SYSTEM_SERVICE_EXCEPTION
On Thu 15/08/2013 01:56:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081513-52931-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x1A654C)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\tcpip.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote TCP/IP
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 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.