Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: D:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Sun 9.10.2011 16:15:32 GMT your computer crashed
crash dump file: D:\WINDOWS\memory.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0xB8 (0x0, 0x0, 0x0, 0x0)
Error: ATTEMPTED_SWITCH_FROM_DPC
Bug check description: This indicates that an illegal operation was attempted by a delayed procedure call (DPC) routine.
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: Unknown .
Google query: Unknown ATTEMPTED_SWITCH_FROM_DPC
On Fri 19.8.2011 06:30:18 GMT your computer crashed
crash dump file: D:\WINDOWS\Minidump\Mini081911-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x22E0B)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFFE35047F7, 0xFFFFFFFFE3505007, 0xD020600)
Error: BAD_POOL_HEADER
file path: D:\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 which cannot be identified at this time.
On Thu 11.8.2011 07:07:18 GMT your computer crashed
crash dump file: D:\WINDOWS\Minidump\Mini081111-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xEAA88)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF805C1A88, 0xFFFFFFFFA9336A48, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: D:\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 which cannot be identified at this time.
mr. mad