阅读294 返回首页    go 小米 go 小米 note

Windows10只要一访问iis express 或者 iis 内网网址的网站就蓝屏

以下是我winDbg 的分析日志


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


Loading Dump File [C:\Users\greedy\Desktop\053117-12250-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 14393 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 14393.1198.amd64fre.rs1_release_sec.170427-1353
Machine Name:
Kernel base = 0xfffff803`a6475000 PsLoadedModuleList = 0xfffff803`a6774000
Debug session time: Wed May 31 14:57:14.775 2017 (UTC + 8:00)
System Uptime: 0 days 0:17:04.559
Loading Kernel Symbols
..........................Missing image name, possible paged-out or corrupt data.
.....................................
................................................................
.............................................
Loading User Symbols
Loading unloaded module list
.......................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffcb814ac9f000, 0, fffff807b3f3163a, 0}


Could not read faulting driver name
Unable to load image Qghehd.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Qghehd.SYS
*** ERROR: Module load completed but symbols could not be loaded for Qghehd.SYS
Probably caused by : Unknown_Image ( PAGE_NOT_ZERO )

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

 *** Memory manager detected 106819 instance(s) of page corruption, target is likely to have memory corruption.

1: 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: ffffcb814ac9f000, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff807b3f3163a, 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: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
 ffffcb814ac9f000 

FAULTING_IP: 
Qghehd+163a
fffff807`b3f3163a 478a0c23        mov     r9b,byte ptr [r11+r12]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  iisexpress.exe

CURRENT_IRQL:  2

BAD_PAGES_DETECTED: 1a143

LAST_CONTROL_TRANSFER:  from fffff803a65eea88 to fffff803a65c3c00

STACK_TEXT:  
ffffcb81`4b0d97a8 fffff803`a65eea88 : 00000000`00000050 ffffcb81`4ac9f000 00000000`00000000 ffffcb81`4b0d9aa0 : nt!KeBugCheckEx
ffffcb81`4b0d97b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x1b9f8


STACK_COMMAND:  kb

SYMBOL_NAME:  PAGE_NOT_ZERO

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

BUCKET_ID:  PAGE_NOT_ZERO

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

 *** Memory manager detected 106819 instance(s) of page corruption, target is likely to have memory corruption.

最后更新：2017-05-31 15:40:59

  上一篇：go Win10 insider preview 15048rs2更新新版，提示0xc0000409错误。
  下一篇：go 安装更新时出现一些问题，但我们稍后会重试。如果你继续看到此错误，并且想要搜索 Web