New build BSOD 0x101

Sniper296 · 17 Jan 2012 at 21:57

My first build just entered a runnable state on Saturday and on Monday and twice today I have received BSODs with the STOP code 0x00000101. The first with the driver win32k.sys the last two with ntoskrnl.exe. It appears to be happening under some load, the first two while 3DS Max were running but not rendering and the last with GTA IV running but tabbed out. I am not sure what the problem is, any help?

Intel i7-2600k stock
ASRock Z68 Extreme4 B3 BIOS 1.10
Corsair Vengeance 8GB DDR3 @ 1666 9-10-9-27
XFX Pro 850W Core Edition
7 Home Premium 64-bit

beejjacobs · 17 Jan 2012 at 22:49

Try reseating the ram? Try one stick at a time? Try resetting the CMOS?

Check all power cables just in case too.

Sniper296 · 17 Jan 2012 at 23:30

Tried resetting the CMOS after the second BSOD. RAM and cables are all in tight, triple checked. And a memtest ran for about 4 hours yesterday rules out the RAM.

beejjacobs · 17 Jan 2012 at 23:31

Have you checked temperatures? Worth a check. Coretemp/realtemp/hwmonitor

Sniper296 · 17 Jan 2012 at 23:47

HWMonitor reports ~35° idle with Prime95 or IntelBurnTest taking it up to no more than 75° with stock Intel cooler.

beejjacobs · 17 Jan 2012 at 23:48

Can you try a repair install with the Windows 7 disk?

Someone else may have ideas of things to try as I'm running out!

Sniper296 · 18 Jan 2012 at 00:51

I have done a startup repair of Windows, I am not sure that it would be the problem. 0x101 is "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.

Sniper296 · 18 Jan 2012 at 12:58

I have just updated the BIOS(1.50 says "Update CPU code.") will see if it BSODs.

Sniper296 · 19 Jan 2012 at 14:19

Nothing since, anyone else who gets this with a ASRock Z68 Extreme4 B3 board try updating BIOS to 1.50.