Skip to main content
R
richt_66
New Participant
February 23, 2010
Question

AdobeARM.exe Application Error

  • February 23, 2010
  • 6 replies
  • 60510 views

I get an Application Error with "AdobeARM.exe" every time I boot my computer and frequently when running my Acrobat Pro Version 9.3.0. It is an "unknown software exception". I am running XP-64 bit. Otherwise the program seems to run okay. Anyone know what this is and why this is happening?  -Thanks

    This topic has been closed for replies.

    6 replies

    S
    strn.29849877k6ri
    New Participant
    May 12, 2023

    Try this simple tricks,

    go to the path where adobeARM is :

    C:\Program Files (x86)\Common Files\Adobe\ARM\1.0

    then move the program adobeARM.exe to other folder, or.. delete it

    close all application, then try open pdf file

    done.. works for me

     

    A
    Anonymous
    June 16, 2010

    I currently have the same problem, using Acrobat Pro 9.3.0 on Win7 64-bit

    .

    I then upgraded manually to 9.3.2, but still having the same error.

    The crash happens on startup and also when manually run.

    AdobeARM.exe v1.1.5.0

    Any software updates for this?

    update: creating the registry keys as indicated in a previous post does not create a logfile for me

    Best regards

    L
    LeoUpdaterX
    Participating Frequently
    June 16, 2010

    You should be using registry key below on 64bit:

    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Adobe\Adobe ARM\1.0\ARM

    Thanks

    A
    Anonymous
    June 16, 2010

    Thank you for the info but I already was using that key, with no success.

    I managed to get the logfile created when I changed updater settings in Acrobat Pro (edit->preferences...->Updater).

    Following was written to logfile:

    [2010-06-16 23:41:00] Adobe ARM launcher started.
    [2010-06-16 23:41:00] Command Line: /ArmPrefs /MODE:0
    [2010-06-16 23:41:00] updating preferences...
    [2010-06-16 23:41:00] mode: 0
    [2010-06-16 23:41:00] Set preference in registry.
    [2010-06-16 23:41:00] Adobe ARM launcher finished.

    Then I tried to run 'Check for Updates' again from 'Help' menu, it crashed, but no info written to logfile.

    update: here is the logfile windows created:

    Version=1
    EventType=APPCRASH
    EventTime=129211985880762875
    ReportType=2
    Consent=1
    UploadTime=129211985958341178
    ReportIdentifier=14c84f5b-7991-11df-ac86-005056c00008
    IntegratorReportIdentifier=14c84f5a-7991-11df-ac86-005056c00008
    WOW64=1
    Response.BucketId=1752369600
    Response.BucketTable=1
    Response.type=4
    Sig[0].Name=Application Name
    Sig[0].Value=AdobeARM.exe
    Sig[1].Name=Application Version
    Sig[1].Value=1.1.5.0
    Sig[2].Name=Application Timestamp
    Sig[2].Value=4b22dc74
    Sig[3].Name=Fault Module Name
    Sig[3].Value=AdobeARM.exe
    Sig[4].Name=Fault Module Version
    Sig[4].Value=1.1.5.0
    Sig[5].Name=Fault Module Timestamp
    Sig[5].Value=4b22dc74
    Sig[6].Name=Exception Code
    Sig[6].Value=c0000005
    Sig[7].Name=Exception Offset
    Sig[7].Value=000293c0
    DynamicSig[1].Name=OS Version
    DynamicSig[1].Value=6.1.7600.2.0.0.256.1
    DynamicSig[2].Name=Locale ID
    DynamicSig[2].Value=2067
    DynamicSig[22].Name=Additional Information 1
    DynamicSig[22].Value=0a9e
    DynamicSig[23].Name=Additional Information 2
    DynamicSig[23].Value=0a9e372d3b4ad19135b953a78882e789
    DynamicSig[24].Name=Additional Information 3
    DynamicSig[24].Value=0a9e
    DynamicSig[25].Name=Additional Information 4
    DynamicSig[25].Value=0a9e372d3b4ad19135b953a78882e789
    UI[2]=C:\Program Files (x86)\Common Files\Adobe\ARM\1.0\AdobeARM.exe
    UI[3]=Adobe Reader and Acrobat Manager has stopped working
    UI[4]=Windows can check online for a solution to the problem.
    UI[5]=Check online for a solution and close the program
    UI[6]=Check online for a solution later and close the program
    UI[7]=Close the program
    LoadedModule[0]=C:\Program Files (x86)\Common Files\Adobe\ARM\1.0\AdobeARM.exe
    LoadedModule[1]=C:\Windows\SysWOW64\ntdll.dll
    LoadedModule[2]=C:\Windows\syswow64\kernel32.dll
    LoadedModule[3]=C:\Windows\syswow64\KERNELBASE.dll
    LoadedModule[4]=C:\Windows\system32\msi.dll
    LoadedModule[5]=C:\Windows\syswow64\msvcrt.dll
    LoadedModule[6]=C:\Windows\syswow64\ADVAPI32.dll
    LoadedModule[7]=C:\Windows\SysWOW64\sechost.dll
    LoadedModule[8]=C:\Windows\syswow64\RPCRT4.dll
    LoadedModule[9]=C:\Windows\syswow64\SspiCli.dll
    LoadedModule[10]=C:\Windows\syswow64\CRYPTBASE.dll
    LoadedModule[11]=C:\Windows\syswow64\USER32.dll
    LoadedModule[12]=C:\Windows\syswow64\GDI32.dll
    LoadedModule[13]=C:\Windows\syswow64\LPK.dll
    LoadedModule[14]=C:\Windows\syswow64\USP10.dll
    LoadedModule[15]=C:\Windows\syswow64\SHLWAPI.dll
    LoadedModule[16]=C:\Windows\syswow64\ole32.dll
    LoadedModule[17]=C:\Windows\syswow64\PSAPI.DLL
    LoadedModule[18]=C:\Windows\system32\VERSION.dll
    LoadedModule[19]=C:\Windows\syswow64\COMDLG32.dll
    LoadedModule[20]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7600.16385_none_421189da2b7fabfc\COMCTL32.dll
    LoadedModule[21]=C:\Windows\syswow64\SHELL32.dll
    LoadedModule[22]=C:\Windows\system32\WINSPOOL.DRV
    LoadedModule[23]=C:\Windows\system32\oledlg.dll
    LoadedModule[24]=C:\Windows\syswow64\OLEAUT32.dll
    LoadedModule[25]=C:\Windows\syswow64\urlmon.dll
    LoadedModule[26]=C:\Windows\syswow64\CRYPT32.dll
    LoadedModule[27]=C:\Windows\syswow64\MSASN1.dll
    LoadedModule[28]=C:\Windows\syswow64\iertutil.dll
    LoadedModule[29]=C:\Windows\syswow64\WINTRUST.dll
    LoadedModule[30]=C:\Windows\system32\USERENV.dll
    LoadedModule[31]=C:\Windows\system32\profapi.dll
    LoadedModule[32]=C:\Windows\system32\IMM32.DLL
    LoadedModule[33]=C:\Windows\syswow64\MSCTF.dll
    State[0].Key=Transport.DoneStage1
    State[0].Value=1
    State[1].Key=DataRequest
    State[1].Value=iData=1/nDumpFile=//Upload//iCab//579D96D7BD6541A9827689F81A936EDB.cab/nDumpServer=watson103.Watson.microsoft.com/nResponseServer=watson103.Watson.microsoft.com/nResponseURL=//dw//StageFour.asp?iBucket=1752369600&szCab=579D96D7BD6541A9827689F81A936EDB.cab&EventType=AppCrash32&MID=73E0C566-8B0D-48D6-BA95-5B734F39B62F/nBucket=1752369600/nBucketTable=1/nResponse=1/n
    FriendlyEventName=Stopped working
    ConsentKey=APPCRASH
    AppName=Adobe Reader and Acrobat Manager
    AppPath=C:\Program Files (x86)\Common Files\Adobe\ARM\1.0\AdobeARM.exe

    N
    nstrom
    New Participant
    April 14, 2010

    I also get the same error fairly regularly on my PC and can generally trigger it by going to select Help | Check for Updates in Acrobat, although sometimes it does work without the error. Windows XP Professional x64 SP2, 4GB RAM, w/ all current Windows updates. Just updated to Acrobat Standard v8.2.2 though I got the same error on the previous version as well.

    Let me know anything else I can do to help diagnose this -- it looks to be an identical crash signature (ntdll.dll offset 0004f053) as the others in this thread.

    L
    LeoUpdaterX
    Participating Frequently
    April 14, 2010

    The crash is in ntdll.dll and Google returns some info on search for 0004f053, but I could not find a solid solution.

    Meanwhile, can you please set

    DWORD value iForbidURLDownloadToFile to 1 in the following registry key below? It should prevent crash in the future.

    HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Adobe ARM\1.0\ARM

    Thanks

    A
    atosbur
    Participating Frequently
    April 15, 2010

    After upgrading to the latest patch 9.3.2 (April Release), the version of AdobeARM.exe is shown as 1.1.7.0 and with this exe there's no crash happening at startup on my XP 64 bit machine.

    B
    barnicoat
    New Participant
    March 23, 2010

    I have the same problem and YES I am running the 64 bit version of Windows Server 2003.  Is there an update to correct this problem? It is filling up my Application Event Viewer.

    R
    richt_66Author
    New Participant
    March 23, 2010

    I have not found one yet. I am very frustrated.

    I
    Ivanstankovic
    New Participant
    March 23, 2010

    guys,

    this is what worked for me ...

    I have XP64

    remove content from

    C:\Program Files\Common Files\Adobe\ARM

    Uncheck and delete reg key from "msconfig" (start-->run--> type msconfig -->enter) as start up item.

    Hope this helps for some of you .....

    R
    richt_66Author
    New Participant
    March 23, 2010

    Leo,

    Here is the last part of 'AdobeARM.log' after I replaced the 'AdobeARM.exe' with 1.1.6.0 and it contued to crash. It shows 1.1.7.0. so apparently it us using a newer version possibly from a different location? I placed 1.1.6.0 in the Program Files (x64) folder (non x64 folder did not have 'AdobeARM.exe'). I have not updated the program although it asked me to. I am officially confused...

    Regards.

    A
    Anonymous
    March 13, 2010

    I receive the same errors frequently at system startup. It seems it is related to operating system version - this error appears at my systems with XP x64 and Server 2003 x64 installed only, not at x86 systems. I tried set AdobeARM.exe compatibility mode - XP, W2K, NT4 - with no success. What is the most annoying thing: faulting AdobeARM residing in memory effectively blocks Internet Explorer html rendering engine. This causes impossibility to:

    - run Internet Explorer (no window appears)

    - see e-mails in Outlook (empty message subwindow, no text.

    The only way to gain access to IE & e-mails is to kill AdobeARM.exe (or disable its autorun).

    Can we know solution of this problem? The exact error message follows.

    "Faulting application adobearm.exe, version 1.1.5.0, faulting module ntdll.dll, version 5.2.3790.4455, fault address 0x0004f053."

    L
    LeoUpdaterX
    Participating Frequently
    March 14, 2010

    Will the same error happen if you start your Acrobat application and select menu Help\Check for Updates?

    A
    Anonymous
    March 14, 2010

    "Will the same error happen if you start your Acrobat application and select menu Help\Check for Updates?"

    Afaik no, if I test manual update all is OK, AdobeARM hangs only when it runs automatically at user logon. But it may also depend on fact that there are no updates for Adobe Reader right now.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices