System BSOD - Clock

Page 1 of 5 123 ... LastLast

  1. Posts : 225
    windows 7 professional x32
       #1

    System BSOD - Clock


    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
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    It is a clock watchdog timeout.
    Code:
    *******************************************************************************
    *                                                                             *
    *                        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: 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



    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.
      My Computer


  3. Posts : 225
    windows 7 professional x32
    Thread Starter
       #3

    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
      My Computer


  4. Posts : 225
    windows 7 professional x32
    Thread Starter
       #4

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


  5. Posts : 225
    windows 7 professional x32
    Thread Starter
       #5

    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.
      My Computer


  6. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #6

    The BSOD is caused by Total Recorder WDM audio filter driver.
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck D1, {fffff880046c0490, 2, 8, fffff880046c0490}
    
    *** WARNING: Unable to verify timestamp for TotRec8.sys
    *** ERROR: Module load completed but symbols could not be loaded for TotRec8.sys
    Probably caused by : TotRec8.sys ( TotRec8+1e490 )
    
    Followup: MachineOwner
    ---------
    And the driver is old.
    Code:
    fffff880`046a2000 fffff880`046ca000   TotRec8  T (no symbols)           
        Loaded symbol image file: TotRec8.sys
        Image path: \??\C:\Windows\system32\drivers\TotRec8.sys
        Image name: TotRec8.sys
        Timestamp:        Wed Dec 14 23:22:54 2011 (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.
      My Computer


  7. Posts : 225
    windows 7 professional x32
    Thread Starter
       #7

    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.
      My Computer


  8. Posts : 225
    windows 7 professional x32
    Thread Starter
       #8

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


  9. Posts : 225
    windows 7 professional x32
    Thread Starter
       #9

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

  10.    #10

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


 
Page 1 of 5 123 ... LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 18:08.
Find Us