DirectX DEVICE_HUNG error after 15hrs gameplay - can't launch game

CPU: 12900K

OS: Windows 11 Pro

Memory: 64GB

GPU: Gigabyte GeForce RTX 5090 WINDFORCE OC 32G

**Title: Game crashes immediately on startup with DirectX error after 15 hours of gameplay**

I've been playing continuously for approximately 15 hours, reached level 20, and nearly completed all challenges (only the Engineer's repair challenge remaining).

However, during one session, the game screen suddenly froze and the system became completely unresponsive. I had to force shutdown my PC. After restarting, I encountered the DirectX error shown in the attached screenshot (DirectX function "GetDeviceRemovedReason" failed with DXGI_ERROR_DEVICE_HUNG).

**Current issue:** The game is now completely unplayable. Every time I launch the game, it crashes within a few seconds during shader compilation with the same DirectX error.

**I have attempted the following solutions:**

* Clean reinstalled drivers using DDU, also tried older driver version 577

* Reduced GPU frequency, clock speeds, and power limits

* Modified registry settings for `TdrDdiDelay`, `TdrDelay`, and `TdrLevel`

* Disabled XMP in BIOS

* Updated motherboard BIOS to the latest version

* **Tried both Steam and EA app versions:**

  - Originally played on Steam version (where the issue first occurred)

  - Downloaded and installed fresh copy through EA app

  - EA app version launched successfully once and I was able to enter multiplayer, but crashed after a few minutes of gameplay

  - Now both versions crash identically during shader compilation

I've tried every possible solution I could find, but nothing works. Both game clients crash immediately upon launch during the shader compilation process.

I'm now considering building another PC to test if it's a hardware issue, as I haven't had time to perform a full system backup yet.

**Attachments:**

- DxDiag.txt (full system specifications)

- Screenshot of the DirectX error

The game was working perfectly fine for 15+ hours before this issue occurred. This appears to be a persistent corruption or compatibility issue that started after the system freeze. Any assistance would be greatly appreciated.