Fix STATUS_ADAPTER_HARDWARE_ERROR 0XC00000C2

Quick answer: reboot and reseat the storage controller. This error means Windows hit a hardware adapter failure, usually a disk or RAID card. Most fixes involve reseating or replacing hardware.

Quick answer

Reseat the storage controller or drive, then reboot. If that doesn't work, update the controller firmware or replace the failing hardware. This error is almost always hardware, not software.

What's going on

You're staring at a blue screen or a boot failure that says STATUS_ADAPTER_HARDWARE_ERROR (0XC00000C2). In plain English: Windows tried to talk to an I/O adapter – like a SATA controller, SCSI card, RAID card, or even a USB host controller – and the hardware didn't answer. That's it. The adapter reported a hardware-level fault, and Windows bailed out to avoid corrupting your data.

I've seen this exact error on an HP ProLiant DL380 running Windows Server 2016, where the RAID battery died and the cache went into write-through mode. The controller kept throwing this error every few hours until we replaced the battery. Also hit it on a Dell PowerEdge T430 with a flaky SAS cable – the connector had worked loose after a technician fiddled inside the case. Both times, the fix was purely hardware.

Sometimes it's not the adapter itself but a drive connected to it. Smart diagnostics often point to the controller, but don't trust that blindly. The drive can fail in a way that makes the controller throw a generic I/O error. So approach this methodically.

Fix steps

Power down and reseat everything. Unplug the machine, open the case, and reseat the controller card (if it's a PCIe card) and all drive cables. Push connectors firmly until they click. While you're in there, blow out dust – I've fixed overheat-related crashes with a can of compressed air.
Check drive connections. On a SATA or SAS setup, swap the data cable on the affected drive. A bent pin or damaged cable can produce exactly this error. I've had a bent pin on a SATA connector cause a near-mirror of this error. Try a different port on the controller, too.
Update firmware and drivers. If reseating doesn't do it, boot into Windows Safe Mode if you can (sometimes the error only appears during boot, not Safe Mode). Then head to the manufacturer's site – Intel, LSI, Broadcom – and grab the latest firmware for your controller. Also, get the latest Windows driver. A half-broken driver can make a healthy adapter misbehave, but treat this as a long shot.
Test with the drive in another system. Pull the boot drive and connect it to a known-good machine as a secondary drive. If it reads fine, the drive is likely okay and the problem is the controller or cables. If it doesn't, the drive itself is the culprit. Back up data now if you can.
Replace the controller or drive. If you've reseated, updated, and tested, the hardware is just worn out. I've replaced more SATA controllers than I can count on old desktops. Sometimes it's cheaper to swap the whole machine, but for a server, a new controller is usually worth it.

If the main fix doesn't work

Reseating didn't cut it? Try these:

Change the SATA mode in BIOS. Switch from AHCI to IDE, or vice versa. If the drives are set to RAID but you're not using RAID, change that. I've seen a misconfigured BIOS setting produce this exact error on a Dell Precision workstation. Just remember, changing modes can make an existing Windows install unbootable – so only try this if you're prepared to reinstall.
Check for loose RAM. Weird, I know, but a loose RAM stick can cause all sorts of bizarre hardware errors, including this one. Re-seat RAM modules and see if the error stops.
Look at the event log. If you can get into Windows at all, open Event Viewer and look under System for entries around the time of the error. They'll often point to the specific device (like "disk" or "storport"). That's a breadcrumb to the failing hardware.
Run a hardware diagnostic. Boot into Dell's ePSA, HP's UEFI Diagnostic, or use a bootable tool like MemTest86+ for RAM. These can isolate the failing component without guessing.
Check for overheating. Feel the controller card and drives. If they're scorching hot, you need better airflow. Overheating causes intermittent hardware errors that are maddening to chase.

Prevention tip

Back up your data and back up again. This error is a harbinger of hardware death. Once you've fixed it, replace the questionable component proactively. Also, keep your firmware updated – manufacturers fix bugs that cause these issues. And for the love of all that's holy, shut down the machine before going inside. Loose cables are the number one cause of this error in the wild.