WHEN WILL DXGI DEVICE_REMOVE/DEVICE_HUNG CRASHES BE FIXED

FREESTYLEkill3r​ this is the most recent error code at the bottom of your DxDiag.txt .

---------------

Diagnostics

---------------

Windows Error Reporting:

+++ WER0 +++:

Fault bucket , type 0

Event Name: BlueScreen

Response: Not available

Cab Id: 0

Problem signature:

P1: 9f

P2: 3

P3: ffff80893c252120

P4: fffffb891676f580

P5: ffff80893c2b3280

P6: 10_0_26200

P7: 0_0

P8: 768_1

P9: 

P10: 

Here's what Google Gemini AI says.

This WER0 BlueScreen error (P1: 9f) indicates a critical system crash, likely due to a bad driver, faulty hardware (like RAM/disk), overheating, or a problematic update/software conflict, with the 10_0_26200 pointing to a newer Windows build (likely Windows 11 Insider/Preview).

To fix it, you'll need to update drivers (especially graphics/network), run sfc /scannow & DISM, check for Windows Updates, potentially remove new hardware/software, and look for overheating. 

1. 
   1. Identify the Stop Code
   The "9f" in P1 usually relates to a driver failure or hardware issue. Look for the actual stop code (e.g., DRIVER_POWER_STATE_FAILURE) on the blue screen itself for more clues. 
2.  
3. 2. Common Fixes (Software/Driver First)
   Update Drivers: Go to Device Manager and update your graphics, network, and other key drivers, or download them directly from the manufacturer's website.
   Run System File Checker: Open Command Prompt as admin and run sfc /scannow, then DISM /Online /Cleanup-Image /RestoreHealth to repair corrupted system files.
4. 
   Check Windows Update: Install any pending updates or uninstall recent ones if the issue started after an update.
   Check for Overheating: Monitor CPU/GPU temps; high temps can cause crashes.
   Scan for Malware/Viruses: Run a full system scan. 
5.  
6. 3. Hardware & Advanced Steps
   Remove New Hardware: If you recently added any, remove it.
   Test RAM: Run the Windows Memory Diagnostic tool.
   System Restore: Roll back your system to a point before the crashes started.
   Clean Boot: Start Windows with minimal drivers to isolate software conflicts. 
7.  
8. 4. For Insider Builds (If Applicable)
   Since P6 is 10_0_26200, you're on a newer Windows build. These can be less stable. Ensure everything is updated, and consider reporting the bug to Microsoft or using the Feedback Hub if it's a preview build.

 OskooI_007​ recommends running HCI MemTest to check for memory errors.

Download HCI MemTest and see if there's any memory errors.

https://hcidesign.com/memtest/

Open Windows Task Manager and check how much available memory there is.

Open multiple MemTest windows. Have each MemTest window scan 3000MB of memory.

Never let the available memory in Windows Task Manager reach 0. Always leave at least 1GB of available memory because if it reaches 0 then MemTest will start testing the Windows page file on the SSD.

If I don't reply to your post then personal message me. Sometimes the forum fails to notify me when someone replies.