Nvidia Geforce RTX 50xx experiences

[Florin]

Had some other stuff to deal with so I only really started playing around with the Gigabyte RTX 5090 Aorus Master yesterday.

I'm on a fresh system based on a Gigabyte X870 Aorus Elite Wifi 7 running a Ryzen 7 9800X3D with a fresh Windows 11 Pro 24H2 install.

So at first my benchmark scores weren't all that hot and I was wondering what was going on.



Had to dig around for a bit to find the culprit on this one: Windows Virtualization Based Security or VBS.

The old ways to disable VBS no longer seem to do the job completely on 24H2.

Eventually, I found that that in addition to the other tricks, you are now supposed to use Regedit to set:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\WindowsHello\Enable to 0
.. for VBS to finally be gone completely.

And hoo boy what a difference that makes for this class of system:



- edit - Turns out VBS was not actually the root cause, I still have this issue on some boots.

When it happens, the GPU only clocks to 750Mhz and then stays there, and performance is compromised proportionally.

Rebooting and running the benchmark again fixes it.

 

[digitalwanderer]

Don't update drivers on a 5090! The new drivers have bricked some cards.

https://videocardz.com/newz/some-geforce-rtx-5090d-5090-users-report-issues-following-first-driver-update

 

[Florin]

I noticed the card has a screen of its own:

Ready for liftoff. I think that's.. 11 fans you're hearing?

 

[Florin]

Don't update drivers on a 5090! The new drivers have bricked some cards.

https://videocardz.com/newz/some-geforce-rtx-5090d-5090-users-report-issues-following-first-driver-update

Hmmm.. well, I pretty much did that already. So far so good. Fingers crossed

I'm reading that this is actually supposedly the highest boosting 5090 out there so far, according to the list from TechPowerUp.
So I guess I ought to be extra careful then..

- edit - and it looks like it is doing a decent job actually boosting to near that level during much of a benchmark run:

 

[Discord]

Don't update drivers on a 5090! The new drivers have bricked some cards.

https://videocardz.com/newz/some-geforce-rtx-5090d-5090-users-report-issues-following-first-driver-update

There is an update and might appear related to PCIE compatibility on certain motherboards.



There was another black screen issue but currently the temporary fix is switching to PCIE-4.

https://www.eteknix.com/rtx-5090-users-report-black-screen-issues-after-driver-update/

Users experiencing this issue have attempted various troubleshooting steps recommended by NVIDIA and affected manufacturers such as Manli and Colorful, but the problem persists. Even some NVIDIA RTX 5090 Founders Edition units have been affected. Reports suggest that the issue may be related to compatibility between the new PCIe 5.0 bus used by these GPUs and certain motherboard models.

No Official Solution Yet, But a Temporary Fix Exists​

The most serious cases indicate that some users have been unable to restore functionality to their graphics cards, even after rolling back to an older driver version. At this time, there is no official solution or response from NVIDIA or the manufacturers. However, a temporary fix could be to manually set the PCIe bus to version 4.0 in the BIOS, rather than using the newer PCIe 5.0, while waiting for more details and a permanent resolution.

 

[Bludd]

Had some other stuff to deal with so I only really started playing around with the Gigabyte RTX 5090 Aorus Master yesterday.

I'm on a fresh system based on a Gigabyte X870 Aorus Elite Wifi 7 running a Ryzen 7 9800X3D with a fresh Windows 11 Pro 24H2 install.

So at first my benchmark scores weren't all that hot and I was wondering what was going on.

Spoiler

View attachment 13039

Had to dig around for a bit to find the culprit on this one: Windows Virtualization Based Security or VBS.

The old ways to disable VBS no longer seem to do the job completely on 24H2.

Eventually, I found that that in addition to the other tricks, you are now supposed to use Regedit to set:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\WindowsHello\Enable to 0
.. for VBS to finally be gone completely.

And hoo boy what a difference that makes for this class of system:

Spoiler

View attachment 13041

weird, is that huge performance regression with VBS enabled an amd cpu issue, a 5090 issue or a 24h2 issue?

 

[Potato Head]

There is an update and might appear related to PCIE compatibility on certain motherboards.

View attachment 13052

There was another black screen issue but currently the temporary fix is switching to PCIE-4.

https://www.eteknix.com/rtx-5090-users-report-black-screen-issues-after-driver-update/

All blown out of proportion as usual. And the usual culprits won’t publish corrections because they already got their clicks.

 

[Florin]

weird, is that huge performance regression with VBS enabled an amd cpu issue, a 5090 issue or a 24h2 issue?

It's a me issue.. even though it looked as if the VBS fix resolved it, the problem returned.

On some boots the GPU will clock to exactly 750Mhz and no higher, and performance will be bad.

Still looking for the root cause. World of Warships has been downloading for 3 days straight and is still only at 57%, that running in background may have something to do with it. Further investigation needed.

Just a reminder that buying on launch day can end up making you a bit of a beta tester.

 

[Florin]

Should I be worried?

That's technically more than what the 12v2x6 connector is rated for, isn't it?
Hopefully some is coming from the PCIE slot.

 

[Discord]

Are you running PCIE-4 or PCIE-5?

 

[Discord]

Here's another boot issue temporarily solved by switching to PCIE-4:

https://videocardz.com/newz/club386-encounters-geforce-rtx-5080-black-screens-issue-pcie-4-0-fix-shows-promise

 

[Florin]

Are you running PCIE-4 or PCIE-5?

Still at the default PCIE5. That's one of the things I plan on trying soon.



Hey, I just noticed no fizzyX support reported on this card.
Checkmark is still there on my 4080.

 

[trinibwoy]

Still at the default PCIE5. That's one of the things I plan on trying soon.

View attachment 13057

Hey, I just noticed no fizzyX support reported on this card.
Checkmark is still there on my 4080.

Make sure PhysX is set to run on the GPU in the control panel. Last Nvidia driver install reset it to CPU for some reason and I’ve had a bunch of crashes too. Driver seems flaky.

 

[Florin]

Make sure PhysX is set to run on the GPU in the control panel. Last Nvidia driver install reset it to CPU for some reason and I’ve had a bunch of crashes too. Driver seems flaky.

It was set to 'Auto-select (recommended)'.

Tried manually selecting the 5090 and rebooting but still no PhysX support reported. I may actually have heard this mention in a Youtube video but I can't recall which one.

Also, I posted the GPU-Z screenshot above to demonstrate PCIE5 and now I just noticed it had switched to 'PCie x16 5.0 @ x16 2.0'.
It actually seems to switch dynamically every few seconds. Below it says 5.0 but it also says 2.0 and 1.1 intermittently. Maybe a power saving thing.
Gonna try force that too in a bit.

Beta testing continues hehe

 

[digitalwanderer]

All blown out of proportion as usual. And the usual culprits won’t publish corrections because they already got their clicks

Really? If my $2,000 video card bricked from a driver update and I wasn't savvy enough to know to switch it from PCIE-5 to PCIE-4.

Is there any performance loss going to PCIE-4?

 

[Albuquerque]

Make sure PhysX is set to run on the GPU in the control panel. Last Nvidia driver install reset it to CPU for some reason and I’ve had a bunch of crashes too. Driver seems flaky.

Hey, I'm glad you mentioned this, because I've noticed some problems and sorta assumed it was just my undervolt + overclock needed some adjusting. To some extent I was right, because a tiny bit of extra voltage at the same speed seems to have solved the random instability I was getting with longer play sessions of CP2077 + DLSS 4 Transformer mode (which is a new change for me), but I've also been having problems with Space Engineers crashing randomly -- and it is NOT a GPU-intensive title by any stretch. On a whim I fired up some Skyrim SE for my little dude to play, and after like 15 minutes it CTD'd too. Don't get me wrong, that's totally a Bethesda Game thing to do, buuuut Skyrim SE has bee historically pretty damned stable for me (thanks to all that 64 bit goodness that will just absorb all the memory leaks without running into the 32-bit app limit lol.)

I think it's this latest driver and I'm a little unhappy about it.

 

[Bludd]

Really? If my $2,000 video card bricked from a driver update and I wasn't savvy enough to know to switch it from PCIE-5 to PCIE-4.

Is there any performance loss going to PCIE-4?

no a few % at most

 

[T2098]

Also, I posted the GPU-Z screenshot above to demonstrate PCIE5 and now I just noticed it had switched to 'PCie x16 5.0 @ x16 2.0'.
It actually seems to switch dynamically every few seconds. Below it says 5.0 but it also says 2.0 and 1.1 intermittently. Maybe a power saving thing.
Gonna try force that too in a bit.

That's normal thankfully, if you hover over the little question mark next to the PCIe link speed there's a helpful tooltip that prompts you to click on it:

 

[homerdog]

Is there any performance loss going to PCIE-4?

It doesn't matter for performance. It's likely these systems had never run at PCIe5x16 (no available GPUs), so they could've always been iffy on that.

At least you can get an eeprom programmer pretty cheap these days

 

[Florin]

Got it up and running on Linux, including secure boot and Gsync enabled on my compatible but uncertified Gigabyte monitor.

Even though my usual go to repository for Nvidia drivers already has the required 570.86.16 driver, that method wouldn't quite work.
I reckon it's either because they compiled with the proprietary Nvidia driver interface or because they're pulling in Optimus (and trying to use the 9800X3D integrated Radeon).

The good old Nvidia .run installer had no problems tho using the GPL/MIT open modules interface: