none
win10 RS3 16215版本,test HLK,在HLK client端安装网卡驱动之后,打开网络和共享中心查看链接状态会弹出The exception unknown software exception (0xc000000d)occurred in the application at location 0x00007FF8934F7030 RRS feed

  • 问题

  • 让HLK测项跑起来之后,测试DF部分测项fail之后会出现蓝屏问题BSOD,通过windbg tool查看memory.dmp及minidump下的dmp文件,可以看到是ntkrnlmp.exe导致的蓝屏,不知道是不是OS本身的问题。

    dump文件如下:

    Loading Dump File [E:\RS3_test\062017-22593-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available


    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 10 Kernel Version 16215 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 16215.1000.amd64fre.rs_prerelease.170603-1840
    Machine Name:
    Kernel base = 0xfffff801`d4489000 PsLoadedModuleList = 0xfffff801`d47e5b70
    Debug session time: Tue Jun 20 21:38:05.524 2017 (UTC - 7:00)
    System Uptime: 0 days 2:53:45.189
    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 A, {fffff801d4910c3c, 2, 8, fffff801d4910c3c}

    Probably caused by : ntkrnlmp.exe ( nt!NtSetInformationThread+168c )

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

    3: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: fffff801d4910c3c, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000008, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff801d4910c3c, address which referenced memory

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


    SYSTEM_SKU:  SKU

    SYSTEM_VERSION:  System Version

    BIOS_DATE:  11/05/2015

    BASEBOARD_PRODUCT:  B150-PRO

    BASEBOARD_VERSION:  Rev X.0x

    BUGCHECK_P1: fffff801d4910c3c

    BUGCHECK_P2: 2

    BUGCHECK_P3: 8

    BUGCHECK_P4: fffff801d4910c3c

    READ_ADDRESS: fffff801d487c378: Unable to get MiVisibleState
     fffff801d4910c3c 

    CURRENT_IRQL:  2

    FAULTING_IP: 
    nt!NtSetInformationThread+168c
    fffff801`d4910c3c 4989be78070000  mov     qword ptr [r14+778h],rdi

    IP_IN_PAGED_CODE: 
    nt!NtSetInformationThread+168c
    fffff801`d4910c3c 4989be78070000  mov     qword ptr [r14+778h],rdi

    CPU_COUNT: 4

    CPU_MHZ: c78

    CPU_VENDOR:  GenuineIntel

    CPU_FAMILY: 6

    CPU_MODEL: 5e

    CPU_STEPPING: 3

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

    BUGCHECK_STR:  AV

    PROCESS_NAME:  svchost.exe

    ANALYSIS_VERSION: 10.0.10240.9 x86fre

    STACK_COMMAND:  kb

    FOLLOWUP_IP: 
    nt!NtSetInformationThread+168c
    fffff801`d4910c3c 4989be78070000  mov     qword ptr [r14+778h],rdi

    SYMBOL_STACK_INDEX:  3

    SYMBOL_NAME:  nt!NtSetInformationThread+168c

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME:  ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP:  5933a904

    IMAGE_VERSION:  10.0.16215.1000

    BUCKET_ID_FUNC_OFFSET:  168c

    FAILURE_BUCKET_ID:  AV_VRF_CODE_AV_PAGED_IP_nt!NtSetInformationThread

    BUCKET_ID:  AV_VRF_CODE_AV_PAGED_IP_nt!NtSetInformationThread

    PRIMARY_PROBLEM_CLASS:  AV_VRF_CODE_AV_PAGED_IP_nt!NtSetInformationThread

    ANALYSIS_SOURCE:  KM

    FAILURE_ID_HASH_STRING:  km:av_vrf_code_av_paged_ip_nt!ntsetinformationthread

    FAILURE_ID_HASH:  {1a8d713a-fa5e-ce29-22cf-58c80383fa06}

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

    3: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: fffff801d4910c3c, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000008, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff801d4910c3c, address which referenced memory

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


    SYSTEM_SKU:  SKU

    SYSTEM_VERSION:  System Version

    BIOS_DATE:  11/05/2015

    BASEBOARD_PRODUCT:  B150-PRO

    BASEBOARD_VERSION:  Rev X.0x

    BUGCHECK_P1: fffff801d4910c3c

    BUGCHECK_P2: 2

    BUGCHECK_P3: 8

    BUGCHECK_P4: fffff801d4910c3c

    READ_ADDRESS: fffff801d487c378: Unable to get MiVisibleState
     fffff801d4910c3c 

    CURRENT_IRQL:  2

    FAULTING_IP: 
    nt!NtSetInformationThread+168c
    fffff801`d4910c3c 4989be78070000  mov     qword ptr [r14+778h],rdi

    IP_IN_PAGED_CODE: 
    nt!NtSetInformationThread+168c
    fffff801`d4910c3c 4989be78070000  mov     qword ptr [r14+778h],rdi

    CPU_COUNT: 4

    CPU_MHZ: c78

    CPU_VENDOR:  GenuineIntel

    CPU_FAMILY: 6

    CPU_MODEL: 5e

    CPU_STEPPING: 3

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

    BUGCHECK_STR:  AV

    PROCESS_NAME:  svchost.exe

    ANALYSIS_VERSION: 10.0.10240.9 x86fre

    TRAP_FRAME:  fffffd822cfc75c0 -- (.trap 0xfffffd822cfc75c0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000002 rbx=0000000000000000 rcx=0000000080000000
    rdx=0000000080000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff801d4910c3c rsp=fffffd822cfc7750 rbp=fffffd822cfc7a80
     r8=ffff9d0df2e63ca0  r9=0000000000000001 r10=fffff801d490f5b0
    r11=0000000000141290 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    nt!NtSetInformationThread+0x168c:
    fffff801`d4910c3c 4989be78070000  mov     qword ptr [r14+778h],rdi ds:00000000`00000778=????????????????
    Resetting default scope

    LAST_CONTROL_TRANSFER:  from fffff801d4618fe9 to fffff801d460d740

    FAILED_INSTRUCTION_ADDRESS: 
    nt!NtSetInformationThread+168c
    fffff801`d4910c3c 4989be78070000  mov     qword ptr [r14+778h],rdi



    STACK_COMMAND:  kb

    FOLLOWUP_IP: 
    nt!NtSetInformationThread+168c
    fffff801`d4910c3c 4989be78070000  mov     qword ptr [r14+778h],rdi

    SYMBOL_STACK_INDEX:  3

    SYMBOL_NAME:  nt!NtSetInformationThread+168c

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME:  ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP:  5933a904

    IMAGE_VERSION:  10.0.16215.1000

    BUCKET_ID_FUNC_OFFSET:  168c

    FAILURE_BUCKET_ID:  AV_VRF_CODE_AV_PAGED_IP_nt!NtSetInformationThread

    BUCKET_ID:  AV_VRF_CODE_AV_PAGED_IP_nt!NtSetInformationThread

    PRIMARY_PROBLEM_CLASS:  AV_VRF_CODE_AV_PAGED_IP_nt!NtSetInformationThread

    ANALYSIS_SOURCE:  KM

    FAILURE_ID_HASH_STRING:  km:av_vrf_code_av_paged_ip_nt!ntsetinformationthread

    FAILURE_ID_HASH:  {1a8d713a-fa5e-ce29-22cf-58c80383fa06}

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


    2017年6月22日 5:18

全部回复