none
Windows 10蓝屏(在插/拨TYPE-C接口的DOCK时) RRS feed

  • 问题

  • 我在插/拨Type-C接口的Dock时,PC经常发生蓝屏(Win10 1803)。

    Dock上带有1个Type-C电源输入、Type-C输出、1个以太网卡、2个USB、1个VGA。平时插着网线、外接显示器。

    我换过其它厂家Type-C接口的Dock,在插/拔时,也偶尔会发生蓝屏。

    我使用了WinDbg Preview工具,分析了最近两次Mini Dump文件,都发现ntkrnlmp.exe相关报错信息。

    请帮助分析下原因。

    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck E6, {26, ffffcb05df2d1060, 31, 6}
    
    *** WARNING: Unable to verify checksum for win32k.sys
    Probably caused by : ntkrnlmp.exe ( nt!KiCallInterruptServiceRoutine+a5 )
    
    Followup:     MachineOwner
    ---------
    
    nt!KeBugCheckEx:
    fffff800`2a5b6380 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff800`2c682ed0=00000000000000e6

    详细信息,如下:

    Microsoft (R) Windows Debugger Version 10.0.18239.1000 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\xxxxxx\Desktop\102218-37921-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 (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 17134.1.amd64fre.rs4_release.180410-1804
    Machine Name:
    Kernel base = 0xfffff800`2a40d000 PsLoadedModuleList = 0xfffff800`2a7bb210
    Debug session time: Mon Oct 22 11:29:45.463 2018 (UTC + 8:00)
    System Uptime: 0 days 1:29:30.986
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ................................................................
    .....................
    Loading User Symbols
    Loading unloaded module list
    ................
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck E6, {26, ffffcb05df2d1060, 31, 6}
    
    *** WARNING: Unable to verify checksum for win32k.sys
    Probably caused by : ntkrnlmp.exe ( nt!KiCallInterruptServiceRoutine+a5 )
    
    Followup:     MachineOwner
    ---------
    
    nt!KeBugCheckEx:
    fffff800`2a5b6380 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff800`2c682ed0=00000000000000e6
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_VERIFIER_DMA_VIOLATION (e6)
    An illegal DMA operation was attempted by a driver being verified.
    Arguments:
    Arg1: 0000000000000026, IOMMU detected DMA violation.
    Arg2: ffffcb05df2d1060, Device Object of faulting device.
    Arg3: 0000000000000031, Faulting information (usually faulting physical address).
    Arg4: 0000000000000006, Fault type (hardware specific).
    
    Debugging Details:
    ------------------
    
    
    KEY_VALUES_STRING: 1
    
    
    STACKHASH_ANALYSIS: 1
    
    TIMELINE_ANALYSIS: 1
    
    
    DUMP_CLASS: 1
    
    DUMP_QUALIFIER: 400
    
    BUILD_VERSION_STRING:  17134.1.amd64fre.rs4_release.180410-1804
    
    SYSTEM_MANUFACTURER:  TOSHIBA
    
    SYSTEM_PRODUCT_NAME:  PORTEGE X30-E
    
    SYSTEM_SKU:  PT282E
    
    SYSTEM_VERSION:  PT282E-00G003GR
    
    BIOS_VENDOR:  TOSHIBA
    
    BIOS_VERSION:  Version 1.30  
    
    BIOS_DATE:  01/05/2018
    
    BASEBOARD_MANUFACTURER:  TOSHIBA
    
    BASEBOARD_PRODUCT:  20 PCBA 3
    
    BASEBOARD_VERSION:  Version A0
    
    DUMP_TYPE:  2
    
    BUGCHECK_P1: 26
    
    BUGCHECK_P2: ffffcb05df2d1060
    
    BUGCHECK_P3: 31
    
    BUGCHECK_P4: 6
    
    CPU_COUNT: 8
    
    CPU_MHZ: 708
    
    CPU_VENDOR:  GenuineIntel
    
    CPU_FAMILY: 6
    
    CPU_MODEL: 8e
    
    CPU_STEPPING: a
    
    CPU_MICROCODE: 6,8e,a,0 (F,M,S,R)  SIG: 84'00000000 (cache) 84'00000000 (init)
    
    BLACKBOXBSD: 1 (!blackboxbsd)
    
    
    BLACKBOXPNP: 1 (!blackboxpnp)
    
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    BUGCHECK_STR:  0xE6
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  c
    
    ANALYSIS_SESSION_HOST:  <主机名 略>
    ANALYSIS_SESSION_TIME:  10-22-2018 14:18:17.0228
    
    ANALYSIS_VERSION: 10.0.18239.1000 amd64fre
    
    LAST_CONTROL_TRANSFER:  from fffff8002ad9c48b to fffff8002a5b6380
    
    STACK_TEXT:  
    fffff800`2c682ec8 fffff800`2ad9c48b : 00000000`000000e6 00000000`00000026 ffffcb05`df2d1060 00000000`00000031 : nt!KeBugCheckEx
    fffff800`2c682ed0 fffff800`2ad98fdc : fffff800`2adbff40 fffff800`2adbff40 fffff800`2adc2e00 00000000`00000001 : hal!IvtHandleInterrupt+0x1ab
    fffff800`2c682f20 fffff800`2a539d85 : fffff800`2adc2db0 fffff800`2c673a50 fffff800`2adc2e60 00000000`0000000c : hal!HalpIommuInterruptRoutine+0x4c
    fffff800`2c682f50 fffff800`2a5b7b1c : fffff800`2c673a50 fffff800`2adc2db0 00000000`00000424 ffffcb05`dd293040 : nt!KiCallInterruptServiceRoutine+0xa5
    fffff800`2c682f90 fffff800`2a5b7ed7 : ffffcb05`ed7e2000 00000000`00000002 fffff800`2c673b00 00000000`00000001 : nt!KiInterruptSubDispatchNoLock+0x10c
    fffff800`2c6739d0 fffff800`2a5b9a92 : 00000000`00000000 fffff800`29004180 fffff800`2a877400 ffffcb05`de3ab040 : nt!KiInterruptDispatchNoLock+0x37
    fffff800`2c673b60 00000000`00000000 : fffff800`2c674000 fffff800`2c66d000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x32
    
    
    THREAD_SHA1_HASH_MOD_FUNC:  0cfc1e867edaaf1fd57f2eadb5ab73d7c233a354
    
    THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  d58d1d1f150f91190ce276247572346681cbdb18
    
    THREAD_SHA1_HASH_MOD:  782650af79f96574cdba6be2f36ad0d2d7924552
    
    FOLLOWUP_IP: 
    nt!KiCallInterruptServiceRoutine+a5
    fffff800`2a539d85 0fb6e8          movzx   ebp,al
    
    FAULT_INSTR_CODE:  45e8b60f
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  nt!KiCallInterruptServiceRoutine+a5
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  5b9c6be1
    
    IMAGE_VERSION:  10.0.17134.286
    
    STACK_COMMAND:  .thread ; .cxr ; kb
    
    BUCKET_ID_FUNC_OFFSET:  a5
    
    FAILURE_BUCKET_ID:  0xE6_nt!KiCallInterruptServiceRoutine
    
    BUCKET_ID:  0xE6_nt!KiCallInterruptServiceRoutine
    
    PRIMARY_PROBLEM_CLASS:  0xE6_nt!KiCallInterruptServiceRoutine
    
    TARGET_TIME:  2018-10-22T03:29:45.000Z
    
    OSBUILD:  17134
    
    OSSERVICEPACK:  286
    
    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:  2018-09-15 10:18:09
    
    BUILDDATESTAMP_STR:  180410-1804
    
    BUILDLAB_STR:  rs4_release
    
    BUILDOSVER_STR:  10.0.17134.1.amd64fre.rs4_release.180410-1804
    
    ANALYSIS_SESSION_ELAPSED_TIME:  14fa
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:0xe6_nt!kicallinterruptserviceroutine
    
    FAILURE_ID_HASH:  {2b0e63ba-aae0-93ee-5379-fdfd15c60138}
    
    Followup:     MachineOwner
    ---------
    
    


    • 已编辑 Xuejun Liao 2018年10月22日 6:34 标题更正
    2018年10月22日 6:33

全部回复

  • 您好,

    请测试一下安全模式和干净模式的环境下是否仍旧存在此问题。

    其次请将minidump( C:\Windows\) 文件以及相同路径下的memory.dmp文件上传至网盘,然后将链接贴在这里以便分析。

    感谢您的配合。 


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

    • 已编辑 Joy-Qiao 2018年10月23日 7:36
    2018年10月23日 7:35