How often do the lockups when entering sleep occur? In other words, how many times can you Sleep/Hibernate your system before a lockup occurs?
On all Windows systems, there are memory leaks. A process requests memory resources from the OS to do a job and is supposed to free those resources back to the OS when finished, or when the application is shut down. However, due to poor coding, some processes may fail to release the memory they are allocated. As a result, they use more and more memory over time.
Eventually, one of 2 things will happen, a) the OS runs out of memory (typically this is the Nonpaged Memory pool, a special pool of memory used by the OS that is a smaller subset of total RAM) and the system locks up or BSOD's, or more commonly, 2) the memory is freed and recovered by the OS on a system restart.
When you Sleep or Hibernate a system, the current memory snapshot is saved and read back into RAM on Resume. Since this is not a Restart, the leaked memory is stilll held by the errant process and is not freed to the OS. More and more memory will be consumed by the errant process until a Restart occurs.
Your habit of only Sleeping or Hibernating your system will ALWAYS end in a lockup due to leaked memory. It is only a matter of time...
If you launch Task Manager and configure it to show Nonpaged Memory in use, the number of Handles, or number of GDI Objects in use by a process, and sort them in descending order by these fields, the processes leaking memory or specific memory objects will rise to the top of the list over time. There are better methods of identifying processes that leak memory if you search the Internet.
Once an errant process is identified, a case can be opened with the developer of the program that uses the process to initiate a code change to resolve the issue. This is a never-ending battle as the OS and other 3rd Party drivers are constantly updated, resulting in new memory leaks.
My recommendation is to a) attempt to identify the errant process if you only get a couple of Sleep/Hibernations before lockup, or b) throw a System Restart in every few days to allow the OS to recover leaked memory.
If the lockup only occurs when you Hibernate the system, you could try recreating C:\HIBERFIL.SYS, where the memory snapshot is stored, by disabling Hibernation from an elevated Command Prompt using
powercfg -h off, to delete the file, then enabling Hibernation with
powercfg -h on to recreate hiberfil.sys.
Some programs may just not play nice with Sleep/Hibernate. That's why I asked you what programs are in use when you initiate it. If you could identify such a problem program or process through trial and error, simply shutting the problem program down before Sleep/Hibernate could work around your lockup issue.
G74SX-A1 - stock hardware - BIOS 202 - 2nd Monitor VISIO VF551XVT
