Windows BSOD Error 0x00000044 — MULTIPLE_IRP_COMPLETE_REQUESTS Fix

What Does This Error Mean?

The 0x00000044 blue screen means a driver tried to complete the same I/O request twice. In Windows, when a driver finishes handling a hardware request, it marks it as complete. If a buggy driver marks the same request complete a second time, Windows detects this and crashes. This is called MULTIPLE_IRP_COMPLETE_REQUESTS.

Affected Models

Windows 10
Windows 11
Windows 8.1
Windows Server

Common Causes

A storage driver (hard drive, SSD, or RAID controller) has a bug causing duplicate request completions
A network adapter driver is mishandling I/O requests
A third-party driver for a recently installed device is poorly written or incompatible with your Windows version
Windows system files are corrupted, causing incorrect handling of I/O requests
A hardware fault in your hard drive or SSD is causing the controller to behave incorrectly

How to Fix It

Check Device Manager for driver problems. Right-click the Start button and select Device Manager. Look for any devices marked with a yellow exclamation mark. Update or roll back the driver for any flagged devices.

Drivers with visible problems in Device Manager are the most likely culprit for this specific blue screen.
Update your storage controller drivers. In Device Manager, expand Storage controllers, right-click each controller, and select Update driver.

Storage controller bugs are the number one cause of MULTIPLE_IRP_COMPLETE_REQUESTS. Updating these drivers fixes the issue in most cases.
Roll back any recently installed drivers. If this blue screen started after installing new hardware or updating a driver, go to Device Manager, find that device, right-click it and select Properties > Driver > Roll Back Driver.

If the crash started after a specific driver update, rolling back to the previous version often resolves it immediately.
Run System File Checker to repair corrupted Windows files. Open Command Prompt as Administrator and type: sfc /scannow then press Enter. Let it run to completion.

Corrupted Windows system files can affect how I/O requests are handled, triggering this crash in some cases.
Run a hard drive health check. Download and run CrystalDiskInfo (free tool) to check the health status of your hard drives and SSDs. Look for any warnings about reallocated sectors or pending errors.

A failing drive can cause its controller to misbehave in ways that trigger this crash. If CrystalDiskInfo shows warnings, back up your data immediately.

When to Call a Professional

This blue screen is almost always caused by a specific driver. If you cannot identify or fix the driver using the steps below, a technician can analyse the crash dump to pinpoint the exact cause. If the crash happens at random intervals with no clear pattern, a hardware diagnostic is also recommended.

Frequently Asked Questions

What is an IRP and why does completing it twice cause a crash?

IRP stands for I/O Request Packet — it is a message Windows sends to a driver to request work. When the driver finishes, it sends a completion signal back. Sending that signal twice is like a worker telling their boss a job is done twice in a row — Windows detects this inconsistency and crashes rather than risk corrupting data.

How do I find which driver caused this crash?

Look in the C:\Windows\Minidump folder for a .dmp file created at the time of the crash. You can open this file with WinDbg Preview (free from the Microsoft Store) to see the name of the driver that triggered the crash. The driver name will point you to the specific hardware or software to update.

This crash happens randomly with no pattern. What does that suggest?

Random crashes with no clear pattern often point to intermittent hardware issues. The most common culprits are a failing hard drive, faulty RAM, or loose cables inside the computer. Run the Windows Memory Diagnostic (type mdsched.exe in the Run box) and check drive health with CrystalDiskInfo.