Troubleshooting memory access violation in AcroPDF.dll?

[jarle_0097]

Hello. I am experiencing apparently "random" crashes in a program, where the crash dump logs (analyed with WindDbg) indicate an memory access violation occuring in AcroPDF.dll. The last four function calls in the call stack are always identical:

WARNING: Stack unwind information not available. Following frames may be wrong.

0019ec4c 760cd2d3     003604ec 0000001a 00000014 AcroPDF+0x11c90

0019ec4c 760ad30a     66211c90 003604ec 0000001a user32!_InternalCallWinProc+0x2b

0019ed34 760acf30     66211c90 00000000 0000001a user32!UserCallWinProcCheckWow+0x30a

0019ed94 760b9f1a     01798190 00000000 0000001a user32!DispatchClientMessage+0xf0

Exception code is: c0000005 (Access violation)

Typical values for ExceptionAddress and Failure Bucket are:

Exception address: 66211c90 (AcroPDF+0x00011c90)

Failure bucket: BAD_INSTRUCTION_PTR_c0000005_AcroPDF.dll!Unloaded

What can I do to find the cause of this problem? As a first step for example, I would like to use the offset information to identify exactly which function is being called - is there a way to do that using official documentation or other means?

[gregory_0679]

Hello, 

A little late I know, but I was looking up the same exception code. It seems like this is a known bug that was ackowledged just today, 05/20/2025. 

https://community.adobe.com/t5/acrobat-discussions/windows-application-error-referenced-memory-could...

[jarle_0097]

I'm not sure if it's the same bug, but thanks for the tip and for replying!