Windows 11 Blank Screen & Unresponsive

Question

Dear Team,

We currently have approximately 80 laptops in use, and almost all devices are experiencing the same problem. The systems intermittently display a blank screen and become completely unresponsive. During this state, users are unable to perform any actions, and the only way to restore functionality is by performing a hard reboot. (Windows 11 Pro 64 Bit Version 25H2)

This issue is impacting productivity and requires urgent investigation. Kindly assist us in identifying the root cause and providing a suitable resolution at the earliest.

Please let us know if any additional logs, system details, or troubleshooting steps are required from our side.

Looking forward to your prompt support.
@Note: Tried all the options like reinstalling OS and uninstalling APPS, windows updates but still same problem.

Answer 1

We tried all the above options but still no luck.

Answer 2

Hi Swamy Adireddy,

Thank you for confirming you’ve already tried the standard blank-screen recovery steps as well as OS reinstalls and app removals. Since the issue is occurring across many devices, this strongly suggests a common interaction (for example: a recent Windows update + graphics/chipset driver + firmware combination), rather than a one‑off OS corruption.

1) Check whether this lines up with a specific Windows update

1. Pilot rollback 2–3 representative laptops to 24H2 (if Go back is still available / within the rollback window).
2. If rollback stops the blank-screen freezes, that strongly points to a 25H2/build-update interaction, and you can:
   • Consider a broader rollback or pause 25H2 rollout while collecting logs.
3. If rollback does not help, it suggests the root cause is more likely:
   • OEM GPU/chipset driver, firmware, docking/external display path, or a standard corporate agent that returns after reinstall — and you’ll need to focus on driver/firmware + event logs rather than OS version.

We recommend testing this on 2–3 pilot laptops first before broad deployment.

2) Collect a focused set of logs from a few representative laptops

Because reinstalling Windows did not prevent the problem from returning, the fastest way to identify the root cause is to review system evidence around the hang—especially graphics/display-related events. Microsoft’s blank-screen guidance aligns with treating this as a “Windows running but display stack/shell hung” issue. Please share the following from 3 affected laptops (ideally same model):

• Windows version/build (Winver) + recently installed updates (KB numbers) (run command in PowerShell as administrator: msinfo32 /nfo C:\SYSSUM.NFO /categories +systemsummary+winver -> output file: C:\SYSSUM.NFO)
• Laptop make/model
• DxDiag report (graphics + driver versions) (run command in PowerShell as administrator: dxdiag /t C:\Temp\dxdiag.txt)
• Event Viewer logs (System + Application) around the time of the freeze
• Reliability Monitor history around the freeze

3) Pilot a “known-good” baseline configuration

We will validate stability using a minimal pilot configuration (Windows fully updated + OEM-recommended graphics/chipset drivers + latest BIOS/firmware). If the pilot is stable, we can align the rest of the fleet to that baseline. This is the recommended approach when many devices are affected and reinstalls do not resolve the behavior.

Once we have the pilot results + the logs above, we can pinpoint whether this is driven by a specific update, a graphics driver/firmware interaction, or a third‑party component loaded at startup—and provide the safest fleet-wide remediation.

Please let me know if you need further assistance.

Hope you found something helpful here.

Ivy Bui

Answer 3

Because the issue affects many Windows 11 25H2 devices and persists even after OS reinstalls and app removals, start with systematic blank‑screen troubleshooting and then move to update/driver and health checks across the fleet.

1. Confirm it is a “blank screen” scenario

• If devices show a black/blank screen with or without a cursor and no stop code/BSOD text, treat it as a blank screen issue rather than a crash.
• When the issue occurs, test:
  • Ctrl + Alt + Del → if the security screen appears, it indicates Windows is still running but the shell/graphics stack is hung.
  • Windows logo key + Ctrl + Shift + B → this resets the graphics driver; a beep or screen flicker indicates the reset was triggered.

2. Apply standard blank‑screen remediation On affected devices, validate the following (or script via management tools where possible):

• Check display/output mode
  • Press Windows logo key + P, then press P again and Enter to cycle display modes (PC screen only / Duplicate / Extend). Misconfigured output can present as a blank screen.
• Restart Windows Explorer when the cursor is visible
  • Press Ctrl + Shift + Esc to open Task Manager.
  • If Task Manager opens, restart Windows Explorer:
    • Right‑click Windows Explorer → Restart.
    • If missing, File > Run new task → explorer.exe → Enter.
• Force restart only as last resort
  • If the system is completely unresponsive (no Ctrl + Alt + Del response), hold the power button ~20 seconds to force power‑off, then power on again.

3. Use advanced steps on a pilot device Pick a few representative laptops and run through deeper steps to see if the issue is driver/firmware related:

• Boot into Safe Mode and observe
  1. Force shutdown with power button (10 seconds).
  2. Repeat 2–3 times until Windows Recovery Environment appears.
  3. Troubleshoot > Advanced options > Startup Settings > Restart.
  4. Press F5 for Safe Mode with Networking.
  • If the blank‑screen issue does not occur in Safe Mode, this strongly points to a display driver or third‑party driver/service.
• Update or roll back display drivers
  1. In Safe Mode, open Device Manager.
  2. Expand Display adapters.
  3. For each GPU:
     • Try Update driver.
     • If the issue started after a recent driver rollout, use Properties > Driver > Roll Back Driver.
• Perform a System Restore on a test device
  • If the issue began recently and restore points exist:
    • Boot into Safe Mode or Recovery Mode.
    • Troubleshoot > Advanced options > System Restore.
    • Restore to a point before the first occurrence and validate stability.

4. Check for known Windows 11 24H2/25H2 issues

• Ensure all affected devices are fully updated with the latest cumulative updates for Windows 11 25H2, including any out‑of‑band (OOB) fixes. These updates contain important reliability and black‑screen/connection fixes.
• If any devices are on 24H2 in your environment, be aware of known compatibility issues (for example, with specific third‑party drivers such as sprotect.sys) that can cause blue or black screen errors. Verify such drivers are not deployed in your image or security stack.

5. Differentiate from stop‑code/BSOD problems

• If at any point users see messages like “Your device ran into a problem and needs to restart” or a stop code at the bottom of the screen, treat those as stop‑code/BSOD issues instead of pure blank‑screen hangs.
• For repeated stop‑code errors:
  • Remove any newly added hardware.
  • Boot in Safe Mode and check Device Manager for devices with warning icons and update/disable/uninstall problematic drivers.
  • Ensure sufficient free disk space (10–15% of system drive).
  • Confirm latest Windows 11 updates are installed.
  • Use Recovery options in Windows 11 (e.g., System Restore) if the issue started after a specific change.

6. Fleet‑wide next steps Given the scale (≈80 laptops) and that OS reinstalls did not help:

• Standardize on a known‑good image
  • Build or confirm a reference Windows 11 25H2 image with:
    • Latest cumulative updates and OOB fixes.
    • Vendor‑recommended graphics and chipset drivers only.
    • No third‑party security/overlay/graphics tools initially.
  • Validate this image on a small pilot group for several days.
• Compare pilot vs. affected devices
  • If the pilot image is stable, gradually align the rest of the fleet (via in‑place repair or reimage) to that configuration.
  • If the pilot still shows blank screens, collect:
    • Reliability Monitor reports.
    • Event Viewer logs around the time of the hang (System and Application logs, especially display/driver timeouts).
    • A list of common third‑party drivers/services across all devices.
• Consider in‑place repair for heavily affected machines
  • If individual devices show additional corruption (frequent update failures, service errors, etc.), perform an in‑place repair of Windows 11 using the ISO while keeping apps and data, then re‑apply updates.

7. When to escalate

• If blank screens persist after:
  • Latest Windows 11 25H2 updates and OOB patches are applied,
  • GPU/chipset drivers are updated or rolled back,
  • A clean, minimal pilot image still reproduces the issue, then collect logs from a few representative devices (including crash dumps if any, event logs, and driver lists) and open a support case so the issue can be analyzed as a potential platform/driver interaction specific to your hardware model.

---

References:

• Troubleshooting black or blank screens in Windows
• Troubleshooting blank screens in Windows
• Troubleshooting Windows unexpected restarts and stop code errors
• Resolved issues in Windows 11, version 24H2
• Resolved issues in Windows 11, version 25H2