.NET application/service crash RRS feed

  • Question

  • Hi,
      I have a .NET application(service actually) that runs for few days and then all of a sudden, it crashes.  Initially there was no dump file created, but after I attached ADPlus, it created a dump file.  The memory consumption was normal (<200mb) and resource like threads/handles are also ok.  When I got the stack trace from the dump file:

    ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION}  Breakpoint  A breakpoint has been reached.


    EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid






    MANAGED_STACK: !dumpstack -EE

    OS Thread Id: 0x1618 (0)

    Current frame:

    ChildEBP RetAddr  Caller,Callee






    LAST_CONTROL_TRANSFER:  from 7c827d0b to 7c8285ec



    0c64fe7c 7c827d0b 77e61d1e 000008a0 00000000 ntdll!KiFastSystemCallRet

    0c64fe80 77e61d1e 000008a0 00000000 0c64fec4 ntdll!NtWaitForSingleObject+0xc

    0c64fef0 79e77fd1 000008a0 00004e20 00000000 kernel32!WaitForSingleObjectEx+0xac

    0c64ff34 79e77f9a 000008a0 00004e20 00000000 mscorwks!PEImage::LoadImage+0x199

    0c64ff84 79e77f50 00004e20 00000000 00000000 mscorwks!CLREvent::WaitEx+0x117

    0c64ff94 7a0c61ed 00004e20 00000000 00000000 mscorwks!CLREvent::Wait+0x17

    0c64ffb4 7a0c635b 77e64829 00000000 00000000 mscorwks!WKS::gc_heap::gc_thread_function+0x39

    0c64ffb8 77e64829 00000000 00000000 00000000 mscorwks!WKS::gc_heap::gc_thread_stub+0x7c

    0c64ffec 00000000 7a0c62df 00000000 00000000 kernel32!BaseThreadStart+0x34

    Looks like this is not my application stack, but the .NET GC trying to do something and crashed.  Any idea on why this is happening and any solution to this?

    The machine environment is:

    OS Version: 5.2

    OS Build: 3790


    • Changed type Sean Zhu - Monday, August 31, 2009 3:55 AM
    Friday, August 28, 2009 6:40 AM


  • After checking the issue, it seems this is a general .NET related issue. As this forum focuses on Windows SteadyState specific issues, this inquiry would best be posted to MSDN forum:


    The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us.  Thank you for your understanding.

    Sean Zhu - MSFT
    • Marked as answer by Sean Zhu - Friday, September 4, 2009 1:58 AM
    Monday, August 31, 2009 3:54 AM