> Renamed that DLL -- same behavior, and same access violation in WinDbg. > Killed all Beyond Trust Services/Tasks -- same behavior. Does WinDBG still show the DLL loaded? Anton Lavrentiev Contractor NIH/NLM/NCBI