Dear Wadiska,
Thank you for reaching out.
From my initial review, current evidence suggests the black screen is most likely associated with graphics stack initialization during user logon. The strongest indicators are the AMD Radeon Software crash, followed immediately by multiple NVIDIA recovery events and DWM initialization errors.
At this point, the leading hypothesis is a conflict or instability involving the AMD integrated graphics environment and the NVIDIA RTX 5070 Ti display stack rather than a Windows shell or operating system corruption issue.
The recommended next step is to isolate the AMD graphics layer and validate the behavior under an NVIDIA-only configuration before pursuing deeper escalation.
Here below I attach the Technical Analysis Summary, kindly let me know if further clarification is needed. Thank you.
Issue Description
Users experience a recurring black screen immediately after signing into Windows 11. The system remains powered on and responsive to mouse movement; however, the desktop does not render properly and the user interface becomes unavailable. Continuously moving the mouse for an extended period eventually allows the desktop to appear and the system to function normally.
The issue reproduces consistently and may occur multiple times in the same session.
A clean Windows installation temporarily mitigates the issue before it eventually reoccurs.
Event Log Findings
1. AMD Radeon Software Component Crash - Event ID 1000 (Application Error)
This indicates a crash involving AMD Radeon Software components during user logon.
Notably, the affected system uses a Ryzen 5 8500G processor, which contains an integrated Radeon GPU in addition to the installed NVIDIA RTX 5070 Ti.
Observation: The timing suggests AMD display-related components are actively involved during system initialization and may be interacting with the graphics stack during the failure period.
2. NVIDIA Driver Recovery Events
Multiple NVIDIA driver events were recorded immediately after the black screen occurrence:
Event ID 153 – nvlddmkm
Several instances were observed within seconds of one another.
Event ID 14 – nvlddmkm
This indicates the NVIDIA driver detected an error condition and initiated a GPU recovery procedure.
Observation:These events occur during the exact timeframe when the customer experiences the black screen.
3. Desktop Window Manager (DWM) Involvement
A DwmInit event was also recorded referencing:
The Desktop Window Manager (DWM) is responsible for graphical desktop composition and rendering.
Observation:The coexistence of DWM events and NVIDIA recovery events suggests the graphical desktop rendering pipeline was interrupted or delayed during logon.
4. Secondary Application Hang
Event ID 1002 (Application Hang) was captured for:
This appears to be a downstream symptom occurring after the display stack instability rather than the primary root cause.
Technical Assessment
Based on currently available evidence, the issue appears more related to display stack initialization and GPU recovery than to typical shell startup or Explorer.exe failures.
The following sequence is observed:
- User completes Windows logon.
- AMD display-related component crashes.
- NVIDIA driver records multiple recovery/error events.
- DWM experiences initialization issues.
- Desktop rendering is delayed or unavailable.
- Eventually, the graphics stack recovers and the desktop appears.
The event correlation significantly strengthens the hypothesis of a graphics subsystem issue rather than:
- User profile corruption
- Explorer.exe crashes
- Page file configuration
- Windows file corruption
- Startup application delays
At this stage, the most probable causes are:
Primary Suspect
Interaction between AMD integrated graphics components and NVIDIA RTX 5070 Ti display stack
Evidence:
- AMD Radeon Software crash
- Ryzen 8500G contains integrated Radeon graphics
- NVIDIA recovery events immediately follow
- DWM instability observed
Secondary Suspect
NVIDIA display driver / desktop composition instability
Evidence:
- Multiple nvlddmkm Event 153 errors
- Event 14 GPU recovery action
- DWM involvement
Less Likely
- Hardware GPU defect
- PSU insufficiency
- Windows corruption
- Explorer shell failures
Current evidence does not strongly support these scenarios.
Recommended Next Actions (please ensure a backup is available once needed)
1. Eliminate AMD Graphics Stack from Testing
- Uninstall AMD Radeon Software (retain chipset drivers only)
- Disable AMD integrated graphics in BIOS if not required
- Configure system for NVIDIA-only operation
2. Verify Display Adapter Configuration
Confirm whether Device Manager currently shows:
1-AMD Radeon Graphics
2-NVIDIA GeForce RTX 5070 Ti
If both are present, test with AMD adapter disabled.
3. Test Multiple Reboots
Perform repeated logon cycles after AMD component removal to determine whether the issue reproduces.
4. Collect Additional Data if Repro Persists
- Reliability Monitor logs
- GPUView / ETW traces
- NVIDIA driver diagnostic logs
- ProcDump capture during black screen event