Windows 10 users periodically complain about the WerFault.exe – Application Error that appears when running various applications. In this article, you will find more information about what WerFault.exe is, and why the “WerFault.exe – Application Error” bug happens. Also, we will provide you with some tips on how to fix the “WerFault.exe – Application Error” error in Windows 10.
What is the Werfault.exe Process in Windows?
WerFault.exe is one of many default Windows services responsible for your PC running as smoothly as possible. It does not directly affect a computer’s stability and performance, though. The WerFault.exe main purpose is to collect logs and error reports in different Windows components and apps. It is a part of Windows Error Reporting Service (WerSvc) that runs in the background and monitors your computer.
When any application fails with an unhandled exception in a process, the Windows Error Reporting service starts the werfault.exe process with the following parameters:
C:\WINDOWS\system32\WerFault.exe -pss -s X -p processID -ip processID
* processID is the process ID (PID) of the failed application.
After that, the second instance of WerFault.exe is launched:
WerFault.exe -u -p processID -s X
The following event is written to the Event Viewer log:
Log Name: Application Event ID: 1000 Event source: Application Error Event message: Faulting application name: crashed.EXE, version: EXE_file_version, time stamp: EXE_file_build_time Exception code: Fault application path: EXE_path Fault module path: EXE_or_DLL_path
WerSvc automatically generates and collects error data and then lets the user decide what to do with that information. You can either send the data to Microsoft or third-party developers or leave it as is and do nothing.
Whenever an app encounters an error, WerFault.exe kicks in and collects an error report data. When Windows Error Reporting detects a failed application, the following error appears:
WerFault.exe – Application Error
The instruction at x0000000 referenced memory at x0000000. The memory could not be written.
Click on OK to terminate the program.
Or:
The application was unable to start correctly 0xc0000142. Click OK to close this application.
This error is not caused by WerFault.exe itself, but by some programs on the computer or their components (for example, DLLs). In this case, WerFault only collects the error report. To find the name of the failed process, open the Event Viewer (eventvwr.msc), expand the Application log, and look for the latest event with EventID 1000. The description of this event contains information about the failed exe (dll) file.
Some users think that the easiest way to fix WerFault.exe – Application Error is to delete the WerFault.exe. It is important to mention that WerFaultsystem-protected protected file. That means the user cannot delete it from the computer to fix the error “WerFault.exe – Application Error.”
An intermittent and random WerFault.exe error is not a problem. If you have encountered the problem once or twice, you probably should not care about it at all.
However, if the error appears constantly, you need to fix your machine. One of the side effects of constant WerFault.exe errors is multiple Werfault.exe processes in Task Manager. They cause a high CPU load and reduce performance.
Note. Check how to activate Windows on KMS server.
Fix WerFault.exe App Errors
As usual, we recommend beginning troubleshooting any computer with the following simple tasks that often fix the most common bugs in Windows 10. If nothing below helps, proceed to more complicated options:
- Restart your computer.
- Check for Windows updates and install them if available.
- Check for software updates. That is particularly relevant if the WerFault.exe error happens with some specific application.
- Run the fault app in the compatible mode (Right click > Properties > Run this program in compatible mode > Select the previous version of Windows);
- If possible, reinstall the application that is causing the werfault.exe error;
- If available, use system restore points to roll back your Windows installation to a previously working state.
- Check for drivers updates and install, if available (Win + I > Update and Security > View optional updates > Download and install if there are any driver updates available);
- Temporarily disable your antivirus, especially if you are using free third-party solutions.
The WerFault.exe error may happen if one of the dll libraries in the Windows folder is missing or damaged. Usually, the problem should be gone after checking the integrity of system files using a dedicated command in Command Prompt.
Launch Command Prompt with Administrator privileges and execute the following command:
sfc /scannow
Then, run the next command:
Dism /Online /Cleanup-Image /RestoreHealth
Finally, check your system drive for file system errors. Execute the following command:
chkdsk C: /f
All you need to do is sit back and wait for the system to complete the process. Windows will automatically try to fix detected issues. After executing the commands, you need to restart your computer.
Next, check your computer RAM for errors. To check memory in Windows 10, use the built-in MdSched.exe tool. It is worth mentioning that in case your computer has some hardware problems with RAM, you will notice lots of weird behavior, issues, crashes, and reboots. Still, checking RAM is one step to ensure your components are working properly.
Finally, you can turn off the Windows Error Reporting Service to get rid of the error. Do note that this is how you get rid of symptoms, not the cause of the error, which is not the best way to troubleshoot your computer. Still, if there are no other issues and your computer works fine, disabling the WerSvc may give you peace of mind.
- On your keyboard, press Win + R and enter the services.msc command;
- In the list of services find Windows Error Reporting Service and double-click it;
- Stop the service and change its startup type to Disabled;
- Save the changes and restart the computer.
5 comments
This is an excellent article. Had no idea what WerFault.exe even was. Now I know. Going to try the SFC in SafeMode first, and if that doesn’t resolve the pop-up memory error, I’m just going to disable the Windows Error Reporting Service. IMHO, that service is useless MS fluff. “Send the error report to Microsoft”. Who actually *does* that, anyway?? :-) Like I noted, useless MS fluff. Since my company has rolled-out a lot of Win10 patches recently, this odd error only started to occur (and frequently at that) about a few weeks ago on many PCs. So, I suspect some bad/quirky patch is the root cause of this, although I have no absolute proof of that. Thanks again for this well-written article.
Excellent article – worked for me specifically the Dism /Online /Cleanup-Image /RestoreHealth fix. Read article to learn about it
Great article, I executed both commands (sfc /scannow and Dism /Online /Cleanup-Image /RestoreHealth) and error message disappeard :-)
Thanks!
I tried everything, nothing worked, error still pops up.
Im having the same issue did you ever get it fixed?