New GPU causes PC instability
New GPU causes PC instability
Hey everyone.
I recently changed my 3070 to a new 5070 Ti Gaming OC.
The rest of the PC is brand new, only about two months old, and it has worked perfectly.
Asus A620M Plus - latest BIOS
Ryzen 5 9600X
2x16GB XPG Lancer DDR5 6000MHz - running EXPO II
PSU 850W MSI MAG A850GL
When I connect the 5070 Ti, the motherboard LEDs display "GPU not detected". Sometimes it boots without problems, other times it needs a restart. Generally, it starts Windows but is very slow, around 3 FPS.
After a restart, I managed to reach Windows, played BF6 for 8 hours with 99% GPU usage and no issues, confirming the GPU works fine.
If I disconnect the GPU and boot from integrated graphics, there are no problems, just like before.
I’ve re-seated the GPU, confirmed the 12V cable is connected properly, updated the motherboard BIOS, and cleared CMOS.
What graphics card driver are you employing? Are you relying on the Windows driver or the manufacturer's driver for the graphics card? If it's the latter (manufacturer's driver), is the updated version correctly installed? On the hardware end, what motherboard do you have? Is the card securely placed in the appropriate slot?
Latest updates from NVIDIA 581.80 are available via the Nvidia App.
Asus B620M Plus is correctly installed.
Turning off EXPO now results in a stock 4800MT, and any combination with a new GPU causes significant lag and freezing on Windows.
I’ve successfully booted into Windows four times; the system appears normal, though there’s a minor stutter after about 15 minutes.
Currently running benchmarks and streaming videos simultaneously to test for crashes or disconnections.
This is likely the "5070 Ti Gigabyte Gaming OC" from GEFORCE, a product from NVIDIA.
Are you referring to this graphics card?
https://www.gigabyte.com/Graphics-Card/G...NG-OC-16GD
Would you be using this driver?
https://www.gigabyte.com/Graphics-Card/G...support#dl
Well, the support link I shared points to version 32.0.15.7260. If you're thinking of the earlier 572 driver you installed, which I believe is what you have, did it function properly with that version? Did you run tests using that driver? If not, perhaps a rollback to the 32.0.15.7260 driver would be a good idea to check if the issues persist. It's typical to make changes gradually to pinpoint the problem, so avoid other modifications while rolling back. As always, when reverting the driver, ensure you do it accurately.
No issue at all. Sometimes fixing these kinds of PC problems requires patience and work.