KERNELBASE.dll Exception 0xe0434352 offset 0x000000000000a49d

I recently received some system event logs from one of our clients running our application on a virtual machine.

I noticed these entries in the log:

Description: The process was terminated due to an unhandled exception.
Framework Version: v4.0.30319
4/22/2014 5:05:28 PM;"Error";".NET Runtime";"1026";"Application: MyApp.exe
Report Id: d50fe7ab-ca61-11e3-9e10-6805ca17040a"
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Faulting application path: C:\Program Files\MyApp\bin\MyApp.exe
Faulting application start time: 0x01cf5e44d3e971c2
Faulting process id: 0x13fc
Fault offset: 0x000000000000a49d
Exception code: 0xe0434352
Faulting module name: KERNELBASE.dll  version: 6.1.7601.17514  time stamp: 0x4ce7c78c
4/22/2014 5:05:29 PM;"Error";"Application Error";"1000";"Faulting application name: MyApp.exe  version: 1.2.1403.7002  time stamp: 0x5319d243

Followed by a huge rdlc stacktrace ending in "The directory name is invalid"

I've been trying to determine what Fault offset: 0x000000000000a49d Exception code: 0xe0434352 really means. So far I can only tell that I may be something related to user access rights, KERNELBASE.dll could be corrupted or it may be some mystic Microsoft voodoo.

Does anyone have a definitive answer to what this means? Or a msdn lync explaining this in detail? I'd really like to understand the full details behind this issue.

0xe0434352 is the SEH code for a CLR exception. If you don't understand what that means, stop and read A Crash Course on the Depths of Win32™ Structured Exception Handling. So your process is not handling a CLR exception. Don't shoot the messenger, KERNELBASE.DLL is just the unfortunate victim. The perpetrator is MyApp.exe.

There should be a minidump of the crash in DrWatson folders with a full stack, it will contain everything you need to root cause the issue.

I suggest you wire up, in your myapp.exe code, AppDomain.UnhandledException and Application.ThreadException, as appropriate.