Softwareclient Crashes KERNELBASE.dll RRS feed

  • Question

  • Hello, 

    do you know if there are Ways to "catch" more Info about this "isynet Software Client Crashes?  (it is a software client connected to a SQL Database)

    I don´t what/who "KERNELBASE.dll"   

    I know that its possible to have DEBUGVIEW of Sysinternals running, but a.m. crashes seems random at the Powerusers.

    It happens on a Win2016 Terminalserver.

    Thx, Best Regards

    Name der fehlerhaften Anwendung: MCS-ISYNET.EXE, Version:, Zeitstempel: 0x5c17ce3b
    Name des fehlerhaften Moduls: KERNELBASE.dll, Version: 6.3.9600.18938, Zeitstempel: 0x5a7dd8a7
    Ausnahmecode: 0xe0434352
    Fehleroffset: 0x00015ef8
    ID des fehlerhaften Prozesses: 0x4304
    Startzeit der fehlerhaften Anwendung: 0x01d4ccd863498ba7
    Pfad der fehlerhaften Anwendung: c:\WINACS\MCS-ISYNET.EXE
    Pfad des fehlerhaften Moduls: C:\Windows\SYSTEM32\KERNELBASE.dll
    Berichtskennung: a9d04bc6-3922-11e9-82e0-000c293ce603
    Vollständiger Name des fehlerhaften Pakets: 
    Anwendungs-ID, die relativ zum fehlerhaften Paket ist: 


    Anwendung: MCS-ISYNET.EXE
    Frameworkversion: v4.0.30319
    Beschreibung: Der Prozess wurde aufgrund einer unbehandelten Ausnahme beendet.
    Ausnahmeinformationen: System.Xml.XmlException
       bei System.Xml.XmlTextReaderImpl.Throw(System.Exception)
       bei System.Xml.XmlTextReaderImpl.Throw(System.String, System.String[])
       bei System.Xml.XmlTextReaderImpl.ThrowInvalidChar(Char[], Int32, Int32)
       bei System.Xml.XmlTextReaderImpl.ParseRootLevelWhitespace()
       bei System.Xml.XmlTextReaderImpl.ParseDocumentContent()
       bei System.Xml.XmlTextReaderImpl.Read()
       bei System.Xml.Linq.XElement.ReadElementFrom(System.Xml.XmlReader, System.Xml.Linq.LoadOptions)
       bei System.Xml.Linq.XElement.Load(System.Xml.XmlReader, System.Xml.Linq.LoadOptions)
       bei System.Xml.Linq.XElement.Parse(System.String, System.Xml.Linq.LoadOptions)
       bei ixx.Time.Controller.SamediClient.AktMessageId(System.String)
       bei ixx.Time.Controller.SamediClient.connector_OnMessageReceived(System.Object, ixx.Time.Controller.SocketClient.OnMessageReceivedArgs)
       bei ixx.Time.Controller.SocketClient.SocketConnector.ReceiveListener()
       bei ixx.Time.Controller.SocketClient.SocketConnector.<Connect>b__1()
       bei ixx.Time.Controller.SocketClient.SocketConnector.SafeExecute(System.Action, System.Action`1<System.Exception>)
       bei ixx.Time.Controller.SocketClient.SocketConnector.<Connect>b__0()
       bei System.Threading.ThreadHelper.ThreadStart_Context(System.Object)
       bei System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
       bei System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
       bei System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
       bei System.Threading.ThreadHelper.ThreadStart()

    Tuesday, February 26, 2019 12:24 PM


All replies

  • Hello,

    We can try to create a crash dump file for your app, then get more information about how it crashes. Crash dumps will be created automatically by Windows if the following registry key is present:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps

    In order to help support troubleshoot your problem please do the following:

    Create the registry key LocalDumps if it is not present already.

    Reproduce the problem (i.e. make the application crash).

    Locate the crash dump file in %LOCALAPPDATA%\CrashDumps. Note that if the crashing application runs under the System account, that resolves to C:\Windows\System32\config\systemprofile\AppData\Local\CrashDumps.




    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, February 27, 2019 2:59 AM
  • Dear Teemo,

    thx a lot.

    Do you  know a tool how to open the Files?

    Thx one seems not working.

    Thx a lot in advance!


    Wednesday, February 27, 2019 8:47 AM
  • You are welcome, I usually use WinDbg to analyze BSOD minidump or crash dump file.


    Other tool such as Debug Diagnostic Tool v2 is also widely-used.



    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    • Marked as answer by R2D2-Rev.2 Thursday, February 28, 2019 9:20 AM
    Wednesday, February 27, 2019 9:29 AM