Back to Fix Guides All Beelink GTR9 Pro fixes View Beelink GTR9 Pro Specs
Fix Guide

How to Fix Sleep/Wake Issues — System Won't Wake From Sleep or Randomly Wakes on the Beelink GTR9 Pro

Device: Beelink GTR9 Pro · Beelink Added

Causes

  • Modern Standby (S0ix) conflicts with the AMD Strix Halo chipset — the GTR9 Pro defaults to the S0ix (Modern Standby) sleep state instead of the traditional S3 (Suspend to RAM) state. The AMD PSP (Platform Security Processor) firmware on the Ryzen AI Max+ 395 platform has several known bugs with S0ix state transitions, causing the system to enter a deep sleep from which the USB4 controller, PCIe switches, and display outputs cannot properly reinitialize on resume, resulting in a black screen, frozen system, or spontaneous reboot instead of waking
  • Mediatek MT7925 Wi-Fi 7 card power state transition failure — the MT7925 module's PCIe power management implementation has a known incompatibility with S0ix idle state transitions. When the system enters low-power idle during Modern Standby, the MT7925 can fail to complete its D3hot-to-D0 transition on resume, causing the PCIe bus to hang and preventing the entire system from waking properly. Device Manager shows a Code 10 (device cannot start) on the Wi-Fi card after a failed wake, and the system requires a hard power cycle
  • Dual 10GbE Realtek RTL8125BG NICs preventing low-power C-state entry — both Realtek NICs periodically poll the network stack for WoL (Wake-on-LAN) magic packets and ARP/NS offloads even when the system is in Modern Standby. The constant interrupt traffic from two active 10GbE NICs prevents the CPU from reaching its deepest idle C-state (PC10), causing the system to draw excessive power during sleep and sometimes preventing the sleep state from fully engaging — the fans stay spinning and the power LED remains lit despite the OS reporting "Sleep"
  • USB4 host controller driver not releasing display pipelines during sleep — the AMD USB4 controller's display tunneling driver can leave GPU display pipes in a locked state when entering S0ix, and the AMD Radeon 8060S driver does not properly release these pipes during the suspend callback. On resume, the display driver fails to reacquire the pipes, leaving all connected monitors in a black-screen state even though the system is running (the power LED is solid, fans spin, but no video output appears)
  • BIOS USB wake support enabled for all ports by default — the GTR9 Pro ships with "USB Device Wake from S3/S4" enabled for every USB port, including the internal USB ports for Bluetooth and the SD card reader. Any USB device activity (including electrical noise from a connected but idle hub, a mouse laser that briefly drops, or keyboard backlight polling) can trigger a spurious wake event, causing the system to wake from sleep seconds after entering it
  • Windows Update performing maintenance during Modern Standby — the GTR9 Pro's Modern Standby allows background network activity by design, and Windows Update's "update orchestration" can wake the system from S0ix to install updates, then fail to return to sleep if a driver update for the Mediatek or Realtek devices requires a pending reboot, leaving the system running indefinitely with the display off
  • AMD Adrenalin software's "SmartShift ECO" and "Power Saving" features interfering with sleep state negotiation — when these features are active, the AMD driver sends periodic GPU clock adjustment commands to the Radeon 8060S even during S0ix, which prevents the display controller from reaching its lowest power state and causes the system to stall on the wake path when it attempts to reinitialize the GPU at full clock speed from a partially suspended state

How to Fix

  1. Identify the current sleep state. Open PowerShell as Administrator and run: powercfg /a. Look for the line that reads "Standby (S3)" or "Standby (S0 Low Power Idle)". The GTR9 Pro BIOS typically advertises S0ix (Modern Standby) as available. If S3 (traditional sleep) is listed as "Not available because..." with a reason involving "System firmware does not support this standby state," your system is locked to S0ix. If S3 is listed as available, proceed to step 2 to enable it. If only S0ix is available, skip to step 3.
  2. Enable S3 (traditional sleep) in the BIOS (if available). Restart and press Del to enter the UEFI BIOS. Navigate to Advanced → ACPI Settings → look for Sleep State or Suspend Mode. If the option is present, change it from Windows 10/11 Modern Standby to Linux S3 or S3 only. If the option is not visible (locked by firmware), press Ctrl + F1 in the BIOS main menu to reveal hidden options, then check again. Save with F10 and reboot. After enabling S3, run powercfg /a again — you should now see "Standby (S3)" listed as available.
  3. Disallow Modern Standby via Windows (if S3 is not available in BIOS). Open PowerShell as Administrator and run: powercfg /setacvalueindex scheme_current sub_presence standbybudgetpercent 1 followed by powercfg /setactive scheme_current. Then create a DWORD registry key: reg add HKLM\System\CurrentControlSet\Control\Power /v PlatformAoAcOverride /t REG_DWORD /d 0 /f. Reboot. This tells Windows to treat the GTR9 Pro as a non-modern-standby (desktop) device and fall back to S3-compatible idle behavior even though the BIOS only advertises S0ix. After rebooting, run powercfg /a to verify that "Standby (S3)" now appears.
  4. Disable Wake-on-LAN on both 10GbE NICs. Press Win + X → Device Manager → expand Network adapters. Right-click the first "Realtek PCIe 2.5GbE / 10GbE Family Controller" → Properties → Power Management tab → uncheck Allow this device to wake the computer and uncheck Allow the computer to turn off this device to save power. Repeat for the second Realtek NIC entry. Then go to the Advanced tab and set Wake on Magic Packet to Disabled and Wake on Pattern Match to Disabled for each NIC. This stops the 10GbE controllers from generating interrupt traffic that blocks deep C-state entry during sleep.
  5. Configure USB selective suspend and wake settings. Open Device Manager → expand Universal Serial Bus controllers. For each "USB Root Hub" and "AMD USB 3.20 eXtensible Host Controller" entry: right-click → Properties → Power Management tab → uncheck Allow this device to wake the computer. Keep "Allow the computer to turn off this device to save power" checked — this allows USB selective suspend but prevents USB port noise from triggering wake events. Pay special attention to any "USB Composite Device" entries related to keyboard or mouse — unchecking the wake option for these prevents accidental wake from desk vibration or mouse movement.
  6. Disable Mediatek MT7925 Wi-Fi power saving in Device Manager. Expand Network adapters, right-click "Mediatek MT7925 Wi-Fi 7" → Properties → Power Management tab → uncheck Allow the computer to turn off this device to save power. Then go to the Advanced tab and set Power Saving Mode to Disabled (or the most aggressive power-saving off setting). In the Advanced tab, also set Wake on Wireless LAN to Disabled. This prevents the MT7925 from trying to renegotiate its PCIe link state during S0ix transitions, which is the most common cause of the "fans spin, no display, need hard reset" wake failure.
  7. Disable AMD Adrenalin SmartShift ECO and Power Saving settings. Open AMD Software: Adrenalin Edition → Performance → Tuning. Under Power, set SmartShift ECO to Disabled. Under Display, turn off Vari-Bright and Power Saving. Then go to Settings → System and disable Radeon Chill and Radeon Boost if they are enabled. These AMD power management features interfere with the system's sleep state negotiation by sending periodic GPU management commands that keep the Radeon 8060S display controller partially active during S0ix, preventing clean sleep entry and exit.
  8. Identify what is waking the system. Open PowerShell as Administrator and run: powercfg /lastwake. This shows the device that triggered the last wake event. Common results include: "Realtek PCIe GbE Family Controller" (a 10GbE NIC), "HID-compliant mouse" (a USB device), "High Definition Audio Controller" (HDMI audio from a connected display), or "Mediatek MT7925 Wi-Fi 7" (Wi-Fi wake). Run powercfg /devicequery wake_armed to see all devices currently allowed to wake the system. For any device listed that should NOT wake the GTR9 Pro (e.g., mouse, keyboard, network), disable its wake capability using Device Manager as shown in steps 4–6 above. Then run powercfg /deviceenablewake "Device Name" for devices you want to keep wake-enabled but need to check their wake behavior.