Fix ERROR_LONGJUMP (0x000002AA) in Windows

You're not alone with this one

Getting the ERROR_LONGJUMP error — code 0x000002AA — is frustrating because it usually kills whatever program you're running. I've seen this on Windows 10 and 11 systems, often right after a crash or when booting a game or old software. The message says "A long jump has been executed," but that's Microsoft's way of saying the program tried to leap to a memory spot that doesn't exist anymore. Let's fix it.

Step 1: Run the System File Checker (this works 7 out of 10 times)

Corrupted system files are the main cause. Here's how to find and fix them.

1. Press Windows Key + X and select Terminal (Admin) or Command Prompt (Admin). If you see User Account Control pop up, click Yes.
2. Type this command and press Enter:
   

   sfc /scannow

   After you press Enter, you'll see a progress bar. It takes 10-15 minutes on most machines. Don't close the window.
3. When it finishes, you'll see one of three messages:
   
   • "Windows Resource Protection did not find any integrity violations." — Go to Step 2.
   • "Windows Resource Protection found corrupt files and successfully repaired them." — Reboot your PC and test the program that gave the error.
   • "Windows Resource Protection found corrupt files but was unable to fix some of them." — Run this next command, then run sfc /scannow again.
4. If you got the third message, type this and press Enter:
   

   DISM /Online /Cleanup-Image /RestoreHealth

   DISM takes 20-30 minutes. It downloads clean system files from Windows Update. Let it finish completely.
   After DISM completes, run sfc /scannow again. It should fix everything now.

Step 2: Update or roll back your graphics driver

This error loves to show up when a GPU driver is either too old or too new (yes, beta drivers cause this). Here's what to do.

1. Press Windows Key + X and choose Device Manager.
2. Expand Display adapters. Right-click your graphics card (NVIDIA, AMD, or Intel) and select Properties.
3. Go to the Driver tab. Look at the Driver Date. If it's more than 6 months old, you need an update. If it's less than a month old and the error started after that date, you need a rollback.
4. To update: Click Update Driver → Search automatically for drivers. Windows will find the latest stable version. Reboot after it finishes.
5. To roll back: Click Roll Back Driver. If the button is grayed out, you can't roll back. Instead, go to your GPU manufacturer's site, download the driver from 3-4 months ago, and install it manually. Reboot after.

Step 3: Check for memory corruption — quick test

Sometimes the error is from bad RAM. This is less common but easy to test.

1. Press Windows Key + R, type mdsched.exe, and press Enter.
2. Choose Restart now and check for problems (recommended).
3. Your PC will reboot and run the Windows Memory Diagnostic tool. It takes 10-20 minutes. You'll see a blue screen with a progress bar and a status bar that says "Pass 1 of 2."
4. After it finishes, your PC reboots. When you log back in, a notification will appear in the bottom-right corner. Click it to see results. If it says "No errors were detected," your RAM is fine.

Why this fix works

The ERROR_LONGJUMP error (0x000002AA) happens when a program's code tries to jump to an address that's either corrupted or not mapped into memory. Think of it like giving your GPS a destination that doesn't exist on the map. SFC repairs the corrupted system files that cause these invalid jumps. Drivers — especially graphics drivers — map memory addresses for hardware. When they're wrong, every jump a program makes can land in a garbage spot. Fixing the driver fixes the address map.

Less common variations and their fixes

Sometimes the above steps don't cut it. Here's what else I've seen cause 0x000002AA.

Antivirus interference

Overzealous antivirus software can block certain memory jumps. If you're using a third-party antivirus (Norton, McAfee, Bitdefender, etc.), try disabling it temporarily and see if the error goes away. If it does, add the program that crashed to the antivirus's exclusion list. I've seen this most often with Norton Internet Security on Windows 10.

Corrupted program installation

If the error only happens with one specific program (like a game or an old accounting app), reinstall that program. Uninstall it first via Settings → Apps → Installed apps. Then download a fresh copy from the official source and install it again. This clears any corrupted program files that might contain bad jump instructions.

Outdated BIOS or firmware

This is rare, but I've seen it on Dell Optiplex machines and some HP laptops. A BIOS update can fix memory mapping issues that cause jump errors. Check your motherboard or PC manufacturer's support site for the latest BIOS. Only update BIOS if you're comfortable — a failed update can brick your machine. If that sounds scary, skip this one.

Prevention — keep it from coming back

Once you've fixed the error, do these three things to stop it from returning.

• Run SFC monthly. Open Command Prompt as admin and type sfc /scannow. Make it a habit. Catches corruption early.
• Keep drivers current, but not bleeding edge. Only install WHQL-certified drivers (the signed, stable ones from the manufacturer). Skip beta drivers unless you're testing something specific.
• Don't use registry cleaners. They're snake oil. I've seen them delete valid entries and cause jump errors. Stick with the built-in tools.

That's it. Run SFC, check your GPU driver, and test your RAM. One of those will kill the 0x000002AA error. You're good to go.