BSOD CLOCK_WATCHDOG_TIMEOUT ntoskrnl.exe & hal.dll

[TylerLa]

Can anyone please help me resolve this issue, been happening for over a year and I've not been able to use this new PC i built. Seem to happen all the time and not at any certain point. It doesn't always give me a full BSOD, sometimes its blue with 2 dots for the eyes where the sad face normally is.

Minidumps are attached:
https://www.sendspace.com/filegroup/zng7O8M5ZJO7a%2F6UaIBLF9tUlxhI4MrjlwLkM4djCe2e%2Fdy%2BRRq3UuzF%2FsjbSsbn?_ga=1.160388600.493832974.1491378402

 

[Colif]

Bug Check 0x101: CLOCK_WATCHDOG_TIMEOUT
The CLOCK_WATCHDOG_TIMEOUT bug check has a value of 0x00000101. This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.

ntoskrnl (new technology operating system kernel) and hal (hardware abstraction layer) are parts of windows that deal with hardware reuests (though ntoskrnl does so much more)

what are the specs of the PC? what CPU do you have? what motherboard?

possible fixed with a bios update. Sounds like a CPU error.

 

[TylerLa]

Bug Check 0x101: CLOCK_WATCHDOG_TIMEOUT
The CLOCK_WATCHDOG_TIMEOUT bug check has a value of 0x00000101. This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.

ntoskrnl (new technology operating system kernel) and hal (hardware abstraction layer) are parts of windows that deal with hardware reuests (though ntoskrnl does so much more)

what are the specs of the PC? what CPU do you have? what motherboard?

possible fixed with a bios update. Sounds like a CPU error.

I think I've already updated BIOS a while ago.

Specs:

• 
  MSI AMD Radeon R9 285 Gaming Edition 2048MB GDDR5 PCI-Express Graphics Card
  AMD Piledriver FX-8 Eight Core 8350 Black Edition 4.00GHz (Socket AM3+) Processor
  ASRock 990FX Extreme3 AMD 990FX (Socket AM3+) DDR3 ATX Motherboard
  Microsoft Windows 8.1 64-Bit (BSOD if i try to update to windows 10)
  Corsair CS650M 650W Semi-Modular 80+ GOLD Certified Power Supply (CP-9020077-UK)
  Seagate SSHD 7200RPM 3.5" 1TB SATA 6Gbs 64MB Cache - OEM (ST1000DX001) SSHD Hybrid Drive
  TeamGroup Elite Black 8GB (2x4GB) DDR3 PC3-12800C11 1600MHz Dual Channel Kit (TPKD38G1600HC11DC01)

 

[Colif]

I think the cause is your CPU but I can't read the dumps myself, I just went with the error codes.

You can run Prime 95 to test CPU: http://www.guru3d.com/files-details/prime95-download.html

I don't know if drivers can cause these as from wording it was a core that wasn't answering in the CPU and i doubt software can cause that.

 

[TylerLa]

I think the cause is your CPU but I can't read the dumps myself, I just went with the error codes.

You can run Prime 95 to test CPU: http://www.guru3d.com/files-details/prime95-download.html

I don't know if drivers can cause these as from wording it was a core that wasn't answering in the CPU and i doubt software can cause that.

What would be wrong with my CPU? its been doing it since i built the PC and everything was bought new for the build.
I can't run a Prime95 test as it either just freezes the PC or gives BSOD after a few minutes. MemTest doesn't seem to crash it straight away but PC BSOD's after 10-20mins of being on anyway.

 

[kol12]

Are you overclocking the CPU? Have you adjusted anything in the bios related to the CPU? Does Prime 95 crash instantly?

 

[TylerLa]

Are you overclocking the CPU? Have you adjusted anything in the bios related to the CPU? Does Prime 95 crash instantly?

No, haven't done anything like that. I've taken it all apart and put it back together and reinstalled the operating system on it a few times as well. Prime runs for a minute or two sometimes.

 

[kol12]

Why have you taken it apart a few times? Have you tried resetting the bios?

 

[TylerLa]

Why have you taken it apart a few times? Have you tried resetting the bios?

The first time was to make sure everything was in the correct place and nothing was loose and the second time was to clean it of dust. I haven't tried to do that., how do i do it?

 

[johnbl]

you need to change the memory dump type from minidump to kernel memory dump. Otherwise the correct debug info from this error is not saved.

All i can see in the memory dump is that one processor core timed out waiting for another processor core to respond. I can not see what the second core was doing. (most likely failing to install a driver over and over, most often it will be a USB driver)

a kernel memory dump will show what was running on all of the cores, minidump only shows the active core.