Fix STATUS_DATA_OVERRUN 0xC000003C BSOD – Real Fixes

When This Error Shows Up

You boot your PC, or plug in a USB drive, or maybe just sit down and suddenly your screen goes blue. The error says STATUS_DATA_OVERRUN (0xC000003C). I've seen this mostly on older machines running Windows 10 20H2 or Windows 11, but it's not picky. Happens with external hard drives, USB printers, or even internal SATA controllers when they choke on a data burst. Had a client last month whose backup drive triggered this every time Windows tried to index it. The real trigger? Something sent more data than the buffer could hold, and the OS panicked.

What the Error Means – Plain English

Think of a buffer like a bucket. The driver or hardware is supposed to catch data in that bucket and process it. When the incoming data floods faster than the bucket can empty—say a network driver gets hammered with packets or a USB controller gets a burst from a printer—the bucket overfills. That's the overrun. The system stops dead to prevent data corruption. The cause is almost always a faulty driver that doesn't manage its buffer size correctly, or a hardware device that's borderline failing and sending junk.

Don't waste time reinstalling Windows. That's a last resort. Nine times out of ten, it's a driver conflict or a flaky piece of hardware. Let's narrow it down.

Step-by-Step Fix

1. Identify the Culprit Driver or Device

Open the Start menu, type View reliability history, and check the critical events around the time of the crash. Click on each entry—Windows often lists the module (like ntoskrnl.exe or a specific driver .sys file) that caused it. Write down the driver or device name. If it points to ntoskrnl.exe alone, it's generic, and you'll need to dig deeper.

Also check Event Viewer → Windows Logs → System. Filter for Error with source BugCheck. The event details will list the driver that faulted. Common suspects: usbhub.sys, ntfs.sys, ndis.sys, or video drivers like nvlddmkm.sys or atikmpag.sys.

2. Update the Problem Driver

If you found a specific driver, head to the manufacturer's website—don't trust Windows Update for this. For network cards, grab the latest from Intel, Realtek, or Broadcom directly. For USB controllers, check your motherboard maker (ASUS, Gigabyte, etc.) for chipset drivers. I keep a USB stick with driver installers for this reason. Had a client whose Realtek USB 3.0 driver from 2019 caused this on every USB transfer. Updated to the 2023 version—BSOD gone.

If you're not sure, go broad: download and install the latest chipset driver and storage driver from your OEM. On a Dell or HP? Use their support tool (Dell Command Update, HP Support Assistant) to scan and update all drivers at once.

3. Test Without External Devices

Unplug every USB device except the keyboard and mouse. If the BSOD stops, plug them back one at a time until it crashes again. That pinpoints the device. I've seen cheap USB hubs, webcams, and even a faulty external SSD do this. Once you find it, replace its driver or the hardware itself.

4. Check and Replace Failing Hardware

Sometimes it's not a driver—it's a dying component. Run these tests:

Memory test: Use mdsched.exe (Windows Memory Diagnostic) from the Start menu. Let it run overnight. If it finds errors, replace the RAM stick.
Disk check: Open Command Prompt as admin and run chkdsk C: /f. Then sfc /scannow. If either reports bad sectors or corruption, your disk or SSD might be failing. Backup data immediately and replace the drive.
Stress test the CPU: Use free software like Prime95 or FurMark. If the system crashes during the test, the CPU or power supply is suspect.

Still Crashing? What to Check Next

If the above didn't fix it, you're dealing with something deeper. Here's my checklist:

Disable driver verifier if you turned it on—it's a diagnostic tool that can cause this error by itself. Boot into Safe Mode, open Command Prompt as admin, type verifier /reset, and reboot.
Check for defective RAM slots – try swapping the stick to a different slot on the motherboard.
Update your BIOS – a buggy ACPI table or SATA controller firmware can trigger this. Download the latest BIOS from your motherboard vendor and flash it carefully.
Run a full antivirus scan with Malwarebytes. A rootkit hiding in a driver can cause buffer overflows.
Clean boot Windows – use msconfig to disable all non-Microsoft services and startups. If the crash stops, one of those services is the problem. Re-enable them in groups to find the culprit.

If all else fails, consider a clean install of Windows. But honestly, in my 15 years of fixing this error, only two machines needed that. The rest were fixed with a driver update or a swapped USB cable. Don't give up too soon.