Solved BSOD - Buzzing issues - Clock Interrupt secondary processor

[bobus1964]

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]

Welcome aboard.

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

Use !analyze -v to get detailed debugging information.

[COLOR=Red]BugCheck 101[/COLOR], {19, 0, fffff88002f64180, 2}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
[COLOR=Red]
CLOCK_WATCHDOG_TIMEOUT (101)[/COLOR]
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 http://www.sevenforums.com/crash-lo...0x101-clock_watchdog_timeout-troubleshtg.html.

 

[bobus1964]

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]

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

 

[bobus1964]

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]

Still the same. Clock watchdog timeout.

Seen it? http://www.sevenforums.com/crash-lo...0x101-clock_watchdog_timeout-troubleshtg.html

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]

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]

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]

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]

Same stop 0x101

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

 

[bobus1964]

Current status and a rundown of what I have tried

I have read through Post #6 and thing I have tried almost everything suggested:

Bios is updated
Clean reinstall of OS on a new hard drive
Malware scan - no issues
Video drivers is latest from manufacturer
Chipset drivers updated
All other drivers updated and verifed ( using Driver Verifier Settings )
Furmark stress tested - no errors
CPU stress tested with Prime95 - no errors
Ran SFC.EXE /SCANNOW - no errors
Temperatures checked and none above normal
Memtest has been run twice with no errors
I have disabled the onboard audio in bios and installed a PCI-E audio card with latest drives.
I have disabled the secondary monitor
I turned off hardware sound acceleration in warcraft which is game were the BSOD's occur. (wife has stated that she has gotten a BSOD several times in one particular dungeon at same end boss )
Graphic settings for Warcraft were compared to mine and are identical and not at the highest level. They were at "good" , but were reduced to "fair"

System is now giving BSOD of "Machine Check exemption"
Latest dump attached.
The whocrashed report is now indicating an issue with Hardware Abstraction Layer DLL


I have not replaced memory yet ( I have a compatible set)
I have not replaced video card yet ( I have identical)
I have not turned off a core in the bios ( any link to how to do so?)

I can do any or all of these last three at your suggestion.

Thanks for all the help

 

[bobus1964]

Newer BSOD mentions the audio driver for the sound card.

I have checked and the driver installed is the most current one from the vendor site.

New dump attached

 

[Arc]

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

Use !analyze -v to get detailed debugging information.

[COLOR=Red]BugCheck 9C[/COLOR], {0, fffff88002fddc70, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!KxMcheckAbort+6c )

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

It is a purely hardware error.

► Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight, per RAM module per slot.

► Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

► Stress test the CPU.
Hardware - Stress Test With Prime95

Let us know the results.

 

[bobus1964]

I swapped out the wife's video card with mine (same model) and her RAM with mine (different RAM but on QVL for her board)

This also allows me time to do more testing on her components in my system as hers cannot be tied up running the tests and troubleshooting during normal daylight hours.

I ran the Video Card - Stress Test with Furmark on her card. I ran the test for 15 minutes. Maximum temperature levelled off at a high of 84.

There were no artifacts but at 10 min 10 sec the screen went black for a second, and then returned to normal Furmark testing screen.

Does this mean we have the culprit?

 

[Arc]

Take the other tests too. It seems that furmark went good there.

 

[bobus1964]

Well Wife's system just BSOD'ed (secondary processor interrupt) with the replacement RAM and video card so that's 2 more things that are eliminated as the cause.

So it seems we are down to a MB; CPU or PS hardware issue

I'll re-run the Prime 95 again but it passed the first time and also passed Intel's own processor test .

Any way to test a PS or a program to monitor voltages?

 

[Arc]

There is a way .... http://www.sevenforums.com/vip/257690-psu-how-test.html

I have never tried it. If you want, I will call Britton30 to guide you.

 

[bobus1964]

That link appears to be in a VIP section I have no access to.

I can get a tester at a shop near me for 30 bucks. Are they reliable enough to show if the PS is not sending enough juice?

 

[Britton30]

As stated, this is not s definitive PSU test procedure.
IF you can get a tester as shown below it does put a minor load on it.
You can download HWinfo to check voltages while running, see snip. Acceptable voltage ranges are under Method Two below.

View attachment 241671

PSU - How to Test

Information
The following steps are completely safe if the following steps are done exactly as shown.

Warning
Do not under any circumstances open the case on any PSU!

The capacitors in it will hold enough current to kill or severely burn you for several days even after powered off and unplugged.

Unplug the PSU until instructed to plug it in.

​

Note
This is not meant to be a complete nor definitive PSU test but will determine is the suspect unit will in fact power on. If a system will still not power on even though this test shows the PSU will, further investigation of hardware, CPU, graphics card, motherboard, etc., is needed.




Method One
Step one

1. Switch off the PSU if it has a switch and unplug it from the wall power or UPS. This must be done because even with computer powered off, the PSU is still on and has voltage present in its connectors.

2. Open the computer and locate the large power connector. It is normally on the right side of the motherboard.

3. Locate the locking tab on the connector, press it in to release and wiggle the connector and pull it out of the socket.

This is what it looks like and will have 20 or 24 pins and may be a white color.


Step Two

1. Bend a paper clip as shown in the illustration below.

2. Insert one end in the connector hole with the green wire and the other end to any one with a black wire. We have jumpered the green and a black conductor now.

3. See illustration above to locate the proper connectors.

Warning
Do not jumper ANY conductors other than GREEN and BLACK.

Information
The green wire may be a different color but will be in the same position as the green one shown in the diagram above and below.





4. After jumpering the green and black conductors as shown above, plug in and switch on (if previously switched off) the PSU.

5. Check the PSU fan, it should be running now, if so the PSU is working. The case fans may run at this time which is normal. They may not run too which is also normal.

5. At this point if the PSU fan runs but the PC still won't power on or has other issues, continue to method two below.


Method Two

1. Unplug the PSU. This method will use a Volt/Ohm meter (VOM) if available, to check the voltage out put. Leave the jumper connected. See illustration below.

2. Adjust the VOM to so it will read at least 20VDC, volts DC, direct current. Put the black VOM lead on any black conductor and the red on another color.
Yellow = 12VDC (11.4 - 12.6)
Red = 5VDC (4.75 - 5.25)
Orange = 3.3VDC (3.135 - 3.465)
These color conductors will have the same voltage on any of the PSU connectors.

3. Plug in the PSU and switch it on. Readings should be ± 5% (in red above) of the nominal voltages. In this picture the VOM is reading a 12VDC lead and shows 11.77 which is within specs and ok. If outside if these ranges, the unit is bad.
4. If the volts are within range but there are still problems, go to method three below.



Method Four

1. A better way to test a PSU is with a dedicated PSU tester like below. It will put a load on the PSU and test volts under load. This shows this PSU faulty due to 0VDC on the 12V 2 connector.

2. A PSU tester will automatically let you know if voltages are where they should be. Many will have an LCD display turn red for a bad PSU and emit a loud series of beeps.

 

[bobus1964]

I purchased a Thermaltake Dr. Power II power tester and tested the Power supply.

All numbers well with standards. And I thought this would be an easy troubleshoot

Edit:

Just found out that the GTX260 does not natively support DX11 which is what it was set for in Warcraft. (Blizzard forums are saying Nvidia cards are crashing all over the place after last upgrade)

Have changed settings to DX9 to see if that resolves.