Je viens d'effecuter une analyse avec WhoCrashed pour voir lequel de mes driver bug, voila le rapport :
System Information (local)
--------------------------------------------------------------------------------
computer name: PC-DE-KIREN
windows version: Windows Vista Service Pack 1, 6.0, build: 6001
windows dir: C:\Windows
CPU: AuthenticAMD AMD Phenom(tm) 9500 Quad-Core Processor AMD586, level: 16
4 logical processors, active mask: 15
RAM: 3756670976 total
VM: 2147352576, free: 1997455360
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are disabled for your computer.
On Thu 28/04/2011 21:54:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini042811-06.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xCD1CB)
Bugcheck code: 0xE4 (0x1, 0xFFFFFFFF8FFCFCEC, 0x0, 0x0)
Error: WORKER_INVALID
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 memory that should not contain an executive worker item does contain such an item, or that a currently active worker item was queued.
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 which cannot be identified at this time.
On Thu 28/04/2011 12:07:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini042811-05.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xCD1CB)
Bugcheck code: 0xA0 (0x1, 0x6, 0xFFFFFFFF8A85B658, 0x0)
Error: INTERNAL_POWER_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 the power policy manager experienced a fatal error.
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 which cannot be identified at this time.
On Thu 28/04/2011 12:03:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini042811-04.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xCD1CB)
Bugcheck code: 0xE4 (0x1, 0xFFFFFFFF8FFC7CEC, 0x0, 0x0)
Error: WORKER_INVALID
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 memory that should not contain an executive worker item does contain such an item, or that a currently active worker item was queued.
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 which cannot be identified at this time.
On Thu 28/04/2011 11:55:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini042811-03.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xCD1CB)
Bugcheck code: 0xE4 (0x1, 0xFFFFFFFF8FFCBCEC, 0x0, 0x0)
Error: WORKER_INVALID
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 memory that should not contain an executive worker item does contain such an item, or that a currently active worker item was queued.
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 which cannot be identified at this time.
On Thu 28/04/2011 11:51:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini042811-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xCD1CB)
Bugcheck code: 0xE4 (0x1, 0xFFFFFFFF8FFD3CEC, 0x0, 0x0)
Error: WORKER_INVALID
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 memory that should not contain an executive worker item does contain such an item, or that a currently active worker item was queued.
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 which cannot be identified at this time.
On Wed 27/04/2011 23:21:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini042811-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xCD1CB)
Bugcheck code: 0xA0 (0x1, 0x6, 0xFFFFFFFF8A940658, 0x0)
Error: INTERNAL_POWER_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 the power policy manager experienced a fatal error.
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 which cannot be identified at this time.
On Wed 27/04/2011 21:57:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini042711-06.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xCD1CB)
Bugcheck code: 0xE4 (0x1, 0xFFFFFFFF8FFC3CEC, 0x0, 0x0)
Error: WORKER_INVALID
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 memory that should not contain an executive worker item does contain such an item, or that a currently active worker item was queued.
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 which cannot be identified at this time.
On Wed 27/04/2011 21:53:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini042711-05.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xCD1CB)
Bugcheck code: 0xE4 (0x1, 0xFFFFFFFF8FFD3CEC, 0x0, 0x0)
Error: WORKER_INVALID
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 memory that should not contain an executive worker item does contain such an item, or that a currently active worker item was queued.
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 which cannot be identified at this time.
On Wed 27/04/2011 20:56:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini042711-04.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xCD1CB)
Bugcheck code: 0xE4 (0x1, 0xFFFFFFFF8FFBFCEC, 0x0, 0x0)
Error: WORKER_INVALID
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 memory that should not contain an executive worker item does contain such an item, or that a currently active worker item was queued.
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 which cannot be identified at this time.
On Wed 27/04/2011 11:50:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini042711-03.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xCD1CB)
Bugcheck code: 0xE4 (0x1, 0xFFFFFFFF8FFD3CEC, 0x0, 0x0)
Error: WORKER_INVALID
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 memory that should not contain an executive worker item does contain such an item, or that a currently active worker item was queued.
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 which cannot be identified at this time.
On Tue 26/04/2011 23:50:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini042711-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xCD1CB)
Bugcheck code: 0xA0 (0x1, 0x6, 0xFFFFFFFF8A6E71E8, 0x0)
Error: INTERNAL_POWER_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 the power policy manager experienced a fatal error.
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 which cannot be identified at this time.
On Tue 26/04/2011 22:33:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini042711-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xCD1CB)
Bugcheck code: 0xE4 (0x1, 0xFFFFFFFF8FFCBCEC, 0x0, 0x0)
Error: WORKER_INVALID
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 memory that should not contain an executive worker item does contain such an item, or that a currently active worker item was queued.
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 which cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
12 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.
27 janv. 2014 à 07:51
Tapotez la touche F8 dès le démarrage du PC et voir s'il vous propose : Dernière bonne configuration connue.