Originally Posted by gupsterg
Any info on how this happens? ie settings, etc you guys used that created situation? would like to avoid it.
Originally Posted by SpecChum
What's it doing now to make it limited?
I set the offset to .5 vice what I was intending .05. Failed to check or notice that during the save (bios tells you what has been changed). Then I did not verify proper voltage once system was up, went off and did other stuff. I now go back into the bios after a change to verify the change vice just going straight into Windows.
The limitation now is 3.6ghz max for stability, Windows will not boot with any voltage over 1.4v. So Optimize defaults Windows blue screens within seconds after posting since voltage is at 1.43v. I will most likely get more use out of this processor then the one coming
, that is if it lasts. In the near future I will make a render box using it, low power, on 24/7 at lower frequencies, probably around 3.2ghz. Will need a motherboard MicroATX (64gb of ram) or MiniITX (32gb) that can do PState overclocking/underclocking so as to set the voltage less than 1.4v (more like 1.2v would be my goal). Should get my next 1700x tomorrow - I will definitely be more careful this time.
ASUS C6H bios 6401, Ryzen 2700 @ 4.11ghz, 32gb TridentZ 3333 (Dram Calc 3333safe) Samsung B (2x F4-3200C14D-16GTZSK + 2x F4-3200C14D-16GTZKW),2x Radeon Vega FE, Intel P600 1TB M.2 drive, 950w PC Power and Cooling PS, Samsung HDR 144hz FreeSync monitor, Win 10 64