On Mon 30.12.2019 21:33:06 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\123019-18562-01.dmp
This was probably caused by the following module:
Unknown (0x0000000000000002)
Bugcheck code: 0x101 (0xC, 0x0, 0xFFFF9480F7AC3180, 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 can be caused by non-responding hardware or by a overheated CPU (thermal issue).
A third party driver was identified as the probable root cause of this system error.
Google query:
CLOCK_WATCHDOG_TIMEOUT
On Thu 26.12.2019 19:59:15 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\122619-17765-01.dmp
This was probably caused by the following module:
Unknown (0x0000000000000003)
Bugcheck code: 0x101 (0xC, 0x0, 0xFFFFDC802D979180, 0x3)
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 can be caused by non-responding hardware or by a overheated CPU (thermal issue).
A third party driver was identified as the probable root cause of this system error.
Google query:
CLOCK_WATCHDOG_TIMEOUT
On Thu 26.12.2019 13:08:52 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\122619-17312-01.dmp
This was probably caused by the following module:
Unknown (0x0000000000000003)
Bugcheck code: 0x101 (0xC, 0x0, 0xFFFF8C81F7D79180, 0x3)
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 can be caused by non-responding hardware or by a overheated CPU (thermal issue).
A third party driver was identified as the probable root cause of this system error.
Google query:
CLOCK_WATCHDOG_TIMEOUT