How to Fix a .Net Windows Application Crashing at Startup with Exception Code: 0Xe0434352

How do I fix a .NET windows application crashing at startup with Exception code: 0xE0434352?

0xE0434352 is the exception code for all .NET exceptions so that won't tell you much. How did you got this exception code? The event log?

Your best bet is to use a debugger to get more information. If the Visual Studio debugger won't help you, then you might need to check out WinDbg with SOS. See here and here for an introduction. Let it break on the exception, and see if you can get more information on the why.

If you suspect it is an issue when loading assemblies you might want to check out the Fusion Log.

KERNELBASE.dll Exception 0xe0434352 offset 0x000000000000a49d

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.

WinForms application crashes on startup

Have a look at the Fuslog Assembly Binding Log Viewer.

You can set it up to log attempted assembly bindings so that you can see where your application is trying to read which assemblies from .

This should hopefully help you identify what is missing.

NB: To start the Fuslog viewer, you'll need to call fuslogvw from an administrator developer command prompt. If you don't start it as an administrator, the settings (shown below) will not be editable, and you won't be able to provide your own custom log path.

Sample Image



Related Topics



Leave a reply



Submit