STATUS_SHARED_IRQ_BUSY (0XC000016C) – Fixing IRQ Conflicts on Older PCs
This error pops up when a device can't start because another device is hogging its IRQ. I've seen it most on old XP/Vista boxes with PCI cards sharing an interrupt.
You've got a Windows machine—likely an older one running XP, Vista, or even 7—that boots up fine but throws a blue screen with STATUS_SHARED_IRQ_BUSY (0XC000016C) when a specific PCI device tries to start. Maybe it's a network card, a SCSI controller, or some legacy audio card. I had a client last month whose entire print queue died because their parallel port card refused to load after a CMOS battery swap. The system boots, but that one device just won't work.
The root cause is stupid simple: two devices are fighting over the same interrupt request line (IRQ). On older PCs with ISA slots, each device got its own IRQ. But with PCI and ACPI, Windows tries to share IRQs to save resources. When one device doesn't play nice with sharing—or the BIOS assigns the same IRQ to two devices that can't share—you get this error.
The fix isn't complicated, but it takes some trial and error. Here's the order I'd work through it.
Step 1: Reseat the Card
Half the time, the card's just not seated properly. Power down, unplug the machine, open the case. Pop out the PCI card giving you trouble, clean the edge connector with a pencil eraser (don't use anything wet), and reseat it firmly. Boot up. Fixed it? Done. If not, move on.
Step 2: Move the Card to a Different PCI Slot
Different slots often use different IRQ routing. I've seen a sound card work fine in slot 2 but crash the system in slot 3—same card, same drivers, just different IRQ assignment. Move the device to another slot. If the slot's empty and the error disappears, that's your fix. If it still fails, try yet another slot. On some boards, PCI slots 1 and 2 share an IRQ with the GPU or onboard stuff. Slot 3 or 4 might be isolated.
Step 3: Force a Specific IRQ in BIOS (If Available)
This is the nuclear option. Reboot and mash F2, Del, or whatever key gets you into BIOS. Look for something like IRQ Resources, PCI Configuration, or PnP/PCI Settings. If you see an option to reserve IRQs for legacy devices, you can assign a specific IRQ to the troubled device. Set it to IRQ 5, 7, 9, or 10—pick one that's not already used. Save and exit. Boot into Windows. If it still fails, try a different IRQ. I've had to do this on an old Dell Optiplex GX280 where the NIC just wouldn't share with the onboard audio. Assigned it IRQ 10 and it worked for years.
If your BIOS doesn't have that option (most modern ones don't), skip this step.
Step 4: Disable ACPI IRQ Steering in Windows (If on XP)
This only applies to Windows XP. ACPI was too clever for its own good. Open Device Manager, right-click Computer > Properties > Device Manager. Under System devices, find Advanced Configuration and Power Interface (ACPI) PC. Right-click it, choose Update Driver, then Install from a list or specific location > Don't search > Have disk. Browse to C:\Windows\Inf and select hal.inf. Pick Standard PC (not ACPI). This disables ACPI IRQ steering, giving each device a dedicated IRQ. Reboot. Warning: this can mess up power management and wake timers, but it often fixes the IRQ sharing issue. On Vista and 7, this isn't an option—you'd need to tweak the registry instead.
Step 5: Check for a Bad Card or Driver
If none of the above works, the card itself might be faulty. Try it in another known-working PC. If it throws the same error there, replace the card. Also check if the latest driver is really the right one. I had a client with a Promise SATA card that would only work with the driver from 2005—the 2010 update broke IRQ handling entirely.
What If It Still Fails?
If you've tried all the steps and the error persists, consider replacing the motherboard or the device. Sometimes the board's IRQ routing is just broken. Or you could disable the conflicting device in Device Manager if you don't need it. But let's be real—if you're dealing with a machine that old, it's probably time to retire it. I'm not saying throw it away, but at some point, the effort to fix an IRQ conflict outweighs the cost of a $50 replacement card or a $100 used tower.
One last thing: I've seen a bad PCI riser cable cause this on rackmount servers. If you're using a riser, try the card directly in the motherboard slot. You'd be surprised how often that's the real problem.
Was this solution helpful?