Here is the actual dump file: https://www.dropbox.com/s/c638wvxnv59odbr/DisplayFusion.exe.4236.dmp?dl=0
Is the output from a crash dump using !analyze -v in WinDbg enough?
Or do you guys automatically receive these crash dumps?
Microsoft (R) Windows Debugger Version 6.3.9600.17298 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\swkim\AppData\Local\Binary Fortress Software\DisplayFusion\CrashDumps\DisplayFusion.exe.4236.dmp]
User Mini Dump File with Full Memory: Only application data is available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*DownstreamStore*http://msdl.microsoft.com/download/symbols
Symbol search path is: srv*DownstreamStore*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: SingleUserTS
Machine Name:
Debug session time: Wed Jul 29 08:51:55.000 2015 (UTC - 7:00)
System Uptime: 0 days 17:05:09.789
Process Uptime: 0 days 17:04:08.000
................................................................
....................................................
Loading unloaded module list
.
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(108c.2640): Access violation - code c0000005 (first/second chance not available)
eax=0000006c ebx=051b9e48 ecx=051b9e48 edx=02510000 esi=00000000 edi=0530a1f4
eip=6fcf38a9 esp=0a90e438 ebp=0a90e570 iopl=0 nv up ei pl nz na pe nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010206
clr!WKS::gc_heap:
lan_phase+0x9f2:
6fcf38a9 f70000000080 test dword ptr [eax],80000000h ds:0023:0000006c=
??
0:030> !analyze -v
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************
*** WARNING: Unable to verify checksum for mscorlib.ni.dll
*** WARNING: Unable to verify checksum for System.Windows.Forms.ni.dll
*** ERROR: Module load completed but symbols could not be loaded for DisplayFusion.exe
*** WARNING: Unable to verify checksum for System.Runtime.Remoting.ni.dll
*** WARNING: Unable to verify checksum for System.Management.ni.dll
FAULTING_IP:
clr!WKS::gc_heap:
lan_phase+9f2
6fcf38a9 f70000000080 test dword ptr [eax],80000000h
EXCEPTION_RECORD: ffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 6fcf38a9 (clr!WKS::gc_heap:
lan_phase+0x000009f2)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000001
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 0000006c
Attempt to read from address 0000006c
CONTEXT: 00000000 -- (.cxr 0x0;r)
eax=0000006c ebx=051b9e48 ecx=051b9e48 edx=02510000 esi=00000000 edi=0530a1f4
eip=6fcf38a9 esp=0a90e438 ebp=0a90e570 iopl=0 nv up ei pl nz na pe nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010206
clr!WKS::gc_heap:
lan_phase+0x9f2:
6fcf38a9 f70000000080 test dword ptr [eax],80000000h ds:0023:0000006c=
??
DEFAULT_BUCKET_ID: WRONG_SYMBOLS
PROCESS_NAME: DisplayFusion.exe
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: 00000000
EXCEPTION_PARAMETER2: 0000006c
READ_ADDRESS: 0000006c
FOLLOWUP_IP:
clr!WKS::gc_heap:
lan_phase+9f2
6fcf38a9 f70000000080 test dword ptr [eax],80000000h
NTGLOBALFLAG: 0
APPLICATION_VERIFIER_FLAGS: 0
APP: displayfusion.exe
ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) x86fre
MANAGED_STACK:
(TransitionMU)
0A90E748 04B39AC0 DisplayFusion!..(System.Drawing.Bitmap, Boolean, System.Decimal, System.Drawing.Color, System.Drawing.Color ByRef)+0x70
0A90E8EC 04B39195 DisplayFusion!..(, System.String, System.Drawing.Bitmap)+0xcd
0A90E958 04B32BFE DisplayFusion!..()+0x7f6
0A90EA34 0509BFD5 DisplayFusion!..(IntPtr, System.String, System.String, System.Collections.Generic.List`1<IntPtr>)+0x62d
0A90EAE8 045981F4 DisplayFusion!..()+0x24c
(TransitionUM)
(TransitionMU)
0A90EC28 04B0E81E DisplayFusion!„.+.()+0x1e
0A90EC38 6EABAB43 mscorlib_ni!System.Threading.ThreadHelper.ThreadStart_Context(System.Object)+0x6f
0A90EC44 6EACDA07 mscorlib_ni!System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)+0xa7
0A90ECB0 6EACD956 mscorlib_ni!System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)+0x16
0A90ECC4 6EACD921 mscorlib_ni!System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)+0x41
0A90ECDC 6EABAACC mscorlib_ni!System.Threading.ThreadHelper.ThreadStart()+0x44
(TransitionUM)
EXCEPTION_OBJECT: !pe 2511120
Exception object: 02511120
Exception type: System.ExecutionEngineException
Message: <none>
InnerException: <none>
StackTrace (generated):
<none>
StackTraceString: <none>
HResult: 80131506
MANAGED_OBJECT_NAME: SYSTEM.EXECUTIONENGINEEXCEPTION
MANAGED_STACK_COMMAND: _EFN_StackTrace
PRIMARY_PROBLEM_CLASS: WRONG_SYMBOLS
BUGCHECK_STR: APPLICATION_FAULT_WRONG_SYMBOLS
LAST_CONTROL_TRANSFER: from 6fcf17f7 to 6fcf38a9
STACK_TEXT:
0a90e570 6fcf17f7 70192248 70192614 00000004 clr!WKS::gc_heap:
lan_phase+0x9f2
0a90e5a0 6fcf1b79 6e77b35f 00000000 00000001 clr!WKS::gc_heap::gc1+0xcd
0a90e5e0 6fcf1c69 00000030 00000000 00000003 clr!WKS::gc_heap::garbage_collect+0x5e4
0a90e608 6fcf4c40 00000000 00000000 0056ca18 clr!WKS::GCHeap::GarbageCollectGeneration+0x1aa
0a90e62c 6fcf146f 00000000 0530a1f4 0056ca18 clr!WKS::gc_heap::try_allocate_more_space+0x15a
0a90e644 6fcf1357 00000000 00000030 004b1098 clr!WKS::gc_heap::allocate_more_space+0x18
0a90e65c 6fb52b80 00000030 00000030 00000002 clr!WKS::GCHeap::Alloc+0x4f
0a90e67c 6fb52bf7 01000000 050f0164 0530a194 clr!Alloc+0x54
0a90e6b8 6fb52cd7 6e77b1ff 0000000f 0530a194 clr!AllocateObject+0x94
0a90e740 04b39ac0 0048da50 0520a70c 00000000 clr!JIT_New+0x6b
WARNING: Frame IP not in any known module. Following frames may be wrong.
0a90e8ec 6fb9bd35 6eacc852 00000000 0000005f 0x4b39ac0
0a90e948 04b32bfe 051d1efc 0520a6b0 05186b54 clr!COMNlsInfo::InternalChangeCaseString+0x61
0a90ea2c 0509bfd5 05185868 0526e1bc 051b8d18 0x4b32bfe
0a90ead4 045981f4 05185824 05189ba4 05189bf0 0x509bfd5
0a90ec30 6eabab43 051da1c8 0a90eca0 6eacda07 0x45981f4
0a90ec3c 6eacda07 051897c4 00000000 00000000 mscorlib_ni+0x2fab43
0a90eca0 6eacd956 00000000 051897f8 00000000 mscorlib_ni+0x30da07
0a90ecb4 6eacd921 00000000 051897f8 00000000 mscorlib_ni+0x30d956
0a90ecd0 6eabaacc 051897f8 00000000 00000000 mscorlib_ni+0x30d921
0a90ece8 6fb52552 0056c9d8 0a90ed48 6fb5f237 mscorlib_ni+0x2faacc
0a90ecf4 6fb5f237 0a90ed94 0a90ed38 6fca8ad2 clr!CallDescrWorkerInternal+0x34
0a90ed48 6fb5ff60 6ebc8280 0a90ed6c 6fb5bdc7 clr!CallDescrWorkerWithHandler+0x6b
0a90edc8 6fc1b7ad 0a90ee00 6e77bb67 0a90f014 clr!MethodDescCallSite::CallTargetWorker+0x152
0a90ef3c 6fb64306 0a90f0b8 0056c9d8 0a90f05c clr!ThreadNative::KickOffThread_Worker+0x173
0a90ef54 6fb64374 6e77b947 0a90f05c 00000000 clr!ManagedThreadBase_DispatchInner+0x67
0a90eff8 6fb64441 6e77a6eb 6fc1b5a9 0056c9d8 clr!ManagedThreadBase_DispatchMiddle+0x82
0a90f054 6fb644af 00000001 00000000 00000001 clr!ManagedThreadBase_DispatchOuter+0x5b
0a90f078 6fc1b669 00000001 00000002 6e77a64b clr!ManagedThreadBase_FullTransitionWithAD+0x2f
0a90f0f4 6fcea909 0056c9d8 76ddd38a 000004b4 clr!ThreadNative::KickOffThread+0x246
0a90ff14 768cee6c 09020c38 0a90ff60 76de3a03 clr!Thread::intermediateThreadProc+0x4d
0a90ff20 76de3a03 09020c38 7c759077 00000000 kernel32!BaseThreadInitThunk+0xe
0a90ff60 76de39d6 6fcea8c0 09020c38 00000000 ntdll!__RtlUserThreadStart+0x70
0a90ff78 00000000 6fcea8c0 09020c38 00000000 ntdll!_RtlUserThreadStart+0x1b
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: clr!WKS::gc_heap:
lan_phase+9f2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: clr
IMAGE_NAME: clr.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 5348961e
STACK_COMMAND: ~30s; .ecxr ; kb
FAILURE_BUCKET_ID: WRONG_SYMBOLS_c0000005_clr.dll!WKS::gc_heap:
lan_phase
BUCKET_ID: APPLICATION_FAULT_WRONG_SYMBOLS_clr!WKS::gc_heap:
lan_phase+9f2
ANALYSIS_SOURCE: UM
FAILURE_ID_HASH_STRING: um:wrong_symbols_c0000005_clr.dll!wks::gc_heap:
lan_phase
FAILURE_ID_HASH: {335d984a-5669-b8fd-e98d-700534a6fbec}
Followup: MachineOwner
---------
