New
#1
monthly rollups partially INCOMPATIBLE with Cstates? (cant soft-reset)
more precisely with C3 & C6 C-states (I can still enable C1 states, or C1E or w/e it's called)
so basically after some testing I noticed that after installing a cumulative monthly rollup (the 2 last ones at least KB4074598 & KB4056894 haven't tested the others) it's impossible to restart the PC normally
shutdown still works, however if I choose 'restart' then windows quits but instead of POST-ing the PC just remains blank: no signal to the monitor, but CPU & fans still running
so I have to hard-reset it (reset button)
the only way to restart it normally without it hanging at POST stage, is to disable C3 & C6 states
and btw I did an integrity test (sfc /verifyonly) no prob there the updates installed normally
now I heard that C states are good cause they're meant to lower CPU voltage during low activity period right? (so longer lifespan since core voltage kills faster than core clock)
so if I only leave C1 & disable C3 & C6 that would mean less efficient Vcore control right?
so why the hell do monthly rollups screwup the Cstates like this by disabling restart?
and more importantly is there any way to make the full C-states work again even with the monthly rollup?
Last edited by 7point5; 17 Feb 2018 at 02:20.