登录
Microsoft.com
 
Microsoft
 
 
 

none
windows 10 蓝屏重启之后开机进入系统自动修复，而且自动修复无法完成，DUMP日志请大神帮忙分析下 RRS feed

 > 

  • 问题

  • Question
    登录进行投票
    0
    登录进行投票 
    Microsoft (R) Windows Debugger Version 10.0.18914.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Windows\Minidump\072119-20250-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 17134 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff800`db8a5000 PsLoadedModuleList = 0xfffff800`dbc52170
Debug session time: Sun Jul 21 09:02:28.257 2019 (UTC + 8:00)
System Uptime: 4 days 17:46:53.020
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
..................................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800`dba4fab0 48894c2408      mov     qword ptr [rsp+8],rcx ss:fffff08b`4b179340=0000000000000050
3: 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: ffffa602537a5344, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff800db8c3d53, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 000000000000000c, (reserved)

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


Could not read faulting driver name

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 4

    Key  : Analysis.Elapsed.Sec
    Value: 4

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 68


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  10.0.17134.885 (WinBuild.160101.0800)

SYSTEM_MANUFACTURER:  ASUSTeK COMPUTER INC.

SYSTEM_PRODUCT_NAME:  X550VC

SYSTEM_SKU:  ASUS-NotebookSKU

SYSTEM_VERSION:  1.0       

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  X550VC.213

BIOS_DATE:  06/26/2013

BASEBOARD_MANUFACTURER:  ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT:  X550VC

BASEBOARD_VERSION:  1.0       

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

DUMP_TYPE:  2

BUGCHECK_P1: ffffa602537a5344

BUGCHECK_P2: 0

BUGCHECK_P3: fffff800db8c3d53

BUGCHECK_P4: c

READ_ADDRESS: fffff800dbcf1388: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
 ffffa602537a5344 

FAULTING_IP: 
nt!B_TREE<unsigned long,ST_STORE<SM_TRAITS>::_ST_HASH_ENTRY,4096,NP_CONTEXT,ST_STORE<SM_TRAITS>::ST_HASH_ENTRY_COMPARATOR>::BTreeNodeFindKey+d3
fffff800`db8c3d53 448b442808      mov     r8d,dword ptr [rax+rbp+8]

MM_INTERNAL_CODE:  c

CPU_COUNT: 4

CPU_MHZ: 95b

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3a

CPU_STEPPING: 9

CPU_MICROCODE: 6,3a,9,0 (F,M,S,R)  SIG: 20'00000000 (cache) 20'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  AV

PROCESS_NAME:  MemCompression

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  DESKTOP-46TLFN1

ANALYSIS_SESSION_TIME:  07-21-2019 15:59:54.0269

ANALYSIS_VERSION: 10.0.18914.1001 amd64fre

TRAP_FRAME:  fffff08b4b1795f0 -- (.trap 0xfffff08b4b1795f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffa602537a5324 rbx=0000000000000000 rcx=ffffa602acefe9f0
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800db8c3d53 rsp=fffff08b4b179780 rbp=0000000000000018
 r8=00000000000001e8  r9=0000000000000000 r10=0000000000000299
r11=000000000009e843 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!B_TREE<unsigned long,ST_STORE<SM_TRAITS>::_ST_HASH_ENTRY,4096,NP_CONTEXT,ST_STORE<SM_TRAITS>::ST_HASH_ENTRY_COMPARATOR>::BTreeNodeFindKey+0xd3:
fffff800`db8c3d53 448b442808      mov     r8d,dword ptr [rax+rbp+8] ds:ffffa602`537a5344=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800db98f439 to fffff800dba4fab0

STACK_TEXT:  
fffff08b`4b179338 fffff800`db98f439 : 00000000`00000050 ffffa602`537a5344 00000000`00000000 fffff08b`4b1795f0 : nt!KeBugCheckEx
fffff08b`4b179340 fffff800`db987018 : 00000000`00000000 00000000`00000000 ffff8000`00000000 fffffbfd`feff7fb8 : nt!MiSystemFault+0xcf9
fffff08b`4b179480 fffff800`dba5d1e0 : ffff9481`60a63180 00000000`00000009 00000000`000001ff ffffa602`aa656050 : nt!MmAccessFault+0x1f8
fffff08b`4b1795f0 fffff800`db8c3d53 : 00000000`000000d6 ffffa602`aa6560d0 00000000`000000d5 00000000`000000d4 : nt!KiPageFault+0x320
fffff08b`4b179780 fffff800`db8c3bab : 00000000`00000200 ffffa602`0000000c ffffa602`00000200 00000000`00000000 : nt!B_TREE<unsigned long,ST_STORE<SM_TRAITS>::_ST_HASH_ENTRY,4096,NP_CONTEXT,ST_STORE<SM_TRAITS>::ST_HASH_ENTRY_COMPARATOR>::BTreeNodeFindKey+0xd3
fffff08b`4b1797e0 fffff800`db8c5305 : ffffa602`a5919008 fffff08b`4b179860 ffffa602`a5919010 00000000`00000001 : nt!B_TREE<unsigned long,ST_STORE<SM_TRAITS>::_ST_HASH_ENTRY,4096,NP_CONTEXT,ST_STORE<SM_TRAITS>::ST_HASH_ENTRY_COMPARATOR>::BTreeSearchKey+0x6f
fffff08b`4b179830 fffff800`db8c5096 : ffffa602`a5919000 ffffa602`aa6560a8 ffffa602`aa656050 00000000`00000000 : nt!ST_STORE<SM_TRAITS>::StDmCombineBufferAddEntry+0xfd
fffff08b`4b179900 fffff800`db8c4e94 : ffffa602`a5919000 ffffa602`aa656050 00000000`00000005 ffffa602`aa656580 : nt!ST_STORE<SM_TRAITS>::StDmCombineRegion+0x156
fffff08b`4b179960 fffff800`db8c314b : 00000000`00000000 fffff08b`4b179a09 ffffa602`aa656050 ffffa602`aa656050 : nt!ST_STORE<SM_TRAITS>::StDmpSinglePageFindSpace+0x9c
fffff08b`4b179990 fffff800`db8c24fa : ffffa602`b7d38000 00000000`00000282 ffffa602`a59a2100 ffff9481`60a63180 : nt!ST_STORE<SM_TRAITS>::StDmpSinglePageAdd+0x7f
fffff08b`4b179a70 fffff800`db8c2100 : 00000000`00000000 00000000`00000f45 00000000`000000f5 ffffa602`b7d38000 : nt!ST_STORE<SM_TRAITS>::StDmPageAdd+0x8e
fffff08b`4b179ad0 fffff800`db8c1875 : ffffa602`aa653700 fffff08b`4b179b98 00000000`00000001 ffffa602`aa656000 : nt!ST_STORE<SM_TRAITS>::StWorkItemProcess+0x68
fffff08b`4b179b20 fffff800`db8ca201 : 00000000`00000000 fffff800`00000000 ffffa602`00000000 00000000`00000000 : nt!SMKM_STORE<SM_TRAITS>::SmStWorker+0x2f9
fffff08b`4b179be0 fffff800`db8c9e27 : ffffa602`aa656000 fffff800`db8ca1f0 ffff9481`60d45180 00000004`bd9bbfff : nt!SMKM_STORE<SM_TRAITS>::SmStWorkerThread+0x11
fffff08b`4b179c10 fffff800`dba56f66 : ffff9481`60d45180 ffffa602`aa653700 fffff800`db8c9de0 0004c2c9`08458b10 : nt!PspSystemThreadStartup+0x47
fffff08b`4b179c60 00000000`00000000 : fffff08b`4b17a000 fffff08b`4b174000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


THREAD_SHA1_HASH_MOD_FUNC:  0c2accf13ecc86200390b839df313fce1e230c35

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  d2676fd52a648625862be01b1f56e91399ea5cf7

THREAD_SHA1_HASH_MOD:  9eef8c7ca0ce66f8b8b34848179f303828cff762

FOLLOWUP_IP: 
nt!B_TREE<unsigned long,ST_STORE<SM_TRAITS>::_ST_HASH_ENTRY,4096,NP_CONTEXT,ST_STORE<SM_TRAITS>::ST_HASH_ENTRY_COMPARATOR>::BTreeNodeFindKey+d3
fffff800`db8c3d53 448b442808      mov     r8d,dword ptr [rax+rbp+8]

FAULT_INSTR_CODE:  28448b44

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nt!B_TREE<unsigned long,ST_STORE<SM_TRAITS>::_ST_HASH_ENTRY,4096,NP_CONTEXT,ST_STORE<SM_TRAITS>::ST_HASH_ENTRY_COMPARATOR>::BTreeNodeFindKey+d3

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  5d1d7f6c

IMAGE_VERSION:  10.0.17134.885

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  d3

FAILURE_BUCKET_ID:  AV_R_INVALID_nt!B_TREE_unsigned_long,ST_STORE_SM_TRAITS_::_ST_HASH_ENTRY,4096,NP_CONTEXT,ST_STORE_SM_TRAITS_::ST_HASH_ENTRY_COMPARATOR_::BTreeNodeFindKey

BUCKET_ID:  AV_R_INVALID_nt!B_TREE_unsigned_long,ST_STORE_SM_TRAITS_::_ST_HASH_ENTRY,4096,NP_CONTEXT,ST_STORE_SM_TRAITS_::ST_HASH_ENTRY_COMPARATOR_::BTreeNodeFindKey

PRIMARY_PROBLEM_CLASS:  AV_R_INVALID_nt!B_TREE_unsigned_long,ST_STORE_SM_TRAITS_::_ST_HASH_ENTRY,4096,NP_CONTEXT,ST_STORE_SM_TRAITS_::ST_HASH_ENTRY_COMPARATOR_::BTreeNodeFindKey

TARGET_TIME:  2019-07-21T01:02:28.000Z

OSBUILD:  17134

OSSERVICEPACK:  885

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:  2019-07-04 12:24:12

BUILDDATESTAMP_STR:  160101.0800

BUILDLAB_STR:  WinBuild

BUILDOSVER_STR:  10.0.17134.885

ANALYSIS_SESSION_ELAPSED_TIME:  10bc

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:av_r_invalid_nt!b_tree_unsigned_long,st_store_sm_traits_::_st_hash_entry,4096,np_context,st_store_sm_traits_::st_hash_entry_comparator_::btreenodefindkey

FAILURE_ID_HASH:  {67e44e78-94c1-69c2-0506-931d114b5625}

Followup:     MachineOwner
---------
    2019年7月21日 8:27
    |

全部回复

  • Question
    登录进行投票
    0
    登录进行投票

    您好，

    请问问题发生前，是否做过任何更改？

    PAGE_FAULT_IN_NONPAGED_AREA (50)表示已引用无效的系统内存。 通常的内存地址是错误或内存地址指向已释放内存。

    它可能由错误系统服务或有故障的驱动程序代码的安装引起。 防病毒软件也会触发此错误，如可能已损坏的 NTFS 卷。
    它还可能会出现后安装的硬件故障或发生故障情况下安装的硬件 （通常与有缺陷的 RAM，是其主内存、 RAM L2 缓存或vedio RAM）。

    1. 检查事件查看器中的系统日志可能会帮助找出设备或导致错误的驱动程序的其他错误消息。

    2. 干净启动，禁用所有三方服务：

    https://support.microsoft.com/zh-cn/help/929135/how-to-perform-a-clean-boot-in-windows

    3. 运行Chkdsk /f /r以检测和修复磁盘错误。 系统分区上的磁盘扫描开始之前，必须重新启动系统。 请联系硬驱动程序系统查找任何诊断工具，它们为硬盘驱动器子系统提供的生产。

    另外，请您理解从我们论坛的角度来说，我们不支持Dump的分析，如果您的问题很紧急，或者已经对您的生产环境造成了影响，我这边建议您向微软开启案列以寻求进一步的帮助。

    感谢您的理解！

    Best regards,

    Yilia 

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    2019年7月22日 6:24
    |
    版主