Ocassional BSOD when doing anything that uses much CPU and RAM

Ravenstorm · 31 Dec 2013

Hello guys and thank you for your support, hope you can help me, here are some informations about my problem, BSOD mostly happens when I play video games, or encode videos with Megui or when i watch movies, or do anything that uses much CPU or RAM and heats the computer.

On Tue 31.12.2013. 17:36:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\123113-54272-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x101 (0x61, 0x0, 0xFFFFF880009E8180, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Tue 31.12.2013. 12:00:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\123113-41496-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x101 (0x61, 0x0, 0xFFFFF880009E8180, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Sun 29.12.2013. 18:58:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122913-36878-01.dmp
This was probably caused by the following module: Unknown (0xFFFFF80002C7EF00)
Bugcheck code: 0x101 (0x61, 0x0, 0xFFFFF880009E8180, 0x1)
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 be caused by a thermal issue.
A third party driver was identified as the probable root cause of this system error.
Google query: CLOCK_WATCHDOG_TIMEOUT

On Sun 22.12.2013. 21:42:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122213-38735-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x101 (0x61, 0x0, 0xFFFFF880009E8180, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Sat 7.12.2013. 17:57:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120713-17768-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x101 (0x61, 0x0, 0xFFFFF880009E8180, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Sat 7.12.2013. 15:05:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120713-15724-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71ED0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Sat 30.11.2013. 10:01:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\113013-17565-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x101 (0x61, 0x0, 0xFFFFF880009E8180, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

matts6887 · 31 Dec 2013

When was the last time you have dusted out any dust/dirt that may be accumulating on the inside of the computer case? Reason i ask is because not doing regular cleaning can cause a buildup of dust and dirt which can act as a blanket and will not let heat dissipate as quickly. So i would do a cleaning if it has not been done recently. Also; If you can, go into the bios and check and see what the rpm reads for cpu and chassis fans(chassis fans if applicable). the cpu fan should approx. be no lower than 1000 rpm give or take(someone correct me if wrong) And if you can alter/change the settings for the fan; bump it up to a higher setting and see if that helps any. Also; I would unscrew and take off the cpu fan and make sure there is enough thermal paste which helps in the cooling process. If there is not enough paste on the heat sink; it will not dissipate heat as quickly as the air being drawn out of the system by the fan uses the past to create a sort of cooling effect if you will.

Ravenstorm · 01 Jan 2014

I cleaned computer and everything not so long ago, I changed motherboard and when i was putting back CPU i applied new layer of thermal paste, but I think problem was in cooling fan because of the new motherboard my settings reset and I configured it to work on 50% of the cooling power (max was 1200 rpm), now max is 2100 rpm, and it automatically goes up and down based on system temperature. Thank you for your advice, I will see now how it will react.

Best Regards