閱讀988 返回首頁    go windows

ntkrnlmp.exe 導致win7 64位係統黑屏重啟


Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\112717-21902-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*https://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.23915.amd64fre.win7sp1_ldr.170913-0600
Machine Name:
Kernel base = 0xfffff800`05262000 PsLoadedModuleList = 0xfffff800`054a4750
Debug session time: Mon Nov 27 11:34:11.138 2017 (UTC + 8:00)
System Uptime: 0 days 2:01:00.773
Loading Kernel Symbols
...............................................................
................................................................
.....................................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {ff, 2, 0, fffff800052e8905}

Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000000000000ff, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800052e8905, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000550e100
 00000000000000ff 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!IopCompleteRequest+ae5
fffff800`052e8905 488b09          mov     rcx,qword ptr [rcx]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  explorer.exe

IRP_ADDRESS:  ffffffffffffff89

TRAP_FRAME:  fffff8800e11d1a0 -- (.trap 0xfffff8800e11d1a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8800e11c758 rbx=0000000000000000 rcx=00000000000000ff
rdx=00000000000000ff rsi=0000000000000000 rdi=0000000000000000
rip=fffff800052e8905 rsp=fffff8800e11d330 rbp=fffff8800e11dae0
 r8=0000000000004740  r9=0000000000000280 r10=0000000000000002
r11=00000000000001c8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe cy
nt!IopCompleteRequest+0xae5:
fffff800`052e8905 488b09          mov     rcx,qword ptr [rcx] ds:f118:00000000`000000ff=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800052d23a9 to fffff800052d2e00

STACK_TEXT:  
fffff880`0e11d058 fffff800`052d23a9 : 00000000`0000000a 00000000`000000ff 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0e11d060 fffff800`052d1020 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`0ddd5c60 : nt!KiBugCheckDispatch+0x69
fffff880`0e11d1a0 fffff800`052e8905 : fffffa80`0b4ab060 fffff800`0548c088 fffff6fc`20206f49 ffffffff`ffffffff : nt!KiPageFault+0x260
fffff880`0e11d330 fffff800`052c6b03 : 00000000`00000001 00000000`00000000 00000000`00000000 fffff8a0`00000000 : nt!IopCompleteRequest+0xae5
fffff880`0e11d400 fffff800`0528438d : 00000000`00001000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1e3
fffff880`0e11d480 fffff800`052c24d4 : 00000000`00000000 fffff980`18400000 00000000`6c526d4d fffff980`18400000 : nt!KiCheckForKernelApcDelivery+0x25
fffff880`0e11d4b0 fffff800`055c0ea0 : 00000000`00001000 00000000`00000000 00000000`00000000 fffff880`0e11d5e0 : nt!CcFetchDataForRead+0x174
fffff880`0e11d510 fffff880`0163e5b0 : fffff8a0`00000000 00000000`00000005 fffffa80`00040000 fffff880`01692001 : nt!CcCopyRead+0x180
fffff880`0e11d5d0 fffff880`01640093 : fffffa80`0df516b0 fffff8a0`06fc9701 fffff880`0e11d7d0 00000000`00000001 : Ntfs!NtfsCachedRead+0x180
fffff880`0e11d630 fffff880`01640458 : fffffa80`0b968280 fffffa80`0df516b0 fffff880`0e11d701 fffffa80`0d7ef000 : Ntfs!NtfsCommonRead+0x19ea
fffff880`0e11d7a0 fffff880`0141683f : fffffa80`0df51a50 fffffa80`0df516b0 fffffa80`0d7ef010 00000000`00000001 : Ntfs!NtfsFsdRead+0x1b8
fffff880`0e11d850 fffff880`014156df : fffffa80`09944de0 fffffa80`0bbc6940 fffffa80`0df51600 fffffa80`0df516b0 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`0e11d8e0 fffff800`055c0a0a : fffffa80`0bbc68f0 fffff880`0e11db60 fffffa80`0bbc6940 00000000`00000000 : fltmgr!FltpDispatch+0xcf
fffff880`0e11d940 fffff800`052d2093 : 00000000`00001900 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtReadFile+0x718
fffff880`0e11da70 00000000`7755bd9a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`139bdab8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7755bd9a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiPageFault+260
fffff800`052d1020 440f20c0        mov     rax,cr8

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiPageFault+260

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  59b946d1

FAILURE_BUCKET_ID:  X64_0xA_nt!KiPageFault+260

BUCKET_ID:  X64_0xA_nt!KiPageFault+260

Followup: MachineOwner
---------

最後更新：2017-11-27 14:04:03

  上一篇：go 移動硬盤無法識別
  下一篇：go 玩遊戲時電腦鍵盤輸入區大部分鍵突然失靈