none
BSoD :: storport.sys with WDK sample code "storahci.sys" (Win10 Ver 1803) RRS feed

  • Question

  • Hi ,

    I have BSoD Problem on storport.sys . 

    I am modifying storahci.sys to improve performance .
    storahci.sys source codes have been imported from the follows .

    WDK Sample Code  URL ::
         https://github.com/Microsoft/Windows-driver-samples/tree/master/storage/miniports/storahci

    Build Environment : 
      WDK for Windows 10 Ver 1803
      Visual Studio 2017 


    Under the Prior to Windows 10 Ver 1803 (i.e Ver 1709 Ver 1703 etc ...)

       Mini port driver "storahci.sys" Driver ver 10.0.17134.1 .  : No BSOD happened .

       Mini port driver "storahci.sys" Driver  WDK sample code.  : No BSOD happened .


    Under Windows 10 Ver 1803 :

       Mini port driver "storahci.sys" Driver ver 10.0.17134.1 . : No BSOD happened .

       Mini port driver "storahci.sys" Driver  WDK sample code. : BSOD happened in storport.sys .

     

    I am a PCIe Device developer who is currently working for modifying "storahci.sys" to improve the performance.

    I wish I could have the WDK latest sample code of "storahci". I’d really appreciate it if you could give me some ideas how I can have it.


    When does the BSOD occur?

     1. Turn on the PC and log-on the windows.
     2. No action for 2-5 minutes,( means just leaves the PC without any actions.)
     3. BSOD happens.
     It happens every single time.


    This is storport.sys bug , I think .
    However , I can not wait to fix this problem .
    So I need latest sample code "storahci.sys" .


    Best Regards,


    The following is complete windbg log by using command "analyze -v"

    *****  Log Information    ***********************************


    Symbol search path is: srv*
    Executable search path is: 
    Windows 10 Kernel Version 17134 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 17134.1.amd64fre.rs4_release.180410-1804
    Machine Name:
    Kernel base = 0xfffff803`bb8a5000 PsLoadedModuleList = 0xfffff803`bbc5f1f0
    Debug session time: Fri Jul 20 19:37:46.898 2018 (UTC + 9:00)
    System Uptime: 0 days 0:11:00.612
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .........................................
    Loading User Symbols

    Loading unloaded module list
    .......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1E, {ffffffffc0000094, fffff80b1678791e, 0, 0}

    Probably caused by : storport.sys ( storport!StorpTelemetrySendAdaptiveIdleCounters+159e2 )

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






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

    KMODE_EXCEPTION_NOT_HANDLED (1e)
    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.
    Arguments:
    Arg1: ffffffffc0000094, The exception code that was not handled
    Arg2: fffff80b1678791e, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: 0000000000000000, Parameter 1 of the exception

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


    KEY_VALUES_STRING: 1


    TIMELINE_ANALYSIS: 1


    DUMP_CLASS: 1

    DUMP_QUALIFIER: 401

    BUILD_VERSION_STRING:  17134.1.amd64fre.rs4_release.180410-1804

    SYSTEM_PRODUCT_NAME:  To Be Filled By O.E.M.

    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:  P1.50

    BIOS_DATE:  11/28/2017

    BASEBOARD_MANUFACTURER:  ASRock

    BASEBOARD_PRODUCT:  Z370 Pro4

    BASEBOARD_VERSION:                        

    DUMP_TYPE:  1

    BUGCHECK_P1: ffffffffc0000094

    BUGCHECK_P2: fffff80b1678791e

    BUGCHECK_P3: 0

    BUGCHECK_P4: 0

    EXCEPTION_CODE: (NTSTATUS) 0xc0000094 - <Unable to get error code text>

    FAULTING_IP: 
    storport!StorpTelemetrySendAdaptiveIdleCounters+159e2
    fffff80b`1678791e 49f7f1          div     rax,r9

    BUGCHECK_STR:  0x1E_c0000094

    CPU_COUNT: 4

    CPU_MHZ: e10

    CPU_VENDOR:  GenuineIntel

    CPU_FAMILY: 6

    CPU_MODEL: 9e

    CPU_STEPPING: b

    CPU_MICROCODE: 6,9e,b,0 (F,M,S,R)  SIG: 72'00000000 (cache) 72'00000000 (init)

    BLACKBOXBSD: 1 (!blackboxbsd)


    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

    PROCESS_NAME:  System

    CURRENT_IRQL:  2

    ANALYSIS_SESSION_HOST:  PC

    ANALYSIS_SESSION_TIME:  07-24-2018 17:44:51.0389

    ANALYSIS_VERSION: 10.0.17134.1 amd64fre

    EXCEPTION_RECORD:  0000000000000081 -- (.exr 0x81)
    Cannot read Exception record @ 0000000000000081

    TRAP_FRAME:  fffff803bdc6b270 -- (.trap 0xfffff803bdc6b270)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    Unable to get program counter
    rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff803ba889180 rsp=fffff803bdc6b5b0 rbp=0000000000000000
     r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up di pl nz na po cy
    b500:9180 ??              ???
    Resetting default scope

    IP_IN_FREE_BLOCK: 0

    LAST_CONTROL_TRANSFER:  from fffff803bbaf096a to fffff803bba3d330

    STACK_TEXT:  
    fffff803`bdc6a438 fffff803`bbaf096a : 00000000`0000001e ffffffff`c0000094 fffff80b`1678791e 00000000`00000000 : nt!KeBugCheckEx
    fffff803`bdc6a440 fffff803`bba45c0d : fffff803`bbca2000 fffff803`bb8a5000 00059628`00961000 ffff800c`205e7d60 : nt!KiFatalExceptionHandler+0x22
    fffff803`bdc6a480 fffff803`bb8fcae6 : fffff803`bdc6a5b0 fffff803`bdc6aa70 00000000`00000000 fffff803`bdc6b388 : nt!RtlpExecuteHandlerForException+0xd
    fffff803`bdc6a4b0 fffff803`bb8fdf03 : fffff803`bdc6b388 fffff803`bdc6b0d0 fffff803`bdc6b388 00000000`00000000 : nt!RtlDispatchException+0x416
    fffff803`bdc6aba0 fffff803`bba4df42 : 00000000`00000081 00000000`00000000 fffff803`bdc6b270 00000000`00000000 : nt!KiDispatchException+0x1f3
    fffff803`bdc6b250 fffff803`bba479c6 : ffff800c`00000000 00000000`00000010 ffff800c`1c6b7248 00000000`00000012 : nt!KiExceptionDispatch+0xc2
    fffff803`bdc6b430 fffff80b`1678791e : fffff803`ba889180 fffff803`bb935c4f ffff800c`1cbe41b0 00000000`00000000 : nt!KiDivideErrorFault+0x2c6
    fffff803`bdc6b5c0 fffff80b`16774eaf : fffff80b`167c6300 ffff800c`1cb074d0 00000000`00000008 ffff800c`21ceb740 : storport!StorpTelemetrySendAdaptiveIdleCounters+0x159e2
    fffff803`bdc6b740 fffff80b`16774cd5 : fffff80b`167c6300 ffff800c`1d3211e0 00000000`00000730 ffff800c`1d614a80 : storport!StorpLogPerUnitStatistics+0xd3
    fffff803`bdc6b770 fffff80b`16773f7a : 00000000`00000008 fffff803`ba880000 ffff800c`1cbc7a80 fffff80b`167c6300 : storport!StorpLogStatistics+0x7d
    fffff803`bdc6b820 fffff803`bb93fa39 : 00000000`00000004 00000001`89c17b00 fffff80b`167c6300 00000000`00000000 : storport!StorpTraceLoggingTelemetryTimerDpcRoutine+0xfa
    fffff803`bdc6b860 fffff803`bb93e937 : 00000000`0000000a 00000000`00000000 00000000`0035a4e9 00000000`00000019 : nt!KiProcessExpiredTimerList+0x159
    fffff803`bdc6b950 fffff803`bba40a8a : 00000000`00000000 fffff803`ba889180 00000000`001a6570 fffff803`bbd1c400 : nt!KiRetireDpcList+0x4c7
    fffff803`bdc6bb60 00000000`00000000 : fffff803`bdc6c000 fffff803`bdc65000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


    THREAD_SHA1_HASH_MOD_FUNC:  d960603e5efc5bed98637271972cc11e49401c6c

    THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  084729e1a78f1e08d7a89109e11fd7362722ee69

    THREAD_SHA1_HASH_MOD:  3dd37e6d3112bcceca0e26af84ced24b33dbc0b7

    FOLLOWUP_IP: 
    storport!StorpTelemetrySendAdaptiveIdleCounters+159e2
    fffff80b`1678791e 49f7f1          div     rax,r9

    FAULT_INSTR_CODE:  4cf1f749

    SYMBOL_STACK_INDEX:  7

    SYMBOL_NAME:  storport!StorpTelemetrySendAdaptiveIdleCounters+159e2

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: storport

    IMAGE_NAME:  storport.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  0

    STACK_COMMAND:  .thread ; .cxr ; kb

    BUCKET_ID_FUNC_OFFSET:  159e2

    FAILURE_BUCKET_ID:  0x1E_c0000094_storport!StorpTelemetrySendAdaptiveIdleCounters

    BUCKET_ID:  0x1E_c0000094_storport!StorpTelemetrySendAdaptiveIdleCounters

    PRIMARY_PROBLEM_CLASS:  0x1E_c0000094_storport!StorpTelemetrySendAdaptiveIdleCounters

    TARGET_TIME:  2018-07-20T10:37:46.000Z

    OSBUILD:  17134

    OSSERVICEPACK:  0

    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-06-08 18:00:00

    BUILDDATESTAMP_STR:  180410-1804

    BUILDLAB_STR:  rs4_release

    BUILDOSVER_STR:  10.0.17134.1.amd64fre.rs4_release.180410-1804

    ANALYSIS_SESSION_ELAPSED_TIME:  4fd

    ANALYSIS_SOURCE:  KM

    FAILURE_ID_HASH_STRING:  km:0x1e_c0000094_storport!storptelemetrysendadaptiveidlecounters

    FAILURE_ID_HASH:  {5250c0ed-be63-156d-4cf8-c1138004917d}

    Followup:     MachineOwner
    ---------
    Wednesday, July 25, 2018 5:24 AM