Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD while playing heavy graphics games error 101

21 Sep 2012   #1
RedNinja

Windows 7 Ultimate x64
 
 
BSOD while playing heavy graphics games error 101

Hi mates,

My computer is about 8 months old, problem's been happening since day 1, but I ignored it since it haven't been occurring too often, though recently I started a bit of gaming and it happens every now and then while gaming.

Attached is my zip file from SF Diagnostic Tool. Computer details:

ASUS P8P67-M Pro Rev 3.0
Intel Core i7 2600k 3.4GHz (not OC'ed)
G.Skill 4GB*2 RipJaws DDR
OCZ Vertex 3 as primary HDD with Win7 Ultimate x64.

I upgraded to the latest BIOS from ASUS which was no help.

Should the games I play matter - mainly CS:GO, GTA:IV, Crysis 2, Battle Field 3.


Any assistance will be much appreciated, thanks!


My System SpecsSystem Spec
.
21 Sep 2012   #2
koolkat77

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit
 
 

Welcome

Re your bug check 101
Go through:
STOP 0x101: CLOCK_WATCHDOG_TIMEOUT troubleshtg

If your PC is under warranty, you'd want to have your CPU/Processor replaced.

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {19, 0, fffff88002f65180, 2}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

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

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
My System SpecsSystem Spec
21 Sep 2012   #3
RedNinja

Windows 7 Ultimate x64
 
 

Thanks for your respond koolkat77.

I ruled out BIOS problem since I just updated it, which leaves me with either driver problem or hardware problem.

I ran verifier.exe according the post, which caused blue screens upon startup (couldn't get to desktop). This is the BSOD I had:
Code:
DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 000000000000023e, A driver has marked an IRP pending but didn't return STATUS_PENDING.
Arg2: fffff8800153e324, The address in the driver's code where the error was detected.
Arg3: fffff98009ba4ee0, IRP address.
Arg4: 0000000000000000, Status code.
I also attach a new reading from SF Diagnostic Tool with the recently created dump file caused by the verifier.

My CPU is indeed under warranty but I want to rule out drivers' malfunction before asking my provider for a new CPU.

Any insights?

Thanks again.
My System SpecsSystem Spec
.

21 Sep 2012   #4
koolkat77

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit
 
 

Uninstall Daemon Tools
Let us know if you get any blue screens.
My System SpecsSystem Spec
23 Sep 2012   #5
RedNinja

Windows 7 Ultimate x64
 
 

The system seemed stable until recent crash, again error 101, not during gaming but normal activity (background music).

Attached another SF Diagnostic Tool extract. Relevant dump is from today (09/23/2012 @ 2240~)

Another bad driver or the process goes back to the provider?

Thanks.
My System SpecsSystem Spec
23 Sep 2012   #6
koolkat77

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit
 
 

If you are overclocking any hardware, STOP. Reset any changed values back to default.

Lets enable driver verifier to rule out buggy drivers.

Verifier puts extreme stress on the drivers, bad ones will cause BSOD. If we change all those drivers we hope for no more BSODs, If you get no BSODs, then its not a driver and we look to hardware. With verifier on your computer may be a little laggy, but actually..its just doing its work.

Information
Driver Verifier runs in the background, "testing" drivers for bugs. If it finds one, a Blue Screen of Death (BSOD) will result; the corresponding dump file will hopefully show the faulty driver.

Driver Verifier
Quote:
I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in verifier and press Enter
- Select Create custom settings (for code developers) and click Next
- Select Select individual settings from a full list and click Next
- Select everything EXCEPT FOR Low Resource Simulation and click Next
- Select Select driver names from a list and click Next
Then select all drivers NOT provided by Microsoft and click Next
- Select Finish on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
Driver Verifier - Enable and Disable
Quote   Quote: Originally Posted by Capt.Jack Sparrow View Post
Driver Verifier monitors kernel-mode drivers and graphics drivers to detect illegal function calls or actions that might corrupt the system. It can subject the drivers to a variety of stresses and tests to find improper behavior.

Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.
My System SpecsSystem Spec
24 Sep 2012   #7
RedNinja

Windows 7 Ultimate x64
 
 

Hi koolkat77,

I am not overclocking, and the verifier is up and running for 72 hours~ (since your first comment).

I understand it's hardware problem then?

Thanks.
My System SpecsSystem Spec
24 Sep 2012   #8
koolkat77

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit
 
 

Yes..I rechecked your dumps.. Bug check 101 - It points toward the CPU/Processor.
My System SpecsSystem Spec
09 Oct 2012   #9
nothjarnan

Windows 7 Home Premium x64
 
 

mabey getting a better CPU might work?
My System SpecsSystem Spec
Reply

 BSOD while playing heavy graphics games error 101




Thread Tools




Similar help and support threads
Thread Forum
BSOD playing heavy load games
My PC has been getting BSOD a ton lately while playing graphic heavy games such as Archeage and Guild Wars 2. I have been looking around in BlueScreenView and it seems most of the BSOD are related to ntoskrnl.exe
BSOD Help and Support
BSOD playing BF4 and heavy games 0x00000124
Hello! I had problems before when i got bccodes 124 when playing BF4 and Rome 2 more when playing BF4. So i bought a Corsair H60 Hydro cooler and i could then play BF4 for about 2-3 days without any bluescreens then last night it started again and since then i had 2 last night 1 this morning.
BSOD Help and Support
BSOD while playing Skyrim, other graphics heavy programs. Error 0x07a
First of all, this is going to be quite the tl;dr, so a big thanks to anyone who even takes time to read it. I built my first rig in May, a mid to high grade gaming machine. Got it running successfully, everything seemed great until I started trying to play games. Oblivion was the first one. I...
BSOD Help and Support
BSOD from playing any heavy 3d games, and autoCAD 2010
hi Seven forum, i'm trying to fix my 2 years old notebook ASUS g51J from searching solved problem, but somehow any solved problem similar with me still not solving my problem. my problem related to 3d, at first i thought its my nvidia driver problem, but i was wrong, reverting old driver, updating...
BSOD Help and Support
BSOD: cdd.dll Kernel-Power error while using graphics-heavy apps
I get a BSOD while doing pretty much anything graphics intensive... Before my most recent fresh install of Windows 7, it used to happen while playing games (occasionally while playing StarCraft II or Half-Life 2: Episode 2) but it now is starting to occur (after the fresh install) more...
BSOD Help and Support
BSOD 116 while playing heavy load games
First of all, I don't speak english very well so, sorry for any grammar fails. I've gottin' an annoying problem lately. Started all with black screen with driver(nvlddmkm.sys) stopped responding error. Well, no problems. Checked my temps, everything seems normal.(58~59 idle, 75 full. My GPU...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 04:14.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App