Can DebugDiag cause exceptions to stop being thrown or prevent general .net exceptions?

I know this question sounds nuts but here is my scenario. I have three Windows Server 2012 R2 web servers behind a load balancer and all three are weighted the same (33%). All three servers are running our ASP.NET site on IIS. These servers are identical in every way. Every 2-3 days each server has been throwing an unhandled exception which kills the worker process. Over a week ago I created a crash rule in DebugDiag for our application on "Server A". Servers B & C continue to throw the exception but server A has not thrown the exception since we created the DebugDiag rule. I have verified that all three servers are getting the same amount of requests from our load balancer. Here is the exception we are getting:

Faulting application name: w3wp.exe, version: 8.5.9600.16384, time stamp: 0x5215df96
Faulting module name: KERNELBASE.dll, version: 6.3.9600.18202, time stamp: 0x569e7eb1
Exception code: 0xe0434352

Does anyone have any insight as to why DebugDiag seems to 'solve' the problem for us or how we can debug this?