How to Fix WerFault.exe Application Error in Windows 11

Frequent popups stating “WerFault.exe – Application Error: The instruction at 0x00007FF… referenced memory at 0x00000… The memory could not be read” or “WerFault.exe has encountered a problem and needs to close” disrupt daily computing on Windows 11. WerFault.exe is the executable file for the Windows Error Reporting (WER) service. Whenever a background service, driver, or application crashes, Windows invokes WerFault.exe to log diagnostic crash dumps and transmit telemetry to Microsoft servers. However, when the Windows Error Reporting process itself encounters memory corruption, damaged system DLLs, outdated display drivers, or malware interference, an endless cascade of WerFault.exe crash dialogue boxes can freeze the desktop. This guide outlines practical solutions to repair the underlying corruption and stop WerFault.exe errors.

What Causes WerFault.exe Errors in Windows 11?

Failures within the Windows Error Reporting mechanism originate from system and hardware conflicts:

  • Corrupted Windows System Files: Damaged core system libraries (such as faultrep.dll or wer.dll) failing to execute error reporting routines.
  • Faulty Device Drivers: Outdated graphics drivers or chipset firmware generating unhandled memory exceptions that overwhelm the crash logging service.
  • Hardware Memory (RAM) Faults: Physical memory corruption or defective RAM modules causing read/write violations during memory dump creation.
  • Malware Impersonation: Malicious processes injecting themselves into background processes and masking their activity behind legitimate system names.
  • Corrupted WER Cache: Excessively bloated or corrupt crash dump files residing in %localappdata%CrashDumps.

Method 1: Run SFC and DISM System File Repair Tools

The System File Checker (SFC) and Deployment Image Servicing and Management (DISM) utilities inspect and restore corrupted operating system binaries.

  1. Press Win + S, type cmd, right-click Command Prompt, and select Run as administrator.
  2. Execute the DISM health repair command:
    DISM /Online /Cleanup-Image /RestoreHealth
  3. Wait for the scan to reach 100% and confirm image repair.
  4. Execute the System File Checker scan:
    sfc /scannow
  5. Look for the completion confirmation: “Windows Resource Protection found corrupt files and successfully repaired them.”
  6. Restart your computer.

Method 2: Restart and Reset the Windows Error Reporting Service

Resetting the service state clears lingering memory locks and deadlocked threads.

  1. Press Win + R, type services.msc, and press Enter.
  2. Scroll through the services list and locate Windows Error Reporting Service.
  3. Right-click the service and select Properties.
  4. If the service status is running, click Stop, wait 5 seconds, then click Start.
  5. Ensure the Startup type is set to Manual (the default Windows setting).
  6. Click Apply and OK.

Method 3: Clear Accumulated Crash Dumps and Temp Files

A damaged crash report queue can trap WerFault.exe in an infinite execution loop.

  1. Press Win + R, type %localappdata%CrashDumps, and press Enter.
  2. Select all .dmp files in this folder and delete them.
  3. Press Win + R again, type C:ProgramDataMicrosoftWindowsWERReportArchive, and press Enter.
  4. Delete any orphaned crash report folders.
  5. Empty the Recycle Bin and reboot.

Method 4: Test RAM with Windows Memory Diagnostic

Memory access violation errors (“The memory could not be read”) often signal failing hardware memory sectors.

  1. Press Win + R, type mdsched.exe, and press Enter.
  2. Select Restart now and check for problems (recommended).
  3. Windows will restart into the diagnostic environment and scan your memory modules for hardware read/write defects.
  4. Upon reboot, inspect the results in the notification tray or via Windows Event Viewer. If hardware errors are detected, reseat or replace the malfunctioning RAM stick.

Method 5: Reinstall Display Drivers

Graphics driver crashes are the primary trigger for WER invocation loops.

  1. Press Win + X and select Device Manager.
  2. Expand the Display adapters section.
  3. Right-click your dedicated graphics card (NVIDIA, AMD, or Intel) and select Update driver.
  4. Choose Search automatically for drivers. For comprehensive clean installations, download the latest package directly from NVIDIA or AMD and perform a “Clean Install”.

WerFault.exe Troubleshooting Matrix

Error Characteristic Underlying Root Cause Primary Resolution
WerFault error loops upon launching any 3D game GPU driver crash triggering WER failure Clean reinstall display drivers via GeForce Experience or AMD Adrenalin
“The instruction at 0x… referenced memory” Corrupted system DLLs or failing RAM Run DISM /RestoreHealth and SFC /scannow; test RAM with mdsched.exe
Continuous background CPU spike by WerFault.exe Corrupted crash queue in ReportArchive Purge %localappdata%\CrashDumps and restart Windows Error Reporting service
WerFault executable located outside System32 Malware masquerading as system file Run Windows Defender Offline Scan; verify path is C:\Windows\System32

Frequently Asked Questions

Can I permanently disable WerFault.exe in Windows 11?

You can disable the Windows Error Reporting Service via services.msc (by setting its Startup type to Disabled), which stops error report dialogues from displaying. However, this does not fix the underlying software or driver crashes causing the reports; it merely hides the notifications.

Is WerFault.exe a virus?

No. WerFault.exe is a legitimate, core Windows 11 component located in C:\Windows\System32\WerFault.exe. If you find a file named WerFault.exe located in any other directory (such as AppData or Temp), scan your PC immediately with Windows Defender.

Get the best tech tips delivered straight to your inbox.

Join thousands of readers mastering Apple, Google, Microsoft, and Linux.