System BSOD - Clock

[ZMan]

While just browsing for a file today my system BSOD out. Now I been using the system for about a good year or so and had no problems. I check and no updates been apply in the last few weeks. So I'm not sure what happen. The BSOD said something about an clock and that all I could see before the restart happen. I have a custom built system and have attach But Tool results and the DXDiag information about the system. I have Windows 7 Pro 64-Bit, 24BG of memory. That all I can recall and know about sorry if that not that much help. Thanks if you can give some feedback.
ZMan

 

[Arc]

It is a clock watchdog timeout.

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

[URL="http://www.carrona.org/bsodindx.html#0x00000101"]CLOCK_WATCHDOG_TIMEOUT (101)[/URL]
[COLOR=Red]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.[/COLOR]
Arguments:
Arg1: 0000000000000019, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff8800316a180, The PRCB address of the hung processor.
Arg4: 0000000000000007, 0.

So somehow the processor is failing. It may be processor's own fault, or it may be something else (like any driver or any other failing hardware) is not letting the processor cores work perfectly.

The crash dumps have not caught any driver as failing, but you should take another chance, I guess. Follow Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any. Post it following the Blue Screen of Death (BSOD) Posting Instructions.

But before enabling Driver Verifier, you should perform some hardware tests. Take the following tests:

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.

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

Stress test the CPU.
Hardware - Stress Test With Prime95

Seatool for dos: SeaTools | Seagate download. Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.

Also, do these things, too.

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
At least 30% extra is safe.

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy.

Let us know the results.

 

[ZMan]

It don't seem to be doing it again...I keep an eye out for it and if it does I will post back.
Thanks

 

[ZMan]

Looks like it still doing it. I doing test right now and get back to you on the progress on it.

 

[ZMan]

It would seem that it after turning on drivers it crash upon the reboot. I had to boot to safe mode to change it back so I can do a normal boot up. Here is the the information from the Diagnostics Tools, hopefully it was just a driver causing my problem.

 

[Arc]

The BSOD is caused by Total Recorder WDM audio filter driver.

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

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffff880046c0490, 2, 8, fffff880046c0490}

*** WARNING: Unable to verify timestamp for [URL="http://www.carrona.org/drivers/driver.php?id=TotRec8.sys"]TotRec8.sys[/URL]
*** ERROR: Module load completed but symbols could not be loaded for [URL="http://www.carrona.org/drivers/driver.php?id=TotRec8.sys"]TotRec8.sys[/URL]
Probably caused by : [URL="http://www.carrona.org/drivers/driver.php?id=TotRec8.sys"]TotRec8.sys[/URL] ( TotRec8+1e490 )

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

And the driver is old.

fffff880`046a2000 fffff880`046ca000   TotRec8  T (no symbols)           
    Loaded symbol image file: TotRec8.sys
    Image path: \??\C:\Windows\system32\drivers\TotRec8.sys
[COLOR=Red]    Image name: TotRec8.sys
    Timestamp:        Wed Dec 14 23:22:54 2011[/COLOR] (4EE8E276)
    CheckSum:         00029464
    ImageSize:        00028000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Either you update it from Sound recording tools: Total Recorder - captures any audio from the Internet, records audio from CD, microphone, line-in, converts any sound formats to WAVE and MP3, or uninstall it.

Let us know the results.

 

[ZMan]

I updated from the main website, we see what happens next. Give me a few days to see if it happens again. Thanks for the help.

 

[ZMan]

Happen again wanting for the BSOD to happen will post soon.

 

[ZMan]

Still waiting to for it to fail, testing is still going on.

 

[x BlueRobot]

Can I just ask why do you want your computer to BSOD? What test are you running? Driver Verifier?

 

[Arc]

Can I just ask why do you want your computer to BSOD? What test are you running? Driver Verifier?

My post to him ... a week ago.

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Is he still running it?

 

[ZMan]

Haven't have the time to fully set and watch the test, don't want it to run it by itself and it blow up if that the case. GPU and CPU test will happen this evening. Memory test tomorrow morning.

 

[x BlueRobot]

Driver Verifier will be safe to leave running, it's designed to monitor the drivers installed on your system, and create a BSOD if the drivers' behavior meets a certain variable set when configuring Driver Verifier.

 

[ZMan]

All test show that there nothing wrong but it still doing it....mmmmm Any ideas?

 

[Arc]

All test show that there nothing wrong but it still doing it....mmmmm Any ideas?

Which it is still doing what it?

 

[ZMan]

The original BSOD from the first post
An expected clock interrupt was not received on a secondary processor in anMP system within the allocated interval.

 

[Arc]

The original BSOD from the first post
An expected clock interrupt was not received on a secondary processor in anMP system within the allocated interval.

Post it following the Blue Screen of Death (BSOD) Posting Instructions.

 

[x BlueRobot]

Ensure you have configured a Kernel Memory dump instead, if a Stop 0x101 is still occurring, a Minidump will not contain enough information - http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

You will need to place the file into a zipped folder, and then upload to a file sharing site such as Dropbox or Skydrive. Make sure the folder is placed in the Public folder if using Skydrive. Post the link to the file afterwards.

Is Driver Verifier still running? Stop 0x101's with Driver Verifier running, indicate more of a hardware related issue.

 

[ZMan]

The original BSOD from the first post
An expected clock interrupt was not received on a secondary processor in anMP system within the allocated interval.

Post it following the Blue Screen of Death (BSOD) Posting Instructions.

Here is the BSOD. What going on now is that sometimes the system starts to respond slowly. An example is that the mouse arrow disappear and takes a moment to get caught up with where I'm moving the mouse. Control+Alt+Delete responds slow as well. Only a few moments and then it back to working fully. I check out the processing but couldn't see anything out of the norm. When this is happening I shut down the system and than it all speeds down like it turn off no fans running or CPU spinning away but it still on. I then have to cold boot it to make it turn off. It makes no sense. A full system scan with MSE and other virus and trojan scanners show nothing. :/

 

[ZMan]

Ensure you have configured a Kernel Memory dump instead, if a Stop 0x101 is still occurring, a Minidump will not contain enough information - http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

You will need to place the file into a zipped folder, and then upload to a file sharing site such as Dropbox or Skydrive. Make sure the folder is placed in the Public folder if using Skydrive. Post the link to the file afterwards.

Is Driver Verifier still running? Stop 0x101's with Driver Verifier running, indicate more of a hardware related issue.

Driver Verfier is still running and Kernal Memory dump has been setup up for months before this even started to happen. There is not file tho in the location on the C Root.