Windows 10: Cannot login to the PC after resuming Windows from Sleep/Hibernate mode

Hello,


I am having the following symptoms:


After resuming windows by pressing the power button of my laptop on some occasions I see:

- The windows booting screen

- Then it disappears and I see either my desktop/login background (its the same so I cannot tell which one it is) or a green screen (my colour scheme) or a black screen.

- if I try moving my mouse, it works, but there is nothing but my mouse, and it uses the cursor set for the last user logged in

- waiting for up to 20 minutes does not yield anything



This happens about 70% of the times I try to resume. As I cannot do everything I have to hard reset my laptop to get into windows again. This is bad as I lose all unsaved data.

Please note that I do not have any problem turning on the computer. Just the login mask does not appear. Please do not give me tips regarding turning on the laptop as this works flawlessly.


I have found some events in the event manager from the time when I tried resuming windows last time. 11/01/19 16:20 UTC

"NvAPI_GPU_GetBrandType failed with code=-1" from NVWMI. I could not find any other that seem relevant.



Cheers sirati



***Original title: Log in mask does not load after resuming from either standby or hibernate [not consistently]***

:)

 

sleep or hibernate

I think you have sleep and hibernate confused... sleep just puts the computer in a low power state, making resuming the session faster... hibernate shuts down the whole computer and basically just saves whats in RAM to the hdd and loads it on next startup. IIRC...

 

Hibernate mode Vs Sleep Vs Hybrid sleep.

Make sure your batteries are good. They need to be regularly replaced every 3 - 5 years. Weak batteries make for an unreliable UPS. *Frown But new batteries are cheaper than a whole new UPS.

Totally disagree with that! No way sleep affects performance. As for stability, on rare occasions, a computer will not properly come out of sleep. Typically a simple reboot resolves that. But once a computer boots properly, sleep mode does not interfere.

Sleep mode is nothing new. Microsoft and the applicable hardware makers have had over 20 years to sort problems out.

Sorry, but that makes no sense. First, hibernation was indeed developed for notebooks - so when you close the lid, you can resume exactly where you left off. Yes, you can use hibernation with a PC and you can use hybrid mode on a notebook But hybrid mode was developed for the PC.

Second, if a user suffers from frequent blackouts they should definitely be using a good UPS with AVR. Note I've lived in Tornado Alley for the last 28 years so I have some experience with that. But more importantly, if a user suffers from frequent blackouts and they don't use an UPS, they should be saving their work and "gracefully" shutdown the computer, not put it in sleep mode.

Lastly, hybrid mode is called hybrid mode because it is just that, a mixture of modes. In hybrid mode, data stays in RAM (in a low voltage state) for faster wake times. But in hybrid mode, a full hibernation file is also created in case the user (or Mother Nature) decides to remove power completely.

Newer versions of Windows are not XP. So true, there is no need to reboot Windows just because it has been awhile since the last reboot. I only reboot my 6 W10 systems when some Windows Update or security program update requires it.

Memory leaks should not be part of this discussion. Those are faults and exceptions, and very rare. Exceptions don't make the rule. If a program is that buggy, get rid of the program.

As for things left in memory, as I noted above data is indeed left in memory to speed up wake times from sleep mode. Remember, unless you unplug the computer from the wall (or flip the master power switch on the back of the PSU - if it has one) your PC is in "Standby mode" and +5Vsb standby voltage is being distributed to multiple points across the motherboard.

If you terminate a program, that memory space is freed up. But if you keep, for example, a Word document open and allow your computer to sleep, some of that data will be retained in RAM for quicker wakes.

See Fred Langa, Is Data Safe in Sleep/Standby/Suspend Mode?

 

Hibernate mode Vs Sleep Vs Hybrid sleep.

I'm starting to lose track of what we're disagreeing on. I can't say what was on the mind of whoever designed the technique in the past, but today it is a tool available to any supporting platform where the users need it. Hybrid sleep is functionally a suspension to disk without clearing the ram, at its core it is a hibernation. Arguing which method is for which platform is -with all due respect- a waste of time. I would agree to the argument that Hybrid sleep is more versatile than simple hibernation, though, but that doesn't make hibernation a non valid method of suspension on desktops. And if someone intended for long down-times or expected power loss, the differences between hibernation and hybrid sleep become inexistent.

For the frequent blackouts part, we have to consider the scope of the issue here: whoever opts to use any suspension method, hibernation, sleep or hybrid sleep, does so explicitly to avoid shutting down the computer (for whichever reason they wanted). Anecdotal example: I'm off to work in the morning, but I do not want to close all the software and web pages I have open (and they can be many) and restart them later, so I have the choice of either sleep or hibernate (or hybrid methods), but with any S state less than 4, I run the risk of a blackout forcing me to what I avoided shutting down for, so I elect to use hibernation (or hybrid sleep, of which the hibernation part is what's needed).

A UPS is indeed a must have, but alas, not all of us live in the first world!

VRAM isn't wiped post-wake up, per se. The only way to wipe the entire memory is relieving if of power. Hibernation does have that effect in the suspension process (going into hibernation), upon waking up it repopulates the memory with what was occupying it before turning off (though I don't know if it was actually this simple).
What was I referring to in my previous post is Windows' memory manager's functionality. When a process is closed (eg: Alt+F4ed the main window, killed in task manager, etc), all its memory heap is then freed up for other processes to use. So, any memory that is used when a computer wakes is for actually running processes, waking up won't reserve memory for anything else (other than hardware, I guess?)

Computers can be weird. I once had a recurring issue with Microsoft's Security Essential where it starts eating up all my ram after waking up from sleep. And I'm talking about 20GB of physical memory! Still don't know what caused that bug though. Couldn't reproduce it in later Windows installations on the same hardware either.
And don't get me even started on those cheap Chinese hardware!