PSA Windows 10 + Adaptive Voltage/Offset voltage and you

[OneMoar]

be advised windows 10 seems to use much much more aggressive voltage scaling when using offset/adaptive voltage if your system suddenly is crashing left and right under minimal workload or failing to boot you will need to tweak your voltage range
my system
8.1 idle desktop chrome 800Mhz 0.700v to 0.800v for x 8 multi
windows 10 idle desktop chrome 800mhz 0.368 to 0.600v idle
keep in mind that the scaler is voltage bias meaning it will take away voltage before reducing clock speed and vice-versa
checked with both cpu-z HWmonitor and AIDA64
if somebody with more time then I have would like to spend a few hours mapping the differences please do ...

 

[Deleted member 50521]

I have noticed this! Right after a fresh install I had no stability problem. Then all of a sudden I am having problem booting up. I bumped up vcore to fix this.

 

[Ferrum Master]

I have noticed this! Right after a fresh install I had no stability problem. Then all of a sudden I am having problem booting up. I bumped up vcore to fix this.

Yes, I had to up voltage too to maintain stable 4.8Ghz clock... My Megahalems goes to hell with that... NH-D15S arrives in a week for me...

Althou... I don't complain... bravo to devs, they are doing actually a fine job.

 

[HWTactics]

I had a feeling that might be the case.

I just upgraded an Intel NUC with a Celeron 847 to Windows 10 running a touch screen. It has been noticeably cooler to the touch since moving it off Windows 7.

 

[Swamp Monster]

Maybe this is why my PC needs restart to boot into windows normally, after upgrading to Win10.

 

[Deleted member 50521]

OK this is getting out of control. My system just fell into a non stop booting loop. All kinds of error code. This freaking sucks. I am having more BSOD than the last there years combined. Sometimes even 10 BSOD in a row. Very annoying.

 

[erocker]

Roll back to previous Windows. Fixed. No reason for me to go to Windows 10 until I actually "need" DX12.

 

[Kursah]

I'm curious what activates this???

I have none of those issues on any of my my workstations or laptops that have 10 Pro installed. My idle voltages did not change...so whatever was done here, I'd love to avoid doing! Intel and AMD, various generations.

So far 10 has been a good experience...I am running my CPU under-volted using offset, 0 issues. Idle voltage is the same 0.635 as measured in 8.1 using HW Monitor 1.28.

 

[LAN_deRf_HA]

If this is being done by windows it should be a setting. Settings can be changed.

 

[Deleted member 50521]

OK I have found some possible fix that at least works for me. Most of my crashes happen during initial startup. I checked the mini dump file and it seems the intel GBE driver was causing some of the crashes. So I did another fresh install of Windows 10 and recorded the system stability after each driver installation. The system started to crash right round I install the Intel NIC driver from ASUS. So I immediately uninstalled that driver and stability seems to have improved a lot.

However I still got 2 BSOD from boot up. I did some research. It seems the Windows 10 "Fast Startup" option is the one to blame. It puts your PC into a hybrid sleep mode instead of completely shutting down. However due to change of vcore after overclocking this kind of boosted boot up will do more harm than good. The proof is if I set vcore higher and enable offset mode it will not BSOD. Or if I disable overlock it will stop BSOD as well. So I went ahead and disabled that as well. Now it has been 3 hrs under AIDA64 stress test and no more BSOD. Also I am no longer getting BSOD right after booting up.

Windows 10 still has so many bugs, I kinda regret switching to 10 right away. Should have at leasted waited half a year until all of the major bugs have been fixed.

 

[Arjai]

I don't get BSOD's but, it seems to reboot to the login screen, a lot!!

I will notice it, sometimes hours later!! I Crunch and Fold on it and it is messing it all up! This job that loaded this morning said 9+ hours, I just noticed it and signed back in...8:44 left!! So, Yea, what's up?

 

[OneMoar]

if you think you are having cpu scaling related issues open up the power control panel and set the minimum processor state to 15 or 20%
this will make the scaler ramp faster while preserving power savings
again crashes related to the new scaler should present them selves as crashes during boot or under low loads (such as youtube or office) or when exiting out of a intensive application such as a game please make sure you have evidence before posting here I would like to get this confirmed on more then one machine if you dual boot please take a moment and fire up hwmonitor and check your vcore/vid in both windows 8.1 and windows 10

 

[terroralpha]

WELL F ME SIDEWAYS!!!! i thought i cooked my CPU or something. I had my 5930K OCed to 5.1GHz in windows 7 and 8.1 without problems, clocked down all the way to 1.2GHz when idling or under low loads, or bounced in the 2s and 3s. in windows 10 i get BSODs at 4.6GHz no matter what I do. 4.5 works fine but the CPU wont settle for any speed in between 1.2 and 4.5. mostly stays at 4.5 and guzzles power needlessly.

this is bad and good at the same time. it's bad that I can't OC as high, but good that I didn't fry my 6 Benjamin CPU. i'm going to back to windows 8.1 as soon as i have time to reinstall. there won't be any dx12 games anytime soon anyway.

 

[Deleted member 50521]

I have tried OneMoar's suggestion. Setting the CPU state to 15% still causes BSOD on my system. So I went up in 5% increments. So far the lowest stable state I can set without crashing loop at start up is 45%. Right now I am using manual vcore setting plus level 8 of load line calibration. I will try using the offset/adaptive voltage options in the uefi settings and see if it can improve stability.

 

[OneMoar]

I have tried OneMoar's suggestion. Setting the CPU state to 15% still causes BSOD on my system. So I went up in 5% increments. So far the lowest stable state I can set without crashing loop at start up is 45%. Right now I am using manual vcore setting plus level 8 of load line calibration. I will try using the offset/adaptive voltage options in the uefi settings and see if it can improve stability.

if you aren't using adaptive voltage then changing the power-plan should have no effect
very very odd do you have c-states forcibly enabled ?

 

[Deleted member 50521]

if you aren't using adaptive voltage then changing the power-plan should have no effect
very very odd do you have c-states forcibly enabled ?

I have speed step and all the other power saving option enabled.

So now after setting the system power profile, disable fast boot in uefi, disable hybrid sleep in windows 10 my system has been BSOD free.

 

[OneMoar]

ok the fast boot and the hybrid sleep bsods are likely unrelated ....

 

[johnspack]

Man, so I need to upgrade to a D15 to run windows 10... 140can at ncix..... getting more expensive all the time!

 

[OneMoar]

the more I fiddle with it the more something seems just off ...
@cadaveca you notice anything on with windows 10 when overclocking
it seems like there has been some kind of fiddling somewhere but I just can't nail it down
first I thought it was windows 10 making the sensors read all wonky but I checked it with intel's own XTU and its reading the same
its like suddenly all the adaptive voltage tables got changed
under windows 8.1 I get a steady 1.2000v under load now suddenly its reading all over the place from 1.180 to 1.27 despite no changes to the bios
edit: as expected switching to fully manual mode does away with the wonkyness

 

[MxPhenom 216]

Easy Solution: Dont use adaptive voltage.

 

[Aquinus]

Huh. I overclock the same way on my 3820 as I always have and it seems to work a-okay. That's with offset voltage and additional boost voltage. I can't seem to hit 125Mhz BCLK anymore but, I don't think that's Windows at fault.

 

[Deleted member 50521]

Well I am stupid. On my ASUS board I thought putting in a fixed vcore will be all it is required. Turns out I have to first enable fully manual mode! Then set the vcore to a fixed value. Otherwise windows 10 will still be able to manipulate the voltage. Also I disabled speedstep and C1E which seems to help as well. I hope such issues maybe addressed by ASUS in a later build BIOS, so energy saving and overclocking can be achieved at the same time.