Windows 10: Windows 10 repeating BSOD: WHEA_UNCORRECTABLE_ERROR

Issue:Since yesterday night, I've been unable to spend more than roughly 30 seconds in Windows 10 until running into a BSOD. The screen freezes not the mouse cursor, and eventually bluescreens with WHEA_UNCORRECTABLE_ERROR. This happens even when launching through safe mode tried once. Below is some context. Let me know if more information is needed.Final moments:Symptoms appeared when I was playing Roblox don't bully me, the system would at a few occasions freeze for 30s to a few minutes, system almost completely non-responsive. After maybe 5 times of that happening I held down the po

:)

 

BSOD whea_uncorrectable_error and clock_watchdog_timeout

Hello,

After Cmos reset and clean Windows 10 install I'm started getting some BSODs.
First time I've got whea_uncorrectable_error and some time later clock_watchdog_timeout.

Now I'm getting clock_watchdog_timeout all the time when I try to start AIDA64 stability test and in the middle game of CS:GO.

Here is dump from bluescreenview:
http://tintaiexcess.com/dmp.htm

And here is the dump files from "C:\Windows\Minidump":
http://www.mediafire.com/download/q2oy1mc5ku7girx/080315-7468-01.dmp
http://www.mediafire.com/download/ap25qa4ilr4gtc0/080315-7359-01.dmp

My CPU is running at 4.6G at 1.328V. RAM at 1866Mhz at 1.5V.
Stock looks stable.

Thanks
Tintai

 

BSOD whea_uncorrectable_error and clock_watchdog_timeout

drop your overclock to stock and run it, W10 has some teething to get through

 

BSOD whea_uncorrectable_error and clock_watchdog_timeout

I disagree, it is hardware, windows 10 is using more of the advanced instruction abilities to speed up the OS than Windows 8, just like when we took X86 stable overclocks into X64 and they failed, more data is being moved and used and the chances for failure are significantly higher, and the rounding that every processor does didn't add up in X64.

So as previously suggested, add more volts, or back down the overclock.


Windows 8, and 7 drivers work in Windows 10 as the kernel is very similar, and MS is updating hardware with whatever "stable" WHQL they have for the piece of hardware based off its Hardware ID.

I am fairly certain without even looking that the memory address referenced in your dump files will be very low, and may even be in the processor cache with a pointer to the RAM address.


Yep, your second BSOD referenced "3594f" which is in HEX, and correlates to "219,471" which is the number in Kb from 0 that was in use, so a "101" and "124"BSOD with a very low memory address to me smells exactly like more core voltage needed, or a lower overclock.