You're mid-task, and suddenly a dialog pops up: "The process terminated unexpectedly." The error code is 0X0000042B (that's ERROR_PROCESS_ABORTED). This usually happens right when you launch a specific app — maybe a video editor, a game, or an older business tool. It can also hit during shutdown or when a background service tries to start. The process just dies. No BSOD, no freeze — it's gone.
The root cause is almost always a misbehaving driver or a corrupted system file. Sometimes it's a bad app update. But here's the thing: the error code itself is generic. It doesn't tell you which process failed. So the fix starts with identification, not blind reinstalling.
Step 1: Find the Faulting Process
Open Event Viewer (Win+R, type eventvwr.msc). Go to Windows Logs > System. Look for red error events that match the time your process died. The source might be Application Error or Windows Error Reporting. The details will list the faulting module (e.g., ntdll.dll or nvlddmkm.sys). Write that down — it's your clue.
Step 2: Update or Roll Back the Suspect Driver
If the faulting module is a GPU driver (nvlddmkm.sys, atikmdag.sys, igfx), update it from the manufacturer's site — not from Windows Update. Use DDU (Display Driver Uninstaller) to clean the old one first. If it started after a recent driver update, roll back to the previous version. That's the quickest win.
Step 3: Run System File Checker
Corrupted system files cause this more often than you'd think. Open an elevated Command Prompt and run:
sfc /scannowLet it finish. If it finds issues, reboot and try the app again. If SFC reports errors it can't fix, run DISM next:
DISM /Online /Cleanup-Image /RestoreHealthThat will pull fresh copies from Windows Update. It takes a while, but it's worth it.
Step 4: Check for Conflicting Software
If the event log points to an antivirus or a shell extension (like a right-click menu tool), that's your culprit. Antivirus intercepts process creation and can kill legitimate apps if it misidentifies them. Temporarily disable your AV (not Windows Defender — the third-party one) and test. If the error goes away, add an exclusion for the app.
Step 5: Repair the Application Itself
If it's a specific app, go to Settings > Apps, find the app, and choose Modify or Repair. That's faster than a full uninstall/reinstall. If repair doesn't work, uninstall it, delete leftover folders in %AppData% and %ProgramData% for that app, then reinstall fresh. Don't bother with compatibility mode unless the app is ancient (like pre-Vista).
Step 6: Check for Memory or Overclocking Issues
If the error is random and hits different apps, suspect RAM or an unstable overclock. Run mdsched.exe to test memory. If you've overclocked CPU or GPU, set everything back to stock and see if the error stops. I've seen more than one system where an aggressive XMP profile caused exactly this.
Still Failing? Here's What to Check Next
If you've done all that and the error keeps coming back, check the following:
- Power supply health. A dying PSU can kill processes under load. Check with a PSU tester or swap if you have a spare.
- Disk errors. Run
chkdsk /f /ron your system drive. Bad sectors can cause file corruption that SFC misses. - Windows updates. Install all pending updates, including optional ones. Sometimes a bug fix addresses this exact issue.
- Clean boot. Services from third-party apps can interfere. Do a clean boot (msconfig) and gradually enable services to find the troublemaker.
That last one is tedious, but it works when the event log isn't helpful. I've had cases where a background service from a printer driver kept killing a database app. You won't find that until you do a clean boot.
In my 14 years, I've seen 0X0000042B come down to three things: a GPU driver, a corrupted OS file, or a bad memory stick. The steps above cover all three. Start with the event log, not with reinstalling Windows. You'll save yourself hours.