Monitor constantly "wakes up" when display turns off

I have an Intel NUC Skull Canyon (great device). However, I have one constant problem that I cannot seem to solve.

Whenever the display turns off to power savings mode (Note: I have sleep disabled for the OS, but have monitor set to turn off after 15 minutes), the display will constantly (every few minutes) "wake up" and go from power savings mode to active mode, only to switch back to power savings mode moments later.

This is annoying, in that it forces me to turn off the monitor at night to sleep, and also because after a couple hours of this constantly waking up, the monitor effectively "crashes" and won't turn back on without pulling the power and recycling the monitor.

The monitor is an Auria EQ276W, connected via DisplayPort. The Skull Canyon has an Intel Iris Pro 580 Graphics chipset, and i've tried both the default Windows 10 drivers and the Intel specific ones downloaded from Intel.

This problem isn't new. It's been happening for at least a couple years, through various builds in both the Release and Insider program.

And here's the truly weird part. The issue only presents itself when Windows has been fully installed. If I install a new build, and let it finish and NOT log in (ie i haven't yet gone through the initial "Hello screen") then the problem does not occur. The monitor goes into sleep mode, and it just seems to work correctly.

However, after going through the initial Hello screen, the problem returns.

I have sleep and hibernate disabled. I am running with the High Performance power profile. And again, the OS is not waking up because sleep is disabled.

Does anyone have any suggestions?

I'm not sure what the deal is with that but, it's been commented on quite a bit.
Must be a Windows 10 'background activity' thing, cuz I've got the nircmd 'Turn off Displays' thing installed on both W10 and W7; in W7 the displays stay off, in W10 they always turn back on!

As I said, the display turns off again almost instantly. It's like it wakes up, realizes it's supposed to be asleep and goes back to sleep again. It does this every few minutes (5-10).

You can get a power trace by opening an admin CMD and doing:

Code:

powercfg /energy /trace /d c:\temp /duration 120

Replacing C:\temp with a folder of choice (must exist already) and 120 with the duration you want to trace in seconds. Keep track of the time(s) that the monitor comes on.

This will create an .etl file you can open in Windows Performance Analyzer. Look at Device Dstate around the times the monitor turned on and see if there are any D-state transitions from your display.



This will at least tell you if Windows is responsible for the screen turning on or if it's something from the hardware.

sorry for the necro. hopefully you see this mystere. I'm assuming you never found a solution? I found this thread with a generic search for intel displayport keeps waking, and to my surprise, I see we have the same monitor.. This is a recent development for me, and seems to be an intermittent issue. Sometimes, it blips on every minute. Others, it wakes pretty much immediately and incessantly. And every now and then, it's completely problem-free.

I'm imagining this is just a defect with the monitor. I'm running a multimonitor setup, and none of the other ones are affected (both igpu and not).

i have been dealing with this issue for about 2 months. after reading 1000 help articles and even reaching out to microsoft, your post FINALLY showed me what's happening. my stupid mouse, even though the driver has "allow this device to wake up the computer" unchecked, was waking up the computer immediately after it was going to sleep. thank you PolarNettles for this as the analysis showed me immediately that my mouse was the culprit!

PolarNettles said:

You can get a power trace by opening an admin CMD and doing:

Code:

powercfg /energy /trace /d c:\temp /duration 120

Replacing C:\temp with a folder of choice (must exist already) and 120 with the duration you want to trace in seconds. Keep track of the time(s) that the monitor comes on.

This will create an .etl file you can open in Windows Performance Analyzer. Look at Device Dstate around the times the monitor turned on and see if there are any D-state transitions from your display.



This will at least tell you if Windows is responsible for the screen turning on or if it's something from the hardware.

Hey Guys,

This is happening to me too!
It only happens on a DisplayPort connection; I've changed the monitor, cable and reinstalled Windows 10 and 11.
Strange thing is, it doesn't do it in Linux.
The sleep report shows the graphic card is waking up then going back to sleep instantly.

PolarNettles said:

You can get a power trace by opening an admin CMD and doing:

Code:

powercfg /energy /trace /d c:\temp /duration 120

Replacing C:\temp with a folder of choice (must exist already) and 120 with the duration you want to trace in seconds. Keep track of the time(s) that the monitor comes on.

This will create an .etl file you can open in Windows Performance Analyzer. Look at Device Dstate around the times the monitor turned on and see if there are any D-state transitions from your display.



This will at least tell you if Windows is responsible for the screen turning on or if it's something from the hardware.

Hey, man. How to read this? Please tell more!

I've had this problem for years.

Turns out the cause was because I changed a registry setting called Remove Sleep option from Start > Power with this registry setting, which is a group policy setting called Computer Configuration > Administrative Templates > System > Power Management > Sleep Settings > Allow Standby States (S1-S3) When Sleeping (Plugged In) = [DISABLED]:

Code:

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Power\PowerSettings\abfc2519-3608-4c2a-94ea-171b0ed546ab]
"ACSettingIndex"=dword:00000000

The default for this setting on my Win10 22H2 is:

Code:

[-HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Power]

Stated differently, the default ACSettingIndex is NONEXISTANT.

You can safely delete the Power key UNLESS there are other values inside it besides ACSettingIndex. In that case, just delete the value ACSettingIndex.