BSOD - Buzzing issues - Clock Interrupt secondary processor

bobus1964 · 27 Oct 2012

System that is having the problem is an ASUS Rampage II Gene with Intel i7-920 processor; 6 Gig RAM; and GTX 260 . Power supply is a Coolermaster extreme Powwer plus 600W PS. OS is Windows & 64 bit.

Wife has been experiencing recurring freezes and \or BSOD for a while. She uses the system for playing Warcraft so this is when it is happening. She says that sound will sometimes crackle and buzz at times before the freeze\crash.

I updated with all the O\S patches; all drivers updated, ran driver verifier and Memtest and did full malware scan - all okay.

I just replaced the Hard drive and did clean re install of OS. Issue however has just recurred.

I have attached the following dump file

Arc · 27 Oct 2012

Welcome aboard.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {19, 0, fffff88002f64180, 2}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CLOCK_WATCHDOG_TIMEOUT (101)
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.
Arguments:
Arg1: 0000000000000019, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88002f64180, The PRCB address of the hung processor.
Arg4: 0000000000000002, 0.

Debugging Details:
------------------


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  d

TAG_NOT_DEFINED_c000000f:  FFFFF80000BA2FB0

STACK_TEXT:  
fffff800`00b9c7e8 fffff800`02b1ed5a : 00000000`00000101 00000000`00000019 00000000`00000000 fffff880`02f64180 : nt!KeBugCheckEx
fffff800`00b9c7f0 fffff800`02ad1ad7 : 00000000`00000000 fffff800`00000002 00000000`000186a0 fffff800`00b96080 : nt! ?? ::FNODOBFM::`string'+0x4e2e
fffff800`00b9c880 fffff800`02a0a895 : fffff800`02a30460 fffff800`00b9ca30 fffff800`02a30460 00000000`00000000 : nt!KeUpdateSystemTime+0x377
fffff800`00b9c980 fffff800`02ac4513 : 00000000`08c48acf fffff800`00b9ca30 fffffa80`078921c8 00000000`00000001 : hal!HalpHpetClockInterrupt+0x8d
fffff800`00b9c9b0 fffff800`02aaf083 : fffffa80`07a41700 00000000`00000801 fffffa80`078926a0 fffff880`0444984b : nt!KiInterruptDispatchNoLock+0x163
fffff800`00b9cb40 fffff800`02ad1099 : 00000000`00000002 fffff880`044747ae 00000000`00000103 00000000`00000095 : nt!KxWaitForSpinLockAndAcquire+0x23
fffff800`00b9cb70 fffff880`044740f7 : fffffa80`078911a0 00000000`00000001 00000000`4f444648 fffffa80`064cf8b0 : nt!KeAcquireSpinLockRaiseToDpc+0x89
fffff800`00b9cbc0 fffff800`02b5146a : fffffa80`064cf8b0 00000000`00000000 00000000`00000000 fffffa80`078911a0 : USBPORT!USBPORT_RhIntrEp_Remove_TxqIrp+0x6f
fffff800`00b9cbf0 fffff880`04473e7c : fffffa80`07891002 fffffa80`07f91870 fffffa80`078911a0 fffff800`00b9cc78 : nt!IoCsqRemoveNextIrp+0x6a
fffff800`00b9cc20 fffff880`044739c8 : 00000000`00000001 fffffa80`00000001 fffffa80`09638950 00000000`00000001 : USBPORT!USBPORT_Rh_IntrEp_Worker+0x104
fffff800`00b9cc70 fffff800`02ad26ec : fffff800`02c3ae80 00000002`00040a02 fffffa80`08d218b0 00000000`00000002 : USBPORT!USBPORT_Ev_Rh_IntrEp_Dpc+0x124
fffff800`00b9ccd0 fffff800`02abfcca : fffff800`02c3ae80 fffff800`02c48cc0 00000000`00000000 fffff880`044738a4 : nt!KiRetireDpcList+0x1bc
fffff800`00b9cd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE

Followup: MachineOwner
---------

Follow the guide STOP 0x101: CLOCK_WATCHDOG_TIMEOUT troubleshtg.

bobus1964 · 28 Oct 2012

Update:

"So, check the drivers ( http://www.carrona.org/verifier.html )" -done with no issues reported. Video card has latest drivers from manufacturer

Case is free of dust and not running hot as per temp checking apps . System is not overclocked -fwiw

Using Intel diagnostic utility, CPU returned no errors
Updated the chipset drivers using Intel website application

Ran Prim95 last night - no issues reported

Ran FurMark benchmark\stability test with no errors. Temp was max at only 67 degrees.

BIOS was updated to latest version before clean reinstall of OS 2 weeks ago.

I did see that I am again getting -Session "Microsoft Security Client OOBE" stopped due to the following error: 0xC000000D" -event errors which I did get before the reinstall of the OS .

Any further troubleshooting that I can do? Or just what to see if she gets another BSOD and get the dump file.

Arc · 28 Oct 2012

This time, you wait for another crash. Let us see it, if the clock watchdog timeout issue persists or not.

bobus1964 · 02 Nov 2012

Wife reported 2 more BSOD. One occurred when I was in room . Other occurred the other day, and she said buzzing noise occurred before BSOD.

I am attaching new dump file

Arc · 03 Nov 2012

Still the same. Clock watchdog timeout.

Seen it? STOP 0x101: CLOCK_WATCHDOG_TIMEOUT troubleshtg

Recently it was found (here: BSOD Stop 0x00000101 and Stop 0x0000009c ) that a wipe and reinstall of Windows fixed a STOP 0x101 problem. I'd have to recommend at least running SFC.EXE /SCANNOW on any PC that has this problem (simply because it's too easy easy to do and it may fix things). Thanks to writhziden for pointing this out!

It may give some ides there.

bobus1964 · 04 Nov 2012

To eliminate another factor , I have disabled the secondary monitor connected to the video card.

I went into device manager and found 2 entries for sound devices. under Sound, video and game controllers and High definition Audio controller under System Devises. Apparently they are the same device as disabling either turns off sound. \

I did however get a different BSOD when I tried to re-enable the a Sound Max integrated Digital HD audio " IRQ less or not equal " I did managed to re-enable by selecting reinstall or update (forget which).

I have been considering getting an actual sound card to eliminate the factor of onboard sound causing issue. Any thoughts?

As well, the only time it does seem to bSOD is playing Warcraft. Any settings I could adjust to eliminate that variable . I did just turn off hardware sound acceleration in games as well

Arc · 04 Nov 2012

The plan for a sound card is very good.

As the crash is occurring in a particular game, change its graphics priority settings to low or normal, too.

and, as irql less or not equal may cause for various reasons, we cannot take a decision about it without seeing the crash dump.

bobus1964 · 08 Nov 2012

Have had several BSOD in last several days . Have attached most recent dump file.

I have disabled on board sound in bios.

I have checked and found I have identical video card in my own system which I can swap for troubleshooting, and that my RAM is compatible with my wife's system (also found I can replace RAM for only about $35 )

Arc · 09 Nov 2012

Same stop 0x101

I am asking you to go through the post #6 again, read the entire post please.