SER9 sleep terminated by Lidstate open

yamamotoy

Problem with SER9 sleep.

My SER9 only can be in sleep state for 3minutes. It wakes up without having any user input such as moving mouse nor wake on lan packet.
I use the following to see what made the SER9 wake up from sleep

powercfg /sleepstudy /duration 1

The log showed that wake up event was “LIDSTATE OPEN”
Please tell me how to prevent “LIDSTATE OPEN” happening.
Problem with SER9 sleep.

powercfg /sleepstudy /duration 1

The log showed that wake up event was “LIDSTATE OPEN”
Please tell me how to prevent “LIDSTATE OPEN” happening.

MiniDog

Check your power settings in the Settings menu. Have you opened your case?

yamamotoy

Dear MiniDog-san,

Thanks for reply. Please tell me more.

Which power setting?
1) Power Setting inside Control Panel of Windows 11 do not show option for Lid Open.
2) If setting is for BIOS, please navigate me to the correct setting.

2.I have not opened the case.
1) Is there a sensor inside the case to detect case open?

Because SER9 is a desktop PC, it very strange to see LIDSTATE open event

support6

yamamotoy
Hello,

① Are you using any USB devices other than the keyboard and mouse? If so, please unplug them.
② Are you using a screen splitter?
③ Go to power option and restore the plan management to default values.

Best regards!
Wendy
Customer Support

MiniDog

yamamotoy
Some BIOS consider these as glorified laptops. I had an issue with the screen but is under buttons and lid (screen) opening (LID SWITCH) all under power buttons.

Mine no longer shows this as Microsoft keeps reshuffling these setting! You still may have missed a sleep timer.

Regards

kaws

i’m debugging something similar on a large x299 workstation. it is irritating.

to enable the lid options in powercfg, from an admin cmd prompt:
to enable “lid” and button tabs:
powercfg -attributes SUB_BUTTONS 99ff10e7-23b1-4c07-a9d1-5c3206d741b4 -ATTRIB_HIDE

this seems to help as “lidopen” is causing less waking, however this has not solved my problem.

support7

kaws
Please send us a picture of SN on the bottom of the PC.

Here are some potential solutions:

① Disable the virtual lid sensor

Open the device manager and expand the “System Devices” category
Look for drivers with “Lid”, “GPI” or “ACPI Sensor” in their names (such as “ACPI Lid Sensor”)

② Right-click and select “Disable Device”, then restart and test the sleep state

Power setting correction
powercfg /setacvalueindex SCHEME_CURRENT SUB_NONE lidopen 0
powercfg /setactive SCHEME_CURRENT

③Please press delete key as soon as you turn on the PC, so that you can go to BIOS.Please send us a picture of the Main page.We will check if you need to update the BIOS.

podgabe

Dear Support!

The same thing happens to me with a bunch of SER8s. They are on the same network, and they wake every 60 minutes from sleep.
powercfg -systempowerreport reports System Event Log entry: LidState: Opened. Obviously, the devices have no lid. I haven’t opened any of them. They all wake at the exact same moment every hour, so it’s possible some network packets get translated as a wake/lid open. I need to have wake-on-lan functionality, including broadcast wake, but these hourly wakes imply faulty behavior.
I explicitly disabled waking on lid open in power settings. powercfg -q SCHEME_CURRENT SUB_BUTTONS report (all lid open/closed actions are disabled):

Power Scheme GUID: e9a42b02-d5df-448d-aa00-03f14749eb61  (Ultimate Performance)
  Subgroup GUID: 4f971e89-eebd-4455-a8de-9e59040e7347  (Power buttons and lid)
    GUID Alias: SUB_BUTTONS
    Power Setting GUID: 5ca83367-6e45-459f-a27b-476b1d01c936  (Lid close action)
      GUID Alias: LIDACTION
      Possible Setting Index: 000
      Possible Setting Friendly Name: Do nothing
      Possible Setting Index: 001
      Possible Setting Friendly Name: Sleep
      Possible Setting Index: 002
      Possible Setting Friendly Name: Hibernate
      Possible Setting Index: 003
      Possible Setting Friendly Name: Shut down
    Current AC Power Setting Index: 0x00000000
    Current DC Power Setting Index: 0x00000000

    Power Setting GUID: 99ff10e7-23b1-4c07-a9d1-5c3206d741b4  (Lid open action)
      GUID Alias: LIDOPENWAKE
      Possible Setting Index: 000
      Possible Setting Friendly Name: Do nothing
      Possible Setting Index: 001
      Possible Setting Friendly Name: Turn on the display
    Current AC Power Setting Index: 0x00000000
    Current DC Power Setting Index: 0x00000000

    Power Setting GUID: a7066653-8d6c-40a8-910e-a1f54b84c7e5  (Start menu power button)
      GUID Alias: UIBUTTON_ACTION
      Possible Setting Index: 000
      Possible Setting Friendly Name: Sleep
      Possible Setting Index: 001
      Possible Setting Friendly Name: Hibernate
      Possible Setting Index: 002
      Possible Setting Friendly Name: Shut down
    Current AC Power Setting Index: 0x00000000
    Current DC Power Setting Index: 0x00000000

One product sticker shows:

9B.3600834NB0
SN:B87454BH4****
SER8-L-321TBVK0W64PRO-DP/XA/O

I have been trying to debug this issue on and off for quite a few weeks now. Thanks for your help.

Some additional information: the root cause seems to be the GPIO driver which faultily wakes the devices. Other users on this forum reported high usage as well. The “AMD GPIO Controller” (ACPI\AMDI0030 amdgpio2) system device drives the “GPIO Laptop or Slate Indicator Driver” HID device (ACPI\AMDI0081 msgpiowin32.inf), which seem to be the culprit for both the high usage and the intermittent waking of the device as per a faulty “lidstate open” in event log. Given the AMD driver is the standard driver (not Beelink-specific at all), either the HID driver, firmware or BIOS is probably ultimately at fault. Finally, it is not possible to disable either driver, Device Manager shows no “Disable device” option (and other tools like pnputil will also fail to disable them). Uninstalling the driver will just postpone the issue because it will be automatically reinstalled in the background.

support7

podgabe

①: Please press delete key as soon as you turn on the PC, so that you can go to BIOS. Please send us a picture of the Main page. We will check if you need to update the BIOS.

②: Driver layer processing

Force blocking driver automatic installation (administrator privileges required)
pnputil /disable-device “ACPI\AMDI0081”
pnputil /disable-device “ACPI\AMDI0030”

If access is denied, you need to use the Group Policy Editor (gpedit.msc) to disable automatic driver updates.

③: Power policy correction.Disable all network wake-up functions (Note: Be cautious when retaining LAN wake-up)
powercfg /devicequery wake_armed
powercfg /devicedisablewake “device name”

podgabe

Huh -
pnputil /disable-device ACPI\AMDI0030\0 /force, then reboot. This disables the constant wakes, probably also the power draw issues.

However, (at least) some network features, like Wake-On-WLAN seem to stop working when this is done. So, until a reasonable support solution, you can do the above if you don’t mind WOWLAN not working, I guess.

podgabe

Thanks for the reply, @support7.
① No need, I have the latest BIOS (5.29, 10/23/2024). I’m not even sure you offer an upgrade for these devices. And I’m also sure that blindly trying to update the BIOS wouldn’t fix anything. Either these are known issues resolved in a BIOS update or they’re not.

② As I stated, you have to also use \force to disconnect these devices (ACPI\AMDI0030\0 at least), then reboot.

Disabling only ACPI\AMDI0081\0 doesn’t solve the issue.
Disabling ACPI\AMDI0030\0 does seem to prevent the intermittent wakes, but also kills Wake-On-WLAN. Which I need for remote management of the devices (as they are advertised to have the feature).

③ powercfg /devicequery wake_armed doesn’t even list the WLAN device (Intel AX200). It lists the following devices:

USB4 Root Router (1.0)
HID Keyboard Device
Realtek Gaming 2.5GbE Family Controller

Disabling all of them doesn’t fix the intermittent wake issues either (besides me losing the feature to wake the device from keyboard, obviously). All devices still wake every 60 minutes from sleep, every time, synchronized.

Seeing as all devices wake exactly every 60 minutes, I suspected a scheduled task, but no relevant scheduled tasks are active. I also disabled GTK rekeying on both the router and the WLAN device’s advanced settings, still didn’t help.

I believe you have a rogue driver that somehow routes WLAN through GPIO (which, I believe shouldn’t be the case) and misinterprets some system interrupts as being wake signals.

The only workaround that seems to “work” is to force disable the GPIO driver; which breaks WoWLAN functionality (even though these should not be connected).

support4

podgabe
Hi there.
1.
Please try some solutions here :
Disable Fast Startup
In Control Panel, click the Power Options. Select the Choose what the power buttons do. Uncheck the “Turn on fast startup.”, click save changes.
2.
Please check the save energy in the device manager—universal serial bus controller–USB hub—properties–power management—check “Allow the computer to turn off the device to save power”

podgabe

support4 Thank you, I’ll test these and get back with my findings. Testing is slow unfortunately because of the 60 minutes for each try.

support10

podgabe

Hello there,

We will wait for your reply~

If you have any questions , please feel free to contact us.

Have a nice day!

podgabe

support10 Thanks for the suggestions, here are my findings:

Disabling Fast Startup didn’t help.
Turning the checkbox “Allow the computer to turn off the device to save power” off results in a weird scenario where the PC does wake intermittently but now the display doesn’t turn on (during these times). By running powercfg -systempowerreport I can see that the system actually transitions to a higher-power state and the USB root (whichever ones are allowed to) does take up significantly more energy, so it really is kept on. Somehow these settings seem correlated. In the power report, I found the following:
- Before unchecking “Allow the computer to turn off the device to save power”, the device rotated between “Active” - “Screen Off” - “Sleep” states indefinitely. During this time, the power report reported “Power button” as being the culprit of bringing the device out from “Sleep” state every 60 minutes. “Active” state didn’t report an entry or an exit reason.
- After unchecking said checkbox, the devices now seem to rotate between the “Sleep” - “Screen Off” (no more “Active” state), but the report shows higher power draw on the USB hub. I only have a keyboard and mouse attached to the devices beside the monitor. The power report now shows PDC Task Client: Maintenance Scheduler as potentially causing the wakes.

So, to summarize, the issue might be caused by a combination of some weirdness in drivers, power consumption and a maintenance task (possibly Windows Update or scheduled maintenance related).

support7

podgabe

Thank you for your efforts.Please try to reinstall the system.

Pls backup your data firstly, re-installing the system will make your data in your pc lost.Here is the tutorial: https://url.bee-link.cn/74zu

podgabe

support7 This is a highly customized enterprise image. I reinstalled multiple times, the issue persists.

support7

podgabe

Sorry for inconvenience to you.

Please try without using the USB device (USB hub) to see if the problem exists.