Solved Bsod 101 clock_watchdog_timeout

solution for me: -Vertex 3 Firmware update!

Hey guys,

I tried to put as much information togheter as requested, so i hope theres all you need and someone has time to take a look at it. Im in desperate situation here, cuz like most of you, my rig is half of my brain -.-

All the hopefully necessary files are here:

https://skydrive.live.com/redir.aspx?cid=c83dbd942f38287d&page=self&resid=C83DBD942F38287D!372&parid=C83DBD942F38287D!364&authkey=!AuNhQRqtNbRCbvc&Bpub=SDX.SkyDrive&Bsrc=Share

in the past 2 days i had 5 bluescreens. first 2 off nothing. 1 after a few hours CPU stress test and one after 15min Memtest. if i dont do much, the system runs pretty normal. altho sometimes it just hangs for like 20 seconds and then runs again (music still playing, but mouse not movable)

Brand new system, first BSOD after 3 days of running. Mounted the parts myself, done this for over 10 years.
In case you wonder, I use it for daily taks like outlook, internet, normal stuff. no gaming. preferences are set to be silent, which it is.
-no overclocking, standard BIOS settings. BIOS updates Versiion 4/27/12


What I've done so far:
-hours of forum post reading
-updated all drivers
-sfc.exe hdd check
-scan for viruses MSE
-all windows updates installed
-disabled all unecessary ports in BIOS (Firewire, serial, parallel, marvell sata)
-memtest -> Crash after 15mins
-CPU Test prime 95: -> crash after 3 hours


BSOD_Windows7_Vista_v2.64_jcgriff2_.exe
I let that run, but it didnt give me any results.. it always listend "collecting system info" again and again line by line..

Sorry for the German stuff on screens, tell me if you need any translation.

System Setup:

Intel i5 2550K
4x 3.40GHz, 6MB Cache, 32nm Turbo 3.80GHz, no-chip
GPU DDR3, Sandybridge, Unlock.

ASUS EN 210
1024MB DDR3, 1580/589MHz Nvidia GeForce, Passiv Low
Profile

ASUS P8P67-M Pro
B3, Intel P67 Chipset, 1155Pin PCIE, DDR3, RAID, GLAN,
mATX SATA3, SLI & CFX, Rev.3.0

Kingston Technology DDR3 1333MHz 8GB
8GB Kit, PC10666, 240Pin, CL9 (2x4GB), 1.50V, Dual Channel HyperX Blu Series

Microsoft Win7 SP1 Pro64, D
Win7 SP1 Professional DE 64 Bit Fullversion, DVD, OEM

OCZ Vertex III Series
60GB, 2.5", SATA3 MLC-Chips, 535MB/s inkl. 3.5" Adapter


CPU Temp at 100% Stresstest:


BSOD Info:

[FONT=&quot]Problemsignatur:[/FONT]
[FONT=&quot]Problemereignisname: BlueScreen[/FONT]
[FONT=&quot]Betriebsystemversion: 6.1.7601.2.1.0.256.48[/FONT]
[FONT=&quot]Gebietsschema-ID: 2055[/FONT]

[FONT=&quot]Zusatzinformationen zum Problem:[/FONT]
[FONT=&quot]BCCode: 101[/FONT]
[FONT=&quot]BCP1: 0000000000000031[/FONT]
[FONT=&quot]BCP2: 0000000000000000[/FONT]
[FONT=&quot]BCP3: FFFFF88002065180[/FONT]
[FONT=&quot]BCP4: 0000000000000002[/FONT]
[FONT=&quot]OS Version: 6_1_7601[/FONT]
[FONT=&quot]Service Pack: 1_0[/FONT]
[FONT=&quot]Product: 256_1[/FONT]


[FONT=&quot]System Information (local)[/FONT]
[FONT=&quot]
computer name: I5
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i5-2550K CPU @ 3.40GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8555454464 total
VM: 2147352576, free: 1931014144

[/FONT]
[FONT=&quot]Crash Dump Analysis[/FONT]
[FONT=&quot]
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Tue 01.05.2012 09:08:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050112-21294-01.dmp
This was probably caused by the following module: [/FONT][FONT=&quot]ntoskrnl.exe[/FONT][FONT=&quot] (nt+0x7CC80)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF88002065180, 0x2)
Error: [/FONT][FONT=&quot]CLOCK_WATCHDOG_TIMEOUT[/FONT][FONT=&quot]
file path: C:\Windows\system32\ntoskrnl.exe
product: [/FONT][FONT=&quot]Microsoft® Windows® Operating System[/FONT][FONT=&quot]
company: [/FONT][FONT=&quot]Microsoft Corporation[/FONT][FONT=&quot]
description: NT Kernel & System
[/FONT][FONT=&quot]

On Tue 01.05.2012 09:08:31 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [/FONT][FONT=&quot]iastor.sys[/FONT][FONT=&quot] (iaStor+0x3ED5)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF88002065180, 0x2)
Error: [/FONT][FONT=&quot]CLOCK_WATCHDOG_TIMEOUT[/FONT][FONT=&quot]
file path: C:\Windows\system32\drivers\iastor.sys
product: [/FONT][FONT=&quot]Intel Rapid Storage Technology driver [/FONT][FONT=&quot]
company: [/FONT][FONT=&quot]Intel Corporation[/FONT][FONT=&quot]
description: Intel Rapid Storage Technology driver - x64
[/FONT][FONT=&quot]

On Sun 29.04.2012 19:19:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042912-29686-01.dmp
This was probably caused by the following module: [/FONT][FONT=&quot]ntoskrnl.exe[/FONT][FONT=&quot] (nt+0x7CC80)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF88002065180, 0x2)
Error: [/FONT][FONT=&quot]CLOCK_WATCHDOG_TIMEOUT[/FONT][FONT=&quot]
file path: C:\Windows\system32\ntoskrnl.exe
product: [/FONT][FONT=&quot]Microsoft® Windows® Operating System[/FONT][FONT=&quot]
company: [/FONT][FONT=&quot]Microsoft Corporation[/FONT][FONT=&quot]
description: NT Kernel & System

[/FONT][FONT=&quot]

On Sun 29.04.2012 15:29:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042912-46207-01.dmp
This was probably caused by the following module: [/FONT][FONT=&quot]ntoskrnl.exe[/FONT][FONT=&quot] (nt+0x7CC80)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF880020D7180, 0x3)
Error: [/FONT][FONT=&quot]CLOCK_WATCHDOG_TIMEOUT[/FONT][FONT=&quot]
file path: C:\Windows\system32\ntoskrnl.exe
product: [/FONT][FONT=&quot]Microsoft® Windows® Operating System[/FONT][FONT=&quot]
company: [/FONT][FONT=&quot]Microsoft Corporation[/FONT][FONT=&quot]
description: NT Kernel & System



do you think it could be a hardware problem?

right now its runign with driver verifier.. will post results when im back home..

[/FONT][FONT=&quot]thanks so far and cheers[/FONT]

It could be a hardware problem, drivers problems, or a bad Windows install. See http://www.sevenforums.com/crash-lo...0x101-clock_watchdog_timeout-troubleshtg.html for what we have on this crash. It looks like you have already done many of the steps in that link, so you may have already seen it.

yes read that thread, but thanks anyways. drivers all up to date..
i ve run stresstest with driver verifier, results are here in BSOD_driver_verifier.zip
https://skydrive.live.com/?cid=c83dbd942f38287d&Bsrc=Share&Bpub=SDX.SkyDrive&sc=Photos&resid=C83DBD942F38287D!372&id=C83DBD942F38287D!372

theres also the jcgriff extract.. got it working great tool!

goin to disable C1, C3 and C6 in BIOS... and run stresstest again overnight

I am unable to access your .zip file with my live account. Can you upload the files on here? http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

*&/*6| i thought that would work..

added a few files..

did some settings, maybe im on the right track:

BIOS:
-set from silent and energy saving to normal
-Disabled intel speed step technology
-disabled all C that was settable: C1, C3, C6

then i ran cpu and ram stresstest in windows over night (7 hours) with no BSOD, still runnin in the morning. new record so far.. right now i let boot-memtest run for the whole day..

maybe this works for you!?

Free Cloud Storage - MediaFire

The latest crashes were Verifier enabled. Before doing the following, disable Verifier: Start Menu -> All Programs -> Accessories -> Right click Command Prompt -> Run as administrator -> Type the following command and then Enter: -> Restart your computer.

Your Intel storage controller driver is corrupted. It is the controller for your hard disk through Windows. It may be contributing to the 0x101 crashes. First, download the latest Intel(R) Rapid Storage Technology driver from P8P67-M PRO | Support -> Download -> Windows 7 64bit -> SATA -> Intel(R) Rapid Storage Technology Driver Software V10.5.0.1026 for Windows Vista/7 32bit & 64bit.(WHQL) uninstall your Intel Controller through Device Manager.

1. Log in as an administrative user
2. Click Start Menu
3. Click Control Panel
4. Click Hardware and Sound
5. Click Device Manager
6. Expand IDE ATA/ATAPI Controllers
7. Right click the Intel Controller
8. Click Uninstall (do not hit OK yet)
9. Put a tick in the box to Delete driver software for this device
10. Click OK
11. Restart your computer if asked
12. Install the downloaded drivers.

thanks writhziden for your answer!

well its weird cuz i already had version 10.5.0.1026 installed. but i did follow all your steps, disabled verifier, delete, reboot, install, reboot driver again. lets see.. ill run once again cpu stresstest over night and post again..

btw: boot-memtested RAM for 12 hours, 10 times cycle: 0 Errors.

As I said, your 10.5.0.1026 driver appeared to be corrupted, so re-installing may solve the issue. Let us know how things are going. Glad your RAM came out clean through Memtest86+. That does not rule it out entirely, but it means there is a high likelihood the RAM is okay.

thanks. I did reinstall the driver. Have the PSU in my sight too... maybe low Voltage.. gonna messure it when i have the tools.. ill keep you posted

swisser said:

maybe low Voltage

Click to expand...

On that note, what does CPUz show your VCore is at? It may be necessary for you to bump your VCore slightly. Are you overclocking? Which board revision do you have? Which BIOS version do you have?

Vcore is around 1.240, is that normal?

seems like my rig is fixed..! dont wanna open the champagne bottle yet, but it survived a 20 hours CPU +RAM Stresstest plus a weekend of normal usage.. what ive done the latest is:


-Vertex 3 Firmware update!
-LPM disabled

Vertex 3 - Windows install in AHCI mode on Intel 6 series Chipset platforms

no more freeze, no BSOD. i hope it says.. otherwise ill repost^^ thanks to all who contributed in this or other threads!

No problem.

Sorry, I should have actually mentioned the SSD firmware; I think I missed that you had an SSD. With SSDs, there are four important things to keep up to date:

• SSD firmware
• BIOS version
• Chipset Drivers
• Storage Controller drivers

no problem. i really think it was a interaction problem of all those components you listed.. lets hope at least, that now its fixed

Best wishes that was it. Glad to see the thread marked solved, at any rate.