Crashes with error message

Hello there,
My game crashes a lot since at least 4 to 5 days. I had the occasional crash here and there before, but it was nowhere near as bad as it is.
I got 6 crashes and tried to fix the problem by searching.
CPU is i7-14700K
I tried

  • Updating Nvidia Drivers
  • Using repair tool
  • Reinstalling Overwatch
  • Checking temps (CPU was hot 95 degrees)
  • Tweaking cpu bios voltage etc, until it was stable.

I reverted most of the Bios changes when it crashed again in training, by doing it gradually.
I kept XMP enabled, disabled enhanced turbo for the CPU, and there was a line called CPU Cooler Tuning, which I changed to Msi performance settings, instead of Intel Default. CPU is running nicely, temps are all good, it doesn’t go over 85 degrees in games now.
I did a cinebench R24, Intel cpu diagnostic tool, all passed.

The rest of the settings are default mobo settings, and most are “Intel default settings” or “Auto”.

I didn’t crash for 10 to 15 mins and decided to give it a go in game, which crashed after some minutes. Resulting in a constant cycle of reconnecting, playing 2-3 min and crashing again, and now I’m banned from the season …

I can provide you with the error logs from the most recent crash, to the one I got just before I tried to tweak all the things.

First crash of last session : (With “Stable tweaks” and updated Nvidia Driver, same error code)
https://pastebin.com/XQCAahdg

And last crash of last session : (Which has a different error code)
https://pastebin.com/Q5qN9UmB

I checked all the error codes from all the crashes I got, and they are the same, but not the last one.

I use Windows Defender as my antivirus.

Thank you for your help.

Hello
Can you please also post a DXDiag?

Sure, here is the DXDiag :

https://pastebin.com/9Sf78UBu

Hi DarkSeby,

The error EXCEPTION_ACCESS_VIOLATION is present in both crash reports, reading from 0xffffffffffffffff and 0x00000000000101b1.

These errors, coupled with the Windows Error Reporting section in your DxDiag, confirm the source of instability is your hardware, not the game client.

The WER section logs multiple BlueScreen events with bugcheck codes such as 0xA and 0x1E. These are critical kernel-level faults indicative of an unstable CPU overclock, or RAM instability, or incorrect voltage settings.

Your initial report of CPU temperatures reaching 95C confirms the system was operating outside of stable thermal and voltage parameters. The BIOS modifications you performed were attempts to treat a symptom. The underlying instability remains.

Let’s try and establish a stable baseline.

Restore BIOS Defaults.

  • Enter the motherboard BIOS.
  • Execute the “Load Optimized Defaults” command.
  • Save changes and exit.

Test Overwatch. If crashes cease, the instability was a direct result of your manual BIOS configuration, including XMP and CPU settings.

If the system is stable at default settings, re-introduce changes one at a time.

  • Re-enter BIOS.
  • Enable the XMP profile. Leave all other settings at their default values.
  • Save, exit, and test Overwatch. If crashes recur, the XMP profile is unstable. This is common.

If XMP is unstable, re-enter BIOS. Keep XMP enabled, but manually reduce the “DRAM Frequency” to a lower value, such as 6200MHz or 6000MHz, and test again.

Upgrade your BIOS

Check the support page for your MSI Z790 GAMING PLUS WIFI (MS-7E06) motherboard. If a BIOS version newer than H.80 is available, update it. NEVER DOWNLOAD DRIVERS/FIRMWARE/BIOS FROM GOOGLE. Go directly to the manufacturer website and search for your model number.

If none of the above works (or even if it does) I recommend anyone experiencing hardware issues run some stress/memory tests:

Test your memory for as LONG as possible with Memtest86.

  • You will need a USB stick.
  • Download Memtest from https://www.memtest86.com/downloads/memtest86-usb.zip
  • Run the imageUSB.exe tool from the ZIP file with your USB plugged in (THIS WILL ERASE ALL DATA ON THE USB STICK).
  • Boot from it and let it run as long as possible. 12 hours minimum.

If this detects anything, do not continue. You have faulty RAM.

Stress test your system.

  • Download Furmark https://geeks3d.com/furmark/
  • Download Prime95 https://download.mersenne.ca/gimps/v30/30.19/p95v3019b20.win64.zip
  • Download HWiNFO64 https://www.hwinfo.com/files/hwi_828.zip
  • Run them all at once. Monitor your systems temperatures, and watch for any crashes.

Good luck!

Though, I had a crash earlier on overwatch after I reverted the changes to default and cleaning my case, my front panel was loaded of dust. Pc was built 6 month ago. I underestimated the amount of dust stacking in those fans … It’s on my floor and not my desk, no space for it.
I just updated my Mobo to the beta version of the patch, which is H91, with microcode 0X12F, and so far, it seems ok ?
I could do a 1 hour session, without crashing on customs, then QP.

To clarify for the BSOD, it happened with Vanguard, the anti cheat from Riot. As it runs in the background, I experienced several blue screens on overwatch with vgk.sys errors.
Also happened later on LoL, and contacted their support about it, and following their article changed some parameters from the mobo.
It did alleviate some problems, but I guess worsened overwatch condition with my hardware, even with Vanguard disabled, which did not bluescreen but just returned to desk with the error message, and it degraded over the next days.
I just did the session without crashing with Vanguard running in the background, so far so good.

I did experience some small freezes in ow, but that’s really manageable. Temp spiked at 100 on some cores, but only for 1s, dropping to 85 after and dropping further to 70.
Idling at 40 degrees, and in game it’s around 65 - 70.

Thank you so much for your time and patience, and helping me !
I was reluctant to updating the bios because it was a beta patch … It was the push I needed.

I’ll update when I do the memtest and the rest, and / or if I crash again over the next days (which is hopefully not happening)

Thanks again !

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.