• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.
  • The forums have been upgraded with support for dark mode. By default it will follow the setting on your system/browser. You may override it by scrolling to the end of the page and clicking the gears icon.

GPU performing differently on startup vs restart

Joined
Mar 23, 2024
Messages
10 (0.02/day)
Processor Ryzen 7 7800X3D
Motherboard Aorus Elite AX v2
Memory G.Skill Trident 2x16 GB
Video Card(s) RTX 4080 SUPER
Hey there I have the following issue:
When I boot up my PC and start playing a game or run a benchmark my results/FPS are lower than the average for the hardware.
When I restart the PC and try the same things everything runs as expected.
If I put the PC to sleep and then wake it up and try again my performance is worse just like in the first scenario.

Some concrete numbers:
3D Mark TimeSpy for GPU score specifically runs at about 24-25k when performance is lower and at 28k when everything works fine (after a restart)
Red Dead Redemption 2 - in the bad scenarios I get about 100-110 FPS average, in the good scenario I get about 160-170 FPS

Specs: Ryzen 7 7800X3D, 32GB 6000Mhz RAM, RTX 4080 SUPER

The issue is GPU only, my CPU score when running TimeSpy stays the same in all 3 scenarios while the GPU runs well only after a restart.

I've tried both DDU and fresh windows install, fast boot is off in both windows and bios.
 
What is your windows setting for "what the power button does"?
 
Does the problem persist if you do not run Expo on your memory?
 
Hmm.. Well fill out your system specs in your profile. Give some time for the others here to take a look at your specs and the issue.
 
Hmm.. Well fill out your system specs in your profile. Give some time for the others here to take a look at your specs and the issue.
Hopefully someone can solve this it's driving me crazy. How do you add the specs to your banner? I ran the same validator from cpu-z and have a link but for banner I can only upload an image, no links
 
System specs in your profile.
 
This is Windows-related IMO.

Back a month or two ago, I was testing a RX580.
Reliably, changing the Display Arrangement killed a few percent of performance.
A reboot corrected, and the connected display in question had no bearing on the issue.

Question: is your iGPU in your 7800x3d left enabled? Windows will try to render low-power apps on the IGP and games on the dGPU.
When I had a 6500xt and rx580 in the same system, I was losing performance just from whatever mechanism Windows uses for GPU switching. (Even when only rendered on the displaying card)
 
Honestly, I think more data is needed. Can you pinpoint WHEN you first noticed this behavior? Or is it a completely fresh build? What Windows version are you running? I am hedging my bets that the issue is purely software since the hardware DOES work as expected on reboot.
Out of curiosity, does the behavior persist if instead of the Start Menu you use “shutdown /s /t 0” (no quotes) via cmd or PowerShell?
Turning off hibernation via PowerShell is also worth a try to be sure. The command for it is “powercfg /hibernate off”. After that - Reboot (not Shut Down). And then see on the next boot how shut down works for you.
Oh, and the cmd/PS/Terminal should be run as Admin, obviously.
 
Last edited:
I also believe this may be some sort of software incompatibility.

I have several builds in my house. A brand new RTX 4080 Super FE performed well on an existing ROG Strix B550 system but terribly on a ROG Strix X570 motherboard, lots of stuttering doing basic tasks (I wanted to put the 4080 on the X570). An RTX 3080 Ti worked fine on both systems as did an RTX 3060 Ti. I even tried an old Sapphire Pulse RX 580 on the X570: again no issues.

So I decided to do a clean Windows install on a spare SSD on the X570. The 4080 Super FE worked fine in the BIOS, fine with the generic Windows video driver but had horrible performance as soon as I installed recent Nvidia drivers. Again, the 3080 Ti and 3060 Ti worked fine. Removed the Nvidia drivers with DDU and normal behavior returned to the 4080 Super. All the motherboard software was up to date as well as the AMD chipset software.

Ultimately I decided I spent enough time on the whole matter so I punted and put the 4080 Super FE on the B550 motherboard. The 3080 Ti is living happily with the X570 motherboard.

Maybe some day all the software will work correctly on the X570 + 4080 Super. But I'm not waiting for that magic moment (if it ever comes).
 
Could that have something to do with the chipset drivers? I'm having issues on my 2nd PC with Crosshair VII Hero, no matter which GPU I have, but after I install the chipset drivers, I'm getting horrible latency issues.
 
Could that have something to do with the chipset drivers? I'm having issues on my 2nd PC with Crosshair VII Hero, no matter which GPU I have, but after I install the chipset drivers, I'm getting horrible latency issues.
It might but is there a credible consumer solution?

Let's say your Brand X video card is having problems with your Brand A chipset 1. You've tried various versions of the Brand A chipset software to no avail but the Brand X video card works fine with Brand A chipset 2.

It's not like Joe Consumer can write their own chipset software or use the chipset software from Brand I.
 
It might but is there a credible consumer solution?

Let's say your Brand X video card is having problems with your Brand A chipset 1. You've tried various versions of the Brand A chipset software to no avail but the Brand X video card works fine with Brand A chipset 2.

It's not like Joe Consumer can write their own chipset software or use the chipset software from Brand I.
Hella good point there :D I was just wondering that does OP have similar issues as I have
 
Could that have something to do with the chipset drivers? I'm having issues on my 2nd PC with Crosshair VII Hero, no matter which GPU I have, but after I install the chipset drivers, I'm getting horrible latency issues.
What you describe, reminds me entirely of what happens when overextending over riser, and/or trying to run Gen1.1-2.0 spec risers w/ Gen3 devices.
You get 'signal degradation', 'interferance' or, "EMC incompatibility" generally-speaking.

Possibly related to OP, but specific to your issue:
I'd 'play with' manually setting the chipset and slot link speeds. Sounds almost like it's in a back-forth loop of 'handshaking-unhandshaking' PCIe link.
Even, if CPU-connected, 'state shifts' to other CPU-connected PCIe devices (like the chipset) could be responsible.
On all my AM4 kit, I always manually set the highest-supported 'chipset link' speed.
For some of those w/ 'fake' "mining" Polaris cards, they have issues w/ reliability, performance, and HDMI until being forced to PCIe2.0.
 
What you describe, reminds me entirely of what happens when overextending over riser, and/or trying to run Gen1.1-2.0 spec risers w/ Gen3 devices.
You get 'signal degradation', 'interferance' or, "EMC incompatibility" generally-speaking.

Possibly related to OP, but specific to your issue:
I'd 'play with' manually setting the chipset and slot link speeds. Sounds almost like it's in a back-forth loop of 'handshaking-unhandshaking' PCIe link.
on all my AM4 kit, I always manually set the highest-supported 'chipset link' speed.
For some of those w/ 'fake' "mining" Polaris cards, they have issues w/ reliability, performance, and HDMI until being forced to PCIe2.0.
No risers but I'll keep your solution in mind. Never even thought about that PCIe speeds can cause problems.
 
This is Windows-related IMO.

Back a month or two ago, I was testing a RX580.
Reliably, changing the Display Arrangement killed a few percent of performance.
A reboot corrected, and the connected display in question had no bearing on the issue.

Question: is your iGPU in your 7800x3d left enabled? Windows will try to render low-power apps on the IGP and games on the dGPU.
When I had a 6500xt and rx580 in the same system, I was losing performance just from whatever mechanism Windows uses for GPU switching. (Even when only rendered on the displaying card)
The integrated gpu is disabled, yes

Honestly, I think more data is needed. Can you pinpoint WHEN you first noticed this behavior? Or is it a completely fresh build? What Windows version are you running? I am hedging my bets that the issue is purely software since the hardware DOES work as expected on reboot.
Out of curiosity, does the behavior persist if instead of the Start Menu you use “shutdown /s /t 0” (no quotes) via cmd or PowerShell?
Turning off hibernation via PowerShell is also worth a try to be sure. The command for it is “powercfg /hibernate off”. After that - Reboot (not Shut Down). And then see on the next boot how shut down works for you.
Oh, and the cmd/PS/Terminal should be run as Admin, obviously.
It's a fresh build with a fresh windows install, I started noticing from the first day. I'll try what you suggested and get back to you.
 
This could be just the normal windows restart/shutdown issue that existed forever. :roll: Lol, i know youre probably thinking now, what issue?!? When you restart windows it actually clears all your caches and ram, when you shutdown windows it acts the same as a hibernation or sleep cycle and keeps all the info stored for the reboot. Thats why youre probably seeing the issues the way you describe them. Hope that helps some. :rockout:
 
When you restart windows it actually clears all your caches and ram, when you shutdown windows it acts the same as a hibernation or sleep cycle and keeps all the info stored for the reboot.
Not with Fast Boot and Hibernation disabled. In that case, Shut Down acts as an actual Shut Down.
 
Honestly, I think more data is needed. Can you pinpoint WHEN you first noticed this behavior? Or is it a completely fresh build? What Windows version are you running? I am hedging my bets that the issue is purely software since the hardware DOES work as expected on reboot.
Out of curiosity, does the behavior persist if instead of the Start Menu you use “shutdown /s /t 0” (no quotes) via cmd or PowerShell?
Turning off hibernation via PowerShell is also worth a try to be sure. The command for it is “powercfg /hibernate off”. After that - Reboot (not Shut Down). And then see on the next boot how shut down works for you.
Oh, and the cmd/PS/Terminal should be run as Admin, obviously.
Hey there, so i tried the first command “shutdown /s /t 0” without luck. Then I turned off hibernation via the second one and restarted as you said - everything worked well as expected after a restart. Then I shut it down and turned on again - the issue persists
 
Back
Top