Laptop is the Acer v15 Nitro (vn7-592g-71zl) with a Samsung 960 Pro NVMe M.2 drive. It's running all of the latest firmware (Bios, thunderbolt, etc). I am running an external monitor (does not matter if HDMI or DP, same results) for a desktop configuration with the laptop lid closed and pushed off to the side.
When the laptop goes to sleep (automatically, balanced mode, 30 minutes on AC power), I'll return a while later and move my Logitech m570 wireless mouse (unifying receiver in the USB 2.0 port) to wake the computer. I see the orange standby light change to blue so I know the laptop is resuming, but my backlit USB keyboard does not power back on. It is at this point that the entire system is frozen with a black screen.
The only way to recover from this is to open the laptop and long-press the power button. Here's where I believe the key to discovering what is going wrong occurs and leads me to believe that this is a bios issue with the NVMe support of the M.2 slot. The first time I power the laptop back on, a blue prompt appears something to the effect that no bootable device was found. This occurs every time I hard power-off the device due to this resume from sleep issue. Long-pressing the power button again to turn the laptop off and powering it back on a second time resumes normal operations.
Previously, I had hibernation and hybrid sleep disabled. I've since turned them back on so that the data I had on screen is preserved through all of this.
It is important to note that if I go into Device Manager and adjust the Power Management settings to disallow the mouse to wake the computer, this problem does not seem to happen, at least as often. My laptop sits inside a bracket mounted to the wall with physical security installed -- it is rather bothersome to have to remove it to open the lid every time this occurs. My workaround has been to disable all input devices from being able to wake the computer from sleep, plugging in an Ethernet cable and using a Wake on LAN app on my phone to wake my laptop -- this seems to work 95% of the time.
I have a standard SATA3 Samsung 850 EVO SSD being delivered today that I'll test with, as I suspect the issue resides with the M.2 slot itself. I've found cases where others have experienced similar issues with their M.2 slots populated with an NVMe device (Dell in this case) which was resolved by a Bios update.
Is this a documented/known issue? Any suggestions?