Weird hibernation state on reboot attributed to Win7 patches

Topic

New Reply

We have two reports of Win7 hibernation (?) problems after installing recent Win7 Monthly Rollups. An anonymous poster: I installed KB 4074598 on my W
[See the full post at: Weird hibernation state on reboot attributed to Win7 patches]

5 users thanked author for this post.

Elly, JDeC, Tiernan, Microfix, weedacres

Reply | Quote

Replies

I have the same problem on a HP Z210 Workstation after installing KB4056894. It’s running a Sandy Bridge i7-2600. I normally have this machine reboot every morning and shortly after installing KB4056894 my customer started complaining that it was hanging up after the morning restart.

Symptoms are a black screen, no mouse and no response to keyboard. I have to force a power off then power backup with no problem. After removing KB4056894 it never fails.

I don’t know at this point if I can change the C-State settings in the HP bios but will give that a shot when I can get some system time.

Thanks for the heads up, I thought this was the only system in the world with this problem.

Dave B

3 users thanked author for this post.

Elly, woody, Microfix

Reply | Quote

Pretty sure this has happened before due to a rogue MS patch, although I won’t can’t test due to write cycles on our SSD’s.

Windows - commercial by definition and now function...

Reply | Quote

Looks like the problems started with the January Monthly Rollup, KB 4056894, and continue with this month’s Monthly Rollup KB 4074598. It seems to impact both Intel and AMD chips.

So, if my Windows 7 machine didn’t have this problem after installing January’s KB4056894, do I need to worry about it occurring after I install February’s KB4074598?

Reply | Quote

Good question. I don’t know the answer.

Reply | Quote

I’m wondering if the January Security Only update kb4056897 causes the problem as well?

I’d be happy to not install the cumulative update if the security only update works.

There was reference to removing both kb4056897 and KB4056894 in here:

https://answers.microsoft.com/en-us/windows/forum/windows_7-performance/windows-7-hangs-on-reboot-after-applying/ea13e25f-f41c-4067-93c0-f249857ed018?auth=1&rtAction=1518720538402#

but they didn’t say if they were both installed or separately installed.  It’ll be a couple weeks before I can get system time so I cant test for awhile.

Dave B

Reply | Quote

Doesn’t seem to have anything to do with hibernation, just that some power saving CPU feature has a bug with another botched update.

Ideally you would have all of your CPU low power features enabled since they have virtually no performance impact. (in some cases of typical use it can allow to the CPU to cool faster between turbo boost and actually increase performance).

Reply | Quote

weedacres wrote:

I’m wondering if the January Security Only update kb4056897 causes the problem as well? I’d be happy to not install the cumulative update if the security only update works. Dave B

I was wondering the same thing.  I am still in Group B, and installed the 4056897 (security only) on two machines, and have not seen this problem.  Can we assume it is imbedded in the cum rollups but not in the security only updates?

1 user thanked author for this post.

JDeC

Reply | Quote

dwindstr wrote:

Can we assume it is imbedded in the cum rollups but not in the security only updates?

No idea.

Reply | Quote

I am in group B and installed the security only update on my OLD win 7 AMD machine and have had none of the afore stated problems.  It must be embedded in the monthly rollup only. As to the MS attitude toward Win 7, they put the half baked updates out and we can take it or leave it.

Reply | Quote

I definitely have the restart hang problem on the Dell Inspiron 620 desktop computer using an Intel Sandy Bridge i5-2500 CPU with at least either KB4056984 or KB4056897 for Win7 SP1 installed. KB4074598 for Win7 SP1 does the same thing as well.

This does not seem to happen with my bro’s Sony laptop using Win7 SP1 and the Intel Arrandale i3-380m processor. and my aunt’s Dell Inspiron 580 machine also using Win7 SP1 with an Intel Clarkdale i5-680 processor is also not affected by the KB4056894/KB4056897 & subsequent updates.

2 users thanked author for this post.

woody, weedacres

Reply | Quote

Did you try the C-state juggling detailed here?

https://www.computerworld.com/article/3216425/microsoft-windows/microsoft-patch-alert-februarys-fixes-arent-as-bad-as-last-month-but-problems-abound.html

Reply | Quote

I`m not your usual user.  Group A.  Since I only use it for email, browse and print I shut it off completely every use.  When  I start it back up some times it stays black screen in which case I  turn the power switch off and turn it back on and it starts normally.  Win 7 x64, AMD.  As you say started doing it  January.

1 user thanked author for this post.

woody

Reply | Quote

My understanding is that the reboot hang only effects Sandy and Ivy Bridge Intel processors. They were manufactured in 2011 & 2012, so if you have something older or newer it might not effect it.

I have about 30 Windows 7 pc’s that I take care and as far as I know, only have the problem on the HP Z210 which is the only Sandy Lake PC. The other thing that is somewhat unique is that it has 2 RAID arrays running off of the Intel chipset.

3 users thanked author for this post.

Elly, woody, alpha128

Reply | Quote

weedacres wrote:

My understanding is that the reboot hang only effects Sandy and Ivy Bridge Intel processors. They were manufactured in 2011 & 2012, so if you have something older or newer it might not effect it.

Thanks for the information.

I have an Intel Haswell processor, which is a generation after Ivy Bridge, and two generations after Sandy Bridge.

So hopefully, this won’t be an issue for me.

Reply | Quote

I have several Haswell PC’s running Windows 7. None of them have had this problem.

Reply | Quote

I was a bit incomplete on my symptoms.

Only fails during Restart. All restart messages are normal and when I’d expect to see the HP logo I get a Black screen, no mouse, no response to keyboard, fans running, power light on.

The only way to recover is to force a power off and then power on. Power on and boot is normal.

 

1 user thanked author for this post.

woody

Reply | Quote

Note to Patch Lady: Win7 Pro x64 Zbook 17 workstation, Haswell Intel i7, etc… Group B and don’t exhibit this issue, touch wood. Would be very useful to have the Security Only .Net updates posted so that we don’t have to go digging for them. Always did roll-ups until a couple of months ago the roll-up took out a lot of imaging programs while the SO version didn’t.

Only a user here and non-techie but rely on this machine for photo editing and RAW development program(s).

With no QC department left in Redmond, MS has become…

Reply | Quote

weedacres wrote:

I’m wondering if the January Security Only update kb4056897 causes the problem as well? I’d be happy to not install the cumulative update if the security only update works. There was reference to removing both kb4056897 and KB4056894 in here: https://answers.microsoft.com/en-us/windows/forum/windows_7-performance/windows-7-hangs-on-reboot-after-applying/ea13e25f-f41c-4067-93c0-f249857ed018?auth=1&rtAction=1518720538402# but they didn’t say if they were both installed or separately installed. It’ll be a couple weeks before I can get system time so I cant test for awhile. Dave B

Only one or the other can be installed. This the way that the Monthly Rollups work, versus the alternative monthly Security-only updates, and vice versa. It appears that either update can cause this issue.

3 users thanked author for this post.

weedacres, Elly, woody

Reply | Quote

GoneToPlaid and others:

For what is worth, I installed kb4056897 a week ago, and have had no problems starting Win 7, Pro, SP1, x64, in my machine with an Intel Sandy Bridge CPU circa 2011, or had any other kind of trouble that I have noticed, since then.

 

 

Ex-Windows user (Win. 98, XP, 7); since mid-2017 using also macOS. Presently on Monterey 12.15 & sometimes running also Linux (Mint).

MacBook Pro circa mid-2015, 15" display, with 16GB 1600 GHz DDR3 RAM, 1 TB SSD, a Haswell architecture Intel CPU with 4 Cores and 8 Threads model i7-4870HQ @ 2.50GHz.
Intel Iris Pro GPU with Built-in Bus, VRAM 1.5 GB, Display 2880 x 1800 Retina, 24-Bit color.
macOS Monterey; browsers: Waterfox "Current", Vivaldi and (now and then) Chrome; security apps. Intego AV

Reply | Quote

Same here, except for one random Windows Explorer crash which I initially thought might have been related to this update, yet it turns out that it was not. Yet note that I do not use hibernation on my Win7 computers. With this update or the equivalent monthly rollup, properly awakening a computer from hibernation is the issue, depending on what power level states are set in the computer’s BIOS, and in conjunction with specific generations of Intel CPUs.

Reply | Quote

I have several Haswell PC’s and have had no problems with the reboot issue.

 

Reply | Quote

I finally updated W10 a few days ago. Last time was in December right after purchasing the PC. One of the first things I do after an install or purchase is turn off hibernation, on all Windows OS, and disable quick boot on 8.x and 10. I have WU turned off again on the sole Windows 10 machine. I prefer a desktop when one is available. The rate of attrition in Redmond will leave me going to a nix distro as 10 is barely out of BETA in my eyes. Microsoft is clearly no longer a consumer oriented company. While Steve Balmer could get on my nerves he did have a passion for his product and his team.

Reply | Quote

weedacres wrote:

My understanding is that the reboot hang only effects Sandy and Ivy Bridge Intel processors. They were manufactured in 2011 & 2012, so if you have something older or newer it might not effect it. I have about 30 Windows 7 pc’s that I take care and as far as I know, only have the problem on the HP Z210 which is the only Sandy Lake PC. The other thing that is somewhat unique is that it has 2 RAID arrays running off of the Intel chipset.

Yes, when I said I hadn’t seen the problem on Group B January update, I am mainly referring to a laptop that is Ivy Bridge which I bought in 2013.  Asus K55A, Intel Core I5 3210M Ivy Bridge 22nm, with 6GB Dual Channel DDR3 RAM.  I also haven’t seen the problem on the MSI FX 603 bought in 2012.  This has an Arrandale.  I have yet to apply January to my two desktops as these are more critical. One is an older Bloomfield 45nm Intel I7, and the other is a 2013 Haswell 22nm with 8GB RAM.  I’ve halted updates at December pending further news on this whole fiasco.

Reply | Quote

For what it’s worth,

I have a 64bit Win7 Dell Inspiron 5520 laptop with a Core i5 Ivy Bridge processor that had KB405689 installed 5 February and it boots and starts-up normally.

Gene

Reply | Quote

Oops, the KB should be KB4056894.

Sorry, Gene

Reply | Quote

Well, as usual in my personal custom I’ve tried to install Preview of Feb2018 Rollup KB4075211 onto win7sp1x64 ultimate laptops of good but pretty old hardware (Intel T9500 & 9300 CPUs + 256MB & 512MB nVidia GPUs) for testing, and now can report basically same issues as of all 3 2018 massive patches – KB4056894 Jan2018 Rollup, KB4057400 Preview of Jan2018 Rollup & KB4074598 Feb2018 Rollup.

1. No fatal OS crashes and/or BSOD;

2. The chaotic ErrorID9020 – The Desktop Window Manager has encountered a fatal error (0x8898009b);

3. When the Spectre protection isn’t (yet ?) supported by hardware but with Meltdown one either enabled or disabled in registry by two keys below:

HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\  DWORD FeatureSettingsOverride (value 2 or 3 = disabled or 0 = enabled)
DWORD FeatureSettingsOverrideMask (value always 3)

There were multiple occurrences of the very much odd & annoying issue of chaotic leftovers of already closed windows in win7 taskbar – both of system windows of win7 itself & windows of applications!

So both items 2 & 3 above seem to be a result of windows graphics component updating but it should be mentioned here that these issues occurred less frequently after install of KB4075211 then before while my one by one testing of KB4056894, KB4057400 & KB4074598.

Anyhow all 4 massive patches of 2018 now removed & put to hidden list. Awaiting for a spring fun from m$.

Rgds,

P.S. These is an issue of this web – no registration email was yet delivered to @hotmail in a couple of hours.

Reply | Quote

anonymous wrote:

P.S. These is an issue of this web – no registration email was yet delivered to @hotmail in a couple of hours.

Sorry that didn’t work seamlessly – we have had a few such reports recently. You might like to email Woody, giving your username and a preferred temporary password, which you can change once you get logged in.

2 users thanked author for this post.

laidbacktokyo, woody

Reply | Quote

anonymous wrote:

P.S. These is an issue of this web – no registration email was yet delivered to @hotmail in a couple of hours.

I have the same problem. No idea why, but automatically generated emails to my askwoody address never arrive — and I’ve checked everywhere.

Simple solution: Send me email. woody@askwoody.com

1 user thanked author for this post.

laidbacktokyo

Reply | Quote

…………….I sometimes have visions of all the e-mails lost in eternity circling the sun. Wonder if aliens read them and try to figure out what our civilisation’s like…………………………….

1 user thanked author for this post.

Elly

Reply | Quote

Hello I’m Hali, I wrote about the Windows 7 issue with the KB patch, I should have shared more info in my first post! So here’s my PC tower info ..though it doesn’t have my CPU fan listed on the site but that shouldn’t matter: https://uk.pcpartpicker.com/list/HjtQ7W

I hope this can be useful in some way as to what parts can be affected, for anyone that might use the same/similar parts to these. I’ve actually gotten through January patches (firstly installing the AMD BSOD fix patch introduced later in the month just to be safe, even with my AV being compatible) with no problems. I kinda went with the Group A route because I didn’t know until recently that Security only patches didn’t add up.. ? I’m still kinda clueless on computers it seems. But yeah January Monthly rollup and such went fine, just February being a problem at the moment!

I also don’t know anything about my motherboard, but everything else seems rather standard I think?

1 user thanked author for this post.

woody

Reply | Quote

Group W since December 2017 patches, no problems, fixing spectre/meltdown seems to more malware than the non-existent malware

2 users thanked author for this post.

Microfix

Reply | Quote

Ditto

Windows - commercial by definition and now function...

Reply | Quote

I’m with Cousinjack. From A to Group W for me. Thanks to info from Woody’s site I was able to bring back two BSOD machines. The January fiasco was the last straw. The scales have finally tipped to the point where unreliable MS Updates have themselves become the malware it proposes to protect us from. My older WIN7 machine has been rock solid and I refuse to take another chance of having MS updates harm it before I replace it next year. I keep a regularly updated system image backup stored on an external HD, also a repair disc. Good AV and best practices. I feel safer with that for a year than letting updates ship me who knows what.

3 users thanked author for this post.

Elly, The Surfing Pensioner

Reply | Quote

For anyone fed up with hibernation, just open a command prompt and execute

powercfg.exe /hibernate off

Reply | Quote

This issue had nothing to do with hibernation in the windows powering sense.

Replace “hibernation” with “strange boot issue”.

Reply | Quote

Those who have hibernation turned off are not affected. And… smart folks turn it off anyway.

Reply | Quote

Well… There was one original poster, and what they refer to as “hibernation state” was a way of describing a non-hibernation relegated boot or POST failure. So I don’t think turning hibernation off would have helped…

Reply | Quote

KB 4056894 (January Update)

I have had the same problem with January’s KB 4056894 update. The Restart function puts the computer into a type of hibernation state. After the 3rd computer did this I uninstalled the update on all computers. I hid the KB 4056894 update and it has not represented itself again ans the hidden update is gone. Strange indeed.

I do not plan on installing KB 4056894 at all as it has disappeared from all 8 computers I look after. MS — get your act together!!!!!!!!!!!

KB 4074598 (February Update)

In process of installing this at the moment without any problems.

All computers are  Intel I5 (Haswell) CPU’s and one I7 running Windows 7  64 bit Pro OS

Maurice Helwig

Reply | Quote

EP wrote:

I definitely have the restart hang problem on the Dell Inspiron 620 desktop computer using an Intel Sandy Bridge i5-2500 CPU with at least either KB4056984 or KB4056897 for Win7 SP1 installed. KB4074598 for Win7 SP1 does the same thing as well. This does not seem to happen with my bro’s Sony laptop using Win7 SP1 and the Intel Arrandale i3-380m processor. and my aunt’s Dell Inspiron 580 machine also using Win7 SP1 with an Intel Clarkdale i5-680 processor is also not affected by the KB4056894/KB4056897 & subsequent updates.

Have you tried disabling C3 & C6 in your Dell 620 bios? About 1/3 the way down on the first page of the thread below, Ben1907 reports some success with that. I have not found those setting the HP Bios’s that I’ve looked at.

https://answers.microsoft.com/en-us/windows/forum/windows_7-performance/windows-7-hangs-on-reboot-after-applying/ea13e25f-f41c-4067-93c0-f249857ed018?auth=1&rtAction=1518720538402#

Reply | Quote

I don’t have such BIOS settings in the Power Management section with the Dell 620, weedacres.

On the other hand, there IS an option in the “CPU Configuration” section in the Advanced menu of the Dell AMI Aptio BIOS called “CPU C6 Report” which was set to Enabled by default. I change this to Disabled, save the changes in the BIOS and the restart hang problems go away with the KB4056894 & KB4074598 updates.

Reply | Quote

Hi Woody, Just saw the “SCARD_E_NO_SERVICE” bug and looked a the link in your comments about the bug.  Here is what Microsoft states:

“The LSM.EXE process and applications that call SCardEstablishContext or SCardReleaseContext may experience a handle leak. Once the leaked handle count reaches a certain threshold, smart card-based operations fail with error “SCARD_E_NO_SERVICE”. Confirm the scenario match by reviewing the handle counts for LSM.EXE and the calling processes in the process tab of Task Manager or an equivalent application.
Monitor the handle counts for the LSM.EXE process and the calling process before and after installing this update. Restart the operating system that’s experiencing the handle leak as required.
Microsoft is working on a resolution and will provide an update in an upcoming release.”

Not being a computer guru, I am definitely of the opinion of  not installing this and wait for a future release to fix it.  Any body got a solution yet or do we have to wait for Microsoft?

Reply | Quote

I’ve been hit by the restart/hang problem on an old legacy hardware tower I’ve kept around for playing a few old games I still like. System POSTs normally, then… nothing. Fans are spun up, but no input from mouse or keyboard, LCD backlight is on indicating video output but screen is blank. Hard reset & power on/off does not lead to a successful boot. No C-state bios settings to play with on this old mobo, not even sure such an old setup even has them. The only fix for me was a reinstall which stopped short of KB4074598.

ASRock K7S41Gx mobo / AMD Athlon XP3200+ / 2GB RAM / ATI9700 gfx card / Windows 7 Home Premium 32bit

The culprit is definitely 2018-02 Security Monthly Quality Rollup for Windows 7 for x86-based Systems (KB4074598).

2 users thanked author for this post.

amraybt, MrBrian

Reply | Quote

N00b user here explaining my experience of this situation…it differs slightly as the black background white cursor hand is not endless…well, windows does come through at least but is unuseable.

I have been driven to post here by teh frustrattion of teh hang/slow go patch which has enveloped my 8yr old tower and also (newer) Dell laptop. I think it is teh patch as uninstalling it has allowed me to attain semi-steady states, BUT I AM thinking it could be a graphics bug as it keeps coming back even though I have removed the patch.

1. long windows Welcome Spiny circle on password entry

2. Black screen white cursor which eventually logs on (minutes…on but is PC unusuable as glacial in performance e.g. no point in trying)

3. Hard Reset

4. Safe mode runs find with networking, so Feb security and Jan Security update removed there. Turned updates OFF in windows update

5. Updates still happened(!) so used DOS command C:\>sc config wuaservstart= disabled

6. Can now log on, but after every sucessfull log on there has been the error repeating  itself

I had nearly reached a steady state where 1 in 3 boot ups work.

My last action taken now has been to disable
C6 Report [enabled]

as described above to see if this stops the need to boot 3 times. I will keep you posted if it solves it. Antivirus is turned off (Bitdefender, interstingly) ater restart so I have a bunch of  confusing symptoms of a problem.

Specs:

MB: ASUSTeK Computer INC. P6X58D-E (LGA1366) (Was unable to find Motherboard via WMIC command but Speccy tells me..)

Processor: Intel Core i7 930 @ 2.80GHz

Bloomfield 45nm Technology

(my BIOS is erm..ancient…)

Windows 7 Home Premium 64-bit SP1

12GB RAM

1024MB ATI AMD Radeon HD 5800 Series (XFX Pine Group)

Edit to remove HTML from cut/paste operation.

 

 

Reply | Quote

FWIW – turning C6 off has meant every log on succssful so I guess that is a fix(!).

Dell Laptop..ermm no “updates” since 2015 apparently, yet still displaying very similar symptoms but that is most likley to be a coincidence.

Reply | Quote

KB4074598 caused the boot stall just short of windows splash. Wound up doing a clean install of Win 7 32-bit. I discovered system restore would repair it, so after the first massive updates, started picking out a few at a time until problem happened again.

Booted with the installation USB drive and picked Repair computer and System restore. Listed were two drivers that were restored: MS(HIDClass) 6/21/2006 reverted from 6.1.7601.24014 to same date, 6.1.7601.18199. Also MS(System Devices) 6/21/2006 reverted from 6.1.7601.24000 to 6.1.7601.17514. These may not be the root of the issue, but were all that were listed in the restore log.

Reply | Quote

For those of you that are having this problem on an HP, here’s the setting to disable C-State in the HP Bios:

It’s in    Power > OS Power Management > Idle Power Savings (change from “Extended” to “Normal”), Extended is the default.

This resolves the issue with restart hangs after installing KB4056894 (January Rollup).

2 users thanked author for this post.

Cascadian, MrBrian

Reply | Quote