none
clr exception 0xc0000409 RRS feed

  • Question

  • My app crashed with an exception 0xc0000409. I use procdump.exe to generate a crash dump file. and found the faulting thread has the following stack trace:

    ChildEBP RetAddr  
    072cf04c 71d1df7c clr!__report_gsfailure+0x17
    072cf054 71d1db94 clr!CrawlFrame::SetCurGSCookie+0x2d
    072cf070 71d1d898 clr!StackFrameIterator::Init+0x60
    072cf344 71d1d9cc clr!Thread::StackWalkFramesEx+0x62
    072cf678 71db1946 clr!Thread::StackWalkFrames+0x9d
    072cf6ac 71eaf56e clr!CNameSpace::GcScanRoots+0x101
    072cf6f0 71eaf6db clr!WKS::gc_heap::background_mark_phase+0x3fc
    072cf720 71eaf0e2 clr!WKS::gc_heap::gc1+0xac
    072cf740 71eaf010 clr!WKS::gc_heap::bgc_thread_function+0x128
    072cf744 71ea36f8 clr!WKS::gc_heap::bgc_thread_stub+0x3c
    072cfe60 770e86e3 clr!Thread::intermediateThreadProc+0x4d
    072cfe6c 77d8bf39 kernel32!BaseThreadInitThunk+0xe
    072cfeb0 77d8bf0c ntdll!__RtlUserThreadStart+0x72
    072cfec8 00000000 ntdll!_RtlUserThreadStart+0x1b

    My app is targeting .net 4.0 client profile. the clr.dll version is 4.0.30319.18449. The system is Windows 8 Pro. I have been able to duplicate this issue on Windows 7 as well.


    Wednesday, June 4, 2014 11:14 PM

Answers

All replies