3 weeks ago - last edited 3 weeks ago
Hi guys,
Same issues here: Made a post: ROG Strix Scar 16 / RTX 5090 – nvlddmkm.sys Crashes with External Monitor · Issue #47 · Zephkek/Asus...
Hardware
Laptop: ASUS ROG Strix Scar 16 (2025)
GPU: NVIDIA RTX 5090 Laptop GPU
External Monitor: ASUS ROG XG27UCDMG (4K 240 Hz, HDMI 2.1)
- BIOS: v327 (latest)
Windows 11: Fresh install, fully updated (twice)
NVIDIA drivers: Latest from ASUS support (v576)
Using G-Helper now in standard mode, optimus in Nvidia and Dynamic Bios. Got more issues in Ultimate and dGPU only.
Problem Description
Frequent BSOD with nvlddmkm.sys (SYSTEM_THREAD_EXCEPTION_NOT_HANDLED, exception code c0000094)
part of the dump(s)
Arg1: ffffffffc0000094, The exception code that was not handled
Arg2: fffff8057766f4fa, The address that the exception occurred at
Arg3: ffffd30f9a91d3a8, Exception Record Address
Arg4: ffffd30f9a91cbb0, Context Record Address
DUMP_FILE_ATTRIBUTES: 0x21808 Kernel Generated Triage Dump FAULTING_THREAD: ffffbf88f9b23080EXCEPTION_RECORD: ffffd30f9a91d3a8 -- (.exr 0xffffd30f9a91d3a8)ExceptionAddress: fffff8057766f4fa (nvlddmkm+0x000000000073f4fa) ExceptionCode: c0000094 (Integer divide-by-zero) ExceptionFlags: 00000000 NumberParameters: 0
Before reboot and crash:
Session "dc3a3596-71e1-45a3-b2ea-39ad5322fe51" failed to start with the following error: 0xC0000022
This event happens every 60 seconds:
Crashes occur: (Black screen, then "pc ran into problem")
Using external monitor (HDMI 2.1) in Edge / Netflix or randomly (Funny thing i got it 3 times in a row when browsing to Netflix...)
After closing games and doing something (switch from dGPU to iGPU probable cause)
Sometimes immediately after display wake / GPU power state changes
Internal laptop display havent tested much
DSC, VRR / G-Sync, and monitor power state seem to influence crash frequency
When rebooting the external display sometimes just wont start or boot, need to duplicate the screen and try several times before it wants to go.
Analysis / Likely Cause
NVIDIA driver encounters GPU power-state race when external monitor is connected, consistent with Zephkek GitHub ROG AML deep dive:
GPU enters impossible state: firmware insists OFF, Windows needs ON → driver thread blocks → 30s watchdog expires → BSOD
Contributing factors: (in my eyes possible)
High-res / high-refresh scenarios require DSC on HDMI 2.1 / DP 1.4
HDMI 2.1 / DP 1.4 bandwidth limitations
VRR / G-Sync active during DSC operation
ASUS PowerSync firmware interaction
Windows / NVIDIA Settings (currently testing)
HAGS (Hardware Accelerated GPU Scheduling) OFF
G-Sync / VRR OFF
DSC ON (Off only gets me 4K at 120Hz ofcourse)
NVIDIA GPU: Optimus + Dynamic in Bios (dGPU + Ultimate gave me alot black screens)
PCI Express Link State: max performance / disabled power savings
CPU: set to 100% performance mode in power plan
Turned off hardware acceleration in Edge / browsers / apps
Custom fan curve applied for stable temperatures (Using G-Helper instead of Armory Crate)
BIOS / Hardware Settings
BIOS GPU mode: Dynamic
Latest BIOS v327 installed (this got my temps up quite a bit) Weird thing is this bios came out end of september, hoping this is not their "FIX" for the stutters and black screen BSOD problems MUX related
Monitor Settings
ASUS PowerSync OFF
Variable refresh rate and G-Sync disabled
DSC ON
Other
Fresh Windows 11 install
Temperature monitoring: "normal" (<85°C) topping/spiking to 95-101°C but its not load-related
Nvidia driver recommended by Asus (v576.65)
Critical recommended drivers from Asus
LatencyMon:
Observations from LatencyMon
ACPI.sys shows very high DPC routine execution times (~34,665 µs), which is extremely high.
Wdf01000.sys (Windows Kernel Mode Driver Framework) also has medium high ISR times (~787 µs).
Dxgkrnl.sys (Direct X graphics kernel) also has medium high ISR times (~910 µs).
High DPC / ISR execution times like this often cause:
Combined with previous nvlddmkm.sys BSODs, these ACPI / WDF delays strongly suggest a power-state / driver handshake issue between the laptop, NVIDIA GPU, and external monitor likely caused by ACPI.sys / BIOS issues: Laptop’s ACPI implementation may be delaying GPU power-on or system wake events.
High DPC from system drivers: WDF or ACPI calls take too long, blocking GPU threads → could trigger the “impossible state” Zephkek described.
External monitor + DSC / HDMI 2.1: DSC + VRR / high refresh rates rely on fast DPC/ISR; any delay can trigger GPU driver timeout / BSOD.
Not sure if related but im also getting 20k "Display-External" Errors:
3 weeks ago - last edited 3 weeks ago
@Slytha
Based on the situation you described, since you mentioned the use of G-Helper which is not an application provided by us, it is recommend following the steps below for troubleshooting and restoration:
1. Please completely remove G-Helper
Go to Settings > Apps to fully uninstall G-Helper and delete its folder.
2. Please download and install Armoury Crate from our download section, and also ensure that the graphics card drivers you install are provided by us:
NVIDIA Graphic Driver Version V32.0.15.7665
Intel Graphic Driver Version V32.0.101.6790
If the issue persists, you may try reinstalling the system to rule out any software-related faults.
[Windows 11/10] How to Reset (Reinstall) the Operating System
Sorry for any inconvenience it may be caused.
2 weeks ago
Why always when i reply, my message is gone when I refresh the page?
2 weeks ago
Hi Falcon2_ROG,
I am a senior IT architect and tried everything to resolve this.
As mentioned before I already did 2 fresh windows 11 installs, I had this problem with armory crate and also with the recommended and critical Asus drivers.
This isnt an issue we can fix, this is most likely a firmware related issue.
I am experiencing critical, repeatable BSODs on my brand-new ROG Strix Scar 16 (2025). The crash is a SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e) caused by nvlddmkm.sys, and I have traced the root cause to extremely high DPC latency in ACPI.sys, which appears to be a BIOS/firmware bug.
I am requesting an urgent escalation to the engineering team for a BIOS/firmware fix
Hardware & Software Configuration
Laptop: ASUS ROG Strix Scar 16 (2025)
GPU: NVIDIA RTX 5090 Laptop GPU
BIOS: v327 (Latest)
NVIDIA Driver: v576 (ASUS Recommended)
Intel Gfx Driver: v32.0.101.6790 (ASUS recommended)
OS: Windows 11 Home (Fresh Install, fully updated)
External Monitor: ASUS ROG XG27UCDMG (4K 240Hz via HDMI 2.1) with Firmware MCM10
Software: Armoury Crate installed
The Problem: BSOD Analysis
The system crashes with a "PC ran into a problem" black screen, most often when using the external monitor, waking the display, or switching GPU power states (e.g., closing a game).
The minidump analysis shows a clear "divide by zero" error within the NVIDIA driver:
BUGCHECK_CODE: 7e
BUGCHECK_P1: ffffffffc0000094 (Integer divide-by-zero)
BUGCHECK_P2: fffff8047e7cf4fa (Address of exception)
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
FAULTING_THREAD: ffffe607e690b040
CONTEXT:
...
rax=0000000000000eff rbx=ffffa38f04bcda80 rcx=ffffe607dfec2338
rdx=0000000000000000 rsi=0000000000000f00 rdi=0000000000000000
rip=fffff8047e7cf4fa rsp=ffffa38f04bcd9b0 rbp=0000000000000000
r12=0000000000000000 ...
Instruction that failed:
fffff804`7e7cf4fa 41f7f4 div eax,r12d
The driver attempted to divide eax (0xeff) by r12d, which was 0. This is a classic symptom of a race condition where the driver expected a value in r12 (e.g., from a power state or clock-speed query) but received 0 because another system process was stalled.
The Root Cause: LatencyMon Analysis
LatencyMon reveals the "smoking gun": ACPI.sys (the Windows driver that interfaces with the BIOS for power management) is experiencing catastrophic DPC latency.
ACPI.sys (ACPI Driver for NT)
DPC Routine Execution Time: ~35,000 µs (This is astronomically high)
dxgkrnl.sys (DirectX Graphics Kernel)
ISR Routine Execution Time: ~910 µs
Wdf01000.sys (Kernel Mode Driver Framework)
ISR Routine Execution Time: ~787 µs
A 35,000µs (0.034 seconds) stall in ACPI.sys is more than enough to cause the race condition. The BIOS (v327) is failing to respond to a power-state request from the OS in time. This stalls the NVIDIA driver, which is waiting for a value. The driver's watchdog times out or the function proceeds with a 0 value, causing the "divide by zero" crash.
This aligns perfectly with research done by others, such as the "Asus-ROG-Aml-Deep-Dive" on GitHub, suggesting firmware-level issues with GPU power states.
Triggers & Other Symptoms
Triggers:
Using the external 4K 240Hz monitor (which requires DSC).
Waking the display from sleep.
Switching from dGPU back to iGPU (e.g., after closing a game in Optimus mode).
Sometimes random, like browsing Netflix (which initiates protected video paths).
Other Symptoms:
Over 20,000 "Display-External" errors logged in Event Viewer.
The external display often fails to initialize on boot/reboot, requiring multiple attempts to duplicate/extend the screen.
Troubleshooting Performed
2x Fresh Windows 11 Installs
Latest BIOS v327 (Note: this BIOS seems to have increased idle/load temps)
NVIDIA driver v576 (from ASUS) and more recent tested
Intel Gfx driver v32.0.101.6790 and more recent tested
HAGS (Hardware Accelerated GPU Scheduling) OFF
G-Sync / VRR OFF
Browser Hardware Acceleration OFF
PCI Express Link State Power Management OFF
BIOS Mode: Dynamic (Ultimate/dGPU mode is even less stable)
This is not a faulty Windows install or a simple driver conflict. This is more than likely a deep firmware/BIOS bug in how ACPI.sys handles power-state transitions for the GPU, especially under high-bandwidth (DSC) loads.
Please escalate this to the firmware engineering team. We need a BIOS update that fixes the ACPI.sys DPC latency.
2 weeks ago - last edited 2 weeks ago
Hi Falcon2_ROG,
This isn't a random crash; it's a specific, repeatable driver bug caused by a race condition, and LatencyMon data points directly to the underlying cause.
The system crashes with a "PC ran into a problem" black screen, most often when using the external monitor, waking the display, or switching GPU power states (e.g., closing a game).
The minidump analysis shows a clear "divide by zero" error within the NVIDIA driver:
The driver attempted to divide eax (0xeff) by r12d, which was 0. This is a classic symptom of a race condition where the driver expected a value in r12 (e.g., from a power state or clock-speed query) but received 0 because another system process was stalled.
Here is the exact sequence of events that matches what i'm seeing:
The Root Cause: LatencyMon Analysis
LatencyMon reveals the "smoking gun": ACPI.sys (the Windows driver that interfaces with the BIOS for power management) is experiencing catastrophic DPC latency.
ACPI.sys (ACPI Driver for NT)
DPC Routine Execution Time: ~34,665 µs (This is astronomically high)
dxgkrnl.sys (DirectX Graphics Kernel)
ISR Routine Execution Time: ~910 µs
Wdf01000.sys (Kernel Mode Driver Framework)
ISR Routine Execution Time: ~787 µs
A 34,000µs (0.034 seconds) stall in ACPI.sys is more than enough to cause the race condition. The BIOS (v327) is failing to respond to a power-state request from the OS in time. This stalls the NVIDIA driver, which is waiting for a value. The driver's watchdog times out or the function proceeds with a 0 value, causing the "divide by zero" crash.
This aligns perfectly with research done by others, such as the "Asus-ROG-Aml-Deep-Dive" on GitHub, suggesting firmware-level issues with GPU power states.
Triggers & Other Symptoms
Troubleshooting Performed
2x Fresh Windows 11 Installs
This is not a faulty Windows install or a simple driver conflict. This is a deep firmware/BIOS bug in how ACPI.sys handles power-state transitions for the GPU, especially under high-bandwidth (DSC) loads.
Please escalate this to the firmware engineering team. We need a BIOS update that fixes the ACPI.sys DPC latency.
Thanks,
Kind regards,
Kevin
2 weeks ago
@Slytha
I sent you a message, please check it.
Thank you.
2 weeks ago - last edited 2 weeks ago
Hi @Slytha If you haven't done so already via @Falcon2_ROG can you please provide a memory dump and AsLogDumpTool log and send it to me?
You can find the AsLogDumpTool on your devices at the following path. Simply double-click the file and share the generated .wim log C:\Program Files\ASUS\AsLogDumpTool\AsLogDumpTool2.exe
Currently unable to replicate.
Thanks
2 weeks ago
Hi @Silent_Scone @Falcon2_ROG ,
I have messaged you both the .wim file generated by the AsLogDumpTool.
My issue seems highly related to: GitHub - Zephkek/Asus-ROG-Aml-Deep-Dive: A deep dive into the ACPI.sys DPC latency problems on Asus ...
Also made a post at Intel & Nvidia:
[BUG] 0x7E BSOD in nvlddmkm.sys (Div | NVIDIA GeForce Forums
Kind regards,
Kevin
2 weeks ago
Hello! I have a similar problem on a Scar 18 2025 g835lw 32gb ram/5080/1tb with BIOS 327. With BIOS 325, the problem with switching between integrated and discrete graphics was partially resolved in the BIOS with the DGPU option, but after standby, the laptop would sometimes reboot due to an ACPI error. With BIOS 327, it's even worse and more frequent. I've been struggling with this for three days now, testing the laptop. This includes a clean system installation and installing every latest driver from Intel's website. Integrated graphics drivers are 32.0.101.8247, and discrete NVIDIA drivers are 32.0.15.8257 (581.57). The power plan is set to Balanced. I'd really like this issue resolved so I don't have to return the laptop to the store. Thank you.
2 weeks ago
My initial problem was a nvlddmkm.sys BSOD, which I traced to a catastrophic ~34,000µs DPC latency stall in ACPI.sys.
I have two major issues to report, both of which seem to point to this same ACPI/firmware root cause:
Issue 1: Chronic Intel-Gfx-Display-External Errors
Even when the system was "stable" (i.e., not hanging), I have been logging thousands of Intel-Gfx-Display-External errors in my Event Viewer. These errors have been happening constantly, even when the system would eventually crash with the NVIDIA driver BSOD. This suggests the underlying problem has been affecting the Intel iGPU driver all along.
The description for Event ID 10 from source Intel-Gfx-Display-External cannot be found... The following information was included with the event: 32.0.101.6790 (This is the Intel driver version)
Issue 2: The New System-Wide "Zombie State"
Today, I experienced a new, more severe failure that confirms the problem is a total platform stall.
• I started a benchmark. The dGPU (NVIDIA) on my external monitor engaged.
• The external monitor instantly went black.
• I waited 60 seconds, but this time, I did not get a BSOD.
• I pressed Ctrl+Alt+Delete, and my internal laptop screen (connected to the Intel iGPU) successfully turned on and showed the Ctrl+Alt+Delete screen.
• After logging in, the system was in a "zombie state." The external dGPU screen remained black, and the internal iGPU screen was active but non-functional.
• Any attempt to run a program failed. Taskmgr.exe hung. Browsers would not load. The PC would not reboot. I had to force a hard power-off.
The Event Viewer Evidence (From the Hang)
This hang filled my Event Viewer with errors, proving a system-wide collapse of the hardware communication layer (WMI).
Complete WMI Service Collapse: I am seeing hundreds of WMI query failures with ResultCode = 0x80041032 (Call Canceled) and PossibleCause = Throttling Idle Tasks.
Applications are trying to query basic hardware information and the system is failing to answer:
• Operation = Start IWbemServices::ExecQuery - ROOT\CIMV2 : SELECT Caption FROM Win32_VideoController
• Operation = Start IWbemServices::ExecQuery - root\cimv2 : SELECT SerialNumber FROM Win32_BIOS
• Operation = Start IWbemServices::ExecQuery - ROOT\CIMV2 : SELECT Name FROM Win32_Processor
• Operation = Start IWbemServices::ExecQuery - root\WMI : SELECT InstanceName, VideoOutputTechnology FROM WmiMonitorConnectionParams
System Hangs as a Result: This WMI collapse directly caused the "zombie state" I experienced:
• The program Taskmgr.exe version 10.0.26100.6725 stopped interacting with Windows and was closed.
• An error occurred when transitioning from DesktopLocked... (ErrorCode 0x8007139F)
• ...
Conclusion
This single, chronic stall is:
• Causing the Intel iGPU driver (Intel-Gfx-Display-External) to log thousands of errors.
• Periodically causing the NVIDIA dGPU to hang or BSOD.
• Causing a complete Windows WMI service collapse, preventing it from querying platform hardware like the CPU and BIOS.
Im also "in contact" with intel:
Other guys on Intel fora are also experiencing the massive amount of intel external-display errors:
Intel-Gfx-Display-External error - Intel Community
Intel confirmed: "I want to update you on the status of your case. We are currently investigating this display power management issue, and I can confirm that similar instances have been identified on related platforms. "
Intel is asking for a complete memory dump. I just activated this, and now need to try and get the BSOD back so a full memory dump is created. I will upload the memory dump and also send this to you.
Regards,
Kevin