Analyzing Crash dump - how to pinpoint

0

I have a .NET application which is crashing seemingly randomly. It crashes once every couple of days for the last 4 weeks. I created a DebugDiag Crash rule and viewed the Crash Dump file via WinDbg !analyze -v

Snippet from Dump file:

ExceptionAddress: 75a3c13b (kernel32!SortGetSortKey+0x0000001b)
   ExceptionCode: c00000fd (Stack overflow)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000001
   Parameter[1]: 12ac2e4c

DEFAULT_BUCKET_ID:  NOSOS_STACK_OVERFLOW

PROCESS_NAME:  w3wp.exe

RECURRING_STACK: From frames 0xd to 0x16

ERROR_CODE: (NTSTATUS) 0xc00000fd - A new guard page for the stack cannot be created.

EXCEPTION_CODE: (NTSTATUS) 0xc00000fd - A new guard page for the stack cannot be created.

It appears there may be a stack overflow in my code. However, I have no idea where to go from here. Any ideas?

.net
stack
asked on Stack Overflow Jan 9, 2020 by Joe Walsh • edited Jan 9, 2020 by ChrisMM

0 Answers

Nobody has answered this question yet.


User contributions licensed under CC BY-SA 3.0