阅读145 返回首页    go 阿里云 go 技术社区[云栖]

win10 1703蓝屏

请问下这是什么原因造成的蓝屏?谢谢

WARNING: Inaccessible path: '\MyCodesSymbols'

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


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

WARNING: Inaccessible path: '\MyCodesSymbols'
Symbol search path is: SRV*F:\Symbols*https://msdl.microsoft.com/download/symbols;\MyCodesSymbols;SRV*C:\MyLocalSymbols*https://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 15063 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 15063.0.amd64fre.rs2_release.170317-1834
Machine Name:
Kernel base = 0xfffff803`b8e1f000 PsLoadedModuleList = 0xfffff803`b916b5a0
Debug session time: Tue Jun 27 21:12:37.316 2017 (UTC + 8:00)
System Uptime: 0 days 2:57:00.112
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 1000007E, {ffffffffc0000005, fffff803b8f90ef7, ffff9e80d2553538, ffff9e80d2552d80}

Unable to load image \SystemRoot\System32\drivers\FNETHYRAMAS.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for FNETHYRAMAS.SYS
*** ERROR: Module load completed but symbols could not be loaded for FNETHYRAMAS.SYS
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

Followup: memory_corruption
---------

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff803b8f90ef7, The address that the exception occurred at
Arg3: ffff9e80d2553538, Exception Record Address
Arg4: ffff9e80d2552d80, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - 0x%p

FAULTING_IP: 
nt!ExpInterlockedPopEntrySListFault+0
fffff803`b8f90ef7 498b08          mov     rcx,qword ptr [r8]

EXCEPTION_RECORD:  ffff9e80d2553538 -- (.exr 0xffff9e80d2553538)
ExceptionAddress: fffff803b8f90ef7 (nt!ExpInterlockedPopEntrySListFault)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  ffff9e80d2552d80 -- (.cxr 0xffff9e80d2552d80)
rax=0000000901ae0010 rbx=0000000000000160 rcx=fffffd0000006160
rdx=dffffa0013551420 rsi=0000000000000000 rdi=0000000000000001
rip=fffff803b8f90ef7 rsp=ffff9e80d2553770 rbp=0000000000000001
 r8=dffffa0013551420  r9=0000000000000000 r10=fffffd0000006160
r11=0000000000000000 r12=0000000000000016 r13=0000000000000000
r14=fffff803b919c0c0 r15=0000000000000001
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
nt!ExpInterlockedPopEntrySListFault:
fffff803`b8f90ef7 498b08          mov     rcx,qword ptr [r8] ds:002b:dffffa00`13551420=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - 0x%p

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS:  ffffffffffffffff 

FOLLOWUP_IP: 
nt!ExpInterlockedPopEntrySListFault+0
fffff803`b8f90ef7 498b08          mov     rcx,qword ptr [r8]

BUGCHECK_STR:  0x7E

EXCEPTION_STR:  0x0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff803b8f90ef7

SYMBOL_ON_RAW_STACK:  1

STACK_ADDR_RAW_STACK_SYMBOL: ffff9e80d2553a70

STACK_COMMAND:  dds FFFF9E80D2553A70-0x20 ; kb

STACK_TEXT:  


CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff803b8e89312-fffff803b8e89313  2 bytes - nt!ExFreeLargePool+672
[ 80 f6:00 81 ]
    fffff803b8e98b4b-fffff803b8e98b4c  2 bytes - nt!MiFlushTbAsNeeded+13b (+0xf839)
[ 80 f6:00 81 ]
    fffff803b8e98b9c-fffff803b8e98b9d  2 bytes - nt!MiFlushTbAsNeeded+18c (+0x51)
[ 80 f6:00 81 ]
    fffff803b8e98bd5-fffff803b8e98bd6  2 bytes - nt!MiFlushTbAsNeeded+1c5 (+0x39)
[ 80 f6:00 81 ]
    fffff803b8eb0ac3 - nt!MiGetPage+a3 (+0x17eee)
[ 80:00 ]
    fffff803b8eb0c32 - nt!MiGetFreeOrZeroPage+72 (+0x16f)
[ 80:00 ]
10 errors : !nt (fffff803b8e89312-fffff803b8eb0c32)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE

BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE

Followup: memory_corruption
---------

您好！

由于您的提供的dump文件不完整，建议您按Windows+X打开系统— 高级系统设置，在“启动和故障恢复”里点击“设置”，把写入调试信息修改为“完全内存转储”。重启之后再次出现蓝屏的时候按照C:\Windows\MEMORY.DMP重新上传dump文件。
https://support.microsoft.com/zh-cn/help/307973/how-to-configure-system-failure-and-recovery-options-in-windows

最后更新：2017-07-10 10:33:01

  上一篇：go win8.1的照片磁贴一直不翻转
  下一篇：go edge无法使用，详情如下