Having trouble diagnosing this BSOD, help appreciated!

Glaucus

n00b
Joined
Jan 31, 2009
Messages
17
The only reason that I am making this post here is because what information I could glean from the minidump file stated...

"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."

I assume from that information that there is a problem with my processor, but I decided to post up here before jumping to conclusions.

Either way, while playing Company of Heroes I encountered a BSOD after an hour of play, give or take. I checked for updates for my operating system and my graphics card but everything seems to be up to date.

Below is a link to the minidump file that was generated with the BSOD, any help will be greatly appreciated!

http://www.gigasize.com/get.php?d=z75yr30412d
 
Getting this from the Event Viewer... This is the error that stated a dump file was made.

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000101 (0x0000000000000031, 0x0000000000000000, 0xfffff88002dd3180, 0x0000000000000003). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 042710-34413-01.

Is this what you're looking for? If not I may need a finger pointed in the right direction.
 
Yah. 0x101 is the error code. Unfortunately, I think you'll need higher level support. Try the OS subforum, if you can. I doubt it's a hardware issue. Have you tried updating your drivers? I'm assuming you also have the latest updates? A quick google yielded:
0x101 = CLOCK_WATCHDOG_TIMEOUT = 1 of the CPUs is not processing interrupts and times out. I don't have much to offer you on the hardware end, but if software related it would be a "deadlock" situation. A deadlock occurs when a non-executing thread has an exclusive lock on a resource object and the executing thread needs that resource - which it will never get. A stand-off ensues - and 61 clock-ticks later the CPU throws in the towel. Result = 0x101 BSOD.
I think you'll need to run the windows debug tool to get to the root of the issue. Try http://www.techsupportforum.com/ and http://www.sevenforums.com/crash-lockup-debug-how/
 
Back
Top