Windows 10: LiveKernelEvent 144 makes my PC go into sleep mode/hibernation then turns off.

Hello.I have been having this error and I have no idea what triggers it. Last 2 errors happen when I was just watching YouTube, the other errors has happen while playing games. My CPU and GPU has never been near overheating and is not OC. All drivers are up to date. My pc specs are:Intel Core i7-13700KF Raptor Lake CPU - 16 cores - 3.4 GHz - Intel LGA1700ASUS PRIME Z790-P Motherboard - Intel Z790 - Intel LGA1700 socket - DDR5 RAM - ATXASUS GeForce RTX 4070 DUAL OC White - 12GB GDDR6X RAMKingston FURY Beast DDR5-6000 C36 DC - 32GB AMD EXPOWindows 10 ProSourceWindowsOverviewHardware failureDat

:)

 

PC gets "stuck" in sleep mode

Hello,

There are many ways to shut down your PC, you can turn the PC off completely, you can make it sleep, or you can hibernate the PC.

Sleep Mode uses very little power, your PC starts up faster, and you’re instantly back to where you left off. You don’t have to worry that you'll lose your work because of your battery draining, because Windows automatically saves all
your work and turns off the PC if the battery is too low.

We would suggest that you follow the troubleshooting on this link to Shut down, sleep, or hibernate your PC. Scroll down and check under
"To make your PC sleep" troubleshooting steps to resolve the issue.

We'll be looking forward for your update.

 

Hibernate mode Vs Sleep Vs Hybrid sleep.

From now on i will use the Hybrid sleep mode and let's hope it works as it should.

 

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!