868      windows

无故蓝屏

这是分析，求助

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


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

Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 10586.1106.amd64fre.th2_release.170904-1742
Machine Name:
Kernel base = 0xfffff803`a4419000 PsLoadedModuleList = 0xfffff803`a46f6c70
Debug session time: Tue Sep 26 22:42:21.786 2017 (UTC + 8:00)
System Uptime: 0 days 15:20:53.751
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
.................................................
Loading User Symbols
Loading unloaded module list
............................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffc000c5012e6d, 10, ffffc000c5012e6d, 2}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+10f41 )

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

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

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

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


Could not read faulting driver name

DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  10586.1106.amd64fre.th2_release.170904-1742

SYSTEM_MANUFACTURER:  LENOVO

SYSTEM_PRODUCT_NAME:  20DF0067CD

SYSTEM_SKU:  LENOVO_MT_20DF_BU_Think_FM_ThinkPad E550

SYSTEM_VERSION:  ThinkPad E550

BIOS_VENDOR:  LENOVO

BIOS_VERSION:  J5ET55WW (1.26 )

BIOS_DATE:  09/12/2016

BASEBOARD_MANUFACTURER:  LENOVO

BASEBOARD_PRODUCT:  20DF0067CD

BASEBOARD_VERSION:  SDK0E50518 STD

DUMP_TYPE:  2

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_P1: ffffc000c5012e6d

BUGCHECK_P2: 10

BUGCHECK_P3: ffffc000c5012e6d

BUGCHECK_P4: 2

READ_ADDRESS: fffff803a4796520: Unable to get MiVisibleState
 ffffc000c5012e6d Paged pool

FAULTING_IP: 
+0
ffffc000`c5012e6d ??              ???

MM_INTERNAL_CODE:  2

CPU_COUNT: 4

CPU_MHZ: 893

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3d

CPU_STEPPING: 4

CPU_MICROCODE: 6,3d,4,0 (F,M,S,R)  SIG: 23'00000000 (cache) 23'00000000 (init)

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  AV

PROCESS_NAME:  ShellExperienc

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  DESKTOP-JKPS4KK

ANALYSIS_SESSION_TIME:  09-26-2017 22:51:20.0506

ANALYSIS_VERSION: 10.0.15063.468 amd64fre

TRAP_FRAME:  ffffd0002081c7b0 -- (.trap 0xffffd0002081c7b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000e74
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=ffffc000c5012e6d rsp=ffffd0002081c948 rbp=ffffd0002081ca58
 r8=0000000000000004  r9=ffffc000c50ed128 r10=ffffc000c50e8390
r11=0000000000188c10 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
ffffc000`c5012e6d ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff803a457b341 to fffff803a455ba00

FAILED_INSTRUCTION_ADDRESS: 
+0
ffffc000`c5012e6d ??              ???

STACK_TEXT:  
ffffd000`2081c558 fffff803`a457b341 : 00000000`00000050 ffffc000`c5012e6d 00000000`00000010 ffffd000`2081c7b0 : nt!KeBugCheckEx
ffffd000`2081c560 fffff803`a444d391 : 00000000`00000010 ffffe000`abdf9800 ffffd000`2081c7b0 fffff803`a45606b2 : nt! ?? ::FNODOBFM::`string'+0x10f41
ffffd000`2081c650 fffff803`a4564cbc : 00000000`00000000 fffff803`a4437970 ffff613e`00000000 00000000`00000002 : nt!MmAccessFault+0x5f1
ffffd000`2081c7b0 ffffc000`c5012e6d : ffffc000`c500185a 00000000`00000000 fffff803`a4436ac3 ffffe000`abdf9800 : nt!KiPageFault+0x13c
ffffd000`2081c948 ffffc000`c500185a : 00000000`00000000 fffff803`a4436ac3 ffffe000`abdf9800 00000000`00000000 : 0xffffc000`c5012e6d
ffffd000`2081c950 00000000`00000000 : fffff803`a4436ac3 ffffe000`abdf9800 00000000`00000000 00000000`00000000 : 0xffffc000`c500185a


STACK_COMMAND:  kb

THREAD_SHA1_HASH_MOD_FUNC:  c657d94433f4f33fd268b372caf2b4bbf9b614e8

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  767cc8e47157752f86945f2eb7b2c8602c58f9ea

THREAD_SHA1_HASH_MOD:  d084f7dfa548ce4e51810e4fd5914176ebc66791

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+10f41
fffff803`a457b341 cc              int     3

FAULT_INSTR_CODE:  b60f40cc

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+10f41

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  59ae2ed4

IMAGE_VERSION:  10.0.10586.1106

BUCKET_ID_FUNC_OFFSET:  10f41

FAILURE_BUCKET_ID:  AV_INVALID_BAD_IP_nt!_??_::FNODOBFM::_string_

BUCKET_ID:  AV_INVALID_BAD_IP_nt!_??_::FNODOBFM::_string_

PRIMARY_PROBLEM_CLASS:  AV_INVALID_BAD_IP_nt!_??_::FNODOBFM::_string_

TARGET_TIME:  2017-09-26T14:42:21.000Z

OSBUILD:  10586

OSSERVICEPACK:  1106

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:  2017-09-05 12:57:56

BUILDDATESTAMP_STR:  170904-1742

BUILDLAB_STR:  th2_release

BUILDOSVER_STR:  10.0.10586.1106.amd64fre.th2_release.170904-1742

ANALYSIS_SESSION_ELAPSED_TIME:  81f

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:av_invalid_bad_ip_nt!_??_::fnodobfm::_string_

FAILURE_ID_HASH:  {9a93f5e0-d404-4f82-a10b-0379aeef7cb3}

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

最后更新：2017-09-26 23:03:50

  上一篇： 解码器

  下一篇： 每次启动就大概率蓝屏，之后重启就正常