BSOD Watchdog Timer late

rsmw · 17 Aug 2011

ASRock Z68 Extreme 4 Mother
Intel i7-2600K CPU at 4.4GH Corsair H60 water cooler
(2) Seagate 1TB 7200rpm
System 7 Professional 64 OEM / I built it mid May
Latest BIOS 1.60
more details in my online specs.

First line of code in '61, been in software since then.
Have done embedded OS/Hardware bring up and know how to read a scope, etc.
Have designed and built six different systems based on Windows OS.

This system has the same symptom as the i7-9xx series with this BSOD.
I don't read Windows dumps, so need help to debug (or kiss off)
Have had four of these since bring up.

Jonathan_King · 17 Aug 2011

Hello,

Try running each of the three Prime95 tests: https://www.sevenforums.com/tutorials...t-prime95.html

...Summary of the dumps:

Code:


Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Mon Aug  1 03:14:12.215 2011 (UTC - 4:00)
System Uptime: 0 days 1:29:56.980
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for win32k.sys - 
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  AcroRd32.exe
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun Jun 26 15:06:01.899 2011 (UTC - 4:00)
System Uptime: 0 days 1:20:16.664
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Wed Jun  8 20:14:27.044 2011 (UTC - 4:00)
System Uptime: 0 days 5:05:38.825
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Mon Jun  6 16:39:24.770 2011 (UTC - 4:00)
System Uptime: 0 days 4:00:02.536
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

rsmw · 18 Aug 2011

Hi,
I have run 8 hours of these three tests and the temperature varied between 69C in the cool evening to 74C during the warm afternoon. Seems like expected values. There were no reported errors. I have run the Intel Processor Diagnostic Tool and it also found no errors and a 30 degree safety margin.

I thought that this might be similar to the i7-9xx problem of coming out of processor idle or off state. This was fixed in that series by changes to the BIOS(and interrupt service?).

Jonathan_King · 19 Aug 2011

I'll contact someone who can give a much more in-depth analysis than I can. Maybe he'll post giving advice completely different, in which case take his advice over mine.

Is the CPU still under warranty? If so, you may consider RMA'ing it.

zigzag3143 · 19 Aug 2011

Just passing by but

Best advice that I've seen about this error (from here: https://www.sevenforums.com/crashes-d...tml#post356791 )

What you're looking for will be in one of the following categories:

a) BIOS bug
b) a driver whose activity is causing the target processor to lock up
c) a hardware defect (temperature, voltage, dust, RFI, outright borkedness...)

So, check the drivers
Then check the inside of the case (temperature, voltage, dust, etc).
Then run some hardware stress tests

Try this free video stress test: FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
Try this free stress test: Free Software - GIMPS

Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
The Test selection box and the stress.txt file describes what components that the program stresses.

Then try replacing parts.
Then look up the versions of your BIOS to see what changes were done.[/QUOTE]

**cluberti** · 20 Aug 2011

Usually clock interrupt timeouts are due to either one of the CPUs on the machine really being completely hung and not servicing interrupts, or a known problem with Intel Nehalem-series CPU (see the errata here and here). In any case, a watchdog timeout means one of the CPUs simply stopped serving interrupts, so you may have a hardware problem. If this is a machine purchased from an OEM, you might want to consider checking with them to see if there are any BIOS updates or fixes to their hardware that can eliminate these issues. Also, I would strongly suggest (given these can actually happen due to spurious interrupts specifically on Intel i-series and Xeon 5600+ CPUs, as per the errata linked previously) that you clock back to stock and see if the issue reproduces.

BSOD Watchdog Timer late

BSOD Watchdog Timer late

BSOD Test Reply