Micro Stutter in Games on Ryzen (Win10 1607, 1703, and 1709)

docov06

Reputable
Feb 21, 2014
44
0
4,530
Ryzen 1700X (currently OC to 3.7, custom water-cooled)
Crucial Ballistix Sport LT 16GB 2 x 8GB DDR4-2400
EVGA FTW GTX 1080
AsRock X370 Fatal1ty Pro Gaming (Bios ver 2.4)
Samsung 960 Evo NvME PCI SSD
Corsair AX860 PSU

Since I built this PC, I have had nothing but issues with it. From day one I have had micro stutter in certain games. At first, it was because of Win10 1703, so I reinstalled the 1607 update and it cleared up for most games, except any Battlefield game, Squad, and sometimes Rainbow Six Siege. So I kept it on 1607 for about 3 months, until I just got fed up with the stuttering in Siege (the one game out of those 3 that I play regularly). The stuttering/freezing I was getting in Siege was very short (1 second to 2 seconds) and random throughout a match, usually 4 times a match it would stutter. I tried various fixes, including flashing BIOS to a newer version, which rendered my PC completely unusable. Anything pass ver 2.4 made the PC stutter extremely bad and couldn't even do basic functions, like opening a browser or file explorer. So I rolled back to 2.4 and was stable again, but still stuttering in games. Then I heard that FCU fixed alotta things that 1703 broke, so I just recently did a clean reinstall to the newest Windows update, issue still persists in the same games. I decided that maybe it was the low stock clock speed on the CPU, so I overclocked to 3.7 and noticed the stutters were much better and less jarring, but still just as frequent. I am honestly completely lost, and frustrated, on how to fix this problem as I have been troubleshooting it for so long. It makes me sad too since this is the build that I have dropped the most cash on, and it has performed the worst out of my 4 previous builds. Any help would be amazing!!
 

docov06

Reputable
Feb 21, 2014
44
0
4,530
Also, I forgot to add that when I flashed the bios to 3.1, the system would not boot, it would fail after bios splash screen and would read a 55 post error code, which is a RAM issue. 3.0 and below did not have this problem.