Since Event Viewer is showing Event ID 1000 tied to explorer.exe, the supported next path is to treat this as a post-sign-in black screen caused by Explorer or the user shell failing.
Try these steps in order:
- Reset the graphics driver first Press Windows + Ctrl + Shift + B. If the issue is only a stalled display driver, the screen should flicker or recover.
- Open Task Manager from the black screen Press Ctrl + Alt + Del and select Task Manager. If Task Manager opens, go to the Details tab and check whether explorer.exe and userinit.exe are running.
- Verify the shell registry value
Since the desktop is not loading, check that Windows is still configured to start Explorer as the shell. Warning: Registry changes are risky. Back up the registry before modifying it.
- Press Windows + R, type
regedit, press Enter. - Go to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon - In the right pane, confirm Shell is set to:
explorer.exe - Also check the Permissions on that key and make sure they match a working device.
- Press Windows + R, type
- Use a clean boot to isolate a startup app or service If the shell value is correct, the next supported step is a clean boot to determine whether a startup application or service is causing Explorer to fail after sign-in.
- Capture a dump of explorer.exe if Task Manager is available
Because Event 1000 already points to Explorer crashing, collecting a dump is the most direct way to confirm what module is causing it.
- Press Ctrl + Alt + Del > Task Manager.
- On the Details tab, confirm explorer.exe is present.
- Download ProcDump and extract it to a folder such as
C:\Tools\. - Open an elevated Command Prompt in that folder.
- Run:
procdump -ma explorer.exe explorer.dmp - If userinit.exe is also involved, run:
procdump -ma userinit.exe userinit.dmp
- If explorer.exe is not running, capture an exit dump instead
In an elevated Command Prompt from the ProcDump folder, run:
Then reproduce the black screen and check for a dump inProcdump -e 1 -x C:\Temp explorer.exeC:\Temp. - If Explorer is hanging rather than exiting, enable WER dumps
Since Event 1000 is being logged, Windows Error Reporting can be configured to save dumps when Explorer or Userinit stops responding. Warning: This requires registry edits.
- Create a folder such as
C:\dumps - Open
regedit - Go to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting - If that key does not exist, create it.
- Create these values:
-
DumpCount=10(REG_DWORD) -
DumpType=2(REG_DWORD) -
DumpFolder=C:\dumps(REG_EXPAND_SZ)
-
- Restart and reproduce the issue.
- Create a folder such as
The DLL name reported in the crash is a graphics component, so the combination of a black screen after sign-in plus an Explorer crash makes the graphics driver path especially relevant. The supported actions in the documentation are to reset the graphics driver, verify the shell configuration, isolate startup software with a clean boot, and capture Explorer/Userinit dumps for analysis.
- Scenario guide: Black screen after you sign in to the system
- Scenario guide: Black screen after you sign in to the system
- Scenario guide: Black screen after you sign in to the system
- Scenario guide: Black screen after you sign in to the system
- Troubleshooting blank screens in Windows
- Troubleshooting black or blank screens in Windows