Sign in with
Sign up | Sign in
Your question

Blue Screen of Death Problem 0x101

Last response: in CPUs
Share
August 18, 2009 5:11:29 PM

Hi,

Just recently I finished building a system on a budget but have been getting BSOD 0x101 at random times, mostly more commonly after I overclock from 2.3Ghz to anything over 2.5Ghz.

Here is the BSOD code that windows gave me after I rebooted:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7100.2.0.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 101
BCP1: 00000031
BCP2: 00000000
BCP3: 807C3120
BCP4: 00000001
OS Version: 6_1_7100
Service Pack: 0_0
Product: 256_1

I did a little research and came up with "CLOCK_WATCHDOG_TIMEOUT", which makes me think somethings up with the CPU. I'm not sure what it means but I hope someone here could tell me what it is and how to fix it.

My PC Specs if it helps:

Windows 7 Ultimate 32bit RC
OCZ Reaper 1066 RAM 5-5-5-18 2.0v
ECS A780GM-A AM2/AM2+ Motherboard with all BIOS updates
Raidmax Hybrid 2 550w PSU Crossfire Supported
AMD Phenom 9600 2.5Ghz Agena AM2+ 1.325v
HIS 4850 IceQ4 Turbo 512mb 740/1100 Stable
Raidmax Scorpio Mid ATX (1 LED, 4 Standard 80mm Fans)
Seagate Barracuda 500gb 7200rpm Hard Drive

Thanks
Anonymous
a b à CPUs
December 22, 2009 6:04:55 PM

Any solutions on this? got exact the same problem getting tired of it :( 
m
0
l
a b à CPUs
December 22, 2009 6:15:51 PM

Unstable OC? Was this a BIOS oc or software oc?

What are your voltages and temps?
m
0
l
Related resources
May 5, 2011 2:06:41 AM

Thats easy man, go into Bios and raise your Vcore by the smallest amount possible. It should stabilize your system, run 2 hours of prime95 to be certain. have a nice day.
m
0
l
a b à CPUs
May 5, 2011 11:58:05 AM

Stop code 0x101 is related to CPU interrupts.

Quote:
Bug Check 0x101: CLOCK_WATCHDOG_TIMEOUT- This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.


This also applies to multi-core systems. Sounds like a bad OC to me.

m
0
l
a b à CPUs
August 5, 2011 10:45:16 PM

I Just recently got a BSOD of 0x101 and I Never(Not this error) got one b4, this is my first time in 2 month of my system OC...

Spec:
Windows 7 Ultimate 64-Bit
i7-950 OC to 3841MHz at 1.225v(Should I raise vCore, I Currently got a Tt V1 AX and it can't cool my i7 at 3.8GHz so I cant really test it out more than 2 mins)
KHX 2x2GB OC to 2009MHz 9-10-9-24(Stable with memtest86+ with 6 passes)
Viotek 700W v2
Evga GT220(Currently have it OC which isn't the problem here)
m
0
l
!