Windows 10: windows slowdown at return from sleep mode and hibernate

Windows 10 Pro 1909 (OS Build 18363.535)
MSI GE73 Raider RGB 8RE

since about the December cumulative update for windows 10, when I wake the system, the login screen is acting like I am running windows on a 20 year old machine, not one less than a year old. the cursor severely lags, any sound that plays (i.e. the logon sound) is broken up, like the system is under heavy load, and trying to enter any keyboard input (pin code or password) is severely delayed. once I login to windows, the issue disappears. windows becomes responsive and the input lag disappears as well. looking at the event viewer the problem seems to lay with the lock screen app (which surprised me. I would have thought the locking mechanism of windows would have been built into the system, not relying on an app). I am seeing some strange error messages that give no real info on what went wrong with the app. has anyone else encountered this issue? is there a way to solve it? or do we have to wait for M$ to fix what they broke?

error messages seen in event viewer:


Fault bucket 2218673995797537995, type 5
Event Name: MoAppCrash
Response: Not available
Cab Id: 0
Problem signature:
P1: Microsoft.LockApp_10.0.18362.449_neutral__cw5n1h2txyewy
P2: praid:WindowsDefaultLockScreen
P3: 0.0.0.0
P4: 00000000
P5: StackHash_0000
P6: 0.0.0.0
P7: 00000000
P8: 00000000
P9: PCH_84
P10:
Attached files:
\\?\C:\Users\\AppData\Local\Temp\WERB00E.tmp.WERDataCollectionStatus.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB36A.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB9D4.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBAAC.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC490.tmp.txt
These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Microsoft.LockAp_196ccb5fca52dd6d6a1 038fc51d341a75da856_6df23506_0b05746a-9635-4d12-ac52-1d09d6cf15c4
Analysis symbol:
Rechecking for solution: 0
Report Id: d9240c33-70c7-4c28-a905-70c3b8a1dc6c
Report Status: 268566528
Hashed bucket: c9207e59cf82a3c1aeca503e7fe8a4cb
Cab Guid: 0

Faulting application name: bad_module_info, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0x00000000
Fault offset: 0x0000000000000000
Faulting process id: 0x39b0
Faulting application start time: 0x01d5b38674e30b7d
Faulting application path: bad_module_info
Faulting module path: unknown
Report Id: d9240c33-70c7-4c28-a905-70c3b8a1dc6c
Faulting package full name: Microsoft.LockApp_10.0.18362.449_neutral__cw5n1h2txyewy
Faulting package-relative application ID: WindowsDefaultLockScreen

I have run chkdsk on all my disks (C:, D:, and E
I ran both the standard 'chkdsk x:' command as well as the 'chkdsk /scan /perf x:' command (replace x: with drive letter, i.e. c
i have run sfc /scannow
I have also run DISM /online /cleanup-image /checkhealth
no issues were found

as an extra step due to the windows feature involved, I also ran a scan with MBAM premium and ESET Smart Security Premium.
No threats were found.

I also ran MRT which reported no threats found

editing the registry too disable the lock screen as per instructions from here :

How to disable the Windows 10 lock screen - TechRepublic

seems to make the issue disappear. however this is only a workaround. I would like a fully functional Windows OS, not one where I have to turn off features in order for it too work properly.

:)

 

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!

 

Hibernate mode Vs Sleep Vs Hybrid sleep.

I normally just use sleep mode, though when I'm at my parent's house, I will use hibernate just because it doesn't matter if we have a blackout

 

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?