BF6 crashing and causing PC to restart

When I click on the 'How to troubleshoot graphics issues on PC' link, I am only taken to the DXDiag explanation. I had no issues during the beta and this issue started after the release.

-I still have the same issue after the latest patch. After installing the patch, I was able to play a whole round of the new BR mode, but after my first crash, which occurred about an hour into the game, the PC crashed several times when I started new rounds. 

-I don't receive any error codes. The PC shuts down without displaying any messages, and I have to restart it manually.

-I use the EA App.

Can't even play a redsec match all the way through.

No errors, just darkness
EA App

Didnt have any issues with the beta, not a single crash. Now i cant even load the game for more than 5 minutes without it restarting my PC.

So I solved the issue on my machine.  I had to put my PSU in single rail mode.  It's a Corsair 1500i.  Apparently the 5090 was tripping the current protection, usually when loading into the next round, but sometimes while in game too.

I haven't crashed out since making the change in iCue.  Was hard to track down since nothing is logged when you trip the current protection. 

Symptom (PC was instantly shutting down), didn't seem like it should be a PSU issue since I was well under it's rating, but it was.

I'll try tommorow. I' ve been trying stuf for the last 2 hours and I'm out of pacience

Hi

My fix for this problem  is a bios roll back from bios 17 to  bios 17k for my Z890-AORUS-MASTER..

LInk: Z890 AORUS MASTER https://www.aorus.com/motherboards/z890-aorus-master/Support

I have Report the problem to Gigabyte (via support ticket)

I hope this can help others who experience the same problem

My symptoms:

When I play Battlefield 6 and have BIOS version 17 installed, the PC crashes — the game freezes for a few seconds before the computer restarts.

In the event log, I get the following error:

Error check: 0x00020001 (0x0000000000000011, 0x0000000000225322, 0x0000000000001005, 0xffffe70002a05a90).

Key points from the windows dump file

BugCheck: HYPERVISOR_ERROR (20001)

→ The Windows hypervisor (Hyper-V / VBS) crashed.

Faulting process: bf6.exe

→ The crash occurred while playing Battlefield 6.

Stack trace and module: eaanticheat.sys

→ The game’s anticheat driver is involved, but the actual error is at the hypervisor level.

Note: WinDbg reports *** WARNING: Unable to verify timestamp for eaanticheat.sys. This means the module is signed but the timestamp could not be verified — normal for some anticheat drivers.

Main cause: BIOS version 17 changes CPU virtualization/microcode, which causes the Hyper-V / hypervisor layer to crash when the game and anticheat driver attempt to use virtualization features.

Confirmation: On BIOS 17k, everything works stable → BIOS 17 introduces the issue.

🔹 What the stack trace shows

STACK_TEXT:  

... eaanticheat+0x34b05afThe crash is triggered in eaanticheat.sys, but it’s really the hypervisor failing.

The hypervisor relies on CPU features like VT-x / VMX, and when BIOS misconfigures or changes microcode, it results in a fatal crash under load.

🔹 Hypervisor flags from the dump

Hypervisor is active (Hypervisor.Flags.AnyHypervisorPresent = 1)

Nested virtualization = 0 → no nested VM running

VSM and VP Assist Page = 1 → features used by VBS and Memory Integrity

Core scheduler and Dynamic CPU Disabled = 1 → changes in how CPU cores are managed

This shows that BIOS 17 alters how Hyper-V interacts with the CPU → crash under load.

🔹 Conclusion

The problem lies in BIOS 17, not in RAM, GPU, or Battlefield 6 itself.

eaanticheat.sys is “blamed” only because it uses virtualization features that trigger the hypervisor crash.

Since BIOS 17k works, it is the safe version until Gigabyte releases an updated BIOS fixing hypervisor compatibility

Uppdate:24.11.2025

The crash was resolved completely by uninstalling AI Snatch from Gigabyte Control Center.

No BIOS downgrade or disabling of VT-d was required.
The system now runs:

• BIOS F17
• VT-d enabled
• Secure Boot enabled
• Battlefield 6
• No BSODs, no driver loops

Exactly as expected.

Recommended Final Fix

Do not install AI Snatch on BIOS F17
until Gigabyte updates the module or BIOS to fix the VT-d initialization conflict.

Windows 11 Pro 64-bit 
Case: Fractal Design North XL TG Dark - Charcoal Black
Motherboard: Z890 AORUS MASTER  Intel  FCLGA1851 socket
CPU:Intel®  Intel Core Ultra 9 285K Arrow Lake-S
CPU Cooling :NZXT Kraken Elite V2 360 (2024)
GPU: Gigabyte GeForce RTX 4090  GAMING OC 24GB 
RAM: Kingston FURY Renegade DDR5-8400 - 48GB - CUDIMM for Intel - CL40  
PSU: Corsair HXi Series HX1500i 1500W, ATX 3.0, 80 PLUS Platinum, Fully Modular (2022)

Before the season 1 update, 9/10 times when I would play the game on Steam, my PC would BSOD, and usually throw an error like: “IRQL_NOT_LESS_OR_EQUAL (0xA), What failed: ntoskrnl.exe”, which also occurred in the same manner when I played the Beta back in August. When I was getting the error then it would usually happen after a random amount of time playing the game, but I could usually get 1-2 hours of playtime in occasionally. However, now after the season one update my PC BSODs instantly when trying to boot up the game. I can't even get into the menu anymore its so bad. Furthermore the BSOD error code is now showing: SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. After checking several Windows minidump files each always points to the same thing, either "eaanticheat.sys" for the old IRQL_NOT_LESS_OR_EQUAL error or "bf6.exe" for the new SYSTEM_SERVICE_EXCEPTION (3b) error

Sorry for the wrong link for graphics troubleshooting. You can find the correct one here. Try that and let me know what happens.

Please try the graphics troubleshooting here. Also, make sure your drivers are up to date. 

I have done everything and still have crash... do you have a true solution or a patch to fix the game ?