Microsoft (R) Windows Debugger Version 10.0.19528.1000 AMD64Copyright (c) Microsoft Corporation. All rights reserved.Loading Dump File [C:\Users\11787\Desktop\032020-6906-01.dmp]Mini Kernel Dump File: Only registers and stack trace are available************* Path validation summary **************Response Time (ms) LocationDeferred srv*Symbol search path is: srv*Executable search path is: Windows 10 Kernel Version 18362 MP (8 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSMachine Name:Kernel base = 0xfffff802`3cc00000 PsLoadedModuleList = 0xfffff802`3d048150Debug session time: Fri Mar 20 13:23:02.324 2020 (UTC + 8:00)System Uptime: 0 days 1:53:48.070Loading Kernel Symbols.Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.Run !sym noisy before .reload to track down problems loading symbols......................................................................................................................................................................................Loading User SymbolsLoading unloaded module list
电脑故障吧 关注：594,485贴子：5,380,529
- 5回复贴，共1页
************* Symbol Loading Error Summary **************Module name Errorntkrnlmp The system cannot find the file specifiedYou can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.You should also verify that your symbol search path (.sympath) is correct.For analysis of this file, run !analyze -vnt!KeBugCheckEx:fffff802`3cdc2380 48894c2408 mov qword ptr [rsp+8],rcx ss:fffff88c`f1417860=000000000000001a6: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************
MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined.Arguments:Arg1: 0000000000061941, The subtype of the bugcheck.Arg2: 00000230716b98a8Arg3: 000000000000000dArg4: fffff88cf1417a00Debugging Details:------------------*** WARNING: Unable to verify timestamp for mssmbios.sys***** Kernel 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!_EPROCESS ****** ****************************************************************************
KEY_VALUES_STRING: 1 Key : Analysis.CPU.Sec Value: 0 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on DESKTOP-N6V53Q5 Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.Sec Value: 11 Key : Analysis.Memory.CommitPeak.Mb Value: 59 Key : Analysis.System Value: CreateObjectADDITIONAL_XML: 1ADDITIONAL_DEBUG_TEXT: You can run '.symfix; .reload' to try to fix the symbol path and load symbols.WRONG_SYMBOLS_TIMESTAMP: e45edf24WRONG_SYMBOLS_SIZE: ab7000FAULTING_MODULE: fffff8023cc00000 ntDUMP_FILE_ATTRIBUTES: 0x8 Kernel Generated Triage DumpBUGCHECK_CODE: 1aBUGCHECK_P1: 61941BUGCHECK_P2: 230716b98a8BUGCHECK_P3: dBUGCHECK_P4: fffff88cf1417a00CUSTOMER_CRASH_COUNT: 1STACK_TEXT: fffff88c`f1417858 fffff802`3ce4288c : 00000000`0000001a 00000000`00061941 00000230`716b98a8 00000000`0000000d : nt!KeBugCheckExfffff88c`f1417860 fffff802`3cdd0420 : ffffd18a`00000000 00000230`00000001 00000000`00000000 fffff88c`f1417a80 : nt!memset+0x6d40cfffff88c`f1417a00 00007ffe`62d70cff : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!setjmpex+0x43e000000043`daaff750 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`62d70cffSTACK_COMMAND: .thread ; .cxr ; kbEXCEPTION_CODE_STR: E45EDF24EXCEPTION_STR: WRONG_SYMBOLSPROCESS_NAME: ntoskrnl.wrong.symbols.exeIMAGE_NAME: ntoskrnl.wrong.symbols.exeMODULE_NAME: nt_wrong_symbolsSYMBOL_NAME: nt_wrong_symbols!E45EDF24AB7000FAILURE_BUCKET_ID: WRONG_SYMBOLS_X64_10.0.18362.720_(WinBuild.160101.0800)_TIMESTAMP_910531-040556_E45EDF24_nt_wrong_symbols!E45EDF24AB7000OSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {8f0981e2-86bf-0998-bb22-d17e680b513c}Followup: MachineOwner
