none
The process was terminated due to an internal error in the .NET Runtime at IP 6FAE979D (6F780000) with exit code 80131506. RRS feed

  • 问题

  • Log Name:      Application
    Source:        .NET Runtime
    Date:          1/4/2018 1:26:44 PM
    Event ID:      1023
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      WIN-2ITHK1I8KO9
    Description:
    Application: Chison.UltraSound.Executable.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an internal error in the .NET Runtime at IP 6FAE979D (6F780000) with exit code 80131506.

    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name=".NET Runtime" />
        <EventID Qualifiers="0">1023</EventID>
        <Level>2</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2018-01-04T05:26:44.000000000Z" />
        <EventRecordID>5163</EventRecordID>
        <Channel>Application</Channel>
        <Computer>WIN-2ITHK1I8KO9</Computer>
        <Security />
      </System>
      <EventData>
        <Data>Application: Chison.UltraSound.Executable.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an internal error in the .NET Runtime at IP 6FAE979D (6F780000) with exit code 80131506.
    </Data>
      </EventData>
    </Event>

    WPF程序在启动的时候偶发弹出进程崩溃的系统框,然后OK后会结束进程,系统记录的日志如上。

    网上搜索过有说跟并发GC有关,也改过没用,重新安装.net Framework也没用,有人遇到这样的问题吗?

    • 已移动 Bob Ding 2018年1月11日 6:29 debugging related
    2018年1月8日 0:22

全部回复

  • 重新安装.net Framework,提示中是 Framework Version: v4.0.30319

    考虑下用Microsoft .NET Framework Repair Tool ,先完整卸载,再重新安装。

    Firstly, I suggest you use .NET Framework Setup Verification Tool to check if the .NET
    Framework is ok. 
    http://blogs.msdn.com/b/astebner/archive/2008/10/13/8999004.aspx

    If you find there is anything wrong with .NET Framework, you may use Microsoft .NET Framework Repair Tool to do a repair, This tool detects and tries to fix some frequently occurring issues with the setup of Microsoft .NET Framework or with updates to the Microsoft .NET Framework.
    https://www.microsoft.com/en-us/download/details.aspx?id=30135

    https://social.msdn.microsoft.com/Forums/vstudio/en-US/125e76cc-dc83-436c-8502-9b3e60cfb5d5/net-framework-version-v4030319-description-the-process-was-terminated-due-to-an-unhandled?forum=netfxsetup


    专注于.NET ERP/CRM开发框架,C/S架构,SQL Server + ORM(LLBL Gen Pro) + Infragistics WinForms

    2018年1月8日 1:05
  • 我有.net验证工具验证了所有.net版本,都验证成功。我机器上的.net应该没有问题,之前我也是先卸载再重新安装的,安装包是官网上下载的。

    另外一个Event ID: 1026,我的是1023,好像也不太相关

    2018年1月8日 1:35
  • Hi,

    >> WPF程序在启动的时候偶发弹出进程崩溃的系统框

    您有没有在其他机器上测试你的代码 ?

    请考虑排除程序中的异常,没有程序的崩溃信息?

    你可以考虑捕捉WPF程序的全局异常:

    1. AppDomain.CurrentDomain.UnhandledException From all threads in the AppDomain.
    2. Dispatcher.UnhandledException From a single specific UI dispatcher thread.
    3. Application.Current.DispatcherUnhandledException From the main UI dispatcher thread in your WPF application.
    4. TaskScheduler.UnobservedTaskException from within each AppDomain that uses a task scheduler for asynchronous operations.

    这种异常通常是因为非托管代码导致的托管堆损坏引起的,所以检查你的非托管代码是否有任何类型转换的错误...

    你可以根据下面的博客来debug你的程序:

    https://blogs.msdn.microsoft.com/tess/2006/02/09/net-crash-managed-heap-corruption-calling-unmanaged-code/

    Sincerely,

    Bob


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.


    • 已编辑 Bob Ding 2018年1月8日 2:01
    2018年1月8日 1:44
  • 其他机器也会偶发运行崩溃,软件没有抓到任何异常信息。上面提供的是window log中的Error信息。我的程序确实有调用很多C++ DLL,不过我对这方便调试不太擅长,我只能先试着看看

    2018年1月8日 2:38
  • 现在导出了出错的DUMP文件,大神帮忙分析下:

    0:000> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Exception Analysis                                   *
    *                                                                             *
    *******************************************************************************


    FAULTING_IP: 
    clr!WKS::gc_heap::mark_through_cards_for_segments+1ac
    702056fa f70000000080    test    dword ptr [eax],80000000h

    EXCEPTION_RECORD:  0025c9c0 -- (.exr 0x25c9c0)
    ExceptionAddress: 702056fa (clr!WKS::gc_heap::mark_through_cards_for_segments+0x000001ac)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000001
    NumberParameters: 2
       Parameter[0]: 00000000
       Parameter[1]: 0000fa00
    Attempt to read from address 0000fa00

    FAULTING_THREAD:  00000724

    PROCESS_NAME:  Chison.UltraSound.Executable.exe

    OVERLAPPED_MODULE: Address regions for 'vcomp120' and 'atigktxx.dll' overlap

    ERROR_CODE: (NTSTATUS) 0x80000003 - {

    EXCEPTION_CODE: (NTSTATUS) 0x80000003 (2147483651) - {

    MOD_LIST: <ANALYSIS/>

    NTGLOBALFLAG:  0

    APPLICATION_VERIFIER_FLAGS:  0

    MANAGED_STACK: !dumpstack -EE
    No export dumpstack found

    MANAGED_BITNESS_MISMATCH: 
    Managed code needs matching platform of sos.dll for proper analysis. Use 'x86' debugger.

    CONTEXT:  0025c9dc -- (.cxr 0x25c9dc)
    eax=0000fa00 ebx=0200efc8 ecx=00000026 edx=0200efc8 esi=0200ef00 edi=000401de
    eip=702056fa esp=0025ce28 ebp=0025ceb8 iopl=0         nv up ei pl nz na pe nc
    cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00010206
    clr!WKS::gc_heap::mark_through_cards_for_segments+0x1ac:
    702056fa f70000000080    test    dword ptr [eax],80000000h ds:0023:0000fa00=????????
    Resetting default scope

    READ_ADDRESS:  0000fa00 

    FOLLOWUP_IP: 
    clr!WKS::gc_heap::mark_through_cards_for_segments+0
    70205563 55              push    ebp

    LAST_CONTROL_TRANSFER:  from 70202396 to 702056fa

    ADDITIONAL_DEBUG_TEXT:  Followup set based on attribute [Is_ChosenCrashFollowupThread] from Frame:[0] on thread:[PSEUDO_THREAD]

    DEFAULT_BUCKET_ID:  NOSOS

    PRIMARY_PROBLEM_CLASS:  NOSOS

    BUGCHECK_STR:  APPLICATION_FAULT_NOSOS_WRONG_SYMBOLS

    STACK_TEXT:  
    0025ce28 702056fa clr!WKS::gc_heap::mark_through_cards_for_segments+0x1ac
    0025cec0 70202396 clr!WKS::gc_heap::mark_phase+0x2d3
    0025cf18 702017e4 clr!WKS::gc_heap::gc1+0xba
    0025cf48 70201b79 clr!WKS::gc_heap::garbage_collect+0x5e4
    0025cf88 70201c69 clr!WKS::GCHeap::GarbageCollectGeneration+0x1aa
    0025cfb0 70204c40 clr!WKS::gc_heap::try_allocate_more_space+0x15a
    0025cfd4 7020146f clr!WKS::gc_heap::allocate_more_space+0x18
    0025cfe8 70201357 clr!WKS::GCHeap::Alloc+0x4f
    0025d000 70062b80 clr!Alloc+0x54
    0025d020 70076758 clr!SlowAllocateString+0x3a
    0025d05c 7007679a clr!UnframedAllocateString+0x6
    0025d064 70085923 clr!StringObject::NewString+0x23
    0025d06c 700abc82 clr!COMNlsInfo::InternalChangeCaseString+0xf4
    0025d120 6f2fc852 mscorlib_ni+0x30c852
    0025d13c 6f2fc824 mscorlib_ni+0x30c824
    0025d154 6f37c5c7 mscorlib_ni+0x38c5c7
    0025d178 6f2efb4d mscorlib_ni+0x2ffb4d
    0025d184 06567a82 unknown!unknown+0x0
    0025d1d0 06567691 unknown!unknown+0x0
    0025d1f0 06567538 unknown!unknown+0x0
    0025d208 101d00b6 unknown!unknown+0x0
    0025d230 101bfeb8 unknown!unknown+0x0
    0025d240 101bd340 unknown!unknown+0x0
    0025d280 101bfa80 unknown!unknown+0x0
    0025d380 70062a0c clr!ThePreStub+0x16


    SYMBOL_NAME:  clr!WKS::gc_heap::mark_through_cards_for_segments+0

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: clr

    IMAGE_NAME:  clr.dll

    DEBUG_FLR_IMAGE_TIMESTAMP:  5348961e

    STACK_COMMAND:  .cxr 000000000025C9DC ; kb ; dds 25ce28 ; kb

    FAILURE_BUCKET_ID:  NOSOS_80000003_clr.dll!WKS::gc_heap::mark_through_cards_for_segments

    BUCKET_ID:  APPLICATION_FAULT_NOSOS_WRONG_SYMBOLS_clr!WKS::gc_heap::mark_through_cards_for_segments+0

    Followup: MachineOwner
    ---------

    是不是GC的问题?
    2018年1月10日 3:07
  • 你好,

    对于你的问题更和Debug的问题相关,建议你使用windbg工具来调试分析你的dump文件。

    建议你到微软的Debug论坛询问:Windows Desktop Debugging

    在这个论坛你可以询问关于windbg工具的使用的问题,也可以使用OneDrive上传你的Dump文件,请community member帮助

    你调试Dump文件。

    因为这个论坛是解决方案论坛而不是Debugging论坛,你的帖子将被移入一般讨论区。

    感谢你的合作和理解。

    Sincerely,

    Bob


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    2018年1月10日 9:15