Upcoming driver to fix Nvidia RTX 50-series black screen and BSOD issues

GeForce RTX 5090 Founders Edition
(Image credit: Nvidia)
Latest Videos FromTom's Hardware
Hassam Nasir
Contributing Writer

Hassam Nasir is a die-hard hardware enthusiast with years of experience as a tech editor and writer, focusing on detailed CPU comparisons and general hardware news. When he’s not working, you’ll find him bending tubes for his ever-evolving custom water-loop gaming rig or benchmarking the latest CPUs and GPUs just for fun.

  • flowingbass
    Nvidia was committed to almost be a "mining" company back in crypto days. Now they claim they are now an AI company.

    They keep making excuses and least effort on the consumer market so they can shift more allocation and not sell "barrel bottom" prices to "2nd class citizen customers"
    Reply
  • JayGau
    And what about the 4000 series? I have a 4080 and can't use any 572.## drivers since they make my PC crashing (it literally reboots by itself) if I enable frame gen in some games like Cyberpunk or Stalker 2.

    I found a thread on the Nvidia forum yesterday where plenty of people with 4080 and 4090 say they have the same problem. Some say that disabling G-sync solve it, but I personally think G-sync is more important than frame gen.

    Hopefully the problem with the 5000 series is related and the new driver will fix both. Because I don't like to be stuck with old drivers.
    Reply
  • JayGau
    JayGau said:
    And what about the 4000 series? I have a 4080 and can't use any 572.## drivers since they make my PC crashing (it literally reboots by itself) if I enable frame gen in some games like Cyberpunk or Stalker 2.

    I found a thread on the Nvidia forum yesterday where plenty of people with 4080 and 4090 say they have the same problem. Some say that disabling G-sync solve it, but I personally think G-sync is more important than frame gen.

    Hopefully the problem with the 5000 series is related and the new driver will fix both. Because I don't like to be stuck with old drivers.
    I went back to the thread on the Nvidia forum and people say that the new 572.60 driver didn't solve anything. Even someone with a 5080 said they have the same issue and the new driver didn't fix it.
    Reply