Loading Dump File [C:\Program Files (x86)\QingLu\QLWisdomClass232\crash(14).dmp] User Mini Dump File: Only registers, stack and portions of memory are available ************* Path validation summary ************** Response Time (ms) Location OK C:\Program Files (x86)\QingLu\QLWisdomClass232 Symbol search path is: C:\Program Files (x86)\QingLu\QLWisdomClass232 Executable search path is: Windows 10 Version 19042 MP (6 procs) Free x86 compatible Product: WinNt, suite: SingleUserTS 19041.1.amd64fre.vb_release.191206-1406 Machine Name: Debug session time: Tue Apr 20 16:45:54.000 2021 (UTC + 8:00) System Uptime: not available Process Uptime: 0 days 0:26:48.000 ................................................................ ................................................................ ................................................................ ............. This dump file has an exception of interest stored in it. The stored exception information can be accessed via .ecxr. (b170.f4b0): Access violation - code c0000005 (first/second chance not available) For analysis of this file, run !analyze -v eax=00000000 ebx=0d7e1ca8 ecx=00000000 edx=00000001 esi=0d7e1c58 edi=0d7e1c68 eip=77e43abc esp=00f5a2a8 ebp=00f5a2b4 iopl=0 nv up ei pl nz na po nc cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00200202 ntdll!NtGetContextThread+0xc: 77e43abc c20800 ret 8 0:000> !analyze -v ******************************************************************************* * * * Exception Analysis * * * ******************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: $ntdllsym!_CONTEXT *** *** *** ************************************************************************* ***** OS symbols are WRONG. Please fix symbols to do analysis. ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_CONTEXT *** *** *** ************************************************************************* KEY_VALUES_STRING: 1 PROCESSES_ANALYSIS: 1 SERVICE_ANALYSIS: 1 STACKHASH_ANALYSIS: 1 TIMELINE_ANALYSIS: 1 DUMP_CLASS: 2 DUMP_QUALIFIER: 400 CONTEXT: (.ecxr) eax=0c820990 ebx=1af78cf8 ecx=00000000 edx=00000001 esi=0c820998 edi=00000001 eip=764ce597 esp=00f5ba28 ebp=00f5ba40 iopl=0 nv up ei pl zr na pe nc cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00210246 combase!NdrExtStubInitialize+0xc937: 764ce597 8b8170010000 mov eax,dword ptr [ecx+170h] ds:002b:00000170=???????? Resetting default scope FAULTING_IP: combase!NdrExtStubInitialize+c937 764ce597 8b8170010000 mov eax,dword ptr [ecx+170h] EXCEPTION_RECORD: (.exr -1) ExceptionAddress: 764ce597 (combase!NdrExtStubInitialize+0x0000c937) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 00000000 Parameter[1]: 00000170 Attempt to read from address 00000170 BUGCHECK_STR: A9AC4E88 PROCESS_NAME: ntdll.wrong.symbols.dll WRONG_SYMBOLS_TIMESTAMP: a9ac4e88 WRONG_SYMBOLS_SIZE: 1a3000 FAULTING_MODULE: 77dd0000 ntdll DEBUG_FLR_IMAGE_TIMESTAMP: a9ac4e88 ADDITIONAL_DEBUG_TEXT: You can run '.symfix; .reload' to try to fix the symbol path and load symbols. ; Followup set based on attribute [Is_ChosenCrashFollowupThread] from Frame:[0] on thread:[PSEUDO_THREAD] ANALYSIS_SESSION_HOST: DESKTOP-QGG3SF2 ANALYSIS_SESSION_TIME: 04-21-2021 09:00:56.0813 ANALYSIS_VERSION: 10.0.18362.1 x86fre STACK_TEXT: 00f5ba28 764ce597 combase!NdrExtStubInitialize+0xc937 00f5ba48 764cdcd3 combase!NdrExtStubInitialize+0xc073 00f5bad0 764c6a73 combase!NdrExtStubInitialize+0x4e13 00f5bcb0 764c8b41 combase!NdrExtStubInitialize+0x6ee1 00f5be9c 764609f8 combase!HSTRING_UserSize+0x10e8 00f5bec4 75d05ed6 rpcrt4!NdrClientCall2+0x526 00f5c340 7650e160 combase!ObjectStublessClient32+0x7e80 00f5c360 765060ff combase!RoTransformErrorW+0xeff 00f5c370 76453f5d combase!CStdStubBuffer_AddRef+0x263d 00f5c3cc 764b774d combase!CoMarshalInterface+0x945d 00f5c444 764b7a24 combase!CoMarshalInterface+0x9734 00f5c4c8 7648a644 combase!PropVariantClear+0xb34 00f5c524 764b6b0f combase!CoMarshalInterface+0x881f 00f5c5b8 764b6984 combase!CoMarshalInterface+0x8694 00f5c5d4 7648baeb combase!GetHGlobalFromStream+0x2cb 00f5c610 7642c021 combase!InternalGetWindowPropInterface2+0xb1 00f5c718 7751e407 ole32!ReadFmtUserTypeStg+0x167 00f5c744 775b0524 ole32!GetActiveObjectExt+0x9ba4 00f5c764 775b07e4 ole32!GetActiveObjectExt+0x9e64 00f5c78c 77578452 ole32!OleGetPackageClipboardOwner+0x79a2 00f5c7d4 7757a1b9 ole32!OleGetPackageClipboardOwner+0x9709 00f5c878 7757a821 ole32!DoDragDrop+0xe1 00f5ca00 5de277db qwindows+0x477db 00f5ca2c 6de442e7 Qt5WebEngineWidgets!QWebEngineProfile::qt_static_metacall+0x187 00f5ca3c 5412b4f9 Qt5Core!QObject::inherits+0x9 00f5ca44 5c4e2fff Qt5Widgets!QApplicationPrivate::notifyDragStarted+0x1f 00f5ca4c 795e14bb Qt5Gui!QDragManager::drag+0xfb 00f5ca7c 795e1b48 Qt5Gui!QDrag::exec+0x98 00f5ca98 1114b361 Qt5WebEngineCore!GetHandleVerifier+0x7131 00f5caa4 795e1aab Qt5Gui!QDrag::exec+0xb 00f5cab0 0ffbeee2 Qt5WebEngineCore!QtWebEngineCore::WebContentsAdapter::startDragging+0x152 THREAD_SHA1_HASH_MOD_FUNC: 84e91e75f4810539e31ee0f5812b2edd40aa5043 THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 6fb80c5222c1950a5cdde3cdefa94d245c8b99f0 THREAD_SHA1_HASH_MOD: 019788c8cbb3fdac6af276bff7c4ca57416a362c FOLLOWUP_IP: combase!NdrExtStubInitialize+c937 764ce597 8b8170010000 mov eax,dword ptr [ecx+170h] FAULT_INSTR_CODE: 170818b SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: ntdll_wrong_symbols!A9AC4E881A3000 FOLLOWUP_NAME: MachineOwner STACK_COMMAND: .ecxr ; kb ; ** Pseudo Context ** Pseudo ** Value: 1ab44360 ** ; kb EXCEPTION_CODE: (HRESULT) 0xa9ac4e88 (2846641800) - EXCEPTION_CODE_STR: A9AC4E88 EXCEPTION_STR: WRONG_SYMBOLS IMAGE_NAME: ntdll.wrong.symbols.dll MODULE_NAME: ntdll_wrong_symbols BUCKET_ID: WRONG_SYMBOLS_X86_19041.1.amd64fre.vb_release.191206-1406_TIMESTAMP_600316-055000 DEFAULT_BUCKET_ID: WRONG_SYMBOLS_X86_19041.1.amd64fre.vb_release.191206-1406_TIMESTAMP_600316-055000 PRIMARY_PROBLEM_CLASS: WRONG_SYMBOLS FAILURE_EXCEPTION_CODE: A9AC4E88 FAILURE_IMAGE_NAME: ntdll.wrong.symbols.dll BUCKET_ID_IMAGE_STR: ntdll.wrong.symbols.dll FAILURE_MODULE_NAME: ntdll_wrong_symbols BUCKET_ID_MODULE_STR: ntdll_wrong_symbols FAILURE_FUNCTION_NAME: A9AC4E881A3000 BUCKET_ID_FUNCTION_STR: A9AC4E881A3000 BUCKET_ID_OFFSET: 0 BUCKET_ID_MODTIMEDATESTAMP: 0 BUCKET_ID_MODCHECKSUM: 0 BUCKET_ID_MODVER_STR: 0.0.0.0 BUCKET_ID_PREFIX_STR: WRONG_SYMBOLS_X86_19041.1.amd64fre.vb_release.191206-1406_TIMESTAMP_600316-055000 FAILURE_PROBLEM_CLASS: WRONG_SYMBOLS FAILURE_SYMBOL_NAME: ntdll.wrong.symbols.dll!A9AC4E881A3000 FAILURE_BUCKET_ID: WRONG_SYMBOLS_X86_19041.1.amd64fre.vb_release.191206-1406_TIMESTAMP_600316-055000_A9AC4E88_ntdll.wrong.symbols.dll!A9AC4E881A3000 TARGET_TIME: 2021-04-20T08:45:54.000Z OSBUILD: 19042 OSSERVICEPACK: 804 SERVICEPACK_NUMBER: 0 OS_REVISION: 0 SUITE_MASK: 256 PRODUCT_TYPE: 1 OSPLATFORM_TYPE: x86 OSNAME: Windows 10 OSEDITION: Windows 10 WinNt SingleUserTS OS_LOCALE: USER_LCID: 0 OSBUILD_TIMESTAMP: 2036-02-11 09:40:26 BUILDDATESTAMP_STR: 191206-1406 BUILDLAB_STR: vb_release BUILDOSVER_STR: 10.0.19041.1.amd64fre.vb_release.191206-1406 ANALYSIS_SESSION_ELAPSED_TIME: 28a ANALYSIS_SOURCE: UM FAILURE_ID_HASH_STRING: um:wrong_symbols_x86_19041.1.amd64fre.vb_release.191206-1406_timestamp_600316-055000_a9ac4e88_ntdll.wrong.symbols.dll!a9ac4e881a3000 FAILURE_ID_HASH: {f75deab1-7b7e-40ea-e848-491f084cc0f6} Followup: MachineOwner ---------