Random BSoD's 0x000000ea and 0x000000c2

Prussia · 17 Aug 2014

Hello,

1 and a half year ago i built a new PC, it's been working fine until January.
Then i got a BSoD with error code 0x000000ea, i updated drivers,
deleted virusses etc... Didn't help, so i decided to completely clean out my pc, that helped, until some months later, however then it suddenly stopped again, then i reinstalled windows because of incredibly slow start-up and loading times (which may or may not be related to this, no idea), after that i got a BSoD again, i reseated my GPU which again, helped for 2 months, then i did the same, and haven't had that error since, however today i got this error 0x000000c2, and i don't really know what to do with this, as it appears to be random, i know 0x000000ea is a graphics driver, but my GPU functions perfectly normal except once in a while when it does this, might it be RAM? My specs:
AMD Phenom II 965 BE 3.4 Ghz
XFX Radeon HD 7850
8 GB Corsair Vengeance RAM
650 watt m1211 seasonic 80+ bronze PSU
1 TB WD purple HDD
Gigabyte 990FXA UD3 AM3+ Mobo.

The bsoddump.rar contains 2 dump files.

Arc · 23 Aug 2014

Hi Prussia.

Some more info will be needed.

Click on the button below ....

It will download the DM log collector. Right click on the application and run as administrator. It will generate a .zip file on your desktop. Upload the .zip.
Screenshots and Files - Upload and Post in Seven Forums

Prussia · 24 Aug 2014

Thanks for the reply, here's the zip.

Arc · 24 Aug 2014

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

If it does not show any error, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

Tip

If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.
_______________________________________

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C2, {7, 109b, 1e4, fffff900c2033650}

GetPointerFromAddress: unable to read from fffff80003506100
GetUlongFromAddress: unable to read from fffff800035061c0
GetUlongFromAddress: unable to read from fffff80003474a38
Probably caused by : win32k.sys ( win32k!FreeObject+58 )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 0000000000000007, Attempt to free pool which was already freed
Arg2: 000000000000109b, (reserved)
Arg3: 00000000000001e4, Memory contents of the pool block
Arg4: fffff900c2033650, Address of the block of pool being deallocated

Debugging Details:
------------------

GetUlongFromAddress: unable to read from fffff80003474a38

POOL_ADDRESS:  fffff900c2033650 

BUGCHECK_STR:  0xc2_7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  explorer.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

LAST_CONTROL_TRANSFER:  from fffff80003401be9 to fffff800032cebc0

STACK_TEXT:  
fffff880`08176428 fffff800`03401be9 : 00000000`000000c2 00000000`00000007 00000000`0000109b 00000000`000001e4 : nt!KeBugCheckEx
fffff880`08176430 fffff960`00147184 : 00000000`00000000 000007ff`fffdc000 fffff900`c00c0010 fffff900`c4f5a010 : nt!ExDeferredFreePool+0x1201
fffff880`081764e0 fffff960`0010dd88 : fffff880`08176568 ffffffff`cb0104d8 00000000`00000000 00000000`00000000 : win32k!FreeObject+0x58
fffff880`08176510 fffff960`00148262 : fffff880`08176620 00000000`24010fcd 00000000`00000000 fffff960`001469b2 : win32k!RGNOBJ::vDeleteRGNOBJ+0x24
fffff880`08176540 fffff960`002829b1 : fffff880`08176620 fffff960`0014814b ffffffff`00000000 00000000`00000000 : win32k!XDCOBJ::bCleanDC+0xea
fffff880`081765a0 fffff960`0014999e : fffff880`08176620 00000000`00000000 00000000`00000000 00000000`65050f40 : win32k!bDeleteDCInternalWorker+0x29
fffff880`08176600 fffff960`001084d8 : 00000000`24010fcd fffff880`08176700 00000000`00000000 00000000`00000001 : win32k!bDeleteDCInternal+0x56
fffff880`08176650 fffff800`032cde53 : fffffa80`09f0d060 fffff880`08176700 00000000`0185000f fffff880`08176b68 : win32k!NtGdiDeleteObjectApp+0x120
fffff880`08176680 000007fe`fd62108a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`001bdc68 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fe`fd62108a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!FreeObject+58
fffff960`00147184 488b5c2430      mov     rbx,qword ptr [rsp+30h]

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  win32k!FreeObject+58

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  53c5df64

IMAGE_VERSION:  6.1.7601.18539

FAILURE_BUCKET_ID:  X64_0xc2_7_win32k!FreeObject+58

BUCKET_ID:  X64_0xc2_7_win32k!FreeObject+58

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xc2_7_win32k!freeobject+58

FAILURE_ID_HASH:  {eb18b1d2-fd55-a7f0-4b9e-da66c9cdcedd}

Followup: MachineOwner
---------

Prussia · 24 Aug 2014

I already did a RAM test earlier, also memtest86+, it gave me several errors but still managed to complete the passes, as for the driver verifier, i will do that, thank you.

Arc · 24 Aug 2014

Prussia said:

I already did a RAM test earlier, also memtest86+, it gave me several errors but still managed to complete the passes,

It showed errors?

A single error is enough to rule out the RAM as failing. And in that case that is the source of the issue. Nothing else is required.

Now follow the "Part 3: If You Have Errors:" of How to Test and Diagnose RAM Issues with Memtest86+

Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:

No code has to be inserted here.

It is a RAM, a bad RAM.

But if you have got a result like that:

No code has to be inserted here.

It is a motherboard issue. The particular slot is bad.

Let us know the situation.

Prussia · 24 Aug 2014

Thanks, i will test it and reply back when i found out what it was (might take a while).