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.
Here's the problem I have with this.
I get the same errors, btw - and I've got 30 years of IT experience, and professional system building experience under my belt.
The problem is two-fold:
1. This is getting off into the weeds. As someone who's done these tests many times, and with my current build, I've done them all as well, they don't generally come back with any serious issues. It's a placebo thing, like when it was always "Defrag your disk" type answers.
2. THIS. SHOULD. NOT. BE. HAPPENING. Not with a AAA title in a franchise that's literally been around for more than two decades. This is irresponsible of EA to allow this kind of thing to be published when so many are having these stupid DirectX 12 errors.
I only have this problem with Battlefield 2042 and now 6. I play a ton of games on Steam - Cyberpunk 2077, Hell Let Loose, as well as other games like War Thunder, MS Flight Sim, etc. I don't have any trouble with those games. Specifically, it's EA games,
I have been a customer of Electronic Arts since the 1990s. I've watched game quality fluctuate for all of those years until about when BF1 came out, and it's been downhill since then. Quality, stability, etc - all have taken a giant crap on the fans of this franchise and other EA franchises (looking directly at the abandonment of Titanfall.)
This much work should not be put on the consumer to fix. This is a systemic EA issue. I can't even put blame on Microsoft, for the simple reason that other games work flawlessly.
EA / DICE needs to figure out why this is happening. In my own personal case, I've done the hardware checks. I've installed additional RAM. I've reinstalled Windows, installed drivers, reinstalled the game, turned off in-game overlays for everyone involved, and done everything I can think of from my 30 years of experience.
I even had BF6 to where I could play it mostly reliably up until Season 2 was released yesterday, and now at *BEST* I can get into a match and, if I'm lucky, get through one objective before i get this stupid crash.
I've already cancelled my EA subscription. Unfortunately, I bought BF6, so that's money I won't get back. But, that said, it makes me sad after playing this franchise for 20+ years, I will not be buying the next version. I will not be giving EA one thin dime ever again. (or as the game prices go up, hundreds of dimes) I will also advise people to stay away from EA.
At least until EA not only fixes this specific issue with BF6, but releases stable AAA games for several versions in a row. Then I might consider coming back. There's just too much good stuff out there that's not from EA.
