Pc blue screening?

gregzyme3

Reputable
Jun 19, 2015
32
0
4,530
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 18/12/2016 19:15:36 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFF88002F65180)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF88002F65180, 0x2)
Error: CLOCK_WATCHDOG_TIMEOUT
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 also be caused because of overheating (thermal issue).
A third party driver was identified as the probable root cause of this system error.
Google query: CLOCK_WATCHDOG_TIMEOUT





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

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

From WhoCrashed.

Any idea what on earth this means? How could I possibly fix it?
 
Solution
some hardware did not respond within its timeout period. the timeout was 31 clock ticks. that is pretty fast.

since you have windows 7 make sure you are not installing a usb wireless Ethernet thumb device. Certain ones had bugs and would hang a processor when it tried to reinstall over and over and fail. You had to turn off plug and play, install the updated wireless driver, then turn on plug and play or your machine would bugcheck.

this error also happens with overclocked video cards, or over heated components.

If you change the memory dump type to kernel, then the next system crash will make a file c:\windows\memory.dmp
and that dump will have the actual device info for the failing device.
otherwise you just end up guessing.
some hardware did not respond within its timeout period. the timeout was 31 clock ticks. that is pretty fast.

since you have windows 7 make sure you are not installing a usb wireless Ethernet thumb device. Certain ones had bugs and would hang a processor when it tried to reinstall over and over and fail. You had to turn off plug and play, install the updated wireless driver, then turn on plug and play or your machine would bugcheck.

this error also happens with overclocked video cards, or over heated components.

If you change the memory dump type to kernel, then the next system crash will make a file c:\windows\memory.dmp
and that dump will have the actual device info for the failing device.
otherwise you just end up guessing.
 
Solution