Skip to main content
Participant
October 19, 2015
Question

AcroRd32.exe or WerFault.exe application error

  • October 19, 2015
  • 10 replies
  • 35970 views

Getting an AcroRd32.exe or WerFault.exe application error every time I try to open a pdf. It reads: "Instruction at 0x0000646e referenced memory at 0x0000646e.  The memory could not be written.  Click on OK to terminate the program"  I can't get rid of this popup when I click "OK" or "Close"  I can still open a pdf, but the popup cannot be closed and my PC runs a lot slower, both of which are annoying to say the least.  Can someone help me?

    This topic has been closed for replies.

    10 replies

    Participant
    March 12, 2020

    Hi, I was getting the WERFAULT error for Acrobat Pro DC on Server 2012 R2.  I found that by setting the compatibility mode to Windows 7 on the icon stopped the error from occurring.  Perhaps there's a compatibility issue with Windows 8/2012.

    Participant
    November 21, 2018

    In the latest version of Windows 10 – You may have come across the WerMgr.exe, AcroRd32.exe or WerFault.exe application Error Fix. Which is not a cup of cake for everyone. This error can ruin your laptop experience completely and won’t let you work entirely focused. So, In this article  – I’ve decided to share some of the methods that I’ve tested on my window 10 PC to eliminate this problem. I hope, this information will help you out. Let’s have a look at them.

    This error about the WerFault.exe application mainly occurs due to the incompatibility of the display drivers or other drivers with your system hardware. Thus, windows keep on reporting such issues. But, Most of the time everything seems to work fine. Thus, you must know about these steps – in order to keep things together before they get out of your hands.

    joela18440829
    Participant
    March 15, 2016

    Hi Everyone,

    I was able to fix this error by doing the following steps.

    1. Uninstall adobe reader

    2. Run CCleaner tune up

    3. Run Malwarebytes scan

    4. Checked for any junk that got installed since I started having a problem

    5. Shutdown and waited about 10 seconds

    6. Restarted and downloaded newest version of adobe reader

    7. Tested and no more issues

    Clean up:

    Uninstalled CCleaner and Malwarebytes

    This might have been a little bit of overkill but my customer is happy and adobe is working great again.  When before the program wouldn't even open and they were preforming hard shutdowns to get rid of the error.

    Good Luck all,

    -Joel

    December 8, 2017

    Here is how to fix WerFault.exe Application Error in Windows 10

    Open command prompt.

    Now, write sfc /scannow and hit enter

    The sfc /scannow command will scan all protected system files, and replace the corrupt files with a cached version already stored in windows dllcache folder.

    Source:- http://merabheja.com/werfault-exe-application-error-in-windows-10/

    December 4, 2015

    Hello,

    Has anyone managed to get a response from Adobe support for this issue, we have seen this on 2 PC's in the last 7 days.

    Suggestions on here that have been tried;

    • Disable of the protection mode (Not available Adobe Reader)
    • Updated Application, uninstalled, roled back and installed to older versions (non of which have resolved the issue)
    • Using the cmd "taskkill -im werfault.exe /"f is fine but going to disable the alerts to stop this all together in services

              This is not in my opinion a fix this needs to be addressed by Adobe properly as disabling services in the OS on multi machines in an environment is not going to be a feasible solution, and the only option thus far is re-build the OS from an image.


    Still to be investigated further AV and Processes running with Process ProcessActivityView.


    Please could someone get back to me if anyone has had better luck so far.


    Cheers,

    Martyn


    Participant
    December 2, 2015

    Try scanning for Malware with Malwarebytes and Hitman Pro seemed the fix the issue for me and a couple others.

    ashutoshmehra
    Adobe Employee
    Adobe Employee
    November 25, 2015

    For anyone facing this issue, could you run AcrobatMonitor and share the logs?

    * You can download AcrobatMonitor from this page http://labs.adobe.com/downloads/acrobatmonitor.html that also contains the instructions on running it.

    * See https://forums.adobe.com/message/6127598 on how to share a document

    You can email me the link to the logs at amehra@adobe.com. The logs should hopefully provide some clues why Reader is running into problems in specific environments (malware, conflict with other apps, ...).

    November 23, 2015

    I have a similar problem it began today 23 Nov 2015. Was running Adobe Reader 10.1.7

    Opening a PDF file produces a Werfault.exe application error pop up to appear, with the message "Instruction at 0x746f7465 referred memory at 0x746f7465. Memory could not be written. Clicking OK or cancel just produces another window with the same message.

    Computer almost ground to a halt, checking Task Manager there were hundreds if not thousands of WerFault operating!

    I deleted Adobe Reader 10.1.7 and downloaded the latest version (10 ?) for Windows 7 (UK), the same problem when attempting to run Adobe Reader. ALL other programs seem to be operating OK.

    Here's Task Manager before...

    Here's Task Manager after trying to read an adobe PDF File.

    Note all the WerFault.exe running and the very small scrolling blob top right!

    Participant
    November 23, 2015

    I have the exact same problem.

    I called adobe tech support last week and they attempted to trouble shoot the problem on the [hone for almost an hour. Still no luck. They said that they were creating a case and escalating the the issue and I would receive a call back in two days . That was last Wednesday. Still no call back. I called today and they said the case was in "processing" and I would get a call back in 24 to 48 hours, the same thing I heard last week. I am SUPER tired of this and to say there tech support is horrible would be understating the case.

    November 23, 2015

    Having downloaded Adobe Reader 10.1.4 I ran it and still had the Werfault problem even with it DISABLED in Windows Services.

    In Adobe disabled Protection Mode.

    Shut down the computer and fired it up again.

    Double clicked on Adobe Reader and it fired up without any Werfault.exe pop up, opened a PDF file again no problem.

    To disable Protection Mode:

    In Abode Reader click EDIT

    Select  PREFERENCES (CTRL K)

    Select GENERAL

    Click 'Enable Protection Mode at startup' to remove tick


    Adobe Employee
    November 17, 2015

    Kindly create and share the crash dump next time you see a crash.

    Steps to create Crash Dump:

    1) As soon as Acrobat Reader DC crashes, open Task Manager.

    2) Go to Processes tab and select AcroRd32.exe process.

    3) Right Click on the Acrobat process and select Create Dump File.

    4) Compress and share the dump file created via some file sharing server

    November 23, 2015

    Hello If it's helpful I've uploaded a screen grab.

    October 23, 2015

    So im having the same error to...Basically i have figured out these things so far:

    1) By disabling the "Windows Error Reporting" service, it can disable the alerts.

    2) Open Task Manager, go to Process. Open Adobe Reader, if you see werfault errors pop up, you can kill them by opening cmd and typing "taskkill -im werfault.exe /f"

    Participant
    November 12, 2015

    Same problem here. For me it's always werfault.exe., never AcroRd32.exe. Only seems to be triggered by Adobe Reader though.

    Neither of alexc's suggestions worked, nor did anything else suggested in this thread. Here's how I posted it at another tech support forum. I am at my wit's end.

    "Error message: https://i.imgur.com/XlzspwD.jpghttp://imgur.com/XlzspwD

    I've tried just pushing the error message offscreen, but eventually my computer will slow to a crawl and I have to reboot anyway.

    If you click OK or the X, it will just keep coming back (immediately). Same if you try to kill it in Task Manager. Same if you do a cmd and type "taskkill -im werfault.exe /f" (Doing that produces hilarious results...its tells me SUCCESS a hundred times before returning me to the command line, as if IT was just hitting "okay" over and over).

    My own google-fu comes up with suggestions to either turn off Windows Error Reporting in the action center (since werfault is Windows Error Reporting executable) or opening administrative tools, locating werfault.exe under services, and either choose disable or "stop" (which is always greyed out anyway unless I hit "start" first.) You guessed it, none of these steps work. Neither did uninstalling and reinstall Adobe Reader, which I need.

    I'd be happy if EITHER I could prevent this error message from occuring OR I could kill it without rebooting, but as I've tried to demonstrate, multiple approaches towards both possibilities have all failed.

    Latitude E6400, more computer specs: http://imgur.com/BfB63SR"

    ashutoshmehra
    Adobe Employee
    Adobe Employee
    October 20, 2015

    For troubleshooting, can you disable Protected Mode (https://helpx.adobe.com/reader/using/protected-mode-windows.html#id_94783) and see if that resolves the issue. If the issue still persists, please do enable Protected Mode again for improved security.

    Let us know how it goes.

    Participant
    October 20, 2015

    I opened the link you provided for diabling Protected Mode, but those instructions are not helping me.  I cannot find anything related to Protected Mode in the Properties and the related tabs of Acrobat Reader DC.  Can you be more specific on the steps I need to take to disable the Protected Mode?  Will this be a permanent solution or a "bandaid" fix that still leaves me vulnerable to viruses, malware, etc?  By the way, this problem started with Acrobat Reader XI, so I deleted that version and replaced it with Acrobat Reader DC - hoping that would solve the problem but it obviously has not.