Skip navigation

Tag Archives: crash

Adobe InDesign CS6 on my Windows 7 64-bit laptop with a generally very error-free installation (I own a computer shop, so why wouldn’t it be ultra clean?) insisted on crashing literally every single time I tried to start it recently. I did some tracing of what the program did right before it crashed out and found the problem.

Adobe InDesign CS6, upon “Starting Service Registry,” is probing the default printer, crashing out if the default printer is a network printer that can’t be reached (and thus queried for capabilities or settings or whatever else.)

I use PuTTY with SSH port forwarding for port 631 enabled to be able to print to the office printer from my house while I’m in a SSH session (via the Common UNIX Printing System, CUPS). There is no printer at my house at all, as I have no need for one, so my default printer is a network printer on “localhost:631” using Internet Printing Protocol (IPP), which is “disconnected” if I don’t happen to have PuTTY connected to the office workstation at the time. The problem is that InDesign dies horribly when it queries this default printer at startup and the printer is “missing.” I verified this by connecting with PuTTY to the office, thus making the default printer available again, and the error went away.

SOLUTION: If you are having this problem, see if your default printer is off, disconnected, or a network printer that can’t be reached. In the worst case, try changing the default printer to a virtual printer such as the XPS document writer or Adobe PDF printer, so that the default printer is always available when InDesign starts.

I’d also like to note that Adobe is far from unique in the “default printer problems equals program startup weirdness” category; I’ve seen Microsoft Office applications start extremely slowly, as well as other programs throw errors or crash at startup, all because they’re querying printers at startup and developers clearly never test for “what if the default printer is off or unreachable?” contingencies. I would love to see developers take such things into account more often, because this class of bugs affects more people than one might realize, particularly in corporate environments where “the network printer” might have been turned off for some reason, or on laptops where the office network is not connected.

For reference, my Windows Error Reporting log in the Event Viewer shows the following information for this error:

Faulting application name: InDesign.exe, version:, time stamp: 0x4f72c3ee
Faulting module name: AGM.dll, version:, time stamp: 0x4f3a0265
Exception code: 0xc0000005
Fault offset: 0x0024d0cd
Faulting process id: 0xe2c
Faulting application start time: 0x01ce07030b2c00c8
Faulting application path: C:\Program Files (x86)\Adobe\Adobe InDesign CS6\InDesign.exe
Faulting module path: C:\Program Files (x86)\Adobe\Adobe InDesign CS6\AGM.dll


I ran into a persistent STOP error message that would always be in RTL8185.SYS on a client’s computer today.  He had a TrendNet TEW-421PC (the PCMCIA variant of the TEW-423PI PCI card) based on a Realtek RTL8185 chip.  He uses an older Dell Inspiron 2600 laptop, and you couldn’t remove the card or browse for too long without a crash.  Even updating the drivers with the card inserted would crash the system.

TrendNet’s “latest drivers” are old as dirt for this chip, and it turned out the solution was only a little bit further away: hit up and search for RTL8185!  Downloading the latest drivers straight from Realtek and installing them solves the problem quite nicely.

But how do we update drivers when the card isn’t inserted to avoid the imminent crash?  There are a few ways to do it.  The least complicated way is to delete the file RTL8185.SYS from the “drivers” folder under the “system32” folder (the majority of systems store this at “C:\WINDOWS\System32\drivers” and insert the card.  The driver doesn’t load until the card is inserted, so deleting it before inserting the card will allow you to change out the driver without the crash.

For more advanced users, adding DEVMGR_SHOW_NONPRESENT_DEVICES = 1 to the system-wide environment variables under the System control panel, then starting Device Manager and going to View -> Show Hidden Devices will let you manipulate hardware that’s not plugged in, but the deletion is easier for most people.

If you need help with this process, leave a comment and I’ll get back to you.

Greetings! This article has been moved to the Tritech Computer Solutions page called Fix for STOP 0x0000007E Blue Screen on AMD Platforms. Please update your links and bookmarks to reflect this change.

%d bloggers like this: