it was actually in a .NET assembly being called via COM from something else, and was happening because I had a wrong Assembly value in the registry under InprocServer32, which apparently put the error in some limbo where the COM class loading problem doesn't show up in Process Monitor, but the .NET assembly binding problem doesn't show up in the fusion logs either. very devious, curse you!
