Major Stutter When Gaming (New Setup)

morriiissss

Prominent
May 23, 2017
4
0
510
CPU: Ryzen 5 1600X (Purchased new)
CPU Cooler: Corsair H100i v2 (Purchased new)
GPU: XFX RX 480 8GB (From old build)
Motherboard: MSI B350 Tomahawk (Purchased new)
Ram: 8 GB Crucial Ballistix Sport LT DDR4 (Purchased new)
Storage: Samsung 840 EVO SSD 250GB (From old build)
Seagate Barracuda 500GB 7200rpm (old model) (From old build)
Seagate Barracuda 2TB 7200rpm (new model) (From old build)
Power Supply: Thermaltake 650w (From old build)
OS: Windows 10 Pro 64 bit (Purchased new OEM)
VR: HTC Vive
Display: LG 29 inch Ultrawide 60Hz

Hello everyone,

I'm new to posting on forums so forgive me if I forget some etiquette. I recently upgraded my build to the specs posted above and I was gaming with it no problem until I noticed massive stuttering when trying to play games such as Overwatch, GTA V, or any VR games I play and that my CPU was idling at 60C. I checked the cooler to see if all of the components were working and they were so I assumed it was a bad chip. I exchanged that CPU for a new one and the idle temps went down to about 40C-45C and the stuttering went away for a while. I turned on my computer today to find that the stuttering was back on all games and practically made them unplayable. All temps are fine when running games and I'm pushing about 70-75 frames on Overwatch with settings on Ultra. For anyone confused about what I mean by stuttering, I can watch the frames skip as things are moving such as, when I play Overwatch and I jump or get into a crowded area I can see the game stuttering and becoming unplayable (no fps drop though). With GTA V driving is impossible and I can watch the cars skipping while sitting still. The odd thing is it worked for a while after replacing the CPU just fine. I know with my display I receive screen tearing and things like that because it's only 60Hz but even when trying to use Vsync the stuttering is still there and practically makes the games unplayable. When I installed everything new it was a fresh install of Windows on my build and both games are running on the SSD. All drivers and chipsets are up to date as of this posting date.

I'm debating returning all of the new hardware and going back to my old build because it honestly worked better than this new one and I didn't even have screen tearing with the old build. This is my fourth personal build and I've never experienced something like this before.

What I'm asking the community here is what do you think is causing the problem and what steps should I take to fix it?

 

Supahos

Expert
Ambassador
Idling at 45-50 with that cooler makes me think you've either installed the block incorrectly, too much or too little paste, or the cooler is pump is going bad. What are your max temps (use afterburner or hwinfo to log max temps) also keep GPU temps in mind. Are you at stock speeds? Have you updated your bios? The stock bioses are iffy on ryzen boards.
 

morriiissss

Prominent
May 23, 2017
4
0
510


I checked the block and the backplate to make sure everything was secured properly when I installed the second replacement CPU and I scraped off all of the old thermal paste and reapplied a pea sized dot on the center of the new CPU. I just re-checked everything to make sure it was on there correctly and both tubes are vibrating and I can feel temperatures. All the new hardware I bought is less than a month old. After playing two matches of Overwatch the CPU max temps ring back 55-58C when monitoring, GPU temps ring back 86C on afterburner. I am running stock speeds and I have not updated my BIOS yet.
 

morriiissss

Prominent
May 23, 2017
4
0
510


So I updated the BIOS to most current version that MSI offers and the same thing is occurring on both GTA V and Overwatch. CPU max temps rang back at 52-53C and GPU max temps rang back at 82 on afterburner. The idle temps differ on corsair link compared to MSI BIOS. Corsair link says 45-46C for CPU idle. But while I was in the BIOS it said 35-36C for CPU idle.
 

morriiissss

Prominent
May 23, 2017
4
0
510
UPDATE: I downloaded AMD auto driver recommend and it recommended I rollback to driver 17.4.4 when I had 17.10 installed and I think it may have fixed the issue. I'm going to further test it with VR and other games to see if it actually worked.