I have an application which crashed abruptly, i do have the .dmp file and i was able to get some some info from that. The stack trace is below which does not look that helpful.
0:173> k
*** Stack trace for last set context - .thread/.cxr resets it
# Child-SP RetAddr Call Site
00 000000ca`7fffee10 00000000`00000001 0x000000ca`7fffef08
01 000000ca`7fffee18 000000ca`7ffff048 0x1
02 000000ca`7fffee20 00000000`00000004 0x000000ca`7ffff048
03 000000ca`7fffee28 00007ff9`d34c2493 0x4
04 000000ca`7fffee30 00007ff9`d34c2314 mscorlib_ni+0x542493
05 000000ca`7fffee90 00007ff9`d6016bb3 mscorlib_ni+0x542314
06 000000ca`7fffef30 00007ff9`d6016a70 clr!CallDescrWorkerInternal+0x83
07 000000ca`7fffef70 00007ff9`d601735d clr!CallDescrWorkerWithHandler+0x4e
08 000000ca`7fffefb0 00007ff9`d601b149 clr!MethodDescCallSite::CallTargetWorker+0xf8
09 000000ca`7ffff0b0 00007ff9`d6017b21 clr!QueueUserWorkItemManagedCallback+0x2a
0a 000000ca`7ffff1a0 00007ff9`d6017a90 clr!ManagedThreadBase_DispatchInner+0x39
0b 000000ca`7ffff1e0 00007ff9`d60179cd clr!ManagedThreadBase_DispatchMiddle+0x6c
0c 000000ca`7ffff2e0 00007ff9`d6017b5f clr!ManagedThreadBase_DispatchOuter+0x75
0d 000000ca`7ffff370 00007ff9`d601b0b0 clr!ManagedThreadBase_FullTransitionWithAD+0x2f
0e 000000ca`7ffff3d0 00007ff9`d601819c clr!ManagedPerAppDomainTPCount::DispatchWorkItem+0xa0
0f 000000ca`7ffff550 00007ff9`d6017f45 clr!ThreadpoolMgr::ExecuteWorkRequest+0x64
10 000000ca`7ffff580 00007ff9`d60c2e8f clr!ThreadpoolMgr::WorkerThreadStart+0xf5
11 000000ca`7ffff620 00007ff9`e3848364 clr!Thread::intermediateThreadProc+0x86
12 000000ca`7ffff960 00007ff9`e5ba7091 kernel32!BaseThreadInitThunk+0x14
13 000000ca`7ffff990 00000000`00000000 ntdll!RtlUserThreadStart+0x21
Does any one know what I could do to better analize using windbg, or have you seen this error before?