Anyone having problems with the Acrobat Reader 11.0.9 update on Win7 X64?

Question

I don't know about anyone else, but I sure am.  The symptom I'm getting is that the Acrobat Reader window will sporadically fail to open.  Looking at the process list with Sysinternals Process Explorer, I see that an Acrobat Reader task has been launched for every attempted open, but no windows show.  After clearing out all of the hung tasks, shutting down and re-launching the program trying to launch Acrobat Reader gives some relief for a while.  I have never seen Acrobat Reader display these symptoms before.  As a test, I de-installed Acrobat Reader 11.0.9 completely, and performed a complete fresh install of 11.0.8, which works flawlessly (and had been since it was installed).  I don't want to go back to 11.0.8 because of the security exposures, but I can't get any useful work done in 11.0.9 because I can't reliably open documents!!!  If anyone else knows of an official problem record for this, or is experiencing the same symptoms, or knows of any workarounds, I love to hear about it.
Thanks.
-Mike

Answer 1

It looks like is a memory corruption
APP:  acrobat.exe
BUGCHECK_STR:  APPLICATION_FAULT_MEMORY_CORRUPTION_LARGE
PRIMARY_PROBLEM_CLASS:  MEMORY_CORRUPTION_LARGE
DEFAULT_BUCKET_ID:  MEMORY_CORRUPTION_LARGE
IP_ON_HEAP:  62896df0
The fault address in not in any loaded module, please check your build's rebase log at <releasedir>\bin\build_logs\timebuild\ntrebase.log for module which may contain the address if it were loaded.
IP_IN_FREE_BLOCK: 62896df0
FRAME_ONE_INVALID: 1
STACK_TEXT: 
00000000 00000000 memory_corruption!kernel32+0x0
SYMBOL_STACK_INDEX:  0
SYMBOL_NAME:  memory_corruption!kernel32
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP:  0
STACK_COMMAND:  ** Pseudo Context ** ; kb
FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE_c0000090_memory_corruption!kernel32
BUCKET_ID:  APPLICATION_FAULT_MEMORY_CORRUPTION_LARGE_memory_corruption!kernel32
IMAGE_NAME:  memory_corruption
ANALYSIS_SOURCE:  UM
FAILURE_ID_HASH_STRING:  um:memory_corruption_large_c0000090_memory_corruption!kernel32
FAILURE_ID_HASH:  {50fe489a-6240-e9af-6cec-7a87f3683661}