Originally Posted by lordzed83
Im here from day one and So far I cant remember ANYONE killing their Ryzen CPU with volts on this Forum. If So pealse quote me post with peron taht managed to Do so
Seen few boards that got bricked by bios update (few had to RMA as flashback did not help). Seen RGB memory kits killed and few corrupted ( Repaired with spd rewrite ) and ONE Killed AIO to proof that SenseMI will stop thermal protection from working. Yet not seen Anyone posting here that their CPU got fried by overvolting
But hey im following Ryzen platform on only 3 forum in 2 languages constantly daily.
I'll dig around and find it at some point, it may have been a video from Buildzoid or something similar, as I was watching a lot of that around the same time as that news surfaced, I may not have as much overclocking experience, but I've been dealing with Ryzen just about as long as the rest of everyone here. I'm also not the only one who remembers seeing this info.
Originally Posted by MishelLngelo
I pushed my 1600x over 1.6v trying to go way over 4.1GHz and while it posted it got into several thermal shutdowns running benchmarks and it didn't get damaged in any way. During that time I was more concerned about my Prime x370 Pro than processor itself. During my considerably long life with computers, I managed to blow up few MBs along with few GPUs and RAM but never damaged a processor, not even at times we had to do voltage mods on 386 systems.
You don't THINK you've damaged a processor. My bet is you probably have, and just don't know it. Does that matter in the end? Maybe, maybe not, no real way to know, and everyone's case is different. Every piece of silicon is different, every single CHIP within a line is different. I simply reiterated what AMD themselves said, and that I personally don't want to go above 1.4v, I feel that if I have to do that, it's pushing too far for that particular chip, and often the heat and voltage spiking isn't worth the extra 50-100 mhz of speed. That probably doesn't make me an "extreme overclocker" and I'm ok with that.
Originally Posted by Frikencio
I think that the problem is when I have multiple SPD reading programs open. I think CORSAIR LINK do access to SPD.
Yeah. You definitely don't want other SPD-reading programs open at all when you're running Taiphoon to pull an SPD read on RAM, it'll not work right, or look corrupted. I made the mistake of forgetting aura was running at one point trying to do it. Definitely make sure you're using the latest Aura (others WILL corrupt RGB RAM and even some non-RGB RAM) I've had to re-flash my sticks myself. I haven't seen any further corruption since aura was fixed, but I do have SPD backups of my sticks just in case. If you aren't sure, run Elmor's SPD check tool (with no other programs running--though I believe his latest version can play "nice" with Aura). And make sure it checks out OK, if not, re-flash or RMA your sticks. Just because they "appear to be working fine" that corruption can reach the point they won't boot, then you can't re-flash them in a system, and would have to replace or RMA them.
Edit: As an aside, Aura, Corsairlink, CPUz, Taiphoon, all SPD-reading and using programs, possibly so is HWinfo64/parts of Asus AI Suite, etc. Basically, if you're going to use Taiphoon, try to close everything you can while using it. All of those programs make use of the SMBus, which is where the issue comes in.
Edited by PeerlessGirl - 10/17/17 at 9:12am