New to the forums? Click here to read the "How To" Guide.

Developer? Click here to go to the Developer Forums.

BSOD in VR after NVIDIA 451.48 update

BrandonyubyBrandonyuby Posts: 4
NerveGear

Has any one else experienced Blue Screen of Death after the latest 451.48 Driver update? It happened twice today for me after playing 20 minutes of Beat Saber. My oculus driver is up to date.
And for some reason it only happens in VR. I run a stress test on both my GPU and CPU for an hour and everything seems fine. Also tried using steam VR with Oculus and same thing happened. Blue screen after 10-20 minutes of gaming.

I’m using Oculus rift S with RTX 2080ti and Threadripper 2950X.

----- I downgraded to the 446.14 Driver and no more BSOD, but still have some heavy frame stutter often which I did not experience before.  Again stress testing the GPU shows no issue.  Still getting more than 90 FPS with 3DMark and Superposition under VR benchmark.   Could it be my Oculus Rift S hardware issue? 

Answers

  • TomCgcmfcTomCgcmfc Posts: 2,261 Valuable Player
    Ya, nvidia 451.48 driver is junk, esp. combined with the latest win10 2004 update imho.  I rolled back to 442.59 and all's well.  I think this driver was the last of good performing, stable drivers, at least for me.

    Custom built gaming desktop; i9 9900k (water cooled) oc to 5ghz, gtx 1080 ti, 32 gb 3000hz ram, 1 tb ssd, 4 tb hdd.  Asus  ROG Maximus xi hero wifi mb, StarTech 4 port/4 controller sata powered usb3.0 pcie card, PCI-E PCI Express to USB 3.1 Gen 2 card, Asus VG248QE 1080p 144hz gaming monitor, Oculus Rift cv1 w/2x sensors, Vive Pro w/2.0 base stations/controllers, Quest w/Link and VD wireless (good/close 5Ghz wifi and PC with Ethernet cable to my Router).

  • thekobkthekobk Posts: 4
    NerveGear
    I had this issue recently,  my cv1 was switching between usb 3 and usb 2 by itself.  I plugged my cv1 into usb 2 port and the issue is gone. I think this was caused by the quest update code breaking cv1 code. 
  • BrandonyubyBrandonyuby Posts: 4
    NerveGear
    TomCgcmfc said:
    Ya, nvidia 451.48 driver is junk, esp. combined with the latest win10 2004 update imho.  I rolled back to 442.59 and all's well.  I think this driver was the last of good performing, stable drivers, at least for me.
    I tried both 442.59 and 442.92 studio driver and both worked the same as 446.14, some heavy frame stutter still occur.
  • TomCgcmfcTomCgcmfc Posts: 2,261 Valuable Player
    TomCgcmfc said:
    Ya, nvidia 451.48 driver is junk, esp. combined with the latest win10 2004 update imho.  I rolled back to 442.59 and all's well.  I think this driver was the last of good performing, stable drivers, at least for me.
    I tried both 442.59 and 442.92 studio driver and both worked the same as 446.14, some heavy frame stutter still occur.
    Helps to use DDU in Safe mode when rolling back nvidia drivers imho.

    Custom built gaming desktop; i9 9900k (water cooled) oc to 5ghz, gtx 1080 ti, 32 gb 3000hz ram, 1 tb ssd, 4 tb hdd.  Asus  ROG Maximus xi hero wifi mb, StarTech 4 port/4 controller sata powered usb3.0 pcie card, PCI-E PCI Express to USB 3.1 Gen 2 card, Asus VG248QE 1080p 144hz gaming monitor, Oculus Rift cv1 w/2x sensors, Vive Pro w/2.0 base stations/controllers, Quest w/Link and VD wireless (good/close 5Ghz wifi and PC with Ethernet cable to my Router).

  • BrandonyubyBrandonyuby Posts: 4
    NerveGear
    TomCgcmfc said:
    TomCgcmfc said:
    Ya, nvidia 451.48 driver is junk, esp. combined with the latest win10 2004 update imho.  I rolled back to 442.59 and all's well.  I think this driver was the last of good performing, stable drivers, at least for me.
    I tried both 442.59 and 442.92 studio driver and both worked the same as 446.14, some heavy frame stutter still occur.
    Helps to use DDU in Safe mode when rolling back nvidia drivers imho.
    That is what I did.
  • FelicityCFelicityC Posts: 147
    Art3mis
    441.41 is better than all those drivers tbh
    8700k @ 5ghz allcore, 2070 Super, 3200mhz 2x8gb memory @ CL16 1T, 1tb wd sn750, msi z370 gaming plus, overheating from OVRserver_x64
Sign In or Register to comment.