1 Correct answer
Wow, talk about a blast from the past. As you might have guessed this issue from over 2 years ago was never resolved. I spent a long time just dealing with the delayed opening but just leaving Acrobat running at all times. It didn't get resolved until I took it upon myself to upgrade to the 64 bit version. Creative Cloud refused to give me the 64 bit version and I had to upgrade manually. Since then Acrobat starts right up.
34
Replies
crosby_pm,
I am so sorry I took this long to get back to you on this.
As I examined the minidump there's an error message that the your system detected. I am surprised you didn't get this collected in the event log in your Windows 10 nor an error message that should've popped.
It does seems like everything is normal like you mentioned. But I see that you have an antivirus in your screen shots. Is that McAfee?
Also you're missing two important Adobe Acrobat planned updates since Decembeer 2019. It also surprised me to know that your product hasn't performed this automatically.
UNLESS something like a lack of driver updates, OR between the OS running Windows Defender with MacAfee antivirus simultaneously, for example, I don't know how to resolve this issue if I can't get my hands on that computer.
Could it be possible that you've upgraded this system from a prior version of windows running the upgrade on top of the old version, instead of a clean install from scratch?
Would disabling User Access Control (UAC) for the Acrobat.exe application improve the lag you're experiencing as the application loads up for the first time?
So for now, let's take a look at the minidump:
You may reference to the following Micrososft guidance on "dereferenceing objects" How-to:
https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/object-reference-tracing
And have fun with that 😄 ... just messing! But basically we do have a "Parameter is incorrect message" that could be many many things at this point.
So using the info provided in the slide above as a reference, and keeping in mind that Windows 10 is 64 bit while Acrobat.exe is an application in 32bit, I am thinking that applying the missing updates could resolve the issue.
The main reasoning behind this is the unsigned 64bit integrals captured in the crash dump.
It almost seems like whatever is trying to load up the 64bit integer value is misinterpreted and therefore the resulting integer is using the incorrect amount of storage in memory to process an instruction; the application seems to be expecting value as if it was meant for a 64bit signed register or perhaps a 32 bit unsigned register value.
From a computer repair point of view, these are the areas that I would troubleshoot or check:
- check for macros running in the background (Trust Manager Preferences, Security Enhanced settings, embedded files in the PDF, attachments, etc.)
- antivirus - disable and see if any difference when atring up Acrobat
- missing updates - manually apply the missing updates from here: https://helpx.adobe.com/acrobat/release-note/release-notes-acrobat-reader.html
- increase swap space or virtual memory
- Disbale User Access Control
- Disable Data Execution Prevention
- Disable Acrobat PDF Maker add-on in browser and MS Office applications
- Test these troubleshooting tips with the computer NOT connected to the Internet
- check the memory sticks - Physically inspects the RAM and even replace the memory stick(s) for other known-good RAM to see if this problem only appears with the cuyrrent RAM
Last, let's try some old school DOS shell scripting.
Close Acrobat and open up browser windows , listen to music in Youtube, download files from a website, etc. Do everything that you would normally do in your computer as you perform that batch job below.
Open the command prompt (CMD.exe) and run this line:
for /f %i in ('START ACROBAT.EXE') do START /HIGH %i
Post back and let me know if you notice how fast Acrobat opens up or not when invoked through the command prompt versus double clicking on a PDF file.
AdChoices