Your complete approach is wrong.
Instead of disabling the exception you should find the cause and fix that. Ignoring the execption may lead to a deadlock:
Effect on the Runtime
Typically, several threads inside the process will deadlock. One of those threads is likely to be a thread responsible for performing a garbage collection, so this deadlock can have a major impact on the entire process. Furthermore, it will prevent any additional operations that require the operating system's loader lock, like loading and unloading assemblies or DLLs and starting or stopping threads.
In some unusual cases, it is also possible for access violations or similar problems to be triggered in DLLs which are called before they have been initialized.
The ability to enable/disable these execptions is a debugging aid. It is not intended for release versions.
Have you tried to execute a debug build on a client?
Don't do so.