Ok so I fixed the GTA 5 crashing. I believe it was isolated to that game at this point as if you all remember NOTHING ELSE HAD THAT PROBLEM.
As for the sxs error: it was with a .exe called SETACL64.exe in the amd folder. It was installed with the AMD chipsets. I believe this problem could be for Ryzen users in general? So I'd recommend you all run the .exe in the file and if you get a SXS error window popup the fix is super easy.
As for code 68:
You stated that this was fixed with the reseating of the CPU, correct? I still haven't done this yet but I also haven't had any more crashes since that GTA 5 crash (it woudl appear when this game crashes it crashes so hard it sometimes triggers other issues). And also haven't had a crash since i SLAMMED THIS SYSTEM with FurMark 1440p max and p95 large FTT to get max heat/power usage to simulate a super hard core scenario in attempt to trigger it. I believe that crash was an unstable GPU overclock as nothing since then.
I also am not positive but fixing the sxs error with the .exe related to the AMD chipset could have possibly (?) resolved this? Since the .exe is related to the chipset.
Anyway, with the segfaulting (which I've written in other forums is 100% possible on Windows), do you think that could have contributed to the BSODs as well? Certain ones at least? Or debug 68? I'll RMA the CPU if I have to, I've heard (both from the guy who wrote it here in this thread, and elsewhere) that the RMA process with AMD is painless, quick, and easy. More than willing to wait a week if it guarantees my PC will be 100% rock solid (Which I thought it was/isk, but hey, who knows).
However, from what I remember chew stating, hes had more problems with the NEWER batches of CPUs than the OLDER ones, am I correct on this memory @chew*
? That the newer revisionls seem to cause different/more annoying problems? Or am I losing my memory here?
Once again I'd advise everyone check for the sxs error on SetACL64.exe just to be sure as the fix is easy and will guarantee no crashes due to that.
Also I cannot WAIT for the multi bug to be fixed as I'd like to push my CPU closer to 3.9 as 3.9 isn't very stable for me (requires WAY TOO MANY VOLTS for me to even want to bother with it compared to the super low amount for 3.8, so I"d like to be able to aim for you know like 3850+/-25) and the temporary work around fix chew^ had posted for the multi bug in the BIOS didn't seem to work for me.
I'd love to do some bclk overclocking but i have an m.2 SSD. I'm considering replacing it (or using it as backup storage) and getting a regular Samsun pro (you know the good one?) so I can try to get the bclk up a bit. But then again my system doesn't seem to be stable even with the bclk bumpe dup a single digit
so I am not really sure if that will even help me out.
Thanks once again to everyone for all your support. All of you check the SetACL64.exe in the AMD folder to check for the sxs error, and happy overclocking. I"ll be back around posting more (hopefully helpful to some) info and such now that I've resolved the vast majority of my problems and have a fully functional PC that isn't crashing every time I open GTA 5 so hardcore that I need a fresh windows install.