Random BSOD's
Posted: Fri May 03, 2013 2:07 am
Recently I've been getting this BSOD at random times...but it seems to happen more frequent during load (i.e. Gaming).
I was suspecting it to be temperature related, but it does not seem to be the cause.
- The CPU never exceeds 52*C
- The NB idles at about 41*C, and goes up to 49*C
- SB doesn't go about 35*C
- the GPU caps out at approximately 51*C
- HDD / SSD temps seem to be perfectly normal
I ran WhoCrashed, and it came up with the following:
On Fri 03/05/2013 7:52:53 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050313-5335-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x101 (0x21, 0x0, 0xFFFFF88002FD5180, 0x3)
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 Fri 03/05/2013 7:52:53 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalReturnToFirmware+0xB2D)
Bugcheck code: 0x101 (0x21, 0x0, 0xFFFFF88002FD5180, 0x3)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
Checking the WhoCrashed logs, about 50% of the crashes from the above two - the other 50% is from graphics drivers freaking out at me when I tried to do some OC'ing on my HD 7970 (card is currently at stock so the issue hasn't come back up).
I'm using drivers 13.3 Beta and CAP 10.12 right now...not sure if it may or may not be related...
I thought it was my RAM timings causing issues so I loosened it a tiny bit from 8-9-8-34-21-1T to 8-9-8-36-21-1T...and it didn't help.
Bumped the CPU, CPU-NB, NB, and SB voltage up a tiny bit...and it didn't solve the issue either.
If anyone can help solve my mystery, that you be great!
EDIT:
Dropped my RAM back to stock "Auto" settings; I'll see if that helps.
If not, I guess I'll have to put my CPU and NB OC back down...
Hm...I don't believe my OS is corrupted from too tight RAM timings...
I was suspecting it to be temperature related, but it does not seem to be the cause.
- The CPU never exceeds 52*C
- The NB idles at about 41*C, and goes up to 49*C
- SB doesn't go about 35*C
- the GPU caps out at approximately 51*C
- HDD / SSD temps seem to be perfectly normal
I ran WhoCrashed, and it came up with the following:
On Fri 03/05/2013 7:52:53 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050313-5335-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x101 (0x21, 0x0, 0xFFFFF88002FD5180, 0x3)
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 Fri 03/05/2013 7:52:53 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalReturnToFirmware+0xB2D)
Bugcheck code: 0x101 (0x21, 0x0, 0xFFFFF88002FD5180, 0x3)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
Checking the WhoCrashed logs, about 50% of the crashes from the above two - the other 50% is from graphics drivers freaking out at me when I tried to do some OC'ing on my HD 7970 (card is currently at stock so the issue hasn't come back up).
I'm using drivers 13.3 Beta and CAP 10.12 right now...not sure if it may or may not be related...
I thought it was my RAM timings causing issues so I loosened it a tiny bit from 8-9-8-34-21-1T to 8-9-8-36-21-1T...and it didn't help.
Bumped the CPU, CPU-NB, NB, and SB voltage up a tiny bit...and it didn't solve the issue either.
If anyone can help solve my mystery, that you be great!
EDIT:
Dropped my RAM back to stock "Auto" settings; I'll see if that helps.
If not, I guess I'll have to put my CPU and NB OC back down...
Hm...I don't believe my OS is corrupted from too tight RAM timings...