Windows 10: Brand new Build. BSod CLock_Watchdog_Timeout and Freezes.

CPU is really generating some heat [44c] and I rebooted thinking something odd was going on. I'm webbrowsing on the machine just to see if I get an errors/freezes.

Upon reboot I got the error: BlInitializeLibrary failed 0xc0000009a

 

rebooted into safe mode.
opened photoshop 6
entered develop module
got a good 30 seconds of processing done, then the same FULL system freeze. NO control-alt del. nothing.
after about 10 seconds I get a BSoD

whea_uncorrectable_error

 

something is definitely going on. It was 78F in my office a few minutes ago and after the last error I completely shut that machine down. The temp in has dropped significantly in the 20 minutes its been off.

Could this be a bad power supply?
Could the processor be bad even though it ran prime95 and passed the intel processor testing?

Please help. I've invest $2k in this build and I am completely lost at what the hell is wrong with it. I've built several computers and never had these sort of issues.

 

44C for the CPU is really fine and I can't even reach that at idle. My minimum is around 55CC

Please keep the test running and abort if the CPU reaches around 85C

 

Hi axe.
Did you read my previous posts on bottom of page 3?

passed prine95 twice.
LR6 locks up in safe mode.
had new errors
please read those

 

At 6AM my time I read the posts yes.

Do you have SATA/AHCI/something else in your BIOS enabled?
https://www.tenforums.com/tutorials/2...tallation.html

Please re-run the tool from the BSOD post instructions and upload the zip file.

 

BIOS:
SATA enabled
MODE AHCI

 

heres the new zip file

 

The dump is corrupted.






Diagnostic test

GPU TEST


Run Furmark tutorial



Note Run Furmark for around 30 minutes



Warning Your GPU temperatures will rise quickly while Furmark is running. Keep a keen eye on them and abort the test if temperatures rise too high






Diagnostic Test

RAM TEST


Run MemTest86+ - Test RAM - Windows 10 Forums



Note



MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

 

What do you mean corrupted?

 

I cannot open the dump file properly as it should.
If I run a command on 1 of the parameters I don't get the usual output, but the output of something not being able to load.
This is most likely due to heavy hardware problems.

For example, this is an output of what I get from another thread
Code: 1: kd> !errrec fffe00184374028 =============================================================================== Common Platform Error Record @ ffffe00184374028 ------------------------------------------------------------------------------- Record Id : 01d100eefab7af93 Severity : Fatal (1) Length : 928 Creator : Microsoft Notify Type : Machine Check Exception Timestamp : 10/7/2015 22:01:24 (UTC) Flags : 0x00000000 =============================================================================== Section 0 : Processor Generic ------------------------------------------------------------------------------- Descriptor @ ffffe001843740a8 Section @ ffffe00184374180 Offset : 344 Length : 192 Flags : 0x00000001 Primary Severity : Fatal Proc. Type : x86/x64 Instr. Set : x64 Error Type : Cache error Operation : Data Read Flags : 0x00 Level : 2 CPU Version : 0x00000000000306a9 Processor ID : 0x0000000000000001 =============================================================================== Section 1 : x86/x64 Processor Specific ------------------------------------------------------------------------------- Descriptor @ ffffe001843740f0 Section @ ffffe00184374240 Offset : 536 Length : 128 Flags : 0x00000000 Severity : Fatal Local APIC Id : 0x0000000000000001 CPU Id : a9 06 03 00 00 08 10 01 - bf e3 9a 7f ff fb eb bf 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 Proc. Info 0 @ ffffe00184374240 =============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ ffffe00184374138 Section @ ffffe001843742c0 Offset : 664 Length : 264 Flags : 0x00000000 Severity : Fatal Error : DCACHEL2_DRD_ERR (Proc 1 Bank 6) Status : 0xbe20000000021136 Address : 0x000000008f2cec00 Misc. : 0x000000b041004086[/quote] This is the output I get from your dump
Code: 4: kd> !errrec ffffe00042cf0028 =============================================================================== Common Platform Error Record @ ffffe00042cf0028 ------------------------------------------------------------------------------- Signature : *** INVALID *** Revision : 0.0 Record Id : 0000000000000000 Severity : Recoverable (0) Length : 0 Creator : {00000064-0000-0000-70d5-395133000000} Notify Type : {00000064-0000-0000-70d5-395133000000} Flags : 0x00000000[/quote]

 

Is there something I need to do to make the dump work properly?

I have furmark running. - 8 mins, no issues so far

I ran memtest86+ last week for over 24 hours. went to 6 passes with no errors

 

You can't unfortunately.
Usually it is hardware, sometimes because of a cracked system and rarely (last assord) from Microsoft.

 

just cruised past 30mins of furmark without issue.
max temp was 55c

 

what next? like I said I ran memtest already for about 26 hours