By Speck13
Oct 2, 2014
Post New Reply
  1. Good day,

    My PC has been blue screen crashing for a few weeks. I have the 'Who Crashed' program which generates a report of the recent crash. It finds that it is a CLOCK_WATCHDOG_TIMEOUT error. Anyone know where I should begin to troubleshoot? I have posted the report below. Your help is very much appreciated.

    Thank you,



    Home Edition Notice


    This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.

    Click here for more information on the professional edition.

    Click here to buy the the professional edition of WhoCrashed.


    System Information (local)


    computer name:

    windows version: Windows 7 Service Pack 1, 6.1, build: 7601

    windows dir: C:\Windows

    Hardware: Studio XPS 435T/9000, DELL Inc., 0X501H

    CPU: GenuineIntel Intel(R) Core(TM) i7 CPU 960 @ 3.20GHz Intel586, level: 6

    8 logical processors, active mask: 255

    RAM: 9654226944 total

    VM: 2147352576, free: 1909882880


    Crash Dump Analysis


    Crash dump directory: C:\Windows\Minidump

    Crash dumps are enabled on your computer.

    On Thu 10/2/2014 4:14:32 AM GMT your computer crashed

    crash dump file: C:\Windows\memory.dmp

    This was probably caused by the following module: Unknown (0xFFFFF88003164180)

    Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF88003164180, 0x2)


    Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.

    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.

    A third party driver was identified as the probable root cause of this system error.





    One crash dump has been found and analyzed.

    Read the topic general suggestions for troubleshooting system crashes for more information.

    Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

  2. Tmagic650

    Tmagic650 TS Ambassador Posts: 17,244   +234

    Go to C:\windows\minidump. Minidump files have a .dmp extension. Select all the .dmp files, right-click sending the files to a compressed(zipped)folder. Upload this folder as a file here

Similar Topics

Add your comment to this article

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...