Wake up from sleep different

Topic

New Reply

Hi all and happy New Year, using Win 7 Home and a Microsoft internet keyboard with a sleep button. For many many years now I would push the sleep button and Windows would go to sleep. Very nice. To be awakened the ESC key is used. The desktop would come up as it was before the sleep. This worked for a long time ( years). Now there is a change, when the Computer sleeps overnight, like me, using the same awakening procedure the screen comes up but says start windows normally and it will. This prompt never happened before. Does anyone have any ideas how to correct this behavior? I have not done anything in the settings to cause this. Regards Peter

Reply | Quote

Replies

Please describe the screen you get. It sounds like it’s crashing.

Reply | Quote

Hi gsmith-plm, the screen I get is the windows screen saying start windows normally, safe mode, etc. same as if you had hit f8 at start up. Regards Peter

Reply | Quote

Hi gsmith-plm, the screen I get is the windows screen saying start windows normally, safe mode, etc. same as if you had hit f8 at start up. Regards Peter

Then something is happening when or during the time your computer is sleeping. It’s definitely crashing since the screen you are getting is a reboot screen.

I suggest that you start by putting your computer to sleep then waking it after 5-10 min to see if it behaves properly. If it does not, then it’s crashing when you try and put it to sleep.

If it does behave correctly in the above test, then put it to sleep and note the time. When you return to it in the morning, if it gives you this screen, then once it’s running again, check your event logs and see what happened between the time you put it to sleep and the time it rebooted.

BTW, is your computer set to hibernate after it has slept for a period of time?

Reply | Quote

Hi Sudo15 and gsmith-plm, shutting down and restarting did not clear the concern. However, it appears that the Computer is not shutting down properly. Why I don’t know.
The event viewer shows fault Kernel-Power over and over event 41 catagory 63. There was no power loss or loose connections. Yesterday there also was a HAL fault which says memory fault in first 100 MG. I do not know what is causing these problems all of a sudden unless Windows update did something to my older machine. The HAL fault suggested to get a update to the bios from Manufacturer. There is no update available to my old Asus A8N Sil motherboard.”The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly”. This is the message. Other than this issue the Computer is running just fine. Any help is appreciated. Regards Peter

Reply | Quote

Yesterday there also was a HAL fault which says memory fault in first 100 MG.

I would zero in on this, as it suggests you might have a faulty memory module. Run the Windows 7 memory test utility, which I find works well. Use:

Start | Control Panel | Administrative Tools | Windows Memory Diagnostic

This will run for a while, up to an hour or so. Your computer will not be usable during this time.

Reply | Quote

I would zero in on this, as it suggests you might have a faulty memory module. Run the Windows 7 memory test utility, which I find works well. Use:

Start | Control Panel | Administrative Tools | Windows Memory Diagnostic

This will run for a while, up to an hour or so. Your computer will not be usable during this time.

One thing to remember when running Windows Memory Diagnostic Tool is that it can only map a max of 4GB and should just be run on one module at a time, as with any other memory testing tool.

Reply | Quote

Thank you, BHarder and Sudo15 . I will do the Memory tests and report back. Regards Peter

Reply | Quote

One thing to remember when running Windows Memory Diagnostic Tool is that it can only map a max of 4GB…

Actually, the 4GB limit applies to 32bit Windows, not 64bit (the 32bit limit is less than 4GB, about 3.25GB).

Win7 Home 64bit can use up to 8GB RAM; Win7 Pro & Ultimate 64bit can use up to 32GB RAM. AFAIK it is much the same w/ Win8/8.1 & Win10.

I have used “Windows Memory Diagnostic” in the past but prefer to boot from a Memtest86 CD to run RAM tests (not “Memtest86+”, which apparently hasn’t been updated since 2013 – I just downloaded the latest Memtest86 v7.2 dated 13 December 2016).

Reply | Quote

Hi Sudo15 and BHarder, the problem was with the memory module. The Mem test showed a hardware fault. As the Computer was very old 2009 and the case power-switch failed as well I replaced the Motherboard along with CPU and new Memory also new case. So a new Box. It all behaves different now so I am getting used to UFI and Skylake CPU. The sleep issue is now resolved regarding the shut down fault. Thank you all for the help. Regards Peter

Reply | Quote

After selecting Normal Startup, have you tried doing a proper shutdown for every thing to clear and then see how it performs.

Probably best to perform a cold boot which is done by removing all power sources then hold the power button in for ~30secs.

Reply | Quote

I wonder if it has created a Memory Dump….

Download BlueScreenView to see if that can find any.

http://www.nirsoft.net/utils/blue_screen_view.html

Reply | Quote

Hi Sudo15, I downloaded the nirsoft program but it shows nothing. Thank you for helping. Regards Peter

Reply | Quote

I wonder if it’s the keyboard sleep button ?

Can you give the keyboard a blow out with a can of compressed air – or do you have another kb you could plug in ?

Reply | Quote

Hi Sudo15, I have tried a different keyboard same thing. What I did do was re3membering that all was OK before the Microsoft updates. I went and uninstalled KB3210136 and so far all is well again for now. I will wait to see what the overnight result will be. The other thing KB 3210136 did was to set the sound of my game Kate West the vanishing files, to zero and reduced the screen size of the game to much smaller. This no longer happens. I will let you know how it goes tomorrow. The KB stated was just one of several updates dating from Dec. 2016. Maybe I got lucky picking the correct one first time in. Regards Peter

Reply | Quote

I went and uninstalled KB3210136 and so far all is well again for now.

This is actually quite weird, as it suggests a sensitivity to a specific software patch. Yet as a hardware error you never expect that; the hardware problem should exist regardless of the software you run.

This suggests that perhaps the problem was latent and it took a specific piece of software to reveal the problem.

You learn something every day, if the day is a good one!
:^_^:

Reply | Quote

Dreaded WUs again – do you have your WU settings set to let me choose to prevent it dropping in again ?

Reply | Quote

Hi Sudo15, no luck its doing it again started already yesterday . The system was OK for about 5 sleep and wake ups and then the problem started again and stayed as before. The event viewer show Kernel power error: The system did not shut down properly, many times the latest this morning. I do not know why it was OK for the 5 times yesterday and then reverted. I uninstalled the Keyboard driver and let windows find it again, no luck. Something in the system is preventing a correct sleep shut down. The problem with the Game is staying fixed.Regards Peter

Reply | Quote

Can you check to see if reliability history is reporting anything ?

I wonder if it’s worth disconnecting from your SSID through the Wifi icon before the sleep ?

Reply | Quote

Hi Sudo15, my Computer is hard wired into the router. No wifi icon. No wifi connection. How do I do that if needed? Where is the reliability history? Regards Peter

Reply | Quote

Just disconnect the Ethernet cable.

I was wondering if something was maintaining a connection to home when it shouldn’t.

To view the reliability history, go Start – start to type reliability then press enter when you see View reliability history highlighted.

Reply | Quote

Hi Sudo15, thanks for your continued help. Disconnecting the SSID did not change anything. So I am going to restore the C: drive from a backup. I wil let you know how that turns out. Regards Peter

Reply | Quote

Hi Sudo15, the restore C: drive did not fix the problem. So for now I am going to leave it as is. I don’t know what to do anymore. To sum up, when shutting down the Computer from the start,(bottom left), shut down option, all is well. It starts normally then. When using the sleep button on the keyboard or from the start location sleep option and then waking up using the ESC key it starts with the save mode, start windows normally screen. Event viewer then says windows did not shut down properly. Thank you for all the help. Regards Peter

Reply | Quote

I’m out of ideas as well other than perhaps resetting the power plan config.

Go Start – type cmd then right click on cmd and select Run as administrator – accept the UAC and enter –

powercfg -restoredefaultschemes

exit

Reply | Quote

So will you be upgrading to Win 10 now ?

Google has some articles on MS’s end of support for Skylake CPUs on older Windows versions.

You can still get Win 10 free.

Reply | Quote

So will you be upgrading to Win 10 now ?

Google has some articles on MS’s end of support for Skylake CPUs on older Windows versions.

You can still get Win 10 free.

Hi Sudo15, no I will stay with Win7 as I am used to how it functions. Regards Peter

Reply | Quote

Okay.

After a bad experience first time around with Win 10 last year, I swore off it until 2020 but having had another go this year, I much prefer 10 to 7.

If you do decide to upgrade then before doing so, go into the BIOS and change the Boot order to check DVD and USB before SSD/HDD but you can change things back to Win 7 ways so that the F keys will function as they do in Win 7 by right clicking on the Start button – select Command Prompt (Admin) and enter –

bcdedit

Then using the Identifier which could be either {default} or {current} enter –

bcdedit /set {Identifier} bootmenupolicy legacy

shutdown /r /t 00

To change back, use standard instead of legacy – and remembering to create recovery disks (if OEM machine) and a system image onto media that won’t be used for any other images should things not work out with Win 10 and then you will be able to factory reset then restore with the image.

Reply | Quote