RTX 5090 (GB202): Spontaneous GSP heartbeat timeout / Xid 79 "GPU has fallen off the bus" under Vulkan load and idle

System Information:

  • GPU: NVIDIA GeForce RTX 5090 (GB202, PCI 0000:01:00.0)

  • CPU: AMD Ryzen 9 9950X3D (AMD iGPU also present: Radeon RAPHAEL_MENDOCINO)

  • OS: Kubuntu 25.10 (Questing Quokka)

  • Kernel: 6.17.0-20-generic

  • Driver: 595.58.03 (nvidia-open-dkms, installed via .run)

  • Desktop: KDE Plasma 6 / Wayland

  • Display: 1, Connected to RTX 5090 via DisplayPort

Problem Description:

The system experiences hard crashes, the screen gets black while the audio continues for a bit before that also hangs. A hard reboot is the only way to recover from it.
The GPU seems to spontaneously loose connection to the PCIe bus. This occurs both under Vulkan load (Happens both with Proton games via Steam like Warhammer: Darktide but also Native games like Dota 2). It also happens at idle (no game running) with minimal GPU activity. Sometimes it can go hours between crashes and sometimes several crashes can occur within minutes. Other applications running during this was firefox and discord.

The system was completely stable before March 2026 (580.126.09-0ubuntu0.25.10.1). Crashes began after a kernel + driver update around that time.

Kernel log on 590.48.01:

NVRM: Xid (PCI:0000:01:00): 79, GPU has fallen off the bus.
NVRM: GSP RPC timeout

Kernel log on 595.58.03:

NVRM: GPU0 _kgspRpcRecvPoll: GSP RM heartbeat timed out
NVRM: GPU0 _kgspRpcRecvPoll: LibOS heartbeat timed out
NVRM: GPU0 GSP_LOCKDOWN_NOTICE
NVRM: Xid (PCI:0000:01:00): 79, GPU has fallen off the bus.
NVRM: Xid (PCI:0000:01:00): 154, GPU recovery action changed to Node Reboot Required

What I have tried:

  • Upgraded from 590.48.01 to 595.58.03 — problem persists on both

  • PROTON_VKD3D_HEAP=1 launch option — might reduce frequency, hard to tell. Seems to greatly reduce GPU load in Darktide atleast.

  • VKD3D_CONFIG=no_upload_hvv — no effect

  • Disabled Discord hardware acceleration

  • nvidia-powerd disabled (leftover service from 590)

  • Removed old 590 library packages (libnvidia-gl-590:i386, libnvidia-common-590, etc.)

  • Disabled PCIe ASPM (pcie_aspm=off) — no effect

  • GPU power limit set to 400W — no effect

  • Removed ~/.config/kwinoutputconfig.json — addressed KWin crashes but not Xid 79

I’m starting to reach my wits end regarding this. I doubt that Ubuntu 26.04 will be able to fix this issue. Any ideas or tips is greatly appreciated.

nvidia-bug-report.gz (169.1 KB)

Potentially related issue, supposedly an AGESA downgrade solves it - Bug Report & Fix: RTX 5090 — Xid 79 GSP Firmware Crash Under Sustained CUDA Load - #2 by consume

Thanks for this post!. I was having many crashes with RTX5090 and finally system seems stable with pcie_aspm=off and a Bios update for my Gigabyte Z890 GAMING X WIFI7 motherboard. Posted my related observations here

I got the problem. Did you resolve it? Please advise. Thanks.

Posted my same issue.

Adding a data point that reproduces Xid 79 across two independent CUDA software stacks on a non-AMD platform, which may help narrow down whether this is thermal/AGESA-specific or a broader GB202 issue.

System:

  • GPU: RTX 5090 32GB, PCI 0000:02:00
    • Platform: Intel (Arrow Lake-S), HP OMEN 45L prebuilt desktop — not AMD/AGESA
      • OS: Ubuntu, Driver 595.71.05, CUDA 13.2
    • First occurrence: crash during NVFP4/MXFP4 quantization via llm-compressor (SIGSEGV at varying points).
  • Second occurrence (2026-07-22): crash via NVIDIA’s own official nvcr.io/nvidia/tensorrt-llm/release:1.3.0rc21 container running Model Optimizer. The actual NVFP4 PTQ of ibm-granite/granite-4.1-8b (8B params) completed successfully (14.02GB peak VRAM, no crash during the heavy calibration workload itself). The crash occurred ~60 seconds later, after an unrelated TensorRT-LLM verification step had already failed and was tearing down – i.e. during a low-GPU-activity period, not sustained heavy load:

NVRM: Xid (PCI:0000:02:00): 79, GPU has fallen off the bus.

NVRM: Xid (PCI:0000:02:00): 154, GPU recovery action changed from 0x0 (None) to 0x1 (GPU Reset Required)

Only a full reboot recovers it; no in-OS recovery worked.

Since this happened on Intel (not AMD/AGESA) and during light/idle-ish activity rather than sustained load, it seems more consistent with this thread’s “under Vulkan load and idle” pattern than the other thread’s thermal/sustained-load conclusion. Reproducing across two completely independent CUDA stacks (llmcompressor and NVIDIA’s own ModelOpt/TensorRT-LLM) on a different platform suggests this isn’t application- or vendor-BIOS-specific.

nvidia-bug-report.log.gz available if useful.

For me the system stabilized after I replaced my PSU. You could start with replacing the 12VHPWR/12V-2x6 cable first. I had the same crash and tried 3 different 5090s and all have the same symptom. Took me a month to figure out the PSU might be at fault.