>>This is a long shot, but if you have access to Visual Studio you can
>>attach the debugger to each process one by one and it will show
>>you which DLLs are open on that process. You could compare the
>>safe-mode list to the non-safe-mode list.
>Perhaps something like ProcessExplorer might come in handy for this?
>http://technet.microsoft.com/en-us/sysinternals/bb842062.aspx


Possibly. Does it let you copy-and-paste, or save the loaded DLLs listing to a disk file?