Anyone else getting WHEA uncorrectable error?

[trevorbergershank]

This is the only game I've ever got this blue screen crash and error - WHEA uncorrectable error.

To give a bit of background - I bought the game when it was ver 2.0 and played a 200+ turn RoC campaign on Low > Med settings and had virtually no issues at all, no stuttering or lag. Then 2.1 and the hotfix seemed to break things for me - without any system changes I had near unplayable stuttering, lag and crashes, one of which was the blue screen crash WHEA uncorrectable error. I rolled back but still this crash persisted.

I've tried absolutely every recommended fix that I can find for this, including a full system reset which allowed the game to run smooth as silk on latest version but did not stop the crash. No scan or diagnostic tool, either windows or third party has turned up any hardware or software issues whatsoever.

I've tried disabling non-default audio devices (apparently this can help) and may also try disabling GPU performance scaling in the bios. But really, it seems nothing is working.

Has anyone else had this specific blue screen crash?

[Salty Nobody]

I get a whea uncorrectable error within a few minutes every time I start my new PC. It triggers faster if I make my gpu work hard (so firing up this game is one way to do that but I prefer to start a blender render) and once it restarts, my PC is fine for many hours afterward. Weird and annoying but not caused by this game.

And I'm completely stumped. I know it's the gpu and I know it is weirdly consistent and I strongly suspect it has something to do with said gpu getting up to temperature from a cold start but I have no idea how to fix it other than let it do its thing every day and getting on with things as normal afterward.

[sintri]

WHEA errors really aren't good. Most common cause is a hardware fault or improper setting. Without spending money:
-run software updates across the board, windows updates, whatever drives, maybe a bios update if you're familiar with the steps.
-run cmd as administrator and type /sfc scannow

If those two don't stop it, disable automatic overclock for your cpu and or ram, maybe one set is faulty. Worst case scenario underclock, if that resolves it then that could point to an issue with either parts assuming they're running slower than advertised.

As for the second poster, I'd guess psu, double check your connection, make sure they're actually secure. Also just double check your temps. If you've got a spare psu would try it out if you know what you're doing. Otherwise, all the other steps still help and may resolve your issue.

If you do find a faulty part and it's within warranty, rma it. If it's a hardware fault, it's not going to resolve itself, so rma before your warranty runs out.

[Old Dirty Bingo Caller]

Yeah you guys are having critical hardware failures, get it fixed before you PC dies completely.

[trevorbergershank]

Originally posted by sintri:

WHEA errors really aren't good. Most common cause is a hardware fault or improper setting. Without spending money:
-run software updates across the board, windows updates, whatever drives, maybe a bios update if you're familiar with the steps.
-run cmd as administrator and type /sfc scannow

If those two don't stop it, disable automatic overclock for your cpu and or ram, maybe one set is faulty. Worst case scenario underclock, if that resolves it then that could point to an issue with either parts assuming they're running slower than advertised.

As for the second poster, I'd guess psu, double check your connection, make sure they're actually secure. Also just double check your temps. If you've got a spare psu would try it out if you know what you're doing. Otherwise, all the other steps still help and may resolve your issue.

If you do find a faulty part and it's within warranty, rma it. If it's a hardware fault, it's not going to resolve itself, so rma before your warranty runs out.

Thanks for the response, much appreciated.

I admit I'm not familiar with updating the bios, but I have updated all drivers and windows.

How do I disable overclocking for cpu and ram??

[Falaris]

Intel states this is a Hardware error message. Either the hardware itself (GPU, processor, whatever) caused an error, or the software interfacing with that hardware (drivers).

https://www.intel.com/content/www/us/en/support/articles/000028099/processors/intel-core-processors.html?wapkw=000028099

On the article is also the recommended steps to solve it. Although... usually it means new hardware, and it'll be challenging to find out which piece of hardware.

And, if you start up another game and play it for a while, you're also likely to get this error.
(If you don't, at least that's an indication it's a memory problem, since WH3 is unusually hungry for memory - still bad, but at least less expensive.).

Good luck, man.

[trevorbergershank]

Originally posted by Falaris:

Intel states this is a Hardware error message. Either the hardware itself (GPU, processor, whatever) caused an error, or the software interfacing with that hardware (drivers).

https://www.intel.com/content/www/us/en/support/articles/000028099/processors/intel-core-processors.html?wapkw=000028099

On the article is also the recommended steps to solve it. Although... usually it means new hardware, and it'll be challenging to find out which piece of hardware.

And, if you start up another game and play it for a while, you're also likely to get this error.
(If you don't, at least that's an indication it's a memory problem, since WH3 is unusually hungry for memory - still bad, but at least less expensive.).

Good luck, man.

Thanks for that, much appreciated.

Pretty sure I've tried all of their recommended fixes and no scan has turned out any hardware or software/driver issues.

I haven't had the crash since disabling non-default audio devices although it is highly likely that this is just a coincidence and that the crash will return in time.

[sintri]

Most diy motherboards will ship with automatic overclock settings, and even some oem ones. You can almost always change it in the bios for diy boards, though for oem sometimes you either won't have the setting or the capability. These days motherboard bios are alot more varied so the exact wording for the setting might be different, but typically you're looking some variant of automatic overclock / overclock tuner, typically you just set it from auto to manual and this should throttle back the system a bit.

Though if you're unsure what you're doing, check up guides for your specific system as touching the wrong values (largely anything that says voltage) can result in permanent damage. Underclocking works the same way, setting the overclock to manual and setting a lower speed than it's specifications for either the cpu or ram. If it does resolve it, it's still not garaunteed to be the offending part's issue, but still makes it a decent candidate for an rma if the resulting stable speed is below advertised specifications.

[Salty Nobody]

Originally posted by sintri:

As for the second poster, I'd guess psu, double check your connection, make sure they're actually secure. Also just double check your temps. If you've got a spare psu would try it out if you know what you're doing. Otherwise, all the other steps still help and may resolve your issue.

If you do find a faulty part and it's within warranty, rma it. If it's a hardware fault, it's not going to resolve itself, so rma before your warranty runs out.

Problem is I can't figure out what the faulty part is and I've already tried everything within my capabilities to either do that or fix the issue.

Temps are low, everything does just fine with every test and benchmark I throw at it and all connections are secure. It just has a whea error once a day like clockwork and after that is over with everything works flawlessly.

At this point I would need to take it in somewhere and pay someone else to solve the problem but I'm not willing to do that for something that currently seems like a minor 5 minute time waster.

[trevorbergershank]

Originally posted by sintri:

Most diy motherboards will ship with automatic overclock settings, and even some oem ones. You can almost always change it in the bios for diy boards, though for oem sometimes you either won't have the setting or the capability. These days motherboard bios are alot more varied so the exact wording for the setting might be different, but typically you're looking some variant of automatic overclock / overclock tuner, typically you just set it from auto to manual and this should throttle back the system a bit.

Though if you're unsure what you're doing, check up guides for your specific system as touching the wrong values (largely anything that says voltage) can result in permanent damage. Underclocking works the same way, setting the overclock to manual and setting a lower speed than it's specifications for either the cpu or ram. If it does resolve it, it's still not garaunteed to be the offending part's issue, but still makes it a decent candidate for an rma if the resulting stable speed is below advertised specifications.

Damn, can't see an overclocking option anywhere in the bios - can't even see a 'Performance' section withing advanced settings. Any ideas?

[Salty Nobody]

Originally posted by trevorbergershank:

Damn, can't see an overclocking option anywhere in the bios - can't even see a 'Performance' section withing advanced settings. Any ideas?

Try looking for power settings for the cpu. If you are lucky you will have a blanket setting to adjust but otherwise you should have power settings for each individual core that you can adjust up or down.

There also might be software that came with your board that lets you adjust this, and there is also third party software. Do your research if you are going to mess with this stuff, this is beyond what I was able to figure out on my own and bad things can happen when this is done improperly.

[sintri]

If it's a Dell/Hp computer, there's a decent chance the bios won't have it in which case it's typically just got the one setting. If that's the case if it's within warranty feel free to rma it, if it's only happening for one game you can also just live with it but know it may or may not spread or get worse over time.

If it's a non-oem motherboard, these things are listed in the user guide which are typically posted online, you'll just need to grab your motherboard model which is typically somewhere on the motherboard itself.

Lastly, yes it commonly is a hardware issue, can sometimes be software, and can sometimes be limited to a specific unrelated piece of hardware and hence you can do workarounds without ever having to resolve the underlying issue. Troubleshooting is a time consuming process, which when I was younger I probably would've easily spend a couple hours to do without thinking it was a waste, these days not terribly as much. So really up to you, if you find a workaround and your stuff's already out of warranty, by all means just stick with it. If you've got some extra time and it's in warranty, do feel free to call up on the warranty if you do suspect a part is defective, just note that too is a time consuming process and will leave you week(s) without that part.

[pascal.difolco]

WHEA is a hardware fault like a core dropping not getting enough voltage, it has not much to do with the game but rather with bad board or BIOS, but if it's Dell...