none
Access violation at gc_heap::mark_object_simple RRS feed

  • Question

  • I am having access violation exception in our Windows Service

    In WER416F.tmp.hdmp the assembly instruction at clr!WKS::gc_heap::mark_object_simple+6d in C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll from Microsoft Corporation has caused an access violation exception (0xC0000005) when trying to read from memory location 0x00000000 on thread 42

    Here is call stack:

    Function
    clr!WKS::gc_heap::mark_object_simple+6d
    clr!WKS::GCHeap::Promote+62
    clr!GcStackCrawlCallBack+b9
    clr!Thread::StackWalkFramesEx+fd
    clr!Thread::StackWalkFrames+be
    clr!CNameSpace::GcScanRoots+148
    clr!WKS::gc_heap::mark_phase+177
    clr!WKS::gc_heap::gc1+96
    clr!WKS::gc_heap::garbage_collect+222
    clr!WKS::GCHeap::GarbageCollectGeneration+dd
    clr!WKS::GCHeap::Alloc+31b
    clr!AllocateArrayEx+3ef
    clr!JIT_NewArr1+241
    mscorlib_ni+4fd20d
    mscorlib_ni+4e84ce
    SMDiagnostics_ni+1c0b9
    System_Xml_ni+155312
    System_ServiceModel_ni+e889d5
    System_ServiceModel_ni+10ea678
    SMDiagnostics_ni+1b095
    SMDiagnostics_ni+1b22d
    System_ServiceModel_ni+e07138
    System_ServiceModel_ni+635444
    System_ServiceModel_ni+f5ee13
    System_ServiceModel_ni+f5c689
    System_ServiceModel_ni+12a239f
    System_ServiceModel_ni+123598a
    System_ServiceModel_ni+618d4b
    System_ServiceModel_ni+618bf3
    System_ServiceModel_ni+6189ad
    System_ServiceModel_ni+617a2a
    System_ServiceModel_ni+6124c6
    System_ServiceModel_ni+611b2b
    System_ServiceModel_ni+61053e
    System_ServiceModel_ni+60fa57
    System_ServiceModel_ni+60de03
    System_ServiceModel_ni+60d92b
    System_ServiceModel_Internals_ni+be465
    System_ServiceModel_Internals_ni+be0a4
    System_ServiceModel_Internals_ni+4e651
    System_ServiceModel_Internals_ni+4e5d0
    mscorlib_ni+535c26
    clr!CallDescrWorkerInternal+83
    clr!CallDescrWorkerWithHandler+4a
    clr!DispatchCallSimple+85
    clr!BindIoCompletionCallBack_Worker+b8
    clr!Frame::Push+a0
    clr!Frame::Pop+86
    clr!ManagedPerAppDomainTPCount::DispatchWorkItem+2bd
    clr!ManagedPerAppDomainTPCount::DispatchWorkItem+23b
    clr!BindIoCompletionCallbackStubEx+cd
    clr!BindIoCompletionCallbackStub+9
    clr!ThreadpoolMgr::CompletionPortThreadStart+361
    clr!Thread::intermediateThreadProc+7d
    kernel32!BaseThreadInitThunk+d
    ntdll!RtlUserThreadStart+1d

    Any idea what's wrong or where to start investigating it?


    Thursday, December 26, 2013 9:48 AM

Answers