Computer keeps restarting & minidumps

Gunsr2

Distinguished
Mar 22, 2010
3
0
18,510
My computer keeps restarting for no apparent reason. Can someone make any sense of minidumps? Or these?

Error code 000000c2, parameter1 00000007, parameter2 00000cd4, parameter3 00086c69, parameter4 e1331fc0.

Error code 0000000a, parameter1 00000256, parameter2 0000001c, parameter3 00000000, parameter4 804ec162.

Error code 1000008e, parameter1 c0000005, parameter2 bfa04040, parameter3 ed5363bc, parameter4 00000000.


Really appreciate any help.
 

Gunsr2

Distinguished
Mar 22, 2010
3
0
18,510
OK, I downloaded Whocrashed and ran it. Here is what it has come up with:

On Mon 22/03/2010 7:30:38 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xC2 (0x7, 0xCD4, 0x86C69, 0xE1331FC0)
Error: BAD_POOL_CALLER
Dump file: C:\WINDOWS\Minidump\Mini032210-01.dmp
file path: C:\WINDOWS\System32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sun 21/03/2010 4:45:09 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0x256, 0x1C, 0x0, 0x804EC162)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\WINDOWS\Minidump\Mini032110-01.dmp
file path: C:\WINDOWS\System32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sat 20/03/2010 6:47:49 AM your computer crashed
This was likely caused by the following module: ati2cqag.dll
Bugcheck code: 0x1000008E (0xC0000005, 0xBFA04040, 0xED5363BC, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
Dump file: C:\WINDOWS\Minidump\Mini032010-01.dmp
file path: C:\WINDOWS\System32\ati2cqag.dll
product: ATI Radeon Family
company: ATI Technologies Inc.
description: Central Memory Manager / Queue Server Module



On Mon 8/03/2010 7:00:39 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xC5 (0x71AC2224, 0x2, 0x1, 0x8053A29D)
Error: DRIVER_CORRUPTED_EXPOOL
Dump file: C:\WINDOWS\Minidump\Mini030810-02.dmp
file path: C:\WINDOWS\System32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Mon 8/03/2010 6:43:15 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xC5 (0x0, 0x2, 0x1, 0x8053A29D)
Error: DRIVER_CORRUPTED_EXPOOL
Dump file: C:\WINDOWS\Minidump\Mini030810-01.dmp
file path: C:\WINDOWS\System32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sat 6/03/2010 1:28:39 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000008E (0xC0000005, 0x80539318, 0xB884ABB0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
Dump file: C:\WINDOWS\Minidump\Mini030610-01.dmp
file path: C:\WINDOWS\System32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Wed 3/03/2010 9:46:46 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x4E (0x8F, 0x3AB, 0x10C2B, 0x0)
Error: PFN_LIST_CORRUPT
Dump file: C:\WINDOWS\Minidump\Mini030310-01.dmp
file path: C:\WINDOWS\System32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Fri 5/02/2010 8:55:47 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0xD8740004, 0x1C, 0x0, 0x804D8043)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\WINDOWS\Minidump\Mini020510-01.dmp
file path: C:\WINDOWS\System32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sun 3/01/2010 7:05:18 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000008E (0x80000004, 0x804FA0C2, 0xB7DF2170, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
Dump file: C:\WINDOWS\Minidump\Mini010310-01.dmp
file path: C:\WINDOWS\System32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sun 1/03/2009 8:40:11 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000008E (0x80000004, 0x804FA0C2, 0xEC9A2150, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
Dump file: C:\WINDOWS\Minidump\Mini030109-01.dmp
file path: C:\WINDOWS\System32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sun 10/08/2008 8:22:38 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x76 (0x0, 0x811DEBB0, 0x1, 0x0)
Error: PROCESS_HAS_LOCKED_PAGES
Dump file: C:\WINDOWS\Minidump\Mini081008-01.dmp
file path: C:\WINDOWS\System32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Thu 6/03/2008 2:25:53 AM your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x1000008E (0xC0000005, 0xBF91651F, 0xEC779578, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
Dump file: C:\WINDOWS\Minidump\Mini030608-01.dmp
file path: C:\WINDOWS\System32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Mon 9/04/2007 11:53:01 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x76 (0x0, 0xFEAB5020, 0x1, 0x0)
Error: PROCESS_HAS_LOCKED_PAGES
Dump file: C:\WINDOWS\Minidump\Mini040907-01.dmp
file path: C:\WINDOWS\System32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Wed 20/12/2006 12:33:32 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x76 (0x0, 0x8125AB80, 0x9, 0x0)
Error: PROCESS_HAS_LOCKED_PAGES
Dump file: C:\WINDOWS\Minidump\Mini122006-01.dmp
file path: C:\WINDOWS\System32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Fri 31/03/2006 11:09:24 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x76 (0x0, 0xFB6AF020, 0x2, 0x0)
Error: PROCESS_HAS_LOCKED_PAGES
Dump file: C:\WINDOWS\Minidump\Mini033106-01.dmp
file path: C:\WINDOWS\System32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



The following dump files were found but could not be read. These files may be corrupt:
C:\WINDOWS\Minidump\Mini031010-01.dmp
C:\WINDOWS\Minidump\Mini030910-01.dmp
C:\WINDOWS\Minidump\Mini030810-09.dmp
C:\WINDOWS\Minidump\Mini030810-08.dmp
C:\WINDOWS\Minidump\Mini030810-07.dmp
C:\WINDOWS\Minidump\Mini030810-06.dmp
C:\WINDOWS\Minidump\Mini030810-05.dmp
C:\WINDOWS\Minidump\Mini030810-04.dmp
C:\WINDOWS\Minidump\Mini030810-03.dmp
C:\WINDOWS\Minidump\Mini030410-01.dmp




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

25 crash dumps have been found on your computer. Only 15 could be analyzed. Note that it's not always possible to state with certainty whether a reported driver is really 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.

 

Gunsr2

Distinguished
Mar 22, 2010
3
0
18,510
A couple of new ones...

On Thu 25/03/2010 5:19:34 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x9F (0x2, 0x813D7ED8, 0x81F45D98, 0x81FD1D20)
Error: DRIVER_POWER_STATE_FAILURE
Dump file: C:\WINDOWS\Minidump\Mini032510-02.dmp
file path: C:\WINDOWS\System32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Thu 25/03/2010 12:23:41 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0x0, 0x1C, 0x1, 0x804D9147)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\WINDOWS\Minidump\Mini032510-01.dmp
file path: C:\WINDOWS\System32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.