Hardware Interrupt Storm on RAM/Motherboard – Fix Now

1. Loose or Faulty RAM – Most Common

You're working and then everything freezes. No mouse movement, no keyboard response. Then a blue screen with WHEA-Logger Event ID 47 pops up. Or maybe you just get a hard freeze with no error at all. This is what we call a hardware interrupt storm. It happens when your computer gets so many interrupt requests it can't respond to anything else.

The number one cause? Loose RAM sticks. I've seen this with DDR4 and DDR5 modules. Even if the clips look fine, the stick can wiggle out just enough to cause trouble. Heat cycling from gaming or video rendering makes it worse.

How to fix it

1. Shut down your PC. Unplug the power cord. Wait 30 seconds for the capacitors to drain.
2. Open the case. Locate your RAM sticks on the motherboard.
3. Press down on the clips at both ends of a stick. They should click open.
4. Lift the RAM stick straight out. Don't tilt it.
5. Look at the gold contacts on the bottom. If they're dirty, use a clean pencil eraser to gently rub them. Wipe with a dry cloth after.
6. Line up the notch on the stick with the slot. Press down firmly until both clips snap back into place. You'll hear a click.
7. Do this for every stick you have.
8. Plug the power back in and start the PC.

After this: If the freezes stop, you're done. If they continue, move to the next fix.

2. Bad Device Driver – Second Most Common

If reseating RAM didn't work, the next suspect is a driver that's sending too many interrupts. I've seen this with network cards (Realtek, Intel), USB controllers, and graphics cards (especially older Nvidia GTX 10-series on Windows 10/11). The trigger is often plugging in a new device or updating a driver through Windows Update.

The interrupt storm from a bad driver looks the same – a sudden freeze lasting 10-30 seconds, then maybe a recovery or a crash. The Event Viewer will show WHEA-Logger Event ID 18 or 47 under "Hardware Events."

How to find and fix the bad driver

1. Press Windows + X and select "Device Manager."
2. Look for any device with a yellow exclamation mark. That's a problem.
3. Right-click that device, choose "Properties." Go to the "Driver" tab and click "Update Driver."
4. If no yellow mark, check the list for network adapters. Right-click your network card, select "Update driver," then "Browse my computer for drivers," then "Let me pick from a list." Try an older driver version if the current one is new.
5. Also update your chipset drivers from your motherboard manufacturer's website. Don't use Windows Update for these.
6. After each driver change, restart the PC and test. Use the PC normally for 20 minutes. If the freeze doesn't happen, you found it.

Pro tip: If the freeze happens right when you plug in a USB device, that specific driver is likely the culprit. Uninstall it from Device Manager (right-click > Uninstall device) and let Windows reinstall a generic driver.

3. Motherboard Fault – Least Common but Most Serious

If RAM and drivers are fine, the problem might be the motherboard itself. A failing chipset, a bad capacitor, or a cracked trace can cause interrupt storms. This happens most often on older boards (3+ years) or boards that got a power surge. You might also see random restarts or the PC turning on but not posting.

There's no easy software fix here. But you can test before buying a new board.

Steps to confirm

1. Check for bulging capacitors near the CPU socket. If any are domed on top or leaking brown stuff, the board is done.
2. Reset the BIOS by taking out the round CMOS battery for 5 minutes. Put it back in.
3. Try running the PC with only one RAM stick in slot A2 (the second slot from the CPU). If the storm stops, the board's memory controller might be weak. Use only that one slot.
4. If you have a spare power supply, swap it. Bad power can cause interrupt issues too.

Real talk: If none of this works, the motherboard is toast. Replace it. A new B660 or B760 board isn't expensive and will fix the problem for good.

Quick-Reference Summary Table

Start with the RAM reseat. That's the fix in 80% of the cases I've seen. If you're still getting freezes, go through the driver list. And if that fails, it's time to look at the board. Don't waste days on this – a hardware interrupt storm only gets worse.