After almost a year of trial and error from thousands of users we think we have a lead on the problem. As stated in the title there is a largely known problem that causes shadows to be jagged, low level of detail, jagged AA, and shimmering borders. Most would probably go to the AMD forum of Nvidia as it seems it is a graphical rendering error. Most thought this but through the year of testing Ryzen has come out. Now let me preface and say not everyone has this problem and the cause is still unknown. I am one that is affected by it and it simply started after I turned on my PC the next day. In some games it is more prominent and also some games have issues that are unrelated that some users confuse with what we are talking about. Now the reason Ryzen is important is a user on the LTT forum had the issue before and once they installed a new Ryzen CPU they said everything was better, shadows blended properly and weren't jagged, lighting was better, LOD at greater distances was apparent on the same settings, and the shimmering jagged AA problems were gone. As of now there are 4 confirmed cases of having the problem and upgrading to Ryzen made it vanish. Many users have been turned down from tech support or simply ignored. There has never been a strong answer from a dev and after hundreds of pages on forums no one has yet to find an answer of what causes it and a solution. As you might expect with thousands having the issue hundreds of thousands of combinations of CPUs, motherboards, memory, and every tiny detail about them is different. Every driver setting has been carefully tweaked, people have bought many CPUs over hoping to fix the problem to no avail. I will provide all the forum posts so you can throughly read through every testing means done and the specs. Enough talking and here are some videos showing the issue.
PayDay 2 has head bob with breathing so it works very well to see the shimmering lines and jagged appearance of the escalator. All settings were max and it was played at 1440p
Due to minecraft's grass on top blocks and it being a block based game you can see a grid pattern that shows every border. In the end you can see shimmering on the edges of the block. I used to play on an old macbook pro dual core and the settings were no where near what they are in the video but I never had this issue. I also tested older versions of minecraft and they all share the same problem. Setting again were max 1440p.
This was the first time I noticed the problem. The settings are max 1080p but 4:3 this time so some jaggedness is going to happen but the level of jagged in the video is much greater than what it was the day before. The ump magazine was what caught my eye as it was very jagged compared to the day before.
Now in overwatch the settings were again ultra 1080p and this was the second game I played the day I noticed the issue. The issue I started seeing is apparent in an official Blizzard trailer that was posted a couple months after it started for me. https://www.youtube.com/watch?v=H3xFKckFCGM
You can see as the camera pans slowly white shimmering on all the edges of objects.
The settings of the games is unknown as the user didn't specify but the problem is present through out all games new and old. Users in the comments also say they are having the same issue.
Here are all the forum posts about it.
User who found Ryzen helps https://linustechtips.com/main/topic/784090-4790k-to-r7-1700x-comparison-updated/
According to one user they found this to be the solution
"Imagine running a game such as GTA V. The first time you run it the settings are usually set on lowest meaning no AF or AA, low shadow resolution and distance. So the NvAPI takes these settings and unloads them into the L2 Cache of GPU so that the Stream-multiprocessors can read them and when ever you exit the game NvAPI should force the GPU to flush the settings by writing Global Settings into the cache area. For some reason it's stuck. It can happen when you change a setting by dramatically tuning it up and the variant is not fast enough to rewrite. Now the settings cannot be verified by any variant in order to be flushed. The only way to fix this is to find the way to flush the cache and unload a clean NvAPI into the cache. Now this also answers why this happens again when you insert new parts into the PC and that is because the drivers always keep the same buggy variant in their backup files and loads it into memory if its missing. It also works the other way, if you reinstall the drivers, it automatically reads the variants setting from the cache and make a copy of the variant. In order to fix it we have to unlock the resources and unload a variant . However we have no idea how to do that atm."