Hello again, This will be my last post on this topic as the more I research the more my brain seems to run low on "memory space". After I examined the crash log that you provided I felt like reading about memory addressing tables and memory paging. With just the crash log on hand it is very hard to tell if the segmented fault and its offset is exclusively related to Adobe. The Adobe internet plugin module IA32.api was detected as the faulting module, but so was the pp.exe as the faulting application. If this would've happened over 15 years ago in older computers it would've been easier to trace the exception code 0×c0000005 by referencing to a memory address table. I remeber the days that Dr. Watson (every version of windows used to have it... not sure if still exists in windows 10 as we move to learning power shell skills); it used to save my life many times when performing computer repairs. That little program when it was combined with a good memory adress table as a reference would never fail to get to the root of these hexadecimal and binary "machine word" mysteries. Hypothetically speaking, nowadays people prefer to pay $500 to have a person to erase and reinstall the operating system in their computer as a solution... hold on, wait $500 is just the assessment. Regular computer users get afraid when a real tech guy asks very humbly for $75.00 an hour to get to the root of a problem... but that is beyond the point and far from this topic. Anyway, I think you will see what I meant if you have the time and patience to continue reading beyond this point. Not only that exception code is part of an instruction set that attempted to write itself in an virtual memory area, by which the memory segmentation and the memory paging was handled entirely by the operating system. Furthermore, when you also research about the exception code 0xc0000005 it also manifests when there are viruses in a computer, incorrect browser configurations, plugin issues, hard disk failures, bad memory chips, and anything from incorect upgrades, or lack of applying patches and updates, to corrupted drivers, system files and file servers. In which case there is no physycal trace to reference to as if, for example, a defective memory chip in the physical RAM / CMOS chips was the cause, outdated cpu / chipset drivers, or even in a hard drive where an area was reserved as temporary folder (in windows) or a swap file ( in unix like systems). In today's 64 bit computers with most current operating systems all that memory paging is handled in a virtual memory space; there is no easy way to trace where exactly did the OS assigned available addresses for those two programs that you are using. From further reading I learned that the best way to get a hint of what is the real cause is to examine Windows mini dump file with a debugger program, such as WinDbg. The real key to the problem is in learning to identify and interpret through the debugger the "fault process ID 0x2f90" with the debugging software and which identify which memory page was assigned for pp.exe and IA32.api respectively when they were trying to execute and somehow accessed a forbidden addressing space as indicated in the fault offset 0000573b. In theory, this may lead us to find out that the OS had that space reserved for another program (and maybe uninstalling that program, unknown to us yet, will free up the memory area(s) that the IA32.api and pp.exe need for themselves to coexist). Without a debugger that could help us interpret this information we cannot really tell who is guilty yet; the Adobe product ? or the Printer's Plan software ? (or both ???).
... View more