Display fail to wake up (system reboots / igdkmdn64.sys) after display timeout on Windows 11 25H2 and clean 24H2 via HDMI

Question

System Specifications:

CPU: Intel Core Ultra 9 285K

Motherboard: ASUS ROG Maximus Z890 Hero

Display: ASUS PG27UCDM OLED (Connected via HDMI)

GPU Driver: Intel Arc / Graphics Driver (Version 8864)

Issue Summary: The system fails to restore the display-wake signal after a display timeout (screen off). Instead of waking up, the system encounters a TDR / driver initialization error and forces a system restart.

Testing History & Steps Taken:

Initial Setup (Windows 11 25H2 Fully Updated): The issue occurred consistently after display timeout.

Clean Installation (Windows 11 24H2): Formatted the system drive completely. Installed stock Windows 11 24H2 with zero third-party tuning, antivirus, or background applications. Installed official ASUS chipset drivers and the latest Intel Arc graphics driver (8864).

Result: The exact same failure persists. When the display turns off, moving the mouse/keyboard fails to wake the monitor; the system eventually reboots.

Crucial Clarification: This is NOT a System Sleep Mode issue. The PC itself remains running; it is strictly a Monitor / Display Timeout Wake failure over HDMI.

Intel Customer Support closed my ticket, claiming they tested full system sleep and advised me to contact Microsoft, attributing this to a "system-level Windows configuration issue."

Diagnostic Evidence:

• OneDrive Logs & Reproduction Videos: <PII removed> and <PII removed>
• Minidumps: Recent dumps point to igdkmdn64.sys during display power state transitions.
  [ Minidump Onedrive Link : Moved to Private Message ]

Could the Microsoft OS Kernel & Display Engineering teams please investigate whether this is an ACPI/Display Power State transition bug or an Intel TDR driver recovery defect on Windows 11?

Answer 1

Hi,

Thank you for protecting my personal information and analyzing the minidump file.

To answer your questions:

1. Driver Version: I am using the official, latest Intel Graphics Driver (Version 8864) directly from Intel’s website. Rolling back to outdated Windows Update drivers or lower display resolutions is not a viable long-term solution for high-end hardware.

Display Interface: The monitor is connected via HDMI, which is an officially supported primary interface. Re-cabling to DisplayPort is not feasible in my current setup, and HDMI display-wake state transitions must function reliably.

Manual Sleep vs. Display Timeout: When I put the PC into Manual System Sleep (via Start Menu -> Sleep), the system wakes up fine. The issue occurs specifically during Display Timeout (S0 Idle Display Off) when only the screen turns off due to inactivity, triggering a TDR / igdkmdn64.sys driver crash upon wake-up attempts.

Feedback Hub: I have already submitted a full diagnostic report with logs via Feedback Hub as well.

Since your analysis of the minidump explicitly points to an Intel driver defect, I am forwarding your official assessment directly to Intel Customer Support to pursue a driver-level fix.

Thank you for your support.

Answer 2

Hello Ufuk Özen,

Welcome to Microsoft Q&A forum.

Since this is a public forum, we will hide your personal identifiable information, and I have sent that video of yours containing your personal identifiable information in a private message so we can work together to resolve the issue. Also, please check your private message in case you want to share another screenshot to avoid leaking your PII by click on the Private Message button. Also, since this is a public forum, engineering team don't regularly check it. If you want to submit the issue directly to them, please use the Feedback Hub app.

Based on the description and the minidump file, this point to Intel driver defects or its interaction with the platform. In this case, I'm not sure which edition of driver you are using, but can you try to go to Intel website and download the driver from there? If that doesn't help, you can try the driver from Windows update.

Also, can you please try to test with another monitor connection (Display port for example)? And can you please try to lower the display settings and try again as well?

Lastly, may I know if this happen if you put the computer to sleep proactively instead of waiting for timeout?

I'm waiting for your reply.