Windows Crashing Bluescreen D1

Question

Pc has been crashing for the third time in the same day for no apparent reason, eventvwr doesnt give me a critical error. Does anyone have any tips?

ps. i have ran sfc /scannow and did a virus scan, the game in which it crashed three times (helldivers 2 and minecraft) had been repaired but there was a crash shortly after as well.

During each crash the audio gets stuck at the same tone while everything freezes

Problem signature

Problem Event Name: BlueScreen

Code: d1

Parameter 1: 0

Parameter 2: 9

Parameter 3: 0

Parameter 4: fffff805502f1fd8

OS version: 10_0_26200

Service Pack: 0_0

Product: 256_1

OS Version: 10.0.26200.2.0.0.256.48

Locale ID: 3072

Files that help describe the problem

030126-15671-01.dmp

sysdata.xml

WERInternalMetadata.xml

memory.csv

sysinfo.txt

WERInternalRequest.xml

please ask me for more info if necessary because i have no idea where to go from here

Answer 1

Please check to see if your PC is producing any minidump files, I will check those to see if they provide any insight into a potential cause of the system crashes.

Please do not upload a very large Memory.dmp file.

Open Windows File Explorer.

Navigate to C:\Windows\Minidump

Copy any minidump files onto your Desktop, then zip those up.

Upload the zip file to the Cloud (OneDrive... etc.), then choose to share those and get a share link.

Then post the link here to the zip file, so I can take a look for you.

Answer 2

The D1 bug check (DRIVER_IRQL_NOT_LESS_OR_EQUAL) almost always points to a faulty or misbehaving driver, very often graphics, audio, storage, or a low‑level anti‑cheat/overlay used by games. Since it happens in games with frozen video and stuck audio, start with driver and basic BSOD troubleshooting.

Follow these steps in order:

1. Basic blue screen troubleshooting
2. Remove any recently added hardware (USB devices, new peripherals) and test again.
3. Boot once into Safe Mode to see if the system is stable there. If it is, that strongly suggests a driver or software issue rather than hardware. Steps are in Start your PC in safe mode in Windows 10.
4. Check free disk space on the system drive and keep at least 10–15% free.
5. Install all pending Windows Updates once the system is stable enough to do so.

These steps are summarized in the “Basic troubleshooting steps for Windows blue screens and stop code errors” section.

2. Update and check drivers
3. Open Device Manager (right‑click Start > Device Manager).
4. Look for any devices with a yellow triangle/exclamation mark. For each:
   • Right‑click > Update driver.
   • If that does not help, try Disable device or Uninstall device, then reboot and let Windows reinstall it.
5. Pay special attention to:
   • Display adapter (GPU driver)
   • Sound devices
   • Network adapter
   • Any virtual devices installed by anti‑cheat, VPN, or RGB/overclocking tools.
6. If the crashes started after installing or updating a specific driver or tool (GPU tuning software, overclocking utility, RGB/“gaming” suite), uninstall that software completely and test again.
7. Check for device problems via Device Manager If a device has a problem code, Device Manager will show a yellow triangle. Open its Properties:

• On the General tab, read the Device status text for the problem code.
• On the Details tab, choose Problem status in the Property dropdown to see more detail. If any device shows a problem, resolve it first (update driver, reinstall, or temporarily disable) and then test games again.

4. Analyze the dump (optional, advanced) The .dmp file listed (for example 030126-15671-01.dmp) can be analyzed with the Windows debugger to see which driver was active at the time of the D1 bug check. An advanced user can:

• Enable kernel dump creation if not already enabled.
• Use WinDbg and commands like !analyze -v to identify the faulting module. If a specific third‑party driver is named, update or remove the associated software.

5. Memory and hardware checks Even though D1 is usually driver‑related, unstable RAM or other hardware can make drivers misbehave.
6. Run Windows Memory Diagnostic (type Windows Memory Diagnostic in Start, choose Restart now and check for problems).
7. After reboot, open Event Viewer and navigate to:
   • Event Viewer (Local) > Application and Services Logs > Microsoft > Windows > MemoryDiagnostics-Results > Debug
   • Look for Event ID 2001 which means no memory errors were detected.
8. If memory errors are found, test RAM modules individually and reseat or replace faulty ones.
9. If crashes continue If the above steps do not resolve the issue and D1 blue screens continue:

• Use System Restore to roll back to a point before the crashes started, if available.
• As a last resort, use Windows recovery options (Reset this PC while keeping files) to reinstall Windows while preserving personal data.

If more help is needed, provide:

• Whether Safe Mode is stable.
• Any devices with warnings in Device Manager and their problem codes.
• Whether Windows Memory Diagnostic reports errors.
• If a debugger was used, the name of any driver shown as the probable cause.

---

References:

• Troubleshooting Windows unexpected restarts and stop code errors
• How to fix Error 0xA: IRQL_not_less_or_equal
• Retrieving the Status and Problem Code for a Device Instance