How do I catch a Faulting module name: KERNELBASE.dll RRS feed

  • Question

  • Hi

    I have a C#/WPF program that causes a "Faulting module name: KERNELBASE.dll" and the program stops working.

    I am trying to catch this with an eventhandler - but program terminates with out any of my handlers is called.

    I have setup below handlers - not even FirstChanceException is called. 

    Question 1) That handler am i missing to catch this error ?

        public partial class App : Application
            public App()
                AppDomain.CurrentDomain.FirstChanceException += new EventHandler<FirstChanceExceptionEventArgs>(OnFirstChanceException);
                AppDomain.CurrentDomain.UnhandledException += new UnhandledExceptionEventHandler(OnUnhandledException);
                TaskScheduler.UnobservedTaskException += new EventHandler<UnobservedTaskExceptionEventArgs>(OnTaskSchedulerUnobservedTaskException); 
                System.Windows.Forms.Application.ThreadException += new ThreadExceptionEventHandler(OnWinFormApplicationThreadException);
                DispatcherUnhandledException += new DispatcherUnhandledExceptionEventHandler(OnDispatcherUnhandledException); //Example 2

    Details from event log:

    Faulting application name: XXXXX.exe, version:, time stamp: 0x5b9b5274

    Faulting module name: KERNELBASE.dll, version: 10.0.14393.2189, time stamp: 0x5abdad60

    Exception code: 0xe06d7363

    Fault offset: 0x0000000000033c58

    Faulting process id: 0x36e0

    Faulting application start time: 0x01d44bf3af3fba6e

    Faulting application path: ....\xxxxx.exe

    Faulting module path: C:\Windows\System32\KERNELBASE.dll

    Report Id: 6d40b4bb-38fc-432f-b562-d05de642fc54

    Faulting package full name:

    Faulting package-relative application ID:

    • Edited by K Rasmussen Friday, September 14, 2018 7:23 AM Hide local path
    Friday, September 14, 2018 6:44 AM


  • When your C# application throws KERNELBASE.dll related error, usually there is no way to catch with C# exception handling.

    0xe06d7363 mean it's error thrown by C++ SEH. It can be anything, and you can't know what it is without having source code and use debugger to watch.

    • Marked as answer by K Rasmussen Friday, September 14, 2018 10:44 AM
    Friday, September 14, 2018 7:32 AM