Recovery continuing to happen when laptop should be sleeping

Jdeats,

The F12 is to be pressed when you start the computer to enter Boot https://dell.to/39H4Vzh can surely send us a video of the stuck keys. Make a video of the stuck keys and upload it to Google Drive or Dropbox. Also, Windows 10 sleep mode is different than previous versions of Windows on how it works

What is Modern Standby and how does it differ from S3 Standby

Microsoft introduced Modern Standby in 2012 to improve battery life and the transition between power states, allowing Windows PC’s to transition between on/off states faster, like your smartphone does.

When you wake up your phone, it is instantly ready to go. Your email, messages and notifications are up to date because, even with your phone asleep, it's still connected and updating itself, all without a big hit to the battery life. Modern Standby is Microsoft's effort to bring similar instant-on readiness to Windows systems.

Technical differences:

S3, the traditional standby model triggers the system to power down the CPU along with all power consuming components and peripherals while data are retained in the system memory (RAM). The system only knows two states: on and off. The path to sleep takes longer with the system waiting until all components powered off.

Modern Standby in comparison uses a gradual process to increase battery life. Components are powered down when they are not used, allowing a quicker transition between sleep and resume.

User Experience:

Modern Standby systems show some distinct behaviors compared to S3 when operating on battery.

Hibernation: the system hibernates automatically based on battery drainage by monitoring the Battery Tipping Point (BTP). Users can change hibernation time out manually in Windows Advanced Power Options.

Display brightness: Display brightness adjusts automatically, based on battery level.

Resume: The system resumes from Modern Standby by

pressing the power button briefly or opening the lid

wake words for a personal assistant (e.g. Cortana or Alexa for PC)

Connecting and removing peripherals

Network signals from Bluetooth, Wi-Fi and Ethernet

System approach (walk up) if the system is equipped with a Near Field Proximity (NFP) sensor

Screen Flicker: Some users describe “screen flickering” when the system resumes from stand by. This can occur when the device is equipped with an HDR capable screen. Once the system reaches the desktop the system should be back to full screen resolution and any “flickering” should cease at that time.

Happy to report that this issue has been resolved to my satisfaction. I believe there could still be an underlying bug in the firmware... Steps I formed to get to resolution

1. Went into BIOS settings on the G5 and under power section, disabled the laptop auto powering on when the lid is open. This setting does not seem to impact sleep mode as the system comes alive as desired when the lid is open and its in sleep. But coming out of hibernation or when powered down I have to take the manual step to hit the power button after opening the lid. This is the normal behavior on most laptops anyway, so I'm ok with it.

2. In my Windows power settings for both on-battery and off-battery I had the system going to sleep (not hibernate) when lid-closed. So I didn't have a scenario configured to allow the system to properly hibernate. In sleep mode the battery continues to drain at a fairly rapid rate. The system could not survive on battery over-night in sleep mode... However, even with power plugged in (I leave my laptop plugged in overnight) when set to just "sleep on lid close" I was consistently getting the blue screen indicating Windows didn't restart correctly.

3.) On support call where Dell remoted into my system device firmware update was applied in device manager. I still don't know which device this was for. Additional RAM and an additional M.2 drive were added to the system within a few days of powering it on, however both RAM and new drive cleared the Dell BIOS diagnostics test and showed to be working, so perhaps the firmware update was for the drive. 

One of the three things above fixed my issue as it's been three days and the problem has disappeared. Much thanks to Dell's support for helping me get to a resolution. It was very frustrating early on. It's possible there is something uncovered here between current BIOS settings and Windows power options that needs to be addressed by Dell for the broader audience. I'm not longer impacted so now out of the game.