Read About Werfault Application Error In Brief.

Asked By 30 points N/A Posted on -


I have a question regarding werfault application error. I was not able to find anything about it anywhere; can anyone help me in explaining this?

Thank you.

Answered By 0 points N/A #302408

Read About Werfault Application Error In Brief.


This problem could happen if the file is corrupted due to some reason. If you are receiving this bug frequently, then it will become very irritating.

  •  A fix for this is to run the File checker of System which will scan your computer and repair your system files. After the completion of scan, restart your system.
  •  An alternative would be to execute Windows Memory Diagnostic Tool.
  • If any of the above option helps, then it is good for you. But if it does not, then you must to disable Windows Error Reporting Service.
Answered By 590495 points N/A #303355

Read About Werfault Application Error In Brief.


“werfault” or the “werfault.exe” program is part of the Windows error reporting system that collects and sends error logs from your machine to Microsoft. It has a partner program named “wermgr.exe.” When one of these programs has a problem, you may receive the message “The instruction at the referenced memory could not read. Click on OK to terminate the program.”

This error message is common to Microsoft Windows because I also receive it on other programs. The cause of the error can be from either of the programs or from the physical RAM. If you receive an error related to “wermgr.exe” or “werfault.exe,” try running the SFC utility. The problem happens when either of the files is corrupt.

Click “Start,” “All Programs,” “Accessories” then right-click “Command Prompt” and select “Run as administrator.” In the command prompt window, type without quotes “sfc /scannow” then hit Enter. This scans the protected system files on your system drive and replaces incorrect versions with correct ones. When SFC is finished, close the command prompt and restart your computer. See if it works.

If this fails, try running the Windows Memory Diagnostics Tool.

Related Questions