ERROR - referenced memory at 0x00000000000018. The memory could not be read.

[Malissaf]

Hi, I am having this error like many others and unable to find a resolution.

The instruction at 0x00007ffd3edebf9d referenced memory at 0x00000000000018. The memory could not be read.

This is happening for me and another user. Both of us are using Adobe Acrobat Pro (paid) it doesnt seem to be happening to those that are using Free Adobe Acrobat. The error appears to show up at the same time as the AI banner but when I turn this off the error still shows.

I can close the error and use Acrobat, however every new file I open via email, file manager or Teams triggers the error.

I have:

- Uninstalled and reinstalled

- Disable New Adobe

- moved back to "old" Outlook

- Ran Adobe Repair

- preferences > security (enhanced) > turn OFF Enable protected mode

- preferences > accessibility > turn OFF enable assistive technology

- preferences > generative AI > turn OFF enable

- preferences > generative AI > turn OFF banner

Version is 2025.001.20474 | 64bit

Please help as this is impeding my productivity

[Tariq Ahmad]

Hi @Malissaf, 

Thank you for reaching out, and sorry for the troubled experience. 
As you have already found multiple reports about this issue in the Adobe Community, we are aware of it. Sadly, we have been having trouble recreating this behavior in-house. That being said, we are working on this as a priority. 

Please share the diagnostic logs for the error workflow at your end to investigate further.

1. Download and run Diagnostics utility https://adobe.ly/3SLwj6w
2. Select Start Diagnostics.
3. Now Open Acrobat, execute your file, and see the issue.
4. Select Stop Monitoring, and share the log ID with us.
5. Also, we would require the crash log: https://adobe.ly/3YQM27X. Upload the logs to any cloud drive and share the link to download them. 

Will be waiting for the logs and response. Thank you for your support. 

~Tariq

[Malissaf]

To add: Selecting the compatibility check box in properties stops the error. But this can't be the solution!

I will run the diag and send tomorrow.

[Tariq Ahmad]

Thank you for keeping us posted related to the workaround, @Malissaf.

This is a known issue and is currently being worked on. 

Could you also let us know which banner of the Acrobat AI assistant you were referring to in your initial post? If the issue is still reproducible, please share the requested logs. 

Thank you for continued support.

~Tariq

[Tom B ATF]

Two of us are having the exact same issue with an application error referencing memory at 0x00000000000018.  Are there any updates on this other than selecting the compatibility check box?

[[OXT] Adam]

I have the same issue, however only on the machine which I have VMWare Workstation installed, and as such it has some Windows Virtualisation protection options disabled (Memory integrity monitor and core isolation is disabled, however ASLR is still enabled). This is needed to allow the windows machine to use the CPU's Virtualisation Functions to host a non Hyper-V virtual machnine, but under normal circumstances Windows 11 uses some of the processor's virtualisation features to work-around common side-channel exploitation attacks related speculative execution and cache warming. 

This is probably too technical for most people, but disabling the virtulisation protections isn't exactly trivial to do. So if you've installed a non hyper-v hypervisor, AND have needed to use the CPU's virtualisation capabilities for this, then that may be your cause. 

Whilst I'm not a gamer, I've heard that some video game anti-cheat technolgies and proprietary anti-malware solutions (I'm looking at you Crowd Strike) install kernel mode drivers (a.k.a. rootkits) that may affect behavior in the same way.

This may indicate why it affects only a few people but does so consistently. Hope this helps.