Hi soundofmind,
I went through your nvidia-bug-report.log. Here’s what the data shows.
Three crashes, same channel, across two separate boots
From your journalctl sections in the bug report:
Boot -2 (NVreg_EnableResizableBar=1):
06:51:32 — Xid 109, pid=6855, channel 0x00000014, Info 0x38016
Boot -1 (NVreg_EnableGpuFirmware=0):
07:04:49 — Xid 109, pid=6401, channel 0x00000014, Info 0x38016
07:13:19 — Xid 109, pid=20829, channel 0x00000014, Info 0x3c016
Channel 0x00000014 is allocated every time the game initializes regardless of what kernel parameters you boot with. Same channel across reboots with different parameters rules out transient state — the crash is deterministic and structural.
NVreg_EnableGpuFirmware=0 is silently ignored on GB202
Your boot -1 cmdline has nvidia.NVreg_EnableGpuFirmware=0. Your bug report header shows GSP firmware version 98.02.2E.00.D4 loaded and active regardless. On Blackwell (GB202), GSP is mandatory — the flag is accepted by the kernel module but has no effect. The standard pre-Blackwell workaround for Xid 109 (falling back to RM-managed context scheduling) is not available on your hardware.
No precursor warnings before the Xid fires
The kernel log between drm init and the first Xid 109 is completely clean — no GSP RPC timeout, no PBDMA fault, no memory error. The watchdog fires silently with no logged precursor.
PCIe link negotiated at Gen4 x16, not Gen5
From your log:
0b:00.0: 252.048 Gb/s available, limited by 16.0 GT/s PCIe x16
capable of 504.112 Gb/s with 32.0 GT/s PCIe x16
GB202 is rated for PCIe 5.0 x16. Your slot is running at PCIe 4.0 x16. Platform/BIOS issue, not a driver bug, but worth noting.
MSI-X interrupt vector distribution
From /proc/interrupts in your report:
IRQ 191: 21,636 counts — nvidia MSI-X vector 0
IRQ 192: 0 counts — nvidia MSI-X vector 1
IRQ 193: 167,171 counts — nvidia MSI-X vector 2
IRQs 194–198: 0 counts — nvidia MSI-X vectors 3–7
6 of 8 allocated MSI-X vectors are taking zero interrupts. Flagging for NVIDIA engineers.
Post-crash G-SYNC failures
After the Xid 109 events your log shows:
07:20:40 — nvidia-modeset: WARNING: GPU:0: ROG PG279Q (DP-2): Failed to initialize G-SYNC
07:21:40 — nvidia-modeset: WARNING: GPU:0: ROG PG279Q (DP-2): Failed to initialize G-SYNC
GPU recovered enough to keep the display alive but the display engine did not fully reinitialize after the reset.
NVIDIA has this filed internally
This exact issue — Crimson Desert softlock on Blackwell with 595.58.03 — is confirmed Blackwell-only by multiple reporters and is tracked internally by NVIDIA as bug 6017526, confirmed by NVIDIA staff in the 595 release feedback thread:
595 release feedback & discussion (posts 227–228)
A second RTX 5090 reporter (seldomridgej) confirmed the identical symptom — freeze on loading screen after pressing play or new game, Proton version irrelevant:
595 release feedback & discussion (post 209)