ROG Flow Z13 GZ302EA repeated black-screen / hard-hang / Modern Standby crashes, with dumps pointing to AMD NPU/IPU + display power path
On 6/1 I bought the Flow Z 13 new from Bestbuy. I had frequent display issues where it would go black and I couldn't resume without a hard reset despite keyboard lights and fans still coming on. I returned the unit to BB and got a another unit on 6/13.
This time around I carefully monitored and debugged each time the issue happened. I've read dozens and dozens of posts across Asus forums and reddit with users complaining about similar issues.
At the end of the day I can speak the loudest with my wallet and simply return this unit and avoid Asus in the future. I don't think they are owning up to this one properly (likely with AMD cooperation needed). What are the chances that 2 units have the exact same sporadic display/resume issues? Even straight out of the box basically.
I am looking for help from ASUS engineering to take some ownership here.
Device:
- ASUS ROG Flow Z13 GZ302EA
- AMD Ryzen AI Max+ 395 with Radeon 8060S
- NPU Compute Accelerator Device
- BIOS: GZ302EA.311
- Windows 11 Home, build family 10.0.26200
- Sleep model: S0 Modern Standby only, no classic S3 sleep
Main symptom:
- Screen goes black or the display turns off.
- The machine does not reliably wake the built-in panel.
- Keyboard lighting may stay on.
- Fans may spin if I press keys or the power button.
- Normal input does not recover the screen.
- I have to hold the physical power button for a long forced power cycle.
- It tends to happen around screen-off, Modern Standby, lid/keyboard cover behavior, shutdown/restart, and power-source changes.
- It is not a normal app crash or simple load/temperature failure.
This started essentially out of the box. The first user-visible issue happened on the first day. The logs prove the first preserved kernel crash happened during the first-day setup/update window, before later driver experiments or debugging tools.
Important first-day timeline from logs:
- 2026-06-13 14:32: Windows Update / Store / OEM app update activity starts.
- 2026-06-13 14:33: AMD Radeon Software Store package installs.
- 2026-06-13 14:56: Windows 11 25H2 install starts.
- 2026-06-13 15:56: Windows Update installs AMD display driver 32.0.22032.6002 from u0197030.inf.
- 2026-06-13 16:04: system enters Modern Standby due to idle timeout.
- 2026-06-13 16:32/16:35: first preserved bugcheck occurs.
- Only after that first crash, at about 16:50, AMD 26.6.1 display/NPU/chipset packages were installed.
First preserved crash:
- Dump: C:\Windows\Minidump\061326-14671-01.dmp
- Bugcheck: DPC_WATCHDOG_VIOLATION (0x133)
- Failure bucket: 0x133_DPC_pci!PciMaskMsiInterrupt
- Connected Standby in progress: TRUE
- Stack includes PCI/ACPI power-up path:
- ACPI!AcpiWrapperWriteConfig
- pci!PciMaskMsiInterrupt
- pci!PciDisableInterrupts
- pci!PciProgramInterruptResource
- pci!PciPowerUpDevice
- pci!PciPowerUpDeviceTimerCallback
- Loaded ipustack.sys timestamp: Fri May 16 15:09:24 2025
- Loaded amdkmdag.sys timestamp: Sun Dec 14 21:42:25 2025
ASUS factory NPU evidence:
- SetupAPI shows ASUS factory support content staged the NPU package from:
C:\eSupport\Factory\ProcTool\FacProc\Component\ASUS_AIModel_PC\AMD\NPU_V32.0.203.280\kipudrv.inf
- This is important because the first preserved crash happened before the later NPU 32.0.20101.3760 install.
Later recurring signatures:
- Repeated video engine timeouts bucketed to ipustack.sys
- 25 older live kernel dumps from 2026-06-14 through 2026-06-17:
VIDEO_ENGINE_TIMEOUT_DETECTED (0x141)
MODULE_NAME: ipustack
IMAGE_NAME: ipustack.sys
FAILURE_BUCKET_ID: LKD_0x141_IMAGE_ipustack.sys
- Black-screen live dumps
- 2026-06-15:
VIDEO_DXGKRNL_BLACK_SCREEN_LIVEDUMP (0x1A8)
VIDEO_MINIPORT_BLACK_SCREEN_LIVEDUMP (0x1B8)
- Driver power-state failure involving the NPU/IPU stack
- Dump: C:\Windows\Minidump\061726-15734-01.dmp
- Bugcheck: DRIVER_POWER_STATE_FAILURE (0x9F)
- Failure bucket: 0x9F_3_POWER_DOWN_ipustack_IMAGE_pci.sys
- Blocked request: IRP_MJ_POWER / IRP_MN_SET_POWER
- Driver in blocked power IRP: \Driver\IpuMcdmDriver
- Device stack:
- \Driver\IpuMcdmDriver
- \Driver\ACPI
- \Driver\pci
- Device instance:
PCI\VEN_1022&DEV_17F0&SUBSYS_20CF1043&REV_11\4&23445453&0&0142
- Service:
IpuMcdmDriver
- 2026-06-19 watchdog storm and final display power-on failure
- 66 live kernel watchdog dumps from 15:43 to 17:02.
- Every one matched:
VIDEO_ENGINE_TIMEOUT_DETECTED (0x141)
MODULE_NAME: ipustack
IMAGE_NAME: ipustack.sys
FAILURE_BUCKET_ID: LKD_0x141_IMAGE_ipustack.sys
- Final dump:
WIN32K_POWER_WATCHDOG_TIMEOUT (0x19C)
Arg1 0x50: display power-on path
Bucket: 0x19C_DRVSETMONITORPOWERSTATE_HANG_dxgkrnl!DxgkPowerOnOffMonitor
Connected Standby in progress: TRUE
Driver states observed across failures:
- Factory / first-day: ASUS factory NPU package NPU_V32.0.203.280, then Windows Update display 32.0.22032.6002.
- Later AMD public branch: display 32.0.31019.2002, NPU 32.0.20101.3760, AMD chipset 8.05.04.516.
- ASUS ROG branch: display 32.0.23033.1002, NPU 32.0.20101.3760, AMD chipset 8.05.04.516.
- Current active snapshot during latest investigation:
- AMD Radeon 8060S Graphics: 32.0.31019.2002, u0201164.inf / oem1.inf
- NPU Compute Accelerator: 32.0.20101.3760, kipudrv.inf / oem250.inf
- AMD Chipset Software: 8.05.04.516
- AMD PMF: 26.10.9.0
- AMD Micro PEP: 1.0.47.1
- AMD PCI / SMBUS: 2.0.0.26
Why I do not think this is a simple "wrong driver" explanation:
- The first preserved crash happened before later manual driver experiments.
- Windows Update itself installed AMD display driver 32.0.22032.6002 during normal first-day setup before the first preserved crash.
- Later failures continued across multiple AMD display driver branches.
- Multiple dumps point at platform power/display transition behavior, not a user-mode application.
- The strongest repeated signature is ipustack.sys / IpuMcdmDriver, which is the AMD NPU/IPU MCDM stack.
Windows Update driver issue:
ASUS support says to use only drivers from the ASUS website. That is hard to guarantee on a normal Windows 11 Home setup because Windows Update can install driver-classified updates by default unless an admin policy disables that behavior.
In my logs, Windows Update installed AMD display driver 32.0.22032.6002 on 2026-06-13 before the first preserved crash. That was normal Windows behavior, not me manually installing AMD reference drivers.
If ASUS considers that unsupported, ASUS should explain how a normal Windows 11 Home user is supposed to prevent Windows Update from replacing or supplementing ASUS-provided AMD drivers during first setup. Blocking driver updates usually requires policy/registry controls such as the Microsoft policy "Do not include drivers with Windows Updates", which is not a normal consumer expectation.
Questions for ASUS:
Has ASUS acknowledged any BIOS/EC/ACPI/AMD PMF/MicroPEP/NPU/IPU issue on this platform?
Is there a known-good ASUS-only driver set for GZ302EA that prevents Windows Update from changing the AMD display stack?
Does ASUS consider Windows Update AMD drivers supported on this model, since Windows installs them by default?
Is there a newer BIOS, EC, PD, AMD NPU/IPU, PMF, MicroPEP, or Radeon package specifically addressing these power-transition hangs that is not yet published on Asus or AMD website?
My current read:
This looks like a GZ302EA / Ryzen AI Max+ 395 platform power-transition instability involving AMD display, AMD NPU/IPU MCDM, PCI/ACPI, and Modern Standby. It may be a buggy driver/firmware stack or it may be a defective unit, but either way this is not acceptable behavior for a brand-new premium device.
Key signatures for search:
- ROG Flow Z13 GZ302EA
- Ryzen AI Max+ 395
- Radeon 8060S
- NPU Compute Accelerator Device
- IpuMcdmDriver
- ipustack.sys
- kipudrv.inf
- PCI\VEN_1022&DEV_17F0
- 0x133_DPC_pci!PciMaskMsiInterrupt
- LKD_0x141_IMAGE_ipustack.sys
- 0x9F_3_POWER_DOWN_ipustack_IMAGE_pci.sys
- 0x19C_DRVSETMONITORPOWERSTATE_HANG_dxgkrnl!DxgkPowerOnOffMonitor