Associate
- Joined
- 24 May 2015
- Posts
- 802
I think Nvidia put the work experience kid on the Nvidia app. It's so janky and confusing already. I suppose it's not as ugly and slow as the control panel.
Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.
I got the black screen after installing the new drivers - though turning the monitor on and off gets the signal back. Same happened after my usual new-drivers reboot. I haven't been able to reproduce it since then, but something is still not right in these drivers.
No black screen issues during actual use (though I didn't have on the previous drivers either). Running on a Palit Gamerock 5090.
Yep, 572.83. It very much does not fix it. I had the same problem when I installed the previous game-ready drivers when my 5090 arrived on Saturday - though again, turning the monitor off and on again got the signal back.Wasn’t the latest ones meant to fix that.
What version did you install 572.83?
Installed over the previous ones - again black screen requiring few hard reboots to fix. Then it crashed compiling shaders I'm hlf2 rtx (didn't happen on them previous release). RT still crashing in Riftbreaker. Generally, to me, just as broken (if not more) as previous one. Maybe even they move to the next build it will be fine again - currently it's still a mess.
is it black screen when waking up from sleep ?I got the black screen after installing the new drivers - though turning the monitor on and off gets the signal back. Same happened after my usual new-drivers reboot. I haven't been able to reproduce it since then, but something is still not right in these drivers.
No black screen issues during actual use (though I didn't have on the previous drivers either). Running on a Palit Gamerock 5090.
No - just on installing the drivers and on reboot.It's done it twice now after reboots, so considering going back to the previous version. It's not actually harmful - just turn the monitor off and on again to fix it - but it is annoying.is it black screen when waking up from sleep ?
No - just on installing the drivers and on reboot.It's done it twice now after reboots, so considering going back to the previous version. It's not actually harmful - just turn the monitor off and on again to fix it - but it is annoying.
Yep, 572.83. It very much does not fix it. I had the same problem when I installed the previous game-ready drivers when my 5090 arrived on Saturday - though again, turning the monitor off and on again got the signal back.
Same, though for me after initial spazzing it works fine (no more black screens). That's aside the other issues they introduced.I use an lg oled, will try that next time, ive been powering the pc off and on to fix the issue.
Same here, I had my 5080 overclocked to the max at +475Mhz / +2000Mhz and it was running perfectly fine before this driver update.I swear my 5080 is clocking higher on this new driver. I'm pretty sure it wasn't going past 3200Mhz before but it is consistently now.
Almost word-for-word the same here. Benchmarks like Superposition seem the same at around 3080Mhz but heavy raytracing games were boosting into 3250Mhz and eventually crashing. I wonder if Nvidia tweaked the stock curves.Same here, I had my 5080 overclocked to the max at +475Mhz / +2000Mhz and it was running perfectly fine before this driver update.
I've had to back it down to +400Mhz / +2000Mhz to get it running stable again.