Monday, May 26th 2025
NVIDIA Issues vBIOS Update to Fix RTX 5060 (Ti) Reboot Black Screens
NVIDIA has quietly released a firmware patch for its GeForce RTX 5060 and RTX 5060 Ti graphics cards to fix a frustrating blank-screen issue that appears when users restart their systems. Interestingly, this reboot glitch affects only the RTX 5060 and RTX 5060 Ti models built on NVIDIA's GB206 silicon. Other RTX 50-series cards and the older RTX 20, RTX 30, and RTX 40 generations do not show this behavior. While NVIDIA has not revealed exactly what went wrong, providing a vBIOS patch suggests the issue lies in its own firmware code. This update is delivered as a vBIOS upgrade rather than a traditional driver, and it must be applied manually using NVIDIA's new GPU UEFI Firmware Update Tool v2.0. The problem seems to come from the way the RTX 5060 series vBIOS communicates with certain motherboard BIOS or UEFI implementations.
On systems booting in Legacy (CSM) mode or those lacking full UEFI support, users sometimes encounter a black screen on reboot even if the operating system and drivers are correctly installed. NVIDIA's utility first checks if you need the update, then walks you through the flashing process step by step. Because flashing firmware always carries some risk, especially if your power goes out mid-update, NVIDIA recommends that only those experiencing blank screens should proceed. Before you start, power down your PC completely, make sure you have the latest BIOS from your motherboard maker and switch to UEFI boot mode. If you still cannot get any display, try plugging it into your integrated graphics or a second GPU so you can run the update tool. After closing all your applications and pausing any pending OS updates, follow the on-screen prompts to apply the vBIOS fix. If your motherboard does not support UEFI mode, contact your graphics card vendor for a legacy firmware version.
Source:
NVIDIA
On systems booting in Legacy (CSM) mode or those lacking full UEFI support, users sometimes encounter a black screen on reboot even if the operating system and drivers are correctly installed. NVIDIA's utility first checks if you need the update, then walks you through the flashing process step by step. Because flashing firmware always carries some risk, especially if your power goes out mid-update, NVIDIA recommends that only those experiencing blank screens should proceed. Before you start, power down your PC completely, make sure you have the latest BIOS from your motherboard maker and switch to UEFI boot mode. If you still cannot get any display, try plugging it into your integrated graphics or a second GPU so you can run the update tool. After closing all your applications and pausing any pending OS updates, follow the on-screen prompts to apply the vBIOS fix. If your motherboard does not support UEFI mode, contact your graphics card vendor for a legacy firmware version.
72 Comments on NVIDIA Issues vBIOS Update to Fix RTX 5060 (Ti) Reboot Black Screens
1.) Unstable drivers since the launch, and there are still issues.
2.) Nvidia App also causing issues and crashing
3.) Display connectivity problems
4.) 12VHP burning up and nearly the whole tech sphere and nVidia is gaslighting customers about it to this day
5.) Missing ROPs across multiple SKU's.
6.) Market manipulation
Is ridiculous how I can only use drivers from December last year that are not crashing the games as often as the newest ones. If AMD was atrocious with their drivers a decade ago, now this changed, and changed by a lot. I never seen video drivers so bad in my entire life, and I'm gaming since S3 Trio 64 V+ times.
Either I'm extremely lucky or the issues are overblown and exaggerated... I wonder which one it could be.
The single oc issue I had was on reboot it seemed to subtract my +350 oc rather than add it, and that was fixed months ago. Hard to be annoyed given I was using 3rd party tools to do it, but nonetheless a driver fixed it.
Lot of people having issues are those on newer architecture (ironic) or multi/new-monitor setups. I also think a lot of people don't know that, if their monitors fall out of the their refresh rate range with g-sync enabled, that their displays will flicker/turn black etc.
nGreedia has their hands full.
Never experienced any black screen, stutter, power cable issue (even got per-pin power display on Afterburner OSD to look like a Pro :D).
Only took me a few hours to set up the undervolt because Blackwell clock gen is weird, other than that I can enjoy this card for the next 2 year without the need to tinker with anything.
They really need to overall their driver, firmware and App department.
Yep, another lie.
Note: 2023 this was a supported card by the last drivers. I tested such card on purpose to see if it fits my needs for several months. I doubt this has improved since 2023 with windows and nvidia based graphic cards.
Sometimes it was smarter to buy a nvidia 4090 early at release. For driver quality even 1.5 year later it was a mess for several products these days, e.g. ASUS x670-am5.
#7) Marketing - and all it promises. Regardless if they exists or not. E.g. raytracing, no lag, and so on - feel free to get your own opinion. Cards beeing 5 times faster as nvidia 4090 something, ...
#8) Silent release of bugfixes / Be-Quiet about issues and problems
I saw it ages later that my nvidia 960 had a firmware tool. But the bug with windows was there, even after the firmware update with the nvidia itself downloaded from nvidia.com windows only firmware tool.
The windows and gnu userspace nvidia binary driver did not tell me / notify me / inform me that there is a newer firmware available for any of those 900 and 1000 graphic cards from nivdia itself.
Disabling Resizable BAR also works in some games that are constant crashing.
All and all it seems that the main culprit are the drivers. Each version adds more and more issues than fixing them.sffpc/comments/15q01dn/worlds_first_levitating_pc_case_mod_part_31
Exclusive doesn't like alt-tab when the rendering resolution is different from the desktop resolution. It's usually more a problem of the graphics engine than the driver, especially in non-UE games.
How this company can hold a majority of the marketshare is mind-boggling, it borders on corruption and manipulation when you consider the consoles that dominate the attention of game-developers have been running on AMD graphics since 2013.
2- Lies.
3- Lies.
4- Lies.
5- Lies.
6- Lies.
We all know that its clearly AMD fault.... ;)
/S in case is needed.Yet you rarely see anyone nailing them to the cross in the same way that they all did and are still doing to AMD.
I mean, ask anywhere which company STILL has bad drivers and they all will respond AMD.
How many RDNA4 gpus you saw listed at the last Steam Hardware Survey and how many Ngreedia 5000 series?
Yeah, they are still selling like crazy.
Ps I know, sadly, the SHS is not a reliable source, but still shows some numbers.