閱讀627 返回首頁    go 人物


win7 64位係統一日三次藍屏或重啟 問題一ntkrnlmp.exe 問題二win32k.sys 求解決辦法

問題一

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


Loading Dump File [C:\Windows\Minidump\010518-16068-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.23915.amd64fre.win7sp1_ldr.170913-0600
Machine Name:
Kernel base = 0xfffff800`04649000 PsLoadedModuleList = 0xfffff800`0488b750
Debug session time: Fri Jan  5 22:57:22.682 2018 (UTC + 8:00)
System Uptime: 0 days 1:00:35.009
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {fffff6fc50022ce0, ffffffffc00000c0, 14f143880, fffff8a00459c550}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+3158a )

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

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

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: fffff6fc50022ce0, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc00000c0, error status (normally i/o status code)
Arg3: 000000014f143880, current process (virtual address for lock type 3, or PTE)
Arg4: fffff8a00459c550, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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


ERROR_CODE: (NTSTATUS) 0xc00000c0 - <Unable to get error code text>

BUGCHECK_STR:  0x7a_c00000c0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800a18aad0 -- (.trap 0xfffff8800a18aad0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000046 rbx=0000000000000000 rcx=fffff8a000861004
rdx=0000000003d3b54c rsi=0000000000000000 rdi=0000000000000000
rip=fffff88001230cb1 rsp=fffff8800a18ac68 rbp=fffff8800a18b0a0
 r8=0000000000000046  r9=0000000000000000 r10=fffffa8009cca070
r11=fffff8a000861004 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
Ntfs!memmove+0x41:
fffff880`01230cb1 8b040a          mov     eax,dword ptr [rdx+rcx] ds:008f:fffff8a0`0459c550=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000472e512 to fffff800046b9e00

STACK_TEXT:  
fffff880`0a18a7b8 fffff800`0472e512 : 00000000`0000007a fffff6fc`50022ce0 ffffffff`c00000c0 00000001`4f143880 : nt!KeBugCheckEx
fffff880`0a18a7c0 fffff800`046e1dc7 : fffffa80`0a4f77e0 fffff880`0a18a930 fffff800`048f8600 fffffa80`0a4f77e0 : nt! ?? ::FNODOBFM::`string'+0x3158a
fffff880`0a18a8a0 fffff800`046c8039 : 00000000`00000000 00000000`00000000 ffffffff`ffffffff 000008a1`0000113e : nt!MiIssueHardFault+0x28b
fffff880`0a18a970 fffff800`046b7f2e : 00000000`00000000 fffff8a0`0459c550 000008cc`00001100 00000000`00000046 : nt!MmAccessFault+0x1399
fffff880`0a18aad0 fffff880`01230cb1 : fffff880`012aee2a 00000000`00000000 00000000`000001f1 fffff8a0`0086103e : nt!KiPageFault+0x16e
fffff880`0a18ac68 fffff880`012aee2a : 00000000`00000000 00000000`000001f1 fffff8a0`0086103e fffff8a0`0086103e : Ntfs!memmove+0x41
fffff880`0a18ac70 fffff880`012b05f0 : fffff880`0a18ae80 fffffa80`09cca070 fffff8a0`04405c00 fffff880`0a18ae00 : Ntfs!NtfsQueryNameInfo+0x12a
fffff880`0a18ad10 fffff880`012ae856 : fffff880`0a18ae80 fffffa80`080c6800 fffff880`00001f7a fffffa80`00001fc4 : Ntfs!NtfsCommonQueryInformation+0x86e
fffff880`0a18ade0 fffff880`012af034 : fffff880`0a18ae80 fffffa80`080c6800 fffffa80`080c6b58 fffff880`0a18af20 : Ntfs!NtfsFsdDispatchSwitch+0x106
fffff880`0a18ae60 fffff880`00c02bcf : fffff880`0a18b100 fffff880`00c03329 fffff880`0a18b100 00000000`00000005 : Ntfs!NtfsFsdDispatchWait+0x14
fffff880`0a18b050 fffff880`00c016df : fffffa80`0747da30 fffffa80`0747da30 fffffa80`0747da00 fffffa80`080c6800 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`0a18b0e0 fffff800`04967ac4 : fffffa80`080c6800 fffff8a0`00861000 fffffa80`0747da30 fffffa80`09cca070 : FLTMGR!FltpDispatch+0xcf
fffff880`0a18b140 fffff800`0499c315 : 00000000`00000004 fffff880`0a18b480 fffff8a0`00861000 fffff880`0a18b280 : nt!IopGetFileInformation+0xd4
fffff880`0a18b1c0 fffff800`0499c752 : fffffa80`09cca070 00000000`00000003 fffff880`0a18b300 fffffa80`0b97d000 : nt!IopQueryNameInternal+0x375
fffff880`0a18b260 fffff800`04993bb4 : 00000000`00000001 00000000`0023a000 00000000`04410000 fffff800`046992b4 : nt!IopQueryName+0x26
fffff880`0a18b2b0 fffff800`0499c71e : fffffa80`09cca070 fffffa80`0b97d000 fffffa80`00002000 fffff880`0a18b510 : nt!ObpQueryNameString+0xb0
fffff880`0a18b3b0 fffff800`0495f59f : fffff880`0a18b480 fffffa80`0950d720 fffff8a0`0085d000 00000000`000001a8 : nt!ObQueryNameString+0xe
fffff880`0a18b3f0 fffff800`04973d26 : fffffa80`0950d720 fffffa80`0950d720 00000000`00000000 fffffa80`0a280ac0 : nt!EtwTraceProcess+0xef
fffff880`0a18b7d0 fffff800`04991a38 : 000007ff`fff7a000 fffff880`0a18bae0 00000000`00000000 fffffa80`08f963b0 : nt!PspExitProcess+0x52
fffff880`0a18b830 fffff800`04976645 : fffffa80`c0000005 00000000`c0000001 000007ff`fff7a000 fffffa80`095e09d0 : nt!PspExitThread+0x848
fffff880`0a18b8f0 fffff800`046adc04 : 00000000`00000000 00000000`00000001 fffffa80`0a280ac0 fffff800`046bf23d : nt!PsExitSpecialApc+0x1d
fffff880`0a18b920 fffff800`046adf50 : 00000000`ffffffff fffff880`0a18b9a0 fffff800`049765b8 00000000`00000001 : nt!KiDeliverApc+0x2e4
fffff880`0a18b9a0 fffff800`046b9137 : fffffa80`0a280ac0 00000000`ffffffff 00000000`00000000 fffffa80`0a2773e0 : nt!KiInitiateUserApc+0x70
fffff880`0a18bae0 00000000`77c7bd7a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`02b8fb98 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77c7bd7a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+3158a
fffff800`0472e512 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+3158a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  59b946d1

FAILURE_BUCKET_ID:  X64_0x7a_c00000c0_nt!_??_::FNODOBFM::_string_+3158a

BUCKET_ID:  X64_0x7a_c00000c0_nt!_??_::FNODOBFM::_string_+3158a

Followup: MachineOwner

---------

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~分割線~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~



問題二


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


Loading Dump File [C:\Windows\Minidump\010518-12292-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.23915.amd64fre.win7sp1_ldr.170913-0600
Machine Name:
Kernel base = 0xfffff800`04656000 PsLoadedModuleList = 0xfffff800`04898750
Debug session time: Fri Jan  5 20:41:48.681 2018 (UTC + 8:00)
System Uptime: 0 days 0:26:24.007
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {fffff6fc80603390, ffffffffc000000e, 2152e6880, fffff900c0672108}

Probably caused by : win32k.sys ( win32k!HMAllocObject+14f )

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

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

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: fffff6fc80603390, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 00000002152e6880, current process (virtual address for lock type 3, or PTE)
Arg4: fffff900c0672108, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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


ERROR_CODE: (NTSTATUS) 0xc000000e - <Unable to get error code text>

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR:  0x7a_c000000e

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88005121100 -- (.trap 0xfffff88005121100)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff900c0672100 rbx=0000000000000000 rcx=fffff900c07a8180
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800047fd627 rsp=fffff88005121290 rbp=0000000000001000
 r8=0000000000000021  r9=fffff880053a1e50 r10=fffff880053a1cc8
r11=fffff900c016d010 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!ExAllocatePoolWithTag+0x537:
fffff800`047fd627 48895808        mov     qword ptr [rax+8],rbx ds:c168:fffff900`c0672108=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000473b512 to fffff800046c6e00

STACK_TEXT:  
fffff880`05120de8 fffff800`0473b512 : 00000000`0000007a fffff6fc`80603390 ffffffff`c000000e 00000002`152e6880 : nt!KeBugCheckEx
fffff880`05120df0 fffff800`046eedc7 : fffffa80`0c035010 fffff880`05120f60 fffff880`053a1c00 fffffa80`0c035010 : nt! ?? ::FNODOBFM::`string'+0x3158a
fffff880`05120ed0 fffff800`046d5039 : 00000000`00000000 00000000`00000001 ffffffff`ffffffff fffff880`051210f0 : nt!MiIssueHardFault+0x28b
fffff880`05120fa0 fffff800`046c4f2e : 00000000`00000001 fffff900`c0672108 00000000`00000000 fffff880`053a1e50 : nt!MmAccessFault+0x1399
fffff880`05121100 fffff800`047fd627 : fffffa80`07d64ab8 fffffa80`07d64a70 fffffa80`07d64a20 fffffa80`0806c060 : nt!KiPageFault+0x16e
fffff880`05121290 fffff960`0017482f : 00000000`00000000 00000000`00000024 fffff900`c016d490 00000000`00000000 : nt!ExAllocatePoolWithTag+0x537
fffff880`05121380 fffff960`0020ce9b : fffff900`c1c5a2b0 00000000`00000000 00000000`00000030 fffffa80`0806c0b0 : win32k!HMAllocObject+0x14f
fffff880`051213d0 fffff960`001ab4d5 : fffff900`c1c5a2b0 fffff900`c070831c fffff900`c08452e0 00000000`00000000 : win32k!AllocateHidData+0x67
fffff880`05121410 fffff960`001ae57b : 00000001`00182b82 fffff900`c070831c 00000000`00000661 00000000`00000342 : win32k!PostRawMouseInput+0xbd
fffff880`05121480 fffff960`001acf71 : fffff900`c070831c 00000000`00182b82 fffff900`c0708290 00000000`00182b82 : win32k!xxxMoveEventAbsolute+0x17f
fffff880`05121510 fffff960`001acdc8 : fffff900`c0708290 00000342`00000661 fffff880`05121ae0 00000000`00000018 : win32k!ProcessMouseInput+0x195
fffff880`05121580 fffff800`046bab3d : fffffa80`09216b10 00000000`00000000 00000000`20707249 00000000`00000000 : win32k!InputApc+0x7c
fffff880`051215b0 fffff800`046cc23d : fffffa80`0806c120 00000000`00000000 fffff960`001acd4c 00000000`00000000 : nt!KiDeliverApc+0x21d
fffff880`05121630 fffff800`046cb54a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000002 : nt!KiCommitThreadWait+0x3dd
fffff880`051216c0 fffff960`0014b3f8 : fffff900`00000002 fffffa80`09210a90 fffff900`00000001 fffff880`0000000d : nt!KeWaitForMultipleObjects+0x272
fffff880`05121980 fffff960`0014c417 : 00000000`00000000 fffff900`c016d490 fffff960`003a7780 00000000`00000004 : win32k!xxxMsgWaitForMultipleObjects+0x108
fffff880`05121a00 fffff960`001050d4 : fffffa80`00000001 fffffa80`0000000c fffffa80`0806c060 fffff6fc`40022408 : win32k!xxxDesktopThread+0x253
fffff880`05121a80 fffff960`0018779a : fffffa80`00000001 fffff960`003a7780 00000000`00000020 00000000`00000000 : win32k!xxxCreateSystemThreads+0x64
fffff880`05121ab0 fffff800`046c6093 : fffffa80`0806c060 00000000`00000004 000007ff`fff9c000 00000000`00000000 : win32k!NtUserCallNoParam+0x36
fffff880`05121ae0 000007fe`fcf81f1a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`01b8f848 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fcf81f1a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!HMAllocObject+14f
fffff960`0017482f 488bd8          mov     rbx,rax

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  win32k!HMAllocObject+14f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  59e533c6

FAILURE_BUCKET_ID:  X64_0x7a_c000000e_win32k!HMAllocObject+14f

BUCKET_ID:  X64_0x7a_c000000e_win32k!HMAllocObject+14f

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



最後更新:2018-01-06 01:04:07

  上一篇:go 筆記本電腦在玩大型遊戲時會黑屏自動重啟,求助!
  下一篇:go Win10x64,出現DRIVER