BSOD while playing heavy graphics games error 101

[RedNinja]

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!

 

[koolkat77]

Welcome

Re your bug check 101
Go through:
:ar: http://www.sevenforums.com/crash-lo...0x101-clock_watchdog_timeout-troubleshtg.html

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

[FONT=Verdana][SIZE=2]*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

[COLOR=Red]BugCheck 101[/COLOR], {19, 0, fffff88002f65180, 2}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

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

[COLOR=Red]CLOCK_WATCHDOG_TIMEOUT (101)[/COLOR]
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.[/SIZE][/FONT]

 

[RedNinja]

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:

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.

 

[koolkat77]

Uninstall Daemon Tools
Let us know if you get any blue screens.

 

[RedNinja]

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.

 

[koolkat77]

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

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

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.

 

[RedNinja]

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.

 

[koolkat77]

Yes..I rechecked your dumps.. Bug check 101 - It points toward the CPU/Processor.

 

[nothjarnan]

mabey getting a better CPU might work?