update on my overclocking adventure. a new way to get 4ghz and confuse all ur sensors.
i did the same thing i did on my previous postWarning: Spoiler! (Click to show)
ok now i'm onto overclocking methods.
i have it set in my asrock bios
core speed on auto
core voltage offset +2500
vdroop auto (level 1)
in the pstates
135000uv (or whatever the unit is)
EDIT: OH, THE REST OF THE PSTATES ON AUTO
windows was already in balanced mode so right when i got into windows, first FIRST thing i did was launch hwinfo64 since its pinned in my task bar.
about 1 min and 15 sec is how long i had to wait until hwinfo64 dropped the VID readings and core speeds and everything to sane levels
so pstate overclocking keeps all that in check still
then i ran cinebench r15 multicore and all my cores did go up to 3900mhz (give or take because my bus is locked or misread at 99.8mhz)
good run, max temp (tCTL) of 75.8c (with -20c offset applied) 1677 was the score
but this time i
pstate to 4000mhz
and whatever the next level up of the core voltage offset is 3650 or something like that, sounded like a big number, scary.
got into windows. waited for hwinfo64 again, about 1 min 15 sec. the VID never goes over 1.350v. my VROUT is 1.383v and my vcore seems to go up to 0.712v now... stable with ONE RUN in cinebench r15 with a score of 1749. everything downclocks still. i can tell it pulls more power because the cpu package power now goes up to 136w. interesting. i'll attempt a 3dmark run