Microsoft (R) Windows Debugger Version 10.0.18362.1 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\071719-6234-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Path validation summary **************
Response Time (ms) Location
Deferred srv*d:\SymbolsLocal*http://msdl.microsoft.com/download/symbols
Symbol search path is: srv*d:\SymbolsLocal*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 14393.447.amd64fre.rs1_release_inmarket.161102-0100
Machine Name:
Kernel base = 0xfffff800`92e1a000 PsLoadedModuleList = 0xfffff800`9311f060
Debug session time: Wed Jul 17 05:29:08.193 2019 (UTC + 8:00)
System Uptime: 0 days 0:15:33.069
Loading Kernel Symbols
...............................................................
................................................................
......................................................
Loading User Symbols
Loading unloaded module list
.........
For analysis of this file, run !analyze -v
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000008, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Debugging Details:
------------------
KEY_VALUES_STRING: 1
PROCESSES_ANALYSIS: 1
SERVICE_ANALYSIS: 1
STACKHASH_ANALYSIS: 1
TIMELINE_ANALYSIS: 1
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 14393.447.amd64fre.rs1_release_inmarket.161102-0100
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
DUMP_TYPE: 2
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: 0
BUGCHECK_P3: 8
BUGCHECK_P4: 0
CPU_COUNT: 8
CPU_MHZ: af8
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 9e
CPU_STEPPING: 9
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x1E
PROCESS_NAME: wmiprvse.exe
CURRENT_IRQL: 0
ANALYSIS_SESSION_HOST: DESKTOP-7SPFJ2I
ANALYSIS_SESSION_TIME: 07-17-2019 11:29:38.0955
ANALYSIS_VERSION: 10.0.18362.1 amd64fre
TRAP_FRAME: ffffab01ee723330 -- (.trap 0xffffab01ee723330)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000000e3cc6 rbx=0000000000000000 rcx=000000000000e944
rdx=ffffab01ee7234e0 rsi=0000000000000000 rdi=0000000000000000
rip=0000000000000000 rsp=ffffab01ee7234c0 rbp=0000000000000000
r8=0000000000000014 r9=ffffab01ee7234c0 r10=000000000000097d
r11=ffff9b0f90edab7f r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
00000000`00000000 ?? ???
Resetting default scope
IP_IN_FREE_BLOCK: 0
LAST_CONTROL_TRANSFER: from fffff80092fa9812 to fffff80092f64510
STACK_TEXT:
ffffab01`ee722a78 fffff800`92fa9812 : 00000000`0000001e ffffffff`c0000005 00000000`00000000 00000000`00000008 : nt!KeBugCheckEx
ffffab01`ee722a80 fffff800`92f6f702 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x35e72
ffffab01`ee723150 fffff800`92f6dbe1 : ffffab01`ee723490 ffff300e`7e9bc24f ffffab01`ee723410 ffffab01`ee723490 : nt!KiExceptionDispatch+0xc2
ffffab01`ee723330 00000000`00000000 : 00000000`000e3cc6 00000000`0000001f ffffde0e`0901d000 ffff9b0f`90c08af8 : nt!KiPageFault+0x221
THREAD_SHA1_HASH_MOD_FUNC: 9041c912964ff700ac617b24c2c708d61106b1d9
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 97134509def7aa3fcaf765506bf2b91de6df1603
THREAD_SHA1_HASH_MOD: d084f7dfa548ce4e51810e4fd5914176ebc66791
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+35e72
fffff800`92fa9812 cc int 3
FAULT_INSTR_CODE: 87f741cc
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+35e72
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 5819bd1f
IMAGE_VERSION: 10.0.14393.447
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 35e72
FAILURE_BUCKET_ID: 0x1E_nt!_??_::FNODOBFM::_string_
BUCKET_ID: 0x1E_nt!_??_::FNODOBFM::_string_
PRIMARY_PROBLEM_CLASS: 0x1E_nt!_??_::FNODOBFM::_string_
TARGET_TIME: 2019-07-16T21:29:08.000Z
OSBUILD: 14393
OSSERVICEPACK: 447
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2016-11-02 18:17:03
BUILDDATESTAMP_STR: 161102-0100
BUILDLAB_STR: rs1_release_inmarket
BUILDOSVER_STR: 10.0.14393.447.amd64fre.rs1_release_inmarket.161102-0100
ANALYSIS_SESSION_ELAPSED_TIME: 549
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x1e_nt!_??_::fnodobfm::_string_
FAILURE_ID_HASH: {9e00434f-0111-761e-4d68-b3b5c8ec7243}
Followup: MachineOwner
---------
uj5u.com熱心網友回復：
藍屏代碼多少？uj5u.com熱心網友回復：
0x000000001e
uj5u.com熱心網友回復：
藍屏代碼多少？記憶體不兼容
轉載請註明出處，本文鏈接：https://www.uj5u.com/caozuo/67235.html
標籤：Windows客戶端使用
下一篇：一些關于win10快速訪問的問題