Skip to main content
Toro777
Participant
July 27, 2026
Question

Crashes and loss of bitrate with Quest Pro

Hi all,

I have been experiencing loss of performance and crashes on my Quest Pro. After certain amount of time, it goes from picture perfect to heavy pixelation / posterization (looks like the image has dropped to a very low colour depth, almost "4-bit").

Help is much appreciated

Symptoms:

  • The Oculus Mirror window on the PC remains perfectly normal while the headset image is corrupted.
  • The issue occurs in both Falcon BMS and DCS World.
  • The games eventually crash after the display corruption starts.
  • Windows Event Viewer logs an NVIDIA nvlddmkm Event ID 153 around the time of the crash.
  • I've upgraded to the latest PTC update and the issue still occurs.
  • Temperature on the GPU is high when this occurs, but well within limits (GPU Core at 70 - 75degC and hotspot between 90 - 95degC )

 

Tested:

  • Latest NVIDIA driver
  • Latest Quest firmware
  • Latest Meta Link software
  • Meta Link wired with fast USB cable (tested in Meta) and Virtual Desktop
  • Fixed bitrate (300 Mbps) and variable bitrate
  • Lowered bitrate to 100Mbps
  • GPU undervolted and also completely stock
  • All GPU drivers updated

 

System:

  • Quest Pro
  • RTX 3090 (latest NVIDIA driver)
  • Ryzen 9800X3D
  • Windows 11 installed in M2
  • 32gb RAM
  • SSD with enough disk space.

10 replies

Toro777Author
Participant
July 27, 2026

Now with two pictures that probably explain it better :)

steve40
steve40
Honored Contributor
July 28, 2026

Try downgrading your nVidia GPU driver to v.591.74 or v591.86.

    Toro777Author
    Participant
    July 28, 2026

    Thanks so much! I've rolled back to 581.94 as there was a reddit post  two months ago that suggested that it  was stable and so far no issues! Will report back after more thorough stress testing tonight. Thanks again :)

    • Series 30 (30x0) / 20 (20x0) / 16 (16x0) Geforce GPU owners:

      • Drivers 581.94, 577.00, 576.88, 576.80, 566.36, 561.09
      • NOTEs section [1] has other drivers worth considering e.g. 596.36, 595.79, 591.74 but note potential issues

    • Other drivers worth considering albeit be aware of potential compatibility [4] and/or edge case stability [2][3] issues: 580.97[8] 581.08[8] 581.42[8] 581.47[7][8] 591.67[4][7] 591.74[4] 595.76[4] 595.79[4] 595.97[2][4] OR 596.49[2][4] 596.36[2][4] . Drivers highlighted in BOLD aren't impacted by disclosed security vulnerabilities at the date/time of this comment [9]
      Terms & ConditionsAccessibility statement