FREESTYLEkill3r please post a DxDiag.txt report so we can see the crash log at the bottom of the report.
https://help.ea.com/en/articles/technical-issues/dxdiag-information-pc/
If I don't reply to your post then personal message me. Sometimes the forum fails to notify me when someone replies.
Here is my DxDiag.
I've been having this problem almost constantly.
It's random. Sometimes happens during the opening splash screen, sometimes after hours of gameplay, sometimes while working in the menu / loadout screen. There's no logic to when it happens. I've posted a screenshot of the actual message elsewhere in these support forums.
I have tried:
Booting safe mode, running DDU, updating drivers.
Booting safe mode, running DDU, removing everything including PhysX, etc - and started over.
Tried both with and without the nVidia app, and with and without overlays from both the EA App and from NVidia.
I keep my BIOS updated from the manufacturer.
I've even tried reinstalling Windows.
It's always the same. After a reboot, it comes up and actually says that my laptop GPU (4060) has been removed, then after that it just says that the device has hung.
It's gotten worse with the Winter release. I'm not including the stupid menu issue, as that's a careless issue from DICE.
This has been a problem in both 2142 and now BF6. This is the ONLY game I have this issue with. Otherwise, my system is rock solid and running nicely for a two year old gaming laptop.
I don't know by your handle if you're EA or not, but there is absolutely no excuse for EA to push out releases of AAA titles with these types of issues. Likely, as much as I have loved playing the Battlefield franchise for the last 20+ years, this is going to be my last purchase from EA. I've had it.
Magikf1ngers this is the error at the bottom of your DxDiag.txt
---------------
Diagnostics
---------------
Windows Error Reporting:
+++ WER0 +++:
Fault bucket 1308462448910609720, type 5
Event Name: BEX
Response: Not available
Cab Id: 0
Problem signature:
P1: IGOProxy32.exe
P2: 0.0.0.0
P3: 65f86e25
P4: d3d11.dll_unloaded
P5: 10.0.26100.7309
P6: bc6c3f94
P7: 0006fc40
P8: c0000005
P9: 00000008
P10:
The "BEX" event name typically refers to a Buffer Overflow Exception, a common Windows error where a program tries to write more data into a memory buffer than it can hold, causing it to crash, often related to Windows' Data Execution Prevention (DEP) security feature. This event signals a program failure, common in applications like Microsoft Office, or games, and can be resolved by adjusting DEP settings, updating drivers, running as administrator, or reinstalling software.
What BEX Means
BEX: Buffer Overflow Exception.
Problem: A program tries to overload a memory space, and Windows blocks it for security.
Common Scenarios
Launching games or graphics tests.
Opening Microsoft Office documents.
How to Fix It (General Steps)
Check DEP Settings: Add the problematic application's executable file to the list of programs that DEP allows to run.
Run as Administrator: Right-click the program and select "Run as administrator".
Update/Reinstall: Ensure your application, drivers, and Windows are updated; try reinstalling the software.
Check Antivirus: Temporarily disable your antivirus, as it can sometimes interfere.System Restore: Roll back your system to a point before the error started.
Disable Add-ins: For Office programs, disable COM add-ins in safe mode to find the culprit.
The above ^ is from Google Gemini AI. The below text is from me OskooI_007 .
C:\Program Files\Electronic Arts\EA Desktop\EA Desktop\IGOProxy32.exe appears to be part of the EA app.
Try adding IGOProxy32.exe to Windows' Data Execution Prevention (DEP) exclusion list, or try disabling DEP completely.
Another thing to try is disabling memory XMP overclocking or manually lowering the memory frequency in motherboard BIOS settings. The crash might be due to memory errors and unstable memory.
If I don't reply to your post then personal message me. Sometimes the forum fails to notify me when someone replies.
Tbh... since the winter update I have not got a single crash (though I'm sure they'll start again.. hopefully not). Though this update has been riddled with so many other bugs. If I do get another crash I will post the crash log report from DxDiag.txt here
Just had my first crash with this error since Winter Update sadly... just happened randomly this morning when trying to start matchmaking on first game of the day. See attached for dxdiag.txt report
FREESTYLEkill3r this is the most recent error code at the bottom of your DxDiag.txt .
---------------
Diagnostics
---------------
Windows Error Reporting:
+++ WER0 +++:
Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0
Problem signature:
P1: 9f
P2: 3
P3: ffff80893c252120
P4: fffffb891676f580
P5: ffff80893c2b3280
P6: 10_0_26200
P7: 0_0
P8: 768_1
P9:
P10:
Here's what Google Gemini AI says.
This WER0 BlueScreen error (P1: 9f) indicates a critical system crash, likely due to a bad driver, faulty hardware (like RAM/disk), overheating, or a problematic update/software conflict, with the 10_0_26200 pointing to a newer Windows build (likely Windows 11 Insider/Preview).
To fix it, you'll need to update drivers (especially graphics/network), run sfc /scannow & DISM, check for Windows Updates, potentially remove new hardware/software, and look for overheating.
OskooI_007 recommends running HCI MemTest to check for memory errors.
Download HCI MemTest and see if there's any memory errors.
https://hcidesign.com/memtest/
Open Windows Task Manager and check how much available memory there is.
Open multiple MemTest windows. Have each MemTest window scan 3000MB of memory.
Never let the available memory in Windows Task Manager reach 0. Always leave at least 1GB of available memory because if it reaches 0 then MemTest will start testing the Windows page file on the SSD.
If I don't reply to your post then personal message me. Sometimes the forum fails to notify me when someone replies.
I'm not actually getting a blue screen during these crashes... I just crash to desktop so not sure if it's actually relative to what's going on. I did have a couple blue screens a few months back so not sure if those are old. But when this was happening I did run /sfc scannow and repair and found zero errors to fix. I also ran Windows Memory Diagnostic tool and found zero errors as well. So it could be the version of Windows I'm on? Not positive... I hate Windows 11 and only reason I'm using it is because of them stopping support for Windows 10 (which I wasn't the biggest fan of either if we're being honest... haven't enjoyed Windows since Windows 7).
Anyways... stopped playing the game for about 2 weeks and decided to hop on tonight. Tried checking out the new BF Pro battlepass challenges... device_hung and crashed to desktop. This is the first time I've crashed just browsing the main menu and not when I'm actively joining a server. I took a break from the game because I was tired of dealing with all the issues and lmao first time launching and immediately hit with that just leaves such a bad taste for the consumer.
Have not been able to play a single game today without this crash out of nowhere. I've tried sfc /scannow, restorehealth and then rescanning and have found zero issues. Restarted PC. Still crashing as soon as I start matchmaking. Rescanning steam file integrity right now but I've done this multiple times in the past without it fixing the crash. Like I said it's so weird when this crash decides to happen, it feels so random. Some days I can play perfect. I was able to play at least 5 days after winter update with zero issues. Now the issue is non stop and cannot play.
