Question I keep getting these errors whenever I play a game.

[MrLoopBoop]

I seem to always get these errors whenever I'm playing Cold War and I think they might be related to other games as well since they have the same symptom. Every time I play Cold War, Dead by Daylight, Risk of Rain 2, and a few others, they seem to run perfectly fine for a couple of minutes before crashing.

How do I fix/prevent these errors?

Event Name: BEX64
Event Name: LiveKernelEvent
Event Name: StoreAgentSearchUpdatePackagesFailure1

This is my Build in case:
GPU: RX 580
CPU: Ryzen 5 2600
RAM: 2x8 16Gb Corsair Vengeance LPX
MB: Gigabyte B450M DS3H Micro ATX AM4 Motherboard
CASE: Thermaltake S100 MicroATX Mini Tower
Power Supply: EVGA BR 500 Watt 80+

 

[Colif]

A BEX error is a “Buffer Overflow Exception”. This error is typically raised when Microsoft Windows detects that a program tries to put more data than possible in a region of memory. This is the computer equivalent of overfilling a glass with water until the water spills over

its an application error, in that its a problem with the program. Try uninstalling and reinstalling it again.

it seems odd its a few games but having seen windows error reporting screens, its actually fairly common.

 

[MrLoopBoop]

A BEX error is a “Buffer Overflow Exception”. This error is typically raised when Microsoft Windows detects that a program tries to put more data than possible in a region of memory. This is the computer equivalent of overfilling a glass with water until the water spills over

its an application error, in that its a problem with the program. Try uninstalling and reinstalling it again.

it seems odd its a few games but having seen windows error reporting screens, its actually fairly common.

Didn't seem to work. What makes this more odd is that sometimes in almost a 1/5 chance, the game will run perfectly fine for a good while before coming to a crash 20 or so minutes later.

 

[kerberos_20]

BEX64 is usualy due to some conflicting software installed, like razer synapse conflicting with other apps
...

try running this command in cmd/powershell with admin rights
bcdedit.exe /set {current} nx AlwaysOff
then reboot
then tell if it went away

 

[MrLoopBoop]

BEX64 is usualy due to some conflicting software installed, like razer synapse conflicting with other apps
...

try running this command in cmd/powershell with admin rights
bcdedit.exe /set {current} nx AlwaysOff
then reboot
then tell if it went away

I'll try it, but what does that do exactly?

 

[MrLoopBoop]

Well whatever it did it unfortunately didn't work. Cold War however did manage to run a bit longer than usual, but the crash report still gave me "Event Name: BEX64".

 

[kerberos_20]

can you post what event viewer shows?

 

[MrLoopBoop]

can you post what event viewer shows?

Hoping I did this right. I also included the Cold War crash report.

https://drive.google.com/drive/folders/1UKC8xmdLAJK1xNEdp-CU3WPGT-gxr8YL?usp=sharing

 

[kerberos_20]

Hoping I did this right. I also included the Cold War crash report.

https://drive.google.com/drive/folders/1UKC8xmdLAJK1xNEdp-CU3WPGT-gxr8YL?usp=sharing

eventviewer is wrong, but dxdiag has info needed

what i see is
D3DDRED2 error, which usualy means driver problem (rare for radeon, NVIDIA is plagued by this) or GPU problem

that BEX64 got 0xc000000d stopcode which is access violation (without BSOD its mostly bad driver)

try wiping your radeon drivers with DDU, then install new drivers or try older drivers if you know some time ago they worked

if driver still fails, then it could be hardware issue (GPU), driver can report errors if hardware failing
you can try limiting power profile on your GPU (reducing clock/undervolting) with msi afterburner as GPU faults can be caused by power delivery (PSU)

 

[MrLoopBoop]

I some how resolved my issue. For anyone in the future the views this thread, try all of these methods.

Note: I kinda tried all these methods at once so I honestly don't know which one manage to do it.

Method 1: Using DDU (as posted above) to completely wipe drivers. Afterwards, go to AMD or Nvidia and download the most recent driver. I personally ended up downloading the optional driver instead of the recommended driver since the recommended driver I used ended up to be really buggy for me.

Method 2: Completely turn off the PC (including the PSU) and check your hardware. Make sure everything is plugged in properly. One thing I realized when checking my setup is that my PCI-E cable that was connected to my GPU wasn't plugged in all the way and pushing more in didn't help, so I unplugged it and plugged in another cable and it went all the way in.

Method 3: Update your BIOS to it's latest version. When booting up my pc again I went into the BIOS and took note on the version it was running on. I went to the manufacturer's website and searched the exact model of my motherboard. Turns out, the version of my motherboard was back in 2019 in January. So I ended up updating my BIOS to the most recent version. Also, PLEASE READ EVERYTHING AND KNOW WHAT YOU'RE DOING! I was always told to be careful when updating the BIOS since you could end up bricking the motherboard if not done properly.

Hopefully this can help any future people who is having the same problem.

Thank you @kerberos_20 for the help! I really really really appreciate helping diagnosing the issue.