?!? windows HANGS at P.O.S.T after restart? (have to hard-reset)

[7point5]

so I noticed that only now windows hangs at POST every time I restart (fans running, no signal to monitor)

shutdown goes without a problem, only restart is buggy

2 things:

1) it only hangs after the latest cumulative monthly rollups. before that it would restart normally, signal to monitor would still get cut off but only for a second, then Bios would beep & POST

2) it only hangs if C3 & C6 states are enabled (however before the rollups I could leave them enabled & still restart normally)
which means there's a bug in the rollups (at least the last 2 ones)

so my question is, since disabling C-states is out of the question and since reverting pre-rollup is also out of the question, how can I fix this & have the system restart normally like it used to? :huh:

 

[fireberd]

Just a comment. If it hangs at "POST" (Power On Self Test) that has nothing to do with Windows. Windows hasn't started to load yet.

 

[7point5]

Just a comment. If it hangs at "POST" (Power On Self Test) that has nothing to do with Windows. Windows hasn't started to load yet.

so somehow

- BEFORE installing monthly rollup, Restart works normally

and

- AFTER installing monthly rollup, Restart no long works normally? (no signal to monitor but cpu fan still running)

yet this has nothing to do with windows? so could the monthly rollup somehow alter the bios itself or something???

 

[fireberd]

o I noticed that only now windows hangs at POST every time I restart (fans running, no signal to monitor)

By that statement it hangs up at the Power On Self Test. If this is true then yes it has nothing to do with Windows as its just going through the self test and then the BIOS takes over but even that is not loading Windows.

However, if its really getting by the POST and the BIOS, and hanging up not loading Windows then it could be something in the update. Try starting in Safe Mode (Press F8 before Windows starts to load) and if that starts, you can try a system restore before the updates.

 

[mrjimphelps]

If you shut down first and then restart (as opposed to just restarting), do you have the same problem?

 

[7point5]

By that statement it hangs up at the Power On Self Test. If this is true then yes it has nothing to do with Windows as its just going through the self test and then the BIOS takes over but even that is not loading Windows.

However, if its really getting by the POST and the BIOS, and hanging up not loading Windows then it could be something in the update.

it hangs before the "bios beep" (which happens before POST & before signal to monitor returns right?)

Try starting in Safe Mode (Press F8 before Windows starts to load) and if that starts, you can try a system restore before the updates.

that's the thing I want it to restart normally without uninstalling something as critical as the monthly rollups

 

[7point5]

If you shut down first and then restart (as opposed to just restarting), do you have the same problem?

nope like I said the windows shutdown ("acpi shutdown" as they call it) still works normally after the monthly rollup so I can do a clean shutdown then turn on the PC again as usual

only the direct restart is buggy after the monthly rollup
(and even then, only when C-states are enabled in bios. disabling those allows a normal restart, but then why disable them now when I didn't have to disable them before the monthly rollup?)



so to sum it up Windows 7 + monthly rollup + C-states* = no restarting

basically the monthly rollups are somehow incompatible with C-states

* C3 & C6 only. I can still leave C1 enabled & have a normal restart, even after monthly rollup

 

[Bat 1]

Bat just wondering what led you to disable c states to try to fix the problem ? Something specific to your configuration (Not Listed) that was posted elsewhere ?

 

[7point5]

Bat just wondering what led you to disable c states to try to fix the problem ? Something specific to your configuration (Not Listed) that was posted elsewhere ?

no I just tried changing different bios settings till something worked ^^

then again I shouldn't have to disable the Cstates now since I didn't need to disable them before the monthly rollups

 

[Ranger4]

This website might help you with the Cstates & what the various setting do.

Everything You Need to Know About the CPU C-States Power Saving Modes | Hardware Secrets

 

[7point5]

This website might help you with the Cstates & what the various setting do.

Everything You Need to Know About the CPU C-States Power Saving Modes | Hardware Secrets

cool thx

which one is necessary to significantly reduce cpu voltage while idle? (say when on desktop, when not gaming or not compressing or anything)

is C1 enough or do others like C3 & C6 further reduce vcore voltage when on desktop? I wanna reduce it to the max to preserve cpu life (since cpu voltage kills even faster then cpu clock speed)


and more important how can I fix this? (restart normally without having to disable C states and without uninstalling the monthly rollup)

 

[Ranger4]

There were problems with Windows Updates to do with Meltdown & Spectre & some changes made by MS to prevent infection from Meltdown that became a problem with certain Anti Virus programs. Could you system be one of those, if so have a look in the News section on this Forum & scroll through looking for Spectre & Meltdown.

 

[7point5]

I also tested on a fresh setup (7 SP1 + SSUpdate + super-rollup + various minor updates) : no antivirus or any other 3rd party apps installed

same problem: before latest rollups, restart works fine
after rollup, restart causes PC to hang at POST (unless I disable most Cstates)



but maybe ur onto something is there some possible connection between the specter/meltdown thingie & Cstates?

 

[Bat 1]

System Info - See Your System Specs - Windows 7 Help Forums

More help might be possible if others know what hardware you have.

That will help you find out your system hardware specs so you can post the specs.

 

[7point5]

iirc it's an old Ivy bridge cpu & 1155 mobo. that said I could test on another different older rig with all Cstates enabled just to see when I've time & I'll post results but I say 10 to 1 the result will be the same so the hardware thing would be a red herring (just a hunch tho)

 

[Bat 1]

Most of the problems caused by Spectre/Meltdown patches occurred on AMD CPUs. There are a few posts I read when someone says I also have a problem on an old Intel CPU. :huh: What kind of problem ? What Intel CPU ? The more nfo someone posts on their problem as well as hardware and software configurations, the easier it is to find a pattern with the problems and be able to report to Microsoft.

Since You posted it's a "Old Ivy Bridge & 1155 Mobo" I'll just guess that you're running in BIOS instead of UEFI and something with fast startup/hibernate couldn't be the problem ? Otherwise as posted earlier, what you're describing is happening Before Windows starts and "shouldn't" be caused by the updates.

 

[7point5]

Most of the problems caused by Spectre/Meltdown patches occurred on AMD CPUs. There are a few posts I read when someone says I also have a problem on an old Intel CPU. :huh: What kind of problem ? What Intel CPU ? The more nfo someone posts on their problem as well as hardware and software configurations, the easier it is to find a pattern with the problems and be able to report to Microsoft.

Since You posted it's a "Old Ivy Bridge & 1155 Mobo" I'll just guess that you're running in BIOS instead of UEFI and something with fast startup/hibernate couldn't be the problem ? Otherwise as posted earlier, what you're describing is happening Before Windows starts and "shouldn't" be caused by the updates.

(no actually I use EFI)

and yet problem only occurs with latest monthly rollup updates (and disappears if I uninstall that update)

usually when a PC restarts there's a brief time when signal is lost to monitor, then signal returns & there's bios/efi beep for the POST. when win7 is updated with the monthly rollup then the screen remains blank without signal & I've to hit hard-reset (unless I disable C3 & C6 states. I can leave C1 enabled)

which means the monthly rollups are incompatible with C3 & C6



but you were right it also depends on config!

I tested on an even OLDER rig (lga1156 with P55 chipset, and classic bios only no efi) and the same win7 works when I restart! so it got nothing to do with age
but the Cstate options are a bit different in tat bios: there's only "enable C1" and "set Cstate limit" (with 3 options: C1 C3 & C6. I guess if I set "limit" to C6 this means all 3 Cstates are enabled?)



so it's only with the ivy bridge setup that it doesn't work so basically it's a combo of 3 things, monthly-rollup + C-states + hardware. watta mess

anyway my main setup (the one with the bug after the monthly rollup) is an old I5-2400 lga1155 cpu on a P67 chipset mobo. win7 was installed in EFI mode, sata mode is set to ahci etc. nothing special



anyway gotta not lose sight of the main problem: even if the bug happens with only 1 config & only with C-states, the main cause is still the monthly rollup
before mrollup: no problem, after mrollup: problem, after uninstall mrollup: no problem

 

[Bat 1]

Definitely a Strange One and I really don't have a Clue