Question5090 observers experiencing rapid movements at over 3500 rpm
Question5090 observers experiencing rapid movements at over 3500 rpm
My current PC configuration:
CPU: AMD 9800x38
MOBO: MSI MAG Tomahawk X870e
RAM: 64 GB
PSU: Bequiet Dark Power Pro 1300W
Graphics card: Gigabyte Aorus Master 5090
My card is configured with quiet BIOS and it functions properly, running at a steady speed. The issue arises only during gaming, where the GPU temperature reaches around 83°C and the fans spin up to about 3500 RPM, then slow down within seconds. During Furmark benchmarking, this never occurs, even at those high temperatures.
I have used Gigabyte Control Center and MSI AfterBurner without resolving the problem. Switching to FanControl also doesn’t stop it. When it does happen, I return to the fan control panel and notice something similar in a Reddit thread (https://www.reddit.com/r/FanControl/comm...eed_issue/). The suggested fix was disabling the fan speed target in the Nvidia app. I also tried that.
My main concern is from last week when my PC was running but not showing anything, and the fans were spinning excessively—over 100%. This indicates a potential GPU issue since it was present before. I resolved it using the steps below, and now it’s functioning correctly. Could this be related to any long-term damage? Any advice would be greatly appreciated.
Could it be the resulting damage?
I question if the problem would disappear after using three support members for your GPU.
My concern is about gaming and only during gaming.
Which game are you attempting to stress-test the system/GPU to recreate the issue? What driver version are you using for your RTX 5090? Have you tried adjusting the GPU voltage?
A note, what BIOS version do you have installed on your motherboard?
Games, Legend of Heroes: Trails Through Daybreak and currently Like a Dragon: Pirate Yakuza in Hawaii are being played. I'm using the most recent Nvidia drivers. I'm looking for guidance on undervolting a GPU but don't have a clear starting point. The changelog for 7E59v2A52 mentions a newer version, but it doesn't address this issue.