Originally Posted by gupsterg Warning: Spoiler! (Click to show)
I just had this, never before on say unstable settings for tweaks to RAM / BCLK / CPU OC, etc. IIRC SpecChum, Ubardog and a few others have had this on other UEFI versions perhaps or these newer ones?
Usually I never unhook power from PC when shutdown. I did as wanted to move case to do some tiding up on cabling. The moment I fired her up she went through 3x boots
, which she never usually does.
ProbeIt VCORE point showed ~1.498V
Attached is zip of UEFI screenies showing what I change from defaults.
0079_UEFI_OC_Setup.zip 2878k .zip file
Originally Posted by Reikoji
On every bios I've used, whenever i shut off the power supply for an extended and turn it back on it does the 3 boot thing as well, but my settings have never changed as a result. I never thought anything of it.
However it wont do it if you reset CMOS after re-applying power to the PSU, it will just do its normal initial long post loop and then force you into bios as normal.
After that high VCORE boot, I loaded optimized defaults, let system boot and shutdown. Then mains off and used CLRCMOS, next boot up loaded "base profile" ie everything stock but onboard stuff disabled as needed, fan profiles as want, etc. Then loaded my 3.8GHz 3200MHz C14 OC profile, like I have done when I've had a borked boot from say playing with RAM CLK / BCLK / CPU OC. Shutdown PC as usual (left power on on PSU like usual), waited very little while and switched rig on.
It did 1x post up, did some Q-Codes and shutdown and up again, 3x boot loop and borked again.
I don't think I'm having an issue due to cable tiding earlier.
All I did was remove cable from CHA3 for rear exhaust fans, cable tie and reinsert. Then PCI-E cables to GPU were not removed/relocated just cable tied as needed. Q-Connect / Speaker cable removed to test speaker as for a while it has not worked on C6H, reinserting it solved that issue.
All this has created this now
Like I said I have had borked boots / crashes in OS from unstable OC settings and ever since SpecChum / Ubardog mentioned this issue I have been on the look out if it happens to me and it did not, until today
Loading defaults now, removing power / battery, then reflashing UEFI.