Question Need HELP (like really)

Mar 21, 2021
1
0
10
i am coming here as last resort after months of having a pc problem
rig (ryzen 5 3600) rtx 2060 16gb ram
i have a problem and i will explain everything in detail
a few months ago i decided to change my cpu fan from stock cooler (amd) to dark rock 4 pro and i added 2 fans in the front of the case
in the process i kinda didnt know how to remove gpu so it fot stuck and tought it was damaged , i took the pc to a shop where he actually removed screws , got the gpu out nicely and installed the new cpu cooler
after that i had big decrease in fps like really big , i tought gpu was damaged but after research i understood that a damaged gpu wouldnt work in the first place , i removed it again ( this time without problem) and verified if there was any damage , and there was none
i put i back i then did a time spy test , first result was 5956 ( the average is 7500) , i had exams so i didnt do anything , now a few days ago i updated all windows and gpu drivers from geforce and i put alimentation mode into ryzen high performance and got 6740 (average still 7500) and it was less worse . And now i redid time spy and im having only 6190
the last test i did , all gpu and cpu load were at 100%
so what can be the problem , i tought gpu damage turns out no , then PSU not enough turns out no (since i calculated it on a tool and i have more than needed , i have 550W and load was 420 , also gpu and cpu load were 100%)
please help , i really wanna solve this , i wanna go back to my usual gaming
here is a pic of timespy last result : View: https://imgur.com/a/ovyD8Me

and all results : View: https://imgur.com/a/NjCOwQV
 
Update your post to include full system hardware specs and OS information.

Include PSU: make, model, wattage (550 W noted), age, and condition?

Heavy gaming use?

I am not (full disclosure) not familiar with Time Spy.

Take a different look at your computer's performance by using Task Manager and Resource Monitor.

Use both but only one at a time.

Process Explorer may also prove helpful.

Also look in Reliability History for error codes, etc. Especially any that started appearing when the problems began.