阅读960 返回首页    go 微软 go windows

WIN64位专业版开机出现蓝屏

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


Loading Dump File [C:\Users\Administrator\Desktop\[192.168.0.13][2018-01-04 15-33-34] [2060823775].dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\websymbols*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.18229.amd64fre.win7sp1_gdr.130801-1533
Machine Name:
Kernel base = 0xfffff800`0445d000 PsLoadedModuleList = 0xfffff800`046a06d0
Debug session time: Thu Jan  4 15:33:40.442 2018 (UTC + 8:00)
System Uptime: 0 days 0:00:51.394
Loading Kernel Symbols
...............................................................
................................................................
.............................................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffa802ec7f3b3, 0, fffff880053e6f54, 0}

Unable to load image ppicepynzt.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ppicepynzt.sys
*** ERROR: Module load completed but symbols could not be loaded for ppicepynzt.sys

Could not read faulting driver name
Probably caused by : ppicepynzt.sys ( ppicepynzt+5f54 )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffa802ec7f3b3, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff880053e6f54, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000470a100
 fffffa802ec7f3b3 

FAULTING_IP: 
ppicepynzt+5f54
fffff880`053e6f54 410fb7490a      movzx   ecx,word ptr [r9+0Ah]

MM_INTERNAL_CODE:  0

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800b0f6920 -- (.trap 0xfffff8800b0f6920)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000007757 rbx=0000000000000000 rcx=0000000000000004
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880053e6f54 rsp=fffff8800b0f6ab8 rbp=fffff880053ea7dd
 r8=0000000000000000  r9=fffffa802ec7f3a9 r10=fffffa802ec79016
r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz ac pe cy
ppicepynzt+0x5f54:
fffff880`053e6f54 410fb7490a      movzx   ecx,word ptr [r9+0Ah] ds:e9a0:fffffa80`2ec7f3b3=????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80004550be0 to fffff800044d2b80

STACK_TEXT:  
fffff880`0b0f67b8 fffff800`04550be0 : 00000000`00000050 fffffa80`2ec7f3b3 00000000`00000000 fffff880`0b0f6920 : nt!KeBugCheckEx
fffff880`0b0f67c0 fffff800`044d0cae : 00000000`00000000 fffffa80`2ec7f3b3 00000000`fffff800 00000000`00000004 : nt! ?? ::FNODOBFM::`string'+0x4518f
fffff880`0b0f6920 fffff880`053e6f54 : fffff880`053e721b fffffa80`2ec79010 00000000`00000000 fffff880`053ea7dc : nt!KiPageFault+0x16e
fffff880`0b0f6ab8 fffff880`053e721b : fffffa80`2ec79010 00000000`00000000 fffff880`053ea7dc 00000000`000007ff : ppicepynzt+0x5f54
fffff880`0b0f6ac0 fffffa80`2ec79010 : 00000000`00000000 fffff880`053ea7dc 00000000`000007ff fffff880`04969f40 : ppicepynzt+0x621b
fffff880`0b0f6ac8 00000000`00000000 : fffff880`053ea7dc 00000000`000007ff fffff880`04969f40 00000000`00000000 : 0xfffffa80`2ec79010


STACK_COMMAND:  kb

FOLLOWUP_IP: 
ppicepynzt+5f54
fffff880`053e6f54 410fb7490a      movzx   ecx,word ptr [r9+0Ah]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  ppicepynzt+5f54

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ppicepynzt

IMAGE_NAME:  ppicepynzt.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  57038152

FAILURE_BUCKET_ID:  X64_0x50_ppicepynzt+5f54

BUCKET_ID:  X64_0x50_ppicepynzt+5f54

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

最后更新：2018-01-04 18:04:30

  上一篇：go 我在用电脑管家修复漏洞的时候 重新启动就变成这样了 怎么解决啊
  下一篇：go Windows10文件ntoskrnl.exe引起蓝屏崩溃怎么解决？