Kevin (Banned) Jan 23, 2016 @ 8:05pm
Constantly getting BSOD on dekstop (im a bit scared)
Blue Screen of Death, Error message reads WHEA_UNCORRECTABLE_ERROR everytime, I have run a stress test on gpu which I though was the culprit, no overheating or problems there, Tested memory, no problem there at least from what the test stated, and check hard drive for corruption to no effect

I am running windows 10 i7 4790k at 4ghz with gtx 770 2gb 16gb ram asus maximus hero VII motherboard

My computer will crash after ten minutes in game or 30 minutes of idle without anything harsh running at all other than normal back ground procedures, I am wondering if I should just reseat everything or not?

This only started occuring after I updated to windows 10 from windows 7 (64-bit), But only started a month after the change in operating system.

I am quite alarmed, But I dont have the money to take it in an get it checked out at like microcenter or a mom and pop shop, I am at loss of words because I am not getting any known error code in error log that I can go on, All I get is the WHEA_UNCORRECTABLE_ERROR which tends to always point to hardware,

FYI Nothing in my system is new, all updates for my hardware are updated for windows 10

UGH
< >
Showing 1-11 of 11 comments
Alexalmighty Jan 23, 2016 @ 8:08pm 
This is a bugcheck generated directly by the CPU. Most often it is caused because of incorrect voltage being applied to the CPU.
This can happen because of incorrect settings being applied to the BIOS (often resetting the BIOS to the defaults or updating the BIOS helps) Sometimes it indicates that a Power supply is outside of its correct voltage range. (power supply voltage regulators or mother board voltage regulator is in the process of failing.

2 seconds of internet searching
Alexalmighty Jan 23, 2016 @ 8:09pm 
so increase your cpu voltage a bit and it should stop crashing
since you updated to windows 10 from windows 7, i suggest you (re)install drivers for windows 10 (motherboard chipset, gpu, network, and the like rebooting at each step)
Kevin (Banned) Jan 24, 2016 @ 9:14am 
Originally posted by Alexalmighty502:
This is a bugcheck generated directly by the CPU. Most often it is caused because of incorrect voltage being applied to the CPU.
This can happen because of incorrect settings being applied to the BIOS (often resetting the BIOS to the defaults or updating the BIOS helps) Sometimes it indicates that a Power supply is outside of its correct voltage range. (power supply voltage regulators or mother board voltage regulator is in the process of failing.

2 seconds of internet searching
I will try this, I had already reset bios settings to optimum defaults, so I will attempt to up the voltage a bit
edmond_dixon Jan 26, 2016 @ 5:43pm 
There's a discussion with answers on tomshardware.com about the issue. I'd check it out.
10upN2DOWN Jan 26, 2016 @ 5:49pm 
Originally posted by Kevin:
Originally posted by Alexalmighty502:
This is a bugcheck generated directly by the CPU. Most often it is caused because of incorrect voltage being applied to the CPU.
This can happen because of incorrect settings being applied to the BIOS (often resetting the BIOS to the defaults or updating the BIOS helps) Sometimes it indicates that a Power supply is outside of its correct voltage range. (power supply voltage regulators or mother board voltage regulator is in the process of failing.

2 seconds of internet searching
I will try this, I had already reset bios settings to optimum defaults, so I will attempt to up the voltage a bit

Good way to check, unplug the GPU it draws lots of power
Azza ☠ Jan 26, 2016 @ 6:01pm 
WHEA stands for Windows Hardware Error Architecture. So it's a hardware failure issue, WHEA_UNCORRECTABLE_ERROR indicates that a fatal hardware error has occurred.

Do you know it's parameters given to that error code?

Check the start of it (parameter 1 given is the error type)...

0x0 = machine check exception occurred
0x1 = corrected machine check exception
0x2 = corrected platform error occurred
0x3 = nonmaskable Interrupt (NMI) error
0x4 = uncorrectable PCI Express error (your graphics card)
0x5 = generic hardware error (try removing other devices connected)
0x6 = initalization error
0x7 = BOOT error
0x8 = Scalable Coherent Interface (SCI) error
0x9 = Itanium-based machine check abort
0xA = corrected Itanium-based machine check error occurred
0xB = corrected Itanium-based platform error occurred

From that, you should be able to work out if it's your motherboard faulty, memory, the graphics card, psu (power supply) or another device, etc...
Last edited by Azza ☠; Jan 26, 2016 @ 6:05pm
Kevin (Banned) Jan 27, 2016 @ 5:49am 
all it ever shows is 0x0 which is annoying
Alexalmighty Jan 27, 2016 @ 6:02am 
Maybe this website will help http://www.solvusoft.com/en/errors/runtime-errors/microsoft-corporation/windows-installer/0x0-windows-installation-error-code-0x0/ this slightly beyond me though and I'm on my phone so I can't effectively research it if no one has a solution before I get home I'll spend some time looking up solutions
Kevin (Banned) Jan 27, 2016 @ 7:09am 
No idea :P beyond my knowledge as well of course
Azza ☠ Jan 27, 2016 @ 8:08am 
Originally posted by Kevin:
all it ever shows is 0x0 which is annoying

Okay, so it's a "machine check exception".

---

If you have overclocking in place - reset it back to factory defaults.

Seems you already checked, but ensure that the machine is also adequately cooled and not overheating.

If you have a multimeter and an understanding of electronics - test the PSU (Power Supply Unit) voltage is correct and stable across the rails.

---

Go to your offical motherboard website:
https://www.asus.com/Motherboards/MAXIMUS_VII_HERO/HelpDesk_Download/

Download the latest BIOS and update that. These "Improve system stability".

---

Under Control Panel > Device Manager. On the top menu, click View > "Show hidden devices". Then check if there are there any ? unknown or ! conflicted/error devices? Or multiple "ghost" drivers.

A ghost drivers is one which sticks around, even after updating or changing the device. Windows tends to get stuck using it. If that's the case, right-click and uninstall them. Then clean install the latest "real" driver again, with admin rights (in safe mode if required).
Last edited by Azza ☠; Jan 27, 2016 @ 8:15am
< >
Showing 1-11 of 11 comments
Per page: 1530 50

Date Posted: Jan 23, 2016 @ 8:05pm
Posts: 11