Hmm, I can't think of any circumstance that would happen in practice, unless it's e.g. a butchered Wine setup. The DLLs will already be loaded in other (system) processes, so they'd only have to get mapped (or have their refcount incremented). I guess it could be caused by very specific memory corruption. What would involve graceful handling here - swallowing the error, or printing to an invisible stderr as before?