Running High VDIMM & Low VCORE Risks Killing Your Athlon

If you run a high vdimm and a low vcore with E die etc you are running the risk of killing the cpu's. So if you have VX etc and you are not raising the vcore on your cpu you stand a chance of pumping a lot of current into the memory controller and causing permenant damage.

Im seeing people running $1k cpu's at default vcore and BH5 at 3.4V, this is a sure way to kill the cpu and is NOTHING to do with an issue on the board. If you are going to run high vdimm run a higher vcore also, and keep your CPU's ok.

if your cpu defaults to 1.35, run say 1.45V, you don't need to bash the cpu but you do need to strengthen the diodes that keep the CPU ok.
the newer CPUs run a much lower vcore, IE 1.4 or 1.35V. what you are looking at is the difference between the vcore and the VDD supplied to the memory controller from vdimm in bios. Now if the gap between the vcore and the VDD is huge you stand a chance of breaking down the diodes that protect the core from the high VDD.

All you have to do is strengthen the cpu's defences, you do this with a bump of vcore...thats all.It does not take a lot of vcore, just a bump from say 1.35 to 1.425 or so to help. The older 13nm cpu's don't look as much at risk although many did die quickly with high vdimm if you all think back.....this will have been the reason they died.

It was a long time ago since I overclocked my CPU. I don't think it's needed today. And the CPUs produces so much heat that the computers gets extremly noisy, or you have to buy expensive cooling.

Do you guys remember the good old days when you could double the MHz on your CPU pretty easy, and you got a much faster system then before you started clocking?