@DeathOverload
Yeah, the exceptions are thrown by Windows (SEH?) in this case which has enough info to do a stack trace that you see there. That's not the problem.
Luckily the other exception wasn't a C++ exception either, but I don't know what is precisely is as the stack dump just don't be.
A bunch of prints did show it was caused by a second call to GetCapabilities (only when on a G920 and ScriptHookVDotNet is active though...) and CreateEffect (Any call, also G920 + SHVDN). Still don't know how to fix it as these get valid pointers and data, and should give return values instead of crash and burn. Other devs seem to have worked out that this is caused by crappy Logitech drivers though, so there's not much I can do. Don't have a G920 so I can't validate the "fix" though.
I guess the original question doesn't really apply for the problem itself anymore, and from whatever straight answers I could get from StackOverflow, this is simply impossible. Back to spamming the log it is, then.