F5F Stay Refreshed Software PC Gaming I encounter these issues consistently while playing games.

I encounter these issues consistently while playing games.

I encounter these issues consistently while playing games.

A
AdstaH
Member
76
10-15-2023, 12:13 AM
#1
I notice these issues pop up consistently while playing Cold War and similar games. It looks like they might be linked to other titles as well because the problem appears in multiple games with the same symptoms. Every few minutes I can play without any trouble, but then it crashes abruptly. What steps should I take to resolve or avoid these errors?
A
AdstaH
10-15-2023, 12:13 AM #1

I notice these issues pop up consistently while playing Cold War and similar games. It looks like they might be linked to other titles as well because the problem appears in multiple games with the same symptoms. Every few minutes I can play without any trouble, but then it crashes abruptly. What steps should I take to resolve or avoid these errors?

S
STEGGIESAURUS
Junior Member
3
10-16-2023, 05:43 AM
#2
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.
S
STEGGIESAURUS
10-16-2023, 05:43 AM #2

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.

L
226
10-16-2023, 06:05 AM
#3
It didn't seem to work. What's unusual is that occasionally, with about a one in five chance, the game runs smoothly for a while before crashing after around 20 minutes.
L
LuLuPlaysCraft
10-16-2023, 06:05 AM #3

It didn't seem to work. What's unusual is that occasionally, with about a one in five chance, the game runs smoothly for a while before crashing after around 20 minutes.

P
195
10-22-2023, 08:30 PM
#4
BEX64 often happens because of incompatible software, such as razer synapse interfering with other applications.
...
execute the command via cmd or powershell with administrative privileges
use bcdedit.exe /set {current} nx AlwaysOff
follow up with a reboot
check whether the issue has been resolved
P
PARAN0ID_M3DIC
10-22-2023, 08:30 PM #4

BEX64 often happens because of incompatible software, such as razer synapse interfering with other applications.
...
execute the command via cmd or powershell with administrative privileges
use bcdedit.exe /set {current} nx AlwaysOff
follow up with a reboot
check whether the issue has been resolved

T
theopixel37
Junior Member
34
10-24-2023, 01:55 PM
#5
I'll attempt it, but could you clarify what you mean by "what does that do exactly?"
T
theopixel37
10-24-2023, 01:55 PM #5

I'll attempt it, but could you clarify what you mean by "what does that do exactly?"

K
Karissabebe
Junior Member
4
10-24-2023, 02:37 PM
#6
It seems the attempt didn't succeed, though the Cold War extended beyond expectations. The crash log still displayed "Event Name: BEX64".
K
Karissabebe
10-24-2023, 02:37 PM #6

It seems the attempt didn't succeed, though the Cold War extended beyond expectations. The crash log still displayed "Event Name: BEX64".

Z
ZarkLR
Member
201
11-09-2023, 05:45 PM
#7
Yes, I can tell you what an event viewer displays.
Z
ZarkLR
11-09-2023, 05:45 PM #7

Yes, I can tell you what an event viewer displays.

N
noeljr34
Junior Member
5
11-09-2023, 08:18 PM
#8
I'm also adding the Cold War crash report.
N
noeljr34
11-09-2023, 08:18 PM #8

I'm also adding the Cold War crash report.

T
TommyTheLommy
Posting Freak
846
11-10-2023, 01:11 PM
#9
eventviewer is incorrect, but dxdiag provides the necessary information.
I notice a D3DDRED2 error, often indicating a driver or GPU issue—rare for Radeon, but NVIDIA sometimes faces this.
BEX64 received a 0xc000000d stopcode, suggesting an access violation, usually a bad driver without a BSOD.
Consider clearing your Radeon drivers via DDU, then reinstalling or using older versions if they previously worked.
If the problem persists, it may point to a hardware fault (GPU), and the driver can log errors if the hardware is failing.
You might also try adjusting the power profile on your GPU using MSI afterburner, as power delivery issues can cause such faults.
T
TommyTheLommy
11-10-2023, 01:11 PM #9

eventviewer is incorrect, but dxdiag provides the necessary information.
I notice a D3DDRED2 error, often indicating a driver or GPU issue—rare for Radeon, but NVIDIA sometimes faces this.
BEX64 received a 0xc000000d stopcode, suggesting an access violation, usually a bad driver without a BSOD.
Consider clearing your Radeon drivers via DDU, then reinstalling or using older versions if they previously worked.
If the problem persists, it may point to a hardware fault (GPU), and the driver can log errors if the hardware is failing.
You might also try adjusting the power profile on your GPU using MSI afterburner, as power delivery issues can cause such faults.

P
ProSkipperz
Member
129
11-14-2023, 02:39 AM
#10
I managed to fix my issue. For anyone facing similar problems in the future, try these approaches.
Note: I attempted all these steps simultaneously, so it's hard to say which one worked best.
Approach 1: Use DDU (as mentioned earlier) to reset drivers completely. Then visit AMD or Nvidia websites and install the latest driver. I chose the optional version instead of the recommended one because the latter was quite unstable for me.
Approach 2: Power off the PC entirely, including the power supply unit, and inspect your hardware. Verify all connections are secure. During my setup check, I noticed my PCI-E cable connected to the GPU wasn't fully inserted and adding more didn't improve the situation, so I replaced it with a different one.
Approach 3: Update your BIOS to the newest release. After restarting my computer, I accessed the BIOS settings and checked the current version. I visited the manufacturer's site and found my motherboard model dated back to 2019. Therefore, I updated the BIOS to the latest available version. Also, please read all instructions carefully before proceeding!
I was always advised to handle BIOS updates with caution, as improper changes could damage your motherboard.
Hope this assists anyone encountering the same issue.
Thank you
@kerberos_20
P
ProSkipperz
11-14-2023, 02:39 AM #10

I managed to fix my issue. For anyone facing similar problems in the future, try these approaches.
Note: I attempted all these steps simultaneously, so it's hard to say which one worked best.
Approach 1: Use DDU (as mentioned earlier) to reset drivers completely. Then visit AMD or Nvidia websites and install the latest driver. I chose the optional version instead of the recommended one because the latter was quite unstable for me.
Approach 2: Power off the PC entirely, including the power supply unit, and inspect your hardware. Verify all connections are secure. During my setup check, I noticed my PCI-E cable connected to the GPU wasn't fully inserted and adding more didn't improve the situation, so I replaced it with a different one.
Approach 3: Update your BIOS to the newest release. After restarting my computer, I accessed the BIOS settings and checked the current version. I visited the manufacturer's site and found my motherboard model dated back to 2019. Therefore, I updated the BIOS to the latest available version. Also, please read all instructions carefully before proceeding!
I was always advised to handle BIOS updates with caution, as improper changes could damage your motherboard.
Hope this assists anyone encountering the same issue.
Thank you
@kerberos_20