Issue
Windows reaches sign-in, accepts credentials, and then shows a black screen, sometimes with a movable pointer. Safe Mode works, or the problem began immediately after installing or updating a display driver.
Searchable Windows error codes and exact messages
A post-login black screen has no unique Windows error code. When graphics is responsible, search the black-screen symptom together with the display driver/module, GPU model, bug-check name, Device Manager code, or event shown on the affected machine.
| Type | Searchable identifier | When it applies |
|---|---|---|
| Blue-screen bug check | 0x00000116 — VIDEO_TDR_FAILURE | Windows attempted to reset a timed-out display driver and recovery failed. |
| Blue-screen bug check | 0x00000113 — VIDEO_DXGKRNL_FATAL_ERROR | The DirectX graphics kernel detected a fatal graphics condition. |
| Blue-screen bug check | 0x00000119 — VIDEO_SCHEDULER_INTERNAL_ERROR | The video scheduler detected a fatal violation. |
| Blue-screen bug check | 0x0000010E — VIDEO_MEMORY_MANAGEMENT_INTERNAL | The video memory manager encountered a condition from which it could not recover. |
| Blue-screen bug check | 0x000000EA — THREAD_STUCK_IN_DEVICE_DRIVER | A display driver thread is stuck, commonly while waiting for the GPU. |
| Blue-screen bug check | 0x000000D1 — DRIVER_IRQL_NOT_LESS_OR_EQUAL | Include this guide only when the dump names the display driver. |
| Blue-screen bug check | 0x0000007E — SYSTEM_THREAD_EXCEPTION_NOT_HANDLED | Include this guide only when the screen/dump names a graphics module. |
| Live kernel event | LiveKernelEvent 117 / 0x117 — VIDEO_TDR_TIMEOUT_DETECTED | Reliability Monitor or a live dump records a graphics TDR timeout. |
| Live kernel event | LiveKernelEvent 141 / 0x141 — VIDEO_ENGINE_TIMEOUT_DETECTED | A particular display engine timed out without necessarily causing a conventional blue screen. |
| Live kernel event | LiveKernelEvent 142 / 0x142 — VIDEO_TDR_APPLICATION_BLOCKED | A graphics application was blocked after a TDR-related failure. |
| Event Viewer | Display Event ID 4101 | Display driver [name] stopped responding and has successfully recovered. |
| Device Manager | Code 10 — This device cannot start | The display adapter cannot initialize. |
| Device Manager | Code 31 — This device is not working properly because Windows cannot load the drivers required for this device | The display-driver stack cannot load. |
| Device Manager | Code 39 — Windows cannot load the device driver for this hardware. The driver may be corrupted or missing | The display driver is missing or corrupt. |
| Device Manager | Code 43 — Windows has stopped this device because it has reported problems | The GPU/driver reports a failure; this can be software, firmware, power, or hardware. |
| Device Manager | Code 52 — Windows cannot verify the digital signature for the drivers required for this device | Driver-signature validation blocks the display driver. |
Also search the exact faulting module shown in the dump or event, such as nvlddmkm.sys, amdkmdag.sys, amdwddmg, or the Intel graphics module actually recorded on that computer. A bug check such as 0xD1 or 0x7E is not a graphics diagnosis unless the dump ties it to graphics.
Applies when
Use this procedure when Windows reaches the sign-in stage and evidence points to display initialization or the graphics driver. The display must work in firmware, WinRE, Safe Mode, or through another output.
Does not apply when
Do not classify the problem as a graphics-driver failure merely because the screen is black. If Task Manager opens and manually starting Explorer restores the desktop, use FIX-010. If no image appears even in firmware, troubleshoot the display path or hardware first.
Information that may remain unknown
The exact Windows build may remain unknown during the first recovery attempt. The graphics adapter and installed driver version must be recorded before a replacement driver is installed.
Requirements
- Keyboard access
- Windows Recovery Environment if the normal desktop is unusable
- Safe Mode if available
- Exact PC or graphics-adapter model before installing a replacement driver
Starting position
At the black screen, wait long enough to establish that sign-in completed. Listen for Windows sounds and test whether the pointer moves. Disconnect docks and extra displays before changing drivers.
Confirm the diagnosis
Perform these tests in order:
-
Reset the graphics driver:
Windows key + Ctrl + Shift + BA beep or screen blink confirms Windows received the shortcut; it does not prove the driver is healthy.
-
Press
Ctrl+Shift+Esc. If Task Manager appears, choose Run new task, enterexplorer.exe, and press Enter. -
If Explorer restores the desktop, move to FIX-010 instead of removing the graphics driver.
-
Use
Windows key + P, then the arrow keys and Enter, to test whether Windows selected a nonexistent display path. Disconnect all secondary displays and retest. -
If still black, enter WinRE and select Startup Settings > Restart > Safe Mode.
-
If Safe Mode displays correctly while normal mode does not, the normal graphics-driver path is implicated.
Resolution steps
-
In Safe Mode, right-click Start and open Device Manager.
-
Expand Display adapters.
-
Open the properties of the actual graphics adapter.
-
On the Driver tab, record:
- Driver provider
- Driver date
- Driver version
-
If Roll Back Driver is available and the problem followed an update:
- Select Roll Back Driver.
- Choose the reason that accurately describes the failure.
- Complete the rollback.
- Restart normally.
-
If rollback is unavailable:
- Select Uninstall Device.
- On the first attempt, do not select an option that permanently removes the driver package.
- Confirm uninstall.
- Restart normally so Windows can use a basic or previously staged display driver.
-
If Windows now displays normally, obtain the known-good driver for the exact computer or graphics adapter. Prefer the computer manufacturer's validated package on laptops and tightly integrated systems.
-
Install the selected driver.
-
Restart and test again.
Expected results and branches
- Graphics reset restores the display temporarily: The driver/display path remains suspect; continue with version inspection.
- Explorer manually starts and restores everything: This is primarily a shell-startup problem; use FIX-010.
- Safe Mode is also black: The issue may be a display route, shell, hardware, or broader system problem.
- Rollback restores normal display: Retain the working version number and prevent immediate replacement only long enough to investigate the incompatible update.
- Basic driver works but the replacement driver fails again: The chosen package or hardware-specific interaction remains the likely cause.
Do not do this
- Do not install drivers from generic driver-download or driver-updater sites.
- Do not delete every display driver package at once.
- Do not flash GPU or system firmware merely because the screen is black.
- Do not assume a pointer on a black screen proves Explorer is the cause.
Rollback
Use Device Manager's Roll Back Driver to return from a newly installed test driver when available. Keep a record of the last working package. System Restore is the next rollback option if driver installation changed multiple components.
Verification
- The normal desktop appears after three restarts.
- Sleep and wake restore the display.
- Every intended monitor works after reconnecting them one at a time.
- Device Manager shows the intended driver version without an error symbol.
- Event Viewer does not show repeated display-driver resets during each start.
Confidence and stop conditions
Confidence is approximately 85% when Safe Mode works and the failure immediately follows a display-driver change. Stop if firmware and WinRE are also blank, the GPU reports hardware errors, or the screen remains black with the basic display driver.