Asus ROG Zephyrus G16 GA605WI - BIOS Version 310 (Issues with Waking From Sleep)

[ieraydursun]

Since updating to BIOS version 310, when my laptop sleeps, it will get stuck on a black screen with the fans running, power LED solid, and the device will not wake. Disabling hibernation and fast startup does not resolve. Manually rolling back to BIOS version 306 resolves the problem, and I've tried going back and forth a couple times. The issue is only reproducible on BIOS version 310 and happens both on battery and plugged in. The only way to recover is to force shutdown by holding the power button.

I've found no other way to provide feedback on this issue since ASUS Support routes me to Geek Squad since I purchased at Best Buy. Please advise if this is a known issue.

[ieraydursun]

I should also add that Windows and drivers are both up to date, the latter using the official files here: GA605WI - Support

powercfg /sleepstudy doesn't even show the device going into sleep.

[ieraydursun]

Additionally, here's what Windows Event Viewer shows for the time between closing the lid and performing the manual shutdown. It shows the device rebooted at 9:29pm even though I didn't force a shutdown until an hour later at 10:25pm when I noticed the issue:

Level Date and Time Source Event ID Task Category
Error 3/13/2025 10:26:11 PM EventLog 6008 None The previous system shutdown at 9:29:20 PM on ‎3/‎13/‎2025 was unexpected.
Information 3/13/2025 10:25:50 PM Microsoft-Windows-Hyper-V-Hypervisor 165 None "Hypervisor configured mitigations for CVE-2019-11091, CVE-2018-12126, CVE-2018-12127, CVE-2018-12130 for virtual machines.

Processor not affected: false
Processor family not affected: false
Processor supports microarchitectural buffer flush: false
Buffer flush needed: false
"
Information 3/13/2025 10:25:50 PM Microsoft-Windows-Hyper-V-Hypervisor 156 None "Hypervisor configured mitigations for CVE-2018-3646 for virtual machines.

Processor not affected: false
Processor family not affected: false
Processor supports cache flush: false
HyperThreading enabled: true
Parent hypervisor applies mitigations: false
Mitigations disabled by bcdedit: false
Mitigations enabled: true
Cache flush needed: false
"
Information 3/13/2025 10:25:50 PM Microsoft-Windows-Hyper-V-Hypervisor 129 None "Hypervisor initialized I/O remapping.

Hardware present: true
Hardware enabled: true
Policy: 0x1
Enabled features: 0x34A
Internal information: 0x0
Problems: 0x0
Additional information: 0x0"
Information 3/13/2025 10:25:50 PM Microsoft-Windows-Hyper-V-Hypervisor 2 None Hypervisor scheduler type is 0x4.
Information 3/13/2025 10:25:50 PM Microsoft-Windows-Hyper-V-Hypervisor 1 None Hypervisor successfully started.
Information 3/13/2025 10:25:50 PM Microsoft-Windows-Kernel-Boot 27 (33) The boot type was 0x0.
Information 3/13/2025 10:25:50 PM Microsoft-Windows-Kernel-Boot 25 (32) The boot menu policy was 0x1.
Information 3/13/2025 10:25:50 PM Microsoft-Windows-Kernel-Boot 242 (76) SMM isolation detected. Level: 30
Information 3/13/2025 10:25:50 PM Microsoft-Windows-Kernel-Boot 238 (101) EFI time zone bias: 2047. Daylight flags: 0. Firmware time: ‎2025‎-‎03‎-‎13T22:25:47.000000000Z.
Information 3/13/2025 10:25:50 PM Microsoft-Windows-Kernel-Boot 247 (99) Unable to load Pluton-Windows firmware. StatusCode: STATUS_SUCCESS, Reason: Failed to apply firmware.
Information 3/13/2025 10:25:50 PM Microsoft-Windows-Kernel-Boot 20 (31) The last shutdown's success status was false. The last boot's success status was true.
Information 3/13/2025 10:25:50 PM Microsoft-Windows-Kernel-Boot 32 (58) The bootmgr spent 0 ms waiting for user input.
Information 3/13/2025 10:25:50 PM Microsoft-Windows-Kernel-Boot 18 (57) There are 0x1 boot options on this system.
Information 3/13/2025 10:25:50 PM Microsoft-Windows-Kernel-Boot 153 (62) Virtualization-based security (policies: VBS Enabled,VSM Required,Hvci,Boot Chain Signer Soft Enforced,Measured Launch) is enabled due to VBS registry configuration.
Information 3/13/2025 10:25:50 PM Microsoft-Windows-Kernel-General 25 (12) "The system time was initialized to ‎2025‎-‎03‎-‎14T03:25:49.500000000Z.

Loader time: ‎2025‎-‎03‎-‎14T03:25:47.000000000Z
Internal boot flags: 0x2
HAL RTC error code: 0x0
RTC time is in UTC: false
Soft boot: false
Success: true
Phase: 0"
Information 3/13/2025 10:25:50 PM Microsoft-Windows-Kernel-General 12 (1) The operating system started at system time ‎2025‎-‎03‎-‎14T03:25:49.500000000Z.
Information 3/13/2025 9:29:20 PM googledrivefs31626 1 None Wake from sleep detected.
Information 3/13/2025 9:26:20 PM googledrivefs31626 1 None Wake from sleep detected.
Information 3/13/2025 9:25:23 PM googledrivefs31626 1 None Wake from sleep detected.
Information 3/13/2025 9:23:19 PM Microsoft-Windows-IsolatedUserMode 1 None Secure Trustlet \??\C:\WINDOWS\system32\BioIso.exe Id 4 and Pid 38296 started with status STATUS_SUCCESS.
Information 3/13/2025 9:23:19 PM Microsoft-Windows-IsolatedUserMode 5 None Secure Trustlet NULL Id 0 and Pid 0 started with status STATUS_SUCCESS.
Information 3/13/2025 9:23:18 PM Microsoft-Windows-Kernel-Power 566 (268) "The system session has transitioned from 4 to 5.

Reason PolicyChange

BootId: 160"
Warning 3/13/2025 9:23:16 PM Win32k 700 None Power Manager has requested suppression of all input (INPUT_SUPPRESS_REQUEST=1)
Warning 3/13/2025 9:23:16 PM Win32k 700 None Power Manager has requested suppression of all input (INPUT_SUPPRESS_REQUEST=1)
Information 3/13/2025 9:23:16 PM Microsoft-Windows-Kernel-Power 506 (157) "The system is entering Modern Standby

Reason: Lid."
Information 3/13/2025 9:23:16 PM Microsoft-Windows-Kernel-Power 566 (268) "The system session has transitioned from 3 to 4.

Reason PolicyChange

BootId: 160"

[ieraydursun]

Well, I performed ASUS Cloud Recovery (since I already know I'm going to be asked to do that) and the issue persists. Convinced it's the BIOS version 310. Currently using Microsoft PowerToys to keep the laptop awake since Armoury Crate continues to override my screen and sleep timeouts. If I get no response from ASUS soon, I'll be reverting back to 306.

I closed the lid at 12:21pm. The system appears to crash at 12:25pm (random shutdown). Weirdly, it both exited and entered modern standby at the same time at 12:30:53 PM. I assume this is when it becomes unresponsive, but I didn't come back to the laptop until 2 hours later, when I was again greeted with a black screen, fans running, computer warm, battery significantly drained.

Here's the full Windows event logs between these times: troubleshooting sleep issues bios v310.evtx

[Anbby_ROG]

Thank you for providing information.I have forwarded the information to the relevant department.
We will provide you with any new updates as soon as possible.

[Anbby_ROG]

Thank you for your patience!
Our technical team is currently analyzing this issue further. In the meantime, we would like to confirm whether your NVIDIA graphics driver is updated to Version V32.0.15.6607.

If you're using a different version, could you please test with this specific version to see if the issue persists?
Thank you for your cooperation!

[ieraydursun]

I did try that version with the same end result.

[Anbby_ROG]

Thank you for your reply. May I ask if you have tested the sleep issue without running any background software? Does the issue still occur? Or are there usually any specific programs running in the background when the issue happens? Thank you!

[ieraydursun]

It's practically impossible to stop all background apps but even trying to stop everything running in the system tray yields the same results. All I know for sure is that the issue is NOT present in BIOS version 306. I'm planning to revert back.

[ieraydursun]

Any update? This is incredibly frustrating. I've never had a laptop with this issue before. I've also attempted disabling hibernation and fast startup, the issue still occurs.