Just manually set your voltages, easier and better safe than sorry.Nice Once it's tested for a few weeks in the wild I'll swap my 4090 back over to my 7950x3D system.
Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.
Just manually set your voltages, easier and better safe than sorry.Nice Once it's tested for a few weeks in the wild I'll swap my 4090 back over to my 7950x3D system.
Just manually set your voltages, easier and better safe than sorry.
only way to find out is test.Kinda reserved about lowering voltages. Wouldn't lowering them cause stability issues?
Yeah, I plan on doing the same thing, I got some new fittings coming for my CPU water block, so need to drain the system and get the block off, might as well check the pads and pins at the same time.I've got two rigs setup, 13900k/z690 hero and 7950x3D/X690e Hero, so I've just swapped my 4090 strix over to the 13900k for now, and unplugged the AMD system.
Manually setting voltages is 99.9% likely to be safe, though I'd rather wait for the official fix and spare myself the extra time tinkering.
Will take a thorough look at my 7950X3D pin pads this weekend, to see if any kind of heat/scorch damage to the pads in question, as in the der8auer video etc.
EXPO, AMD screwed the pooch. GPU's ******, now CPU's. Someone needs to be fired.
LOL, im not using EXPO, ive manually set mine to 6000mhz, 2000mhz FLCK and all related voltages, and manually set all my timings including subtimings or rather Buildzoids easy DDR5 timings, are they going to argue that if something goes wrong ?, because if they ask me if I used expo, the answer will be no and id advise anyone faced with the same question to say no too, tell them everything was manually set especially after the news of these issues arose.And best of all, if you use expo = warranty voided. So for the next while anyone trying to RMA a dead x3d is gonna have extra scrutiny applied to see if expo or overvolting is suspected. That guy on Reddit who's 7800x3d got lucky that gamers nexus bought it from him for because Asus/amd declined warranty due to using expo
Most consumers will not have a clue.LOL, im not using EXPO, ive manually set mine to 6000mhz, 2000mhz FLCK and all related voltages, and manually set all my timings including subtimings or rather Buildzoids easy DDR5 timings, are they going to argue that if something goes wrong ?, because if they ask me if I used expo, the answer will be no and id advise anyone faced with the same question to say no too, tell them everything was manually set especially after the news of these issues arose.
ASUS x670e-f, 7800X3D, G.Skill 6000 c30 Neo. Turned off EXPO for now…
Maximums shown in HWiNFO :
EXPO on, CPU SOC = 1.385V
EXPO off (Auto), CPU SOC = 1.048V
I’ve not run any lengthy stress testing luckily
So I guess this is actually dodgy profiles in the actual RAM then?
I take it a non-X CPU is even less likely to have this issue since it's half the watts? Or is it the same chance as it's the same SoC voltage and will still maybe need a BIOS fix?
Not so much dodgy profiles - EXPO spec (if you can call it a spec) calls for up to 1.4v on SoC. However it seems no one has actually confirmed what is a safe voltage, or at least properly tested it long term on a variety of CPU's, in particular the newer X3D CPUs.
AMD are now actually working on this to properly determine what would be a safe setting when it comes to overlocking - and remember that is the primary issue here, AMD spec for SoC is 1.05v....no more, no less. EXPO is some half assed spec for overclocked RAM modules on AMD Ryzen 7000 series processors.
EXPO spec is actually overclocking the RAM, the CPU memory controller and overvolting SoC - which I believe has always been a potential issue with any 7000 series CPU but on the new X3D variants it looks to be a lot more sensitive to SoC voltage and the failure rate has increased dramatically.
Zen 3 chips were very sensitive to SoC voltages, and anything above 1.2v was considered unsafe and could kill the CPU. Why Zen 4 all of a sudden is any different and was thought to be able to handle 1.4v, i don't know - i think there has been some miscommunication going on here between AMD, motherboard manufacturers and RAM manufacturers. Some how 1.4v was now deemed acceptable and with non X3D chips the failures have been few, but there have been CPUs failing - just not many. X3D chips have just highlighted an already existing problem to the point it's now exploded across the internet and they can't ignore it.
You sure your not confusing soc voltage with ram voltage?Not so much dodgy profiles - EXPO spec (if you can call it a spec) calls for up to 1.4v on SoC. However it seems no one has actually confirmed what is a safe voltage, or at least properly tested it long term on a variety of CPU's, in particular the newer X3D CPUs.
AMD are now actually working on this to properly determine what would be a safe setting when it comes to overlocking - and remember that is the primary issue here, AMD spec for SoC is 1.05v....no more, no less. EXPO is some half assed spec for overclocked RAM modules on AMD Ryzen 7000 series processors.
EXPO spec is actually overclocking the RAM, the CPU memory controller and overvolting SoC - which I believe has always been a potential issue with any 7000 series CPU but on the new X3D variants it looks to be a lot more sensitive to SoC voltage and the failure rate has increased dramatically.
Zen 3 chips were very sensitive to SoC voltages, and anything above 1.2v was considered unsafe and could kill the CPU. Why Zen 4 all of a sudden is any different and was thought to be able to handle 1.4v, i don't know - i think there has been some miscommunication going on here between AMD, motherboard manufacturers and RAM manufacturers. Some how 1.4v was now deemed acceptable and with non X3D chips the failures have been few, but there have been CPUs failing - just not many. X3D chips have just highlighted an already existing problem to the point it's now exploded across the internet and they can't ignore it.