Windows 7: Windows 7 BSOD Stop 0xC2 - ntoskrnl.exe

SoulSnatcher · 29 Apr 2012

I've been getting blue-screens on my computer. The error that appears is 'Bad Pool Caller' and the BC Code is 0xC2. I attached the necessary files (from the sticky) below.

As for my system information,
-----------
OS Name Microsoft Windows 7 Ultimate
Version 6.1.7601 Service Pack 1 Build 7601
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name URANIUM-PC
System Manufacturer Gigabyte Technology Co., Ltd.
System Model M68MT-S2
System Type x64-based PC
Processor AMD FX(tm)-4100 Quad-Core Processor, 3600 Mhz, 2 Core(s), 4 Logical Processor(s)
BIOS Version/Date Award Software International, Inc. FCd, 20/02/2012
SMBIOS Version 2.4
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume1
Locale Canada
Hardware Abstraction Layer Version = "6.1.7601.17514"
User Name Uranium-PC\Uranium
Time Zone Eastern Daylight Time
Installed Physical Memory (RAM) 8.00 GB
Total Physical Memory 7.98 GB
Available Physical Memory 6.33 GB
Total Virtual Memory 16.0 GB
Available Virtual Memory 14.0 GB
Page File Space 7.98 GB
Page File C:\pagefile.sys
-----

SoulSnatcher · 29 Apr 2012

Just viewed the sticky and added the necessary info.

Is Windows 7 . . .
- x86 (32-bit) or x64 ?
64 bit
- the original installed OS on the system?
Yes.

- What is the age of system (hardware)?
About two months.

- What is the age of OS installation (have you re-installed the OS?)
About two months. No, I haven't re-installed.

SoulSnatcher · 29 Apr 2012

*bump*

SoulSnatcher · 29 Apr 2012

*yet another bump*

No one knows why this is happening?

writhziden · 30 Apr 2012

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\SoulSnatcher\Windows_NT6_BSOD_jcgriff2\042912-13821-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`02e1d000 PsLoadedModuleList = 0xfffff800`03061650
Debug session time: Sun Apr 29 07:30:10.994 2012 (UTC - 6:00)
System Uptime: 0 days 0:35:21.539
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C2, {b, fffffa8007f3a8f0, 4210007, fffffa8007f3ab10}

Probably caused by : ntkrnlmp.exe ( nt!ObfDereferenceObjectWithTag+93 )

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

2: 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: 000000000000000b, type of pool violation the caller is guilty of.
Arg2: fffffa8007f3a8f0
Arg3: 0000000004210007
Arg4: fffffa8007f3ab10

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


FAULTING_IP: 
nt!ObfDereferenceObjectWithTag+93
fffff800`02e85463 488b742448      mov     rsi,qword ptr [rsp+48h]

BUGCHECK_STR:  0xc2_b

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002fc6c93 to fffff80002e99c80

STACK_TEXT:  
fffff880`031d2a48 fffff800`02fc6c93 : 00000000`000000c2 00000000`0000000b fffffa80`07f3a8f0 00000000`04210007 : nt!KeBugCheckEx
fffff880`031d2a50 fffff800`02e85463 : 00000000`00000001 00000000`00000000 fffffa80`07f3ab60 00000000`00000001 : nt!ExDeferredFreePool+0x12bf
fffff880`031d2b00 fffff800`02e78da1 : 00000000`00000000 fffffa80`06b17560 fffffa80`07f3aef8 fffff6fc`4004ba88 : nt!ObfDereferenceObjectWithTag+0x93
fffff880`031d2b40 fffff800`02ea3361 : fffff800`02e78d08 fffff800`03039310 fffffa80`06b17560 00000000`00000000 : nt!PspReaper+0x99
fffff880`031d2b70 fffff800`03133fda : 00000000`00000000 fffffa80`06b17560 00000000`00000080 fffffa80`069f4040 : nt!ExpWorkerThread+0x111
fffff880`031d2c00 fffff800`02e8a9c6 : fffff880`02fd7180 fffffa80`06b17560 fffff880`02fe1fc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031d2c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!ObfDereferenceObjectWithTag+93
fffff800`02e85463 488b742448      mov     rsi,qword ptr [rsp+48h]

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!ObfDereferenceObjectWithTag+93

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4f558b55

FAILURE_BUCKET_ID:  X64_0xc2_b_nt!ObfDereferenceObjectWithTag+93

BUCKET_ID:  X64_0xc2_b_nt!ObfDereferenceObjectWithTag+93

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

The above crash typically indicates a device driver conflict, but yours does not indicate which driver and blames a Windows process. It could still be an underlying driver, but it may also be Windows corruption. Additionally, your other crash blames audiodg.exe.

See Fix: Audiodg.exe High CPU Usage for the audiodg.exe issue.
If you are overclocking any hardware, please stop.
Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log.
For any drives that do not give the message:
Windows has checked the file system and found no problems
run disk check again as above. In other words, if it says:
Windows has made corrections to the file system
after running the disk check, run the disk check again.
Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations. Use OPTION THREE of SFC /SCANNOW Command - System File Checker to provide us with the sfcdetails.txt file if errors occur.
An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
a. Backup your system and user files
b. Create a system restore point
c. If you do not have a Windows 7 DVD, Create a system repair disc
d. In Windows 7:
- Click the Start Menu
- Type verifier in Search programs and files (do not hit enter)
- Right click verifier and click Run as administrator
- Put a tick in Create custom settings (for code developers) and click next
- Put a tick in Select individual settings from a full list and click next
- Set up the individual settings as in the image and click next
  Attachment 209661
- Put a tick in Select driver names from a list
- Put a tick next to all non-Microsoft drivers.
- Click Finish.
- Restart your computer.
If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using System Restore OPTION TWO.

Thanks to zigzag3143 for contributing to the Verifier steps.
If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.
The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.

When you are ready to disable Verifier: Start Menu -> All Programs -> Accessories -> Right click Command Prompt -> Run as administrator -> Type the following command and then Enter:
verifier /reset
-> Restart your computer.

Since you continue to violate the rules on these forums, I recommend some further reading: Forum Rules and info- Please Read!

Windows 7: Windows 7 BSOD Stop 0xC2 - ntoskrnl.exe

Windows 7 BSOD Stop 0xC2 - ntoskrnl.exe problems?