Metro Exodus's savegame loading process causes WHEA parity cpu errors to appear on _not_ overclocked cpu..

[jEck]

Hi forum. I'm in need of help. On my stock, _not_ overclocked 9900k, Enhanced Edition throws WHEA-logger error 19 AKA corrected parity error in Windows system journal. AFAIK this is basically overclockers' error meaning that cpu voltage is not enough.

Thing is, it happens ONLY when loading a savegame, sometimes causing CTD in the process. Gameplay itself is not a problem. Otherwise, PC is completely fine. I use it for the last 1,5 years and never ever seen this error. Tried Prime95 with avx and passed fine.

I read there was similar problem with minecraft some time ago that was fixed by it's developer.

Does anyone else have this error in windows log?
Thanks.
P.S gog version

[das3erawsdas]

10850K stock fine no wheas. I had wheas on my 9900K oc 5ghz previously on metro exodus normal version. Sometimes very rarely it pops up whea in metro exofus in logs on my 9900K oc to 5ghz.

Its cpu instability.

[jEck]

Originally posted by das3erawsdas:

10850K stock fine no wheas. I had wheas on my 9900K oc 5ghz previously on metro exodus normal version. Sometimes very rarely it pops up whea in metro exofus in logs on my 9900K oc to 5ghz.

Its cpu instability.

Could you please try and reload any given savegame a few times in a row then check for whea again ? thanks.

[das3erawsdas]

Originally posted by jEck:

Originally posted by das3erawsdas:

10850K stock fine no wheas. I had wheas on my 9900K oc 5ghz previously on metro exodus normal version. Sometimes very rarely it pops up whea in metro exofus in logs on my 9900K oc to 5ghz.

Its cpu instability.

Could you please try and reload any given savegame a few times in a row then check for whea again ? thanks.

yeah ok i tried that many times but i can do it again :)

[jEck]

Ok here's the quote I found on overclock.net considering whea parity error in Apex game.

Gsat/Realbench doesn't matter. The old game path generated errors that crashed Intel processors even if you were Gsat/Realbench/Prime95 small FFT AVX stable. The only way to avoid it was to increase CPU voltage extremely high. The problem was, *SOME* users got these errors on *STOCK* 9900K's and 8700K's. Yes, stock.

Ever since it was addressed by Oriostorm and worked around, all these errors stopped unless you were actually unstable.
(that was mentioned in the months old patch notes with even me being given credit for helping: https://www.reddit.com/r/apexlegends/comments/bpxh1f/next_patch_coming_early_next_week_here_are_the/ )
Oriostorm left the "old" path code intact so Intel could actually investigate the cause of the crashes. But other people also reported "Internal Parity Errors" in Battlefield 5 also (usually you would get CPU Cache L0 error or BSOD, right?) and some other games, so it's possible it was just a plain old microcode or internal bug. How much do you want to bet these bugs were caused by mitigation workarounds (even if your OS version was not mitigation aware?). Remember the old first Haswell spectre fixes which generated Internal Parity errors?

If you're too bored, try to test Microcode AE (use the backup bios or something lol) and then use that commandline switch when overclocked.
You also need to monitor HWINFO for WHEA errors while playing. (if the bug is triggered, you will get "CPU Internal Parity Error", or if you're REALLY unstable "CPU translation lookside buffer Error").

So far I finished 2 hours of testing Apex, one at 5.2 ghz 1.335v (HT disabled/LLC Turbo) and one at 5 ghz 1.270v+HT/LLC
Both settings generated Parity errors with the old code path in AE before, but none with BE microcode yet.

I think Exodus has some similar thing going on.
And this is changelog excerpt from Apex:

[PC ONLY] CRASHES SPECIFIC TO INTEL CPUs

We investigated the crash reports from many people who were crashing frequently and found that Intel CPUs sometimes were not executing the instructions properly in one particular function. A common example was an instruction that only reads a register crashed on writing to invalid memory. With the help of many forum users, we found that lowering the clock speed always fixed the crashes, even if the CPU wasn't overclocked or overheating. Thanks everyone, with a big shout out to Falkentyne, TEZZ0FIN0, JorPorCorTTV and MrDakk!

This has been by far the most commonly reported PC crash over the last month or so and we’ve notified Intel about the issue. In the meantime, we’ve put a workaround in this patch to avoid the crashing at your original clock speeds just by changing the instructions used by that one function. Please continue to send your crash logs to our forums so we can analyze and fix any issues you encounter!

So this is the proof that whea parity errors can happen not only in case of instability, but because of software bugs too.

[das3erawsdas]

maybe something with 9900k cpus and this game? On 10850K i dont have that

[jEck]

Yeah, I hope someone else with 9900k will write here.

[Bass Junkie]

increase load line calibration one notch or increase cpu voltage

example = auto = 1.23 v under load
try manual = 1.25 v

whea error = unstable cpu

[jEck]

Yes, this helps, I know. But why should i raise vcore on stock speed? This is certainly a software bug. And don't even start about how this game is sensitive to overclock, etc. It should work on default settings, period. Please read 5th post in this thread.
P.s. btw it requires to set manual around 1.3v with llc high to fight this bug. On STOCK speed. This is insane. Should my cpu be defective so much, I'd never pass p95 avx test on stock voltage.

[DonMcK]

In the past, with Metro Exodus, updating to latest display drivers resulted in WHEA correctable errors. The solution for me was adjust overclock or rollback driver.

[das3erawsdas]

So today i get my first WHEA INTERNAL PARITY ERROR on 10850K stock. LOL!

[jEck]

Lol. Welcome to the club. :))

What I found recently considering this:
https://linustechtips.com/topic/1320357-asus-maximus-13-and-rocket-lake-the-rules-have-changed/


PS - our club grows: https://forums.guru3d.com/threads/whea-internal-parity-error-on-10850k-stock.438138/

[das3erawsdas]

You think its just badly coded game not hardware issue?

[jEck]

I believe so, considering the info I posted above.

[InkoGnito]

The corrected parity error on Intel Haswell and newer CPUs IS NOT an ERROR and will never cause any trouble.
Windows 10 will only report a warning (no Error) and this is correct according to intel specs.

This Warning will only occur when Software is using AVX code.

You can safely ignore this warning.

In the Windows 10 Event Log you will find this STAT:
MciStat 0x9000004000010005

[das3erawsdas]

So if it pops up once for 2 weeks in Metro Exodus nothing to worry about?