Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Windows 7 BSOD Stop 0xC2 - ntoskrnl.exe


  • Please log in to reply
6 replies to this topic

#1 SoulSnatcher

SoulSnatcher

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:10:57 AM

Posted 29 April 2012 - 04:29 PM

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™-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
-----

I ran BlueScreenView and it said 'ntoskrnl.exe' was the faulty driver.

==================================================
Dump File : 042912-13821-01.dmp
Crash Time : 29/04/2012 9:31:10 AM
Bug Check String : BAD_POOL_CALLER
Bug Check Code : 0x000000c2
Parameter 1 : 00000000`0000000b
Parameter 2 : fffffa80`07f3a8f0
Parameter 3 : 00000000`04210007
Parameter 4 : fffffa80`07f3ab10
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7cc80
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17790 (win7sp1_gdr.120305-1505)
Processor : x64
Crash Address : ntoskrnl.exe+7cc80
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\042912-13821-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 276,344
==================================================

I attached a .rar file with a dump file and various info below and info from Performance Monitor below. Help!

Edited by SoulSnatcher, 29 April 2012 - 04:31 PM.


BC AdBot (Login to Remove)

 


#2 AustrAlien

AustrAlien

    Inquisitor


  • BC Advisor
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:01:57 AM

Posted 29 April 2012 - 06:42 PM

GVTDrv64.sys Tue Sep 05 17:10:02 2006


GVTDrv64.sys is a driver belonging to Gigabyte EasyTune6 which has known issues with Windows 7.
Un-install Gigabyte EasyTune6 (ET6) and let us know if you have any further problems.

========================
BSOD BUGCHECK SUMMARY
................................................................
Loading Dump File [C:\CactusIsland\SoulSnatcher_BC\Windows_NT6_BSOD_jcgriff2\042912-15522-01.dmp]
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Debug session time: Sun Apr 29 22:54:08.034 2012 (UTC + 10:00)
System Uptime: 0 days 0:01:19.580
GetPointerFromAddress: unable to read from fffff80003115100
GetUlongFromAddress: unable to read from fffff80003083a18
GetUlongFromAddress: unable to read from fffff80003083a18
Probably caused by : ntkrnlmp.exe ( nt!ObpCloseHandleTableEntry+c4 )
BAD_POOL_CALLER (c2)
BUGCHECK_STR: 0xc2_7
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: audiodg.exe
FAILURE_BUCKET_ID: X64_0xc2_7_nt!ObpCloseHandleTableEntry+c4
Bugcheck code 000000C2
Arguments 00000000`00000007 00000000`0000109b 00000000`08da6af8 fffffa80`08da6b10
BiosVersion = FCd
BiosReleaseDate = 02/20/2012
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = M68MT-S2
................................................................
Loading Dump File [C:\CactusIsland\SoulSnatcher_BC\Windows_NT6_BSOD_jcgriff2\042912-13821-01.dmp]
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Debug session time: Sun Apr 29 23:30:10.994 2012 (UTC + 10:00)
System Uptime: 0 days 0:35:21.539
Probably caused by : ntkrnlmp.exe ( nt!ObfDereferenceObjectWithTag+93 )
BAD_POOL_CALLER (c2)
BUGCHECK_STR: 0xc2_b
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: X64_0xc2_b_nt!ObfDereferenceObjectWithTag+93
Bugcheck code 000000C2
Arguments 00000000`0000000b fffffa80`07f3a8f0 00000000`04210007 fffffa80`07f3ab10
................................................................

AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#3 SoulSnatcher

SoulSnatcher
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:10:57 AM

Posted 09 May 2012 - 06:45 PM

I removed Gigabyte EasyTune6 and manually removed 'GVTDrv64.sys' about a week ago. I thought the problem was fixed but recently I got 2 blue-screens with the same BC Code. :(

I uploaded the mini-dumps here. Help again?

#4 AustrAlien

AustrAlien

    Inquisitor


  • BC Advisor
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:01:57 AM

Posted 09 May 2012 - 06:59 PM

I will have a look at the crash dumps and get back to you.
AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#5 SoulSnatcher

SoulSnatcher
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:10:57 AM

Posted 09 May 2012 - 07:00 PM

I will have a look at the crash dumps and get back to you.

Okay, thanks!

#6 AustrAlien

AustrAlien

    Inquisitor


  • BC Advisor
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:01:57 AM

Posted 09 May 2012 - 10:26 PM

Run Driver Verifier following the instructions DRIVER VERIFIER - Windows 7 & Vista ... by jcgriff2
  • Notes:
  • Do not omit the first step, to create a System Restore point before enabling Driver Verifier.
  • Read the instructions on how to check the Driver Verifier Status.
  • Read the instructions on how To Turn Driver Verifier OFF when you have finished with it.
  • Read the instructions (and record them on paper so you have them if needed) about what to do IF you cannot start the system normally after it crashes under Driver Verifier.
  • Run Driver Verifier for 36 hours unless the system crashes. It doesn't matter whether you are using the computer or not during that time.
If your system BSODís under the Driver Verifier:
  • Locate the minidump file:
    • C:\Windows\Minidump <<< folder
  • Zip up the most recent minidump file:
    • Right-click on the most recent minidump file > Send to ... > Compressed (zipped) Folder.
    • The zip file will be located in the same place
  • Attach the zip file to your next post in this thread.
    • When you click on Add Reply, you will see the facility to attach a file just below the box where you type your message
========================
BSOD BUGCHECK SUMMARY
................................................................
Loading Dump File [C:\CactusIsland\SoulSnatcher_BC\minidump\050912-14367-01.dmp]
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Debug session time: Wed May 9 14:44:40.740 2012 (UTC + 10:00)
System Uptime: 0 days 1:40:14.270
GetPointerFromAddress: unable to read from fffff800030bb100
Probably caused by : ntkrnlmp.exe ( nt!ObfDereferenceObjectWithTag+93 )
BAD_POOL_CALLER (c2)
BUGCHECK_STR: 0xc2_7
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: X64_0xc2_7_nt!ObfDereferenceObjectWithTag+93
Bugcheck code 000000C2
Arguments 00000000`00000007 00000000`0000109b 00000000`080baa28 fffffa80`080bab10
................................................................
Loading Dump File [C:\CactusIsland\SoulSnatcher_BC\minidump\050812-30810-01.dmp]
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Debug session time: Wed May 9 13:03:50.838 2012 (UTC + 10:00)
System Uptime: 2 days 7:18:54.368
Probably caused by : ntkrnlmp.exe ( nt!ObfDereferenceObjectWithTag+93 )
BAD_POOL_CALLER (c2)
BUGCHECK_STR: 0xc2_b
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: X64_0xc2_b_nt!ObfDereferenceObjectWithTag+93
Bugcheck code 000000C2
Arguments 00000000`0000000b fffffa80`07920b80 00000000`0d0b0000 fffffa80`07921b10
................................................................

AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#7 SoulSnatcher

SoulSnatcher
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:10:57 AM

Posted 18 May 2012 - 07:37 PM

Well I've been running Driver Verifier and I haven't got a blue-screen since. :/




1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users