Windows 11 25H2 – System Freeze Issue

The update to 26200.7840 was unstable, so go to 8246. I've had some systems also experiencing this behavior on 26200.8246 on Intel Ultra7 systems which also have the neural processing unit (NPU). Updating the Intel driver for the NPU with Intel's latest version has made all the difference thus far. Check to see if your system is listed as valid for this driver on this page:

https://www.intel.com/content/www/us/en/download/794734/intel-npu-driver-windows.html

Thanks for following up Sreekanth D,

The reason your system failed to generate a memory dump is due to a slight mix-up with the physical execution of the hardware interrupt. You mentioned trying "Right Click," but the kernel-level trigger specifically requires the Right Control key on your keyboard. To successfully force the crash dump, you must hold down the Right Control key and tap the Scroll Lock key twice in rapid succession while the screen is frozen. The system must also have a suitably sized page file enabled on the primary system drive for the memory dump to write successfully.

The Event IDs you discovered in the Event Viewer are cascading secondary failures rather than the root cause of the freezing. When the core graphical subsystem or kernel threads lock up, background processes are abruptly halted. This inevitably causes the Service Control Manager to register timeout errors like Event ID 7009 because services are physically blocked from starting, which subsequently triggers Group Policy processing failures like Event ID 1096 since the system can no longer communicate with the domain controller. Troubleshooting these specific errors will not resolve your issue because they are merely symptoms of the overarching system freeze.

As for alternative bypasses, there are no administrative workarounds or registry hacks that can patch an unstable operating system kernel. Build 26200 is a Windows Insider Canary release, which inherently contains experimental, unpolished code that is explicitly not supported for organizational production environments. The freezing issue you are experiencing is an unresolved bug tied directly to this specific preview build interacting with your hardware fleet. To permanently resolve this and restore stability, your only viable solution is to wipe the affected machines and deploy a commercially supported, stable release channel of Windows 11.

Hope it helps :)

VP

Hi Sreekanth D,

How is your issue going? Has it been resolved yet? If it has, please consider accepting the answer as it helps others sharing the same problem benefit too. Thank you :)

VP

Hi Sreekanth D,

The blank screen with a responsive cursor you are seeing across your fleet indicates a Desktop Window Manager or shell hang, which is an expected risk given your operating system version. Build 26200 is a Windows Insider Preview build from the Canary channel, meaning it contains experimental code that frequently conflicts with existing display drivers and causes user interface deadlocks. Because this is an inherent bug within a preview build, standard troubleshooting will not provide a permanent fix. You will need to either wait for a future Insider patch or roll your production fleet back to a stable, commercially released version of Windows 11.

If you need to identify the exact driver causing the conflict while waiting for a fix, you can configure your endpoints to generate a manual kernel memory dump. You will need to deploy a registry modification to the affected endpoints by navigating to HKEY_LOCAL_MACHINE, opening the System key, going through CurrentControlSet to Services, selecting the kbdhid key, and opening Parameters to create a new DWORD value named CrashOnCtrlScroll set to 1. Holding the right Control key and pressing the Scroll Lock key twice while the machine is frozen will force a system crash. This generates a file at C:\Windows\MEMORY.DMP that you can analyze with the Windows Debugger to isolate the faulting component.

You should also review the Event Viewer logs on a recovered machine by checking the System log for Event ID 4101. This specific code indicates a display driver timeout and operating system recovery attempt, which confirms if your current graphics driver version is directly incompatible with this specific Insider build. Downgrading or updating the display driver may provide temporary stability, but moving your organization off the Canary channel is the only permanent resolution for fleet-wide reliability.

Hope this answer brought you some useful information. If it did, kindly hit "accept answer". Should you have any questions, feel free to leave a comment.

VP

Windows 11, version 25H2 does not currently list a general, widespread “blank screen with cursor” freeze as a known issue in the provided context, but there is official guidance for troubleshooting blank/black screen scenarios that matches the described symptoms.

For devices on Windows 11 25H2 showing a blank screen with only the cursor visible, the following steps are recommended:

1. Confirm basic hardware and display path
   • Ensure laptops are powered, charged, and not in a low‑power or sleep state.
   • If any are docked or using external monitors, verify the monitor is powered on, connected, and on the correct input.
2. Reset the graphics path when the freeze occurs
   • When the screen is blank but the cursor is visible, press:
     Windows + Ctrl + Shift + B
   • This resets the graphics driver. A brief beep or screen flicker indicates the reset was triggered.
   • If the display returns, this points to a graphics/driver pipeline issue rather than a full OS hang.
3. Cycle display modes in case output is being sent to the wrong display
   • Press Windows + P, then tap P again and press Enter to cycle through display modes (PC screen only / Duplicate / Extend / Second screen only).
   • Repeat slowly a few times to ensure the active output is switched back to the laptop panel.
4. Check if Windows shell is responsive via Ctrl+Alt+Del
   • When the freeze occurs, press Ctrl + Alt + Del.
   • If the security screen appears, select Task Manager.
   • In Task Manager, restart Windows Explorer (right‑click “Windows Explorer” → Restart).
   • If this restores the desktop, the issue is likely with the shell or a foreground app rather than a full system hang.
5. Force restart affected devices when fully unresponsive
   • If none of the above works and the system remains frozen, hold the power button for about 20 seconds to force a shutdown, then power it back on.
   • This is a recovery step, not a fix, but it is the supported way to recover from a hard freeze.
6. Keep devices updated with latest fixes
   • Windows 11 25H2 has had several issues already identified and resolved via cumulative updates (for example, Task Manager background instances, protected content playback, and app hangs with cloud‑backed storage).
   • Ensure all affected laptops are fully updated to the latest cumulative update for Windows 11 25H2, as many stability fixes are delivered this way.
7. If the issue persists across the fleet
   • Use Feedback Hub on an affected device to report the problem with logs while the system is in the problematic state (or immediately after reboot).
   • For organizational impact across many devices, monitor and escalate via Windows release health in the Microsoft 365 admin center and, if necessary, open a support case through business support channels so the behavior can be analyzed with full diagnostic data.

These steps align with Microsoft’s official troubleshooting guidance for blank/black screen issues and with the general recommendation to stay current on Windows 11 25H2 cumulative updates, which include reliability and freeze‑related fixes.

References:

• Troubleshooting blank screens in Windows
• Resolved issues in Windows 11, version 25H2
• Windows 11, version 25H2 known issues and notifications
• Resolved issues in Windows 11, version 24H2