閱讀473 返回首頁    go iPhone_iPad_Mac_apple

求助分析藍屏dmp數據

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


Loading Dump File [D:\102517-28062-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 15063 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 15063.0.amd64fre.rs2_release.170317-1834
Machine Name:
Kernel base = 0xfffff801`54c14000 PsLoadedModuleList = 0xfffff801`54f605c0
Debug session time: Wed Oct 25 00:00:37.421 2017 (UTC + 8:00)
System Uptime: 5 days 4:02:19.149
Loading Kernel Symbols
...............................................................
................................................................
...................................................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffb08ec6844cd3, 10, ffffb08ec6844cd3, 0}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiSystemFault+116a0c )

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

nt!KeBugCheckEx:
fffff801`54d80580 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffc080`a5ada6c0=0000000000000050
2: 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: ffffb08ec6844cd3, memory referenced.
Arg2: 0000000000000010, value 0 = read operation, 1 = write operation.
Arg3: ffffb08ec6844cd3, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000000, (reserved)

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


Could not read faulting driver name

DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  15063.0.amd64fre.rs2_release.170317-1834

SYSTEM_MANUFACTURER:  Gigabyte Technology Co., Ltd.

SYSTEM_PRODUCT_NAME:  G1.Sniper Z6

SYSTEM_SKU:  To be filled by O.E.M.

SYSTEM_VERSION:  To be filled by O.E.M.

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  F3

BIOS_DATE:  04/24/2014

BASEBOARD_MANUFACTURER:  Gigabyte Technology Co., Ltd.

BASEBOARD_PRODUCT:  G1.Sniper Z6

BASEBOARD_VERSION:  x.x

DUMP_TYPE:  2

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_P1: ffffb08ec6844cd3

BUGCHECK_P2: 10

BUGCHECK_P3: ffffb08ec6844cd3

BUGCHECK_P4: 0

READ_ADDRESS: Unable to get size of nt!_MMPTE - probably bad symbols
 ffffb08ec6844cd3 

FAULTING_IP: 
+0
ffffb08e`c6844cd3 ??              ???

MM_INTERNAL_CODE:  0

CPU_COUNT: 8

CPU_MHZ: fa0

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3c

CPU_STEPPING: 3

CPU_MICROCODE: 0,0,0,0 (F,M,S,R)  SIG: 1E'00000000 (cache) 0'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  AV

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  TEXT-PC

ANALYSIS_SESSION_TIME:  10-25-2017 01:16:25.0582

ANALYSIS_VERSION: 10.0.17016.1000 amd64fre

TRAP_FRAME:  ffffc080a5ada950 -- (.trap 0xffffc080a5ada950)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000001787d01 rbx=0000000000000000 rcx=fffffffffffffffa
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=ffffb08ec6844cd3 rsp=ffffc080a5adaae0 rbp=ffffc080a5adab80
 r8=000000e6cbfff090  r9=0000000000000058 r10=fffff801550c32b0
r11=00000000001787d0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe cy
ffffb08e`c6844cd3 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80154db5f2c to fffff80154d80580

FAILED_INSTRUCTION_ADDRESS: 
+0
ffffb08e`c6844cd3 ??              ???

STACK_TEXT:  
ffffc080`a5ada6b8 fffff801`54db5f2c : 00000000`00000050 ffffb08e`c6844cd3 00000000`00000010 ffffc080`a5ada950 : nt!KeBugCheckEx
ffffc080`a5ada6c0 fffff801`54ca16c6 : 00000000`00000010 ffffb08e`c6844cd3 ffffc080`a5ada950 ffffd102`9a834380 : nt!MiSystemFault+0x116a0c
ffffc080`a5ada760 fffff801`54d89d72 : 00000000`00000000 fffff801`550b6eec ffffd102`00000000 ffffb08e`acb55c00 : nt!MmAccessFault+0xae6
ffffc080`a5ada950 ffffb08e`c6844cd3 : 00000000`00000000 00000000`01787d01 00000000`00000283 fffff801`54d8b340 : nt!KiPageFault+0x132
ffffc080`a5adaae0 00000000`00000000 : 00000000`01787d01 00000000`00000283 fffff801`54d8b340 ffffd102`8bbfb080 : 0xffffb08e`c6844cd3


THREAD_SHA1_HASH_MOD_FUNC:  35852f70c1fb96d682b5bd0e931cc10c7b9fe1fe

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  3bd3af5941f6b0085cb4893ca316adf6d82d27bb

THREAD_SHA1_HASH_MOD:  d084f7dfa548ce4e51810e4fd5914176ebc66791

FOLLOWUP_IP: 
nt!MiSystemFault+116a0c
fffff801`54db5f2c cc              int     3

FAULT_INSTR_CODE:  d28548cc

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiSystemFault+116a0c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  59cdf43a

IMAGE_VERSION:  10.0.15063.674

STACK_COMMAND:  .thread ; .cxr ; kb

IMAGE_NAME:  memory_corruption

BUCKET_ID_FUNC_OFFSET:  116a0c

FAILURE_BUCKET_ID:  AV_INVALID_BAD_IP_nt!MiSystemFault

BUCKET_ID:  AV_INVALID_BAD_IP_nt!MiSystemFault

PRIMARY_PROBLEM_CLASS:  AV_INVALID_BAD_IP_nt!MiSystemFault

TARGET_TIME:  2017-10-24T16:00:37.000Z

OSBUILD:  15063

OSSERVICEPACK:  674

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-29 15:20:26

BUILDDATESTAMP_STR:  170317-1834

BUILDLAB_STR:  rs2_release

BUILDOSVER_STR:  10.0.15063.0.amd64fre.rs2_release.170317-1834

ANALYSIS_SESSION_ELAPSED_TIME:  153e

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:av_invalid_bad_ip_nt!misystemfault

FAILURE_ID_HASH:  {48ad9531-e3f8-1044-fc5f-d917677674c7}

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

最後更新：2017-10-25 02:03:29

  上一篇：go win10用係統自帶的備份係統，顯示備份失敗
  下一篇：go 微軟推送的更新導致我的電腦無法進入係統，重啟開機自動進入BIOS模式，最後一次進入係統的時候還出現了頻繁彈出wi