none
HI,大佬们,最近经常遇到系统睡眠唤醒后蓝屏,不知道是什么问题,可以帮忙分析下吗? RRS feed

  • 问题

  • C:/Windows下有的Mini dump 和memory dump文件

    https://pan.baidu.com/s/16fLXSUARmDszX3bXicHb8Q


    Microsoft (R) Windows Debugger Version 10.0.18914.1001 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\081919-14609-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 18362 MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 18362.1.amd64fre.19h1_release.190318-1202 Machine Name: Kernel base = 0xfffff807`2ac00000 PsLoadedModuleList = 0xfffff807`2b046490 Debug session time: Mon Aug 19 15:15:15.533 2019 (UTC + 8:00) System Uptime: 1 days 9:57:11.407 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ .......... Loading User Symbols Loading unloaded module list ............. For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff807`2adbfcc0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffb801`219df0d0=000000000000007e 5: kd> !analyze -v ******************************************************************************* * * * 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: fffff8072ad3e841, The address that the exception occurred at Arg3: ffff9f0aad2f1ac8, Exception Record Address Arg4: ffffb801219df930, Context Record Address Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : AV.Fault Value: Read Key : Analysis.CPU.Sec Value: 14 Key : Analysis.Elapsed.Sec Value: 283 Key : Analysis.Memory.CommitPeak.Mb Value: 70 PROCESSES_ANALYSIS: 1 SERVICE_ANALYSIS: 1 STACKHASH_ANALYSIS: 1 TIMELINE_ANALYSIS: 1 DUMP_CLASS: 1 DUMP_QUALIFIER: 400 BUILD_VERSION_STRING: 18362.1.amd64fre.19h1_release.190318-1202 DUMP_TYPE: 2 BUGCHECK_P1: ffffffffc0000005 BUGCHECK_P2: fffff8072ad3e841 BUGCHECK_P3: ffff9f0aad2f1ac8 BUGCHECK_P4: ffffb801219df930 EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - 0x%p 0x%p %s FAULTING_IP: nt!MiDemoteCombinedPte+51 fffff807`2ad3e841 498378f001 cmp qword ptr [r8-10h],1 EXCEPTION_RECORD: ffff9f0aad2f1ac8 -- (.exr 0xffff9f0aad2f1ac8) ExceptionAddress: fffff8072ad3e841 (nt!MiDemoteCombinedPte+0x0000000000000051) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffff Attempt to read from address ffffffffffffffff CONTEXT: ffffb801219df930 -- (.cxr 0xffffb801219df930) rax=ffffb7dbedf6f000 rbx=0600010137ea9005 rcx=ffff8c81e9421580 rdx=ffffb7bffc876628 rsi=ffffb7bffc876628 rdi=ffff9f0aad2f2310 rip=fffff8072ad3e841 rsp=ffff9f0aad2f1d00 rbp=00007ff90ecc5000 r8=8000000000000000 r9=ffff8c81e941cba0 r10=0000000000000000 r11=ffffb78000000000 r12=0000000000000000 r13=ffff9f0aad2f2410 r14=8000000000000000 r15=ffff8c81e9421580 iopl=0 nv up ei ng nz na po cy cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010287 nt!MiDemoteCombinedPte+0x51: fffff807`2ad3e841 498378f001 cmp qword ptr [r8-10h],1 ds:002b:7fffffff`fffffff0=???????????????? Resetting default scope CPU_COUNT: 8 CPU_MHZ: cdc CPU_VENDOR: GenuineIntel CPU_FAMILY: 6 CPU_MODEL: 3c CPU_STEPPING: 3 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT PROCESS_NAME: svchost.exe CURRENT_IRQL: 2 FOLLOWUP_IP: nt!MiDemoteCombinedPte+51 fffff807`2ad3e841 498378f001 cmp qword ptr [r8-10h],1 BUGCHECK_STR: AV READ_ADDRESS: fffff8072b1713b8: Unable to get MiVisibleState Unable to get NonPagedPoolStart Unable to get NonPagedPoolEnd Unable to get PagedPoolStart Unable to get PagedPoolEnd unable to get nt!MmSpecialPagesInUse ffffffffffffffff ERROR_CODE: (NTSTATUS) 0xc0000005 - 0x%p 0x%p %s EXCEPTION_CODE_STR: c0000005 EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: ffffffffffffffff ANALYSIS_SESSION_HOST: ANALYSIS_SESSION_TIME: 08-19-2019 16:43:48.0357 ANALYSIS_VERSION: 10.0.18914.1001 amd64fre BAD_STACK_POINTER: ffffb801219df0c8 LAST_CONTROL_TRANSFER: from fffff8072acb0087 to fffff8072ad3e841 STACK_TEXT: ffff9f0a`ad2f1d00 fffff807`2acb0087 : 00000000`00000000 ffffb7bf`fc876620 00000000`00000002 00000000`dba333c1 : nt!MiDemoteCombinedPte+0x51 ffff9f0a`ad2f1dd0 fffff807`2acac837 : ffff8c81`e9421580 ffff9f0a`ad2f2410 00000000`00000000 00000000`00000000 : nt!MiAgePte+0x427 ffff9f0a`ad2f1e70 fffff807`2acaccf1 : ffff9f0a`ad2f2410 ffff9f0a`ad2f2410 ffff8c81`00000000 ffffb7db`dffe43b0 : nt!MiWalkPageTablesRecursively+0x1e7 ffff9f0a`ad2f1f30 fffff807`2acaccf1 : ffff9f0a`ad2f2410 ffff9f0a`ad2f2410 ffff8c81`00000000 ffffb7db`edefff20 : nt!MiWalkPageTablesRecursively+0x6a1 ffff9f0a`ad2f1ff0 fffff807`2acaccf1 : ffff9f0a`ad2f2410 ffff9f0a`ad2f2410 ffff8c81`00000000 ffffb7db`edf6f7f8 : nt!MiWalkPageTablesRecursively+0x6a1 ffff9f0a`ad2f20b0 fffff807`2acac47c : ffff9f0a`ad2f2410 fffff2b5`827cb007 00000000`00000000 00000000`00000000 : nt!MiWalkPageTablesRecursively+0x6a1 ffff9f0a`ad2f2170 fffff807`2acabf07 : ffff9f0a`ad2f2410 ffff9f0a`00000002 00000000`00000002 00000000`00000000 : nt!MiWalkPageTables+0x36c ffff9f0a`ad2f2270 fffff807`2acab642 : ffff8c81`e937c080 fffff807`00000000 00000000`00aae56c 00000000`00000000 : nt!MiAgeWorkingSet+0x3a7 ffff9f0a`ad2f2790 fffff807`2acaaf5a : ffff8c81`e9421580 ffff9f0a`ad2f2a50 00000000`00000000 00000000`00000000 : nt!MiTrimOrAgeWorkingSet+0x3b2 ffff9f0a`ad2f2880 fffff807`2aca8bb0 : fffff807`2b068340 00000000`00000000 fffff807`2b068340 ffff8c81`e1c3f2b0 : nt!MiProcessWorkingSets+0x1fa ffff9f0a`ad2f2a30 fffff807`2aec8ed6 : 00000000`00000001 00000000`00000006 00000000`ffffffff 00000000`00000001 : nt!MiWorkingSetManager+0xc8 ffff9f0a`ad2f2af0 fffff807`2ad89e65 : 00000000`00000006 00000000`ffffffff fffff807`2b068340 00000000`000001e6 : nt!MmWorkingSetManager+0x12 ffff9f0a`ad2f2b20 fffff807`2ad29e95 : ffff8c81`e1d02080 00000000`00000080 fffff807`2ad89d10 00000000`00000000 : nt!KeBalanceSetManager+0x155 ffff9f0a`ad2f2c10 fffff807`2adc730a : ffffb801`217a4180 ffff8c81`e1d02080 fffff807`2ad29e40 00000000`00000000 : nt!PspSystemThreadStartup+0x55 ffff9f0a`ad2f2c60 00000000`00000000 : ffff9f0a`ad2f3000 ffff9f0a`ad2ed000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x2a THREAD_SHA1_HASH_MOD_FUNC: b7db9ad0a77622195141f6732227a097c9448076 THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 3dfbe6ca4b6bd95f0428b02d52d5e28fad8ead5a THREAD_SHA1_HASH_MOD: 38bc5fec3f0409c265cf5c87da6f8f8859d0711c FAULT_INSTR_CODE: f0788349 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!MiDemoteCombinedPte+51 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 35707659 IMAGE_VERSION: 10.0.18362.295 STACK_COMMAND: .cxr 0xffffb801219df930 ; kb IMAGE_NAME: memory_corruption BUCKET_ID_FUNC_OFFSET: 51 FAILURE_BUCKET_ID: AV_STACKPTR_ERROR_nt!MiDemoteCombinedPte BUCKET_ID: AV_STACKPTR_ERROR_nt!MiDemoteCombinedPte PRIMARY_PROBLEM_CLASS: AV_STACKPTR_ERROR_nt!MiDemoteCombinedPte TARGET_TIME: 2019-08-19T07:15:15.000Z OSBUILD: 18362 OSSERVICEPACK: 295 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: 1998-05-31 05:12:57 BUILDDATESTAMP_STR: 190318-1202 BUILDLAB_STR: 19h1_release BUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202 ANALYSIS_SESSION_ELAPSED_TIME: 45425 ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:av_stackptr_error_nt!midemotecombinedpte FAILURE_ID_HASH: {51bd6656-a4b2-8d9b-1231-94678dd83b3a} Followup: MachineOwner ---------


    2019年8月19日 9:02

全部回复

  • 从日志来看是SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M导致的报1000007e的蓝屏,我猜测像是是第三方驱动导致的。

    https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x1000007e--system-thread-exception-not-handled-m

    2019年8月19日 9:17
  • 你好,

    根据您提供的这个蓝屏日志分析结果,没有记录相关的文件信息。

    请再查看一下C:/Windows下有的Mini dump 和memory dump文件,然后将它上传到One drive或者类似百度云盘的云共享上。

    在回复中附上下载链接,方便进行下载分析。

    希望对您有帮助,如果回答是有帮助的, 请将其标记为答案, 可以帮助其他有相同问题的社区成员, 并快速找到有用的答复。


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

    2019年8月20日 7:45
  • 谢谢回复,那个memory文件有1.8G,这么大。

    百度云链接在这:https://pan.baidu.com/s/16fLXSUARmDszX3bXicHb8Q

    • 已标记为答案 嘟嘟嘟 2019年8月21日 12:42
    • 取消答案标记 嘟嘟嘟 2019年8月21日 12:42
    2019年8月20日 9:19
  • 谢谢回复,我之前在百度上搜出来也是这个第三方驱动问题,大多都是Realtek这个声卡驱动引起的,于是我卸载了这个驱动,但还是有蓝屏现象,不知道是不是我没卸载干净。
    2019年8月20日 9:22