Unable to update windows, error 0xC1900101-0x30018


  1. Posts : 3
    Windows 10 Pro 1607
       #1

    Unable to update windows, error 0xC1900101-0x30018


    Hi,

    I am stuck at Windows 10 Pro 1607 because i couldn't update Windows, always do rollback at 90% of installation.

    Already tried to debug but without success, can please someone tell me what the problem/driver is and how to solve?

    Thank you.
      My Computer


  2. Posts : 1,538
    Windows 8.1 Enterprise x64
       #2

    Update:
    Aten usb to serial bridge driver (check in Snappy Driver Download)
    Code:
    Microsoft (R) Windows Debugger Version 10.0.17763.132 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [F:\011817-25328-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 14393 MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 14393.576.amd64fre.rs1_release_inmarket.161208-2252
    Machine Name:
    Kernel base = 0xfffff803`dae8d000 PsLoadedModuleList = 0xfffff803`db192060
    Debug session time: Wed Jan 18 14:03:03.300 2017 (UTC + 2:00)
    System Uptime: 1 days 19:18:16.017
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ................................................
    Loading User Symbols
    Loading unloaded module list
    ............................
    *** WARNING: Unable to verify timestamp for ser2at64.sys
    *** ERROR: Module load completed but symbols could not be loaded for ser2at64.sys
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1000007E, {ffffffffc0000005, fffff8084b4f810b, ffff8001d0ad4f08, ffff8001d0ad4730}
    
    Probably caused by : ser2at64.sys ( ser2at64+810b )
    
    Followup:     MachineOwner
    ---------
    
    0: 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: fffff8084b4f810b, The address that the exception occurred at
    Arg3: ffff8001d0ad4f08, Exception Record Address
    Arg4: ffff8001d0ad4730, Context Record Address
    
    Debugging Details:
    ------------------
    
    
    KEY_VALUES_STRING: 1
    
    
    STACKHASH_ANALYSIS: 1
    
    TIMELINE_ANALYSIS: 1
    
    
    DUMP_CLASS: 1
    
    DUMP_QUALIFIER: 400
    
    BUILD_VERSION_STRING:  14393.576.amd64fre.rs1_release_inmarket.161208-2252
    
    SYSTEM_MANUFACTURER:  Hewlett-Packard
    
    SYSTEM_PRODUCT_NAME:  HP Pro 3400 Series MT
    
    SYSTEM_SKU:  LH128EA#AB9
    
    BIOS_VENDOR:  AMI
    
    BIOS_VERSION:  7.16
    
    BIOS_DATE:  03/23/2012
    
    BASEBOARD_MANUFACTURER:  Foxconn
    
    BASEBOARD_PRODUCT:  2ABF
    
    BASEBOARD_VERSION:  1.30
    
    DUMP_FILE_ATTRIBUTES: 0x8
      Kernel Generated Triage Dump
    
    DUMP_TYPE:  2
    
    BUGCHECK_P1: ffffffffc0000005
    
    BUGCHECK_P2: fffff8084b4f810b
    
    BUGCHECK_P3: ffff8001d0ad4f08
    
    BUGCHECK_P4: ffff8001d0ad4730
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    FAULTING_IP: 
    ser2at64+810b
    fffff808`4b4f810b 4129825c010000  sub     dword ptr [r10+15Ch],eax
    
    EXCEPTION_RECORD:  ffff8001d0ad4f08 -- (.exr 0xffff8001d0ad4f08)
    ExceptionAddress: fffff8084b4f810b (ser2at64+0x000000000000810b)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000001
       Parameter[1]: 000000000000015c
    Attempt to write to address 000000000000015c
    
    CONTEXT:  ffff8001d0ad4730 -- (.cxr 0xffff8001d0ad4730)
    rax=0000000000000009 rbx=ffffcc864186fe40 rcx=0000000000000004
    rdx=0000000000000010 rsi=ffffcc86425e9890 rdi=00003379be790358
    rip=fffff8084b4f810b rsp=ffff8001d0ad5140 rbp=ffffcc86425e9960
     r8=fffff8084b500fa0  r9=0000000000000004 r10=0000000000000000
    r11=ffff8001d0ad5150 r12=ffffcc86418645b0 r13=0000000000000000
    r14=ffff8001d0ad52b8 r15=00003379bda16888
    iopl=0         nv up ei pl zr na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
    ser2at64+0x810b:
    fffff808`4b4f810b 4129825c010000  sub     dword ptr [r10+15Ch],eax ds:002b:00000000`0000015c=????????
    Resetting default scope
    
    CPU_COUNT: 2
    
    CPU_MHZ: a86
    
    CPU_VENDOR:  GenuineIntel
    
    CPU_FAMILY: 6
    
    CPU_MODEL: 2a
    
    CPU_STEPPING: 7
    
    CPU_MICROCODE: 6,2a,7,0 (F,M,S,R)  SIG: 29'00000000 (cache) 29'00000000 (init)
    
    CUSTOMER_CRASH_COUNT:  1
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    FOLLOWUP_IP: 
    ser2at64+810b
    fffff808`4b4f810b 4129825c010000  sub     dword ptr [r10+15Ch],eax
    
    BUGCHECK_STR:  AV
    
    WRITE_ADDRESS: fffff803db234338: Unable to get MiVisibleState
    Unable to get NonPagedPoolStart
    Unable to get NonPagedPoolEnd
    Unable to get PagedPoolStart
    Unable to get PagedPoolEnd
     000000000000015c 
    
    DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
    
    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    EXCEPTION_CODE_STR:  c0000005
    
    EXCEPTION_PARAMETER1:  0000000000000001
    
    EXCEPTION_PARAMETER2:  000000000000015c
    
    ANALYSIS_SESSION_HOST:  MICHAL
    
    ANALYSIS_SESSION_TIME:  05-22-2019 15:46:04.0415
    
    ANALYSIS_VERSION: 10.0.17763.132 amd64fre
    
    LAST_CONTROL_TRANSFER:  from 00003379be790358 to fffff8084b4f810b
    
    STACK_TEXT:  
    ffff8001`d0ad5140 00003379`be790358 : 00000000`00000000 00000000`00000001 00000000`00000004 ffffcc86`425e9770 : ser2at64+0x810b
    ffff8001`d0ad5148 00000000`00000000 : 00000000`00000001 00000000`00000004 ffffcc86`425e9770 fffff808`481d0550 : 0x00003379`be790358
    
    
    THREAD_SHA1_HASH_MOD_FUNC:  8c544ad4fe9b4fc6d2cd7d0e445d7afa72a523d1
    
    THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  8979d2efda7cc29c9c8eecf3b0a668edff2272b4
    
    THREAD_SHA1_HASH_MOD:  8c544ad4fe9b4fc6d2cd7d0e445d7afa72a523d1
    
    FAULT_INSTR_CODE:  5c822941
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  ser2at64+810b
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: ser2at64
    
    IMAGE_NAME:  ser2at64.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4ad6e7c6
    
    STACK_COMMAND:  .cxr 0xffff8001d0ad4730 ; kb
    
    BUCKET_ID_FUNC_OFFSET:  810b
    
    FAILURE_BUCKET_ID:  AV_ser2at64!unknown_function
    
    BUCKET_ID:  AV_ser2at64!unknown_function
    
    PRIMARY_PROBLEM_CLASS:  AV_ser2at64!unknown_function
    
    TARGET_TIME:  2017-01-18T12:03:03.000Z
    
    OSBUILD:  14393
    
    OSSERVICEPACK:  576
    
    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:  2016-12-09 10:23:02
    
    BUILDDATESTAMP_STR:  161208-2252
    
    BUILDLAB_STR:  rs1_release_inmarket
    
    BUILDOSVER_STR:  10.0.14393.576.amd64fre.rs1_release_inmarket.161208-2252
    
    ANALYSIS_SESSION_ELAPSED_TIME:  991
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:av_ser2at64!unknown_function
    
    FAILURE_ID_HASH:  {728bb753-11fc-63ee-baf1-e1dcde7e693e}
    
    Followup:     MachineOwner
    ---------
    
    0: kd> lmvm ser2at64
    Browse full module list
    start             end                 module name
    fffff808`4b4f0000 fffff808`4b510000   ser2at64 T (no symbols)           
        Loaded symbol image file: ser2at64.sys
        Image path: ser2at64.sys
        Image name: ser2at64.sys
        Browse all global symbols  functions  data
        Timestamp:        Thu Oct 15 02:13:42 2009 (4AD6E7C6)
        CheckSum:         000270B3
        ImageSize:        00020000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
        Information from resource tables:
    0: kd> .load pde
    =========================================================================================
     PDE v11.3 - Copyright 2017 Andrew Richards
    =========================================================================================
    0: kd> !dpx
    Start memory scan  : 0xffff8001d0ad5140 ($csp)
    End memory scan    : 0xffff8001d0ad6000 (Kernel Stack Base)
    
                   r14 : 0xffff8001d0ad52b8 : 0xfffff808481e4600 : Wdf01000!WPP_PowerStateMachine_cpp_Traceguids
    0xffff8001d0ad5168 : 0xfffff808481d0550 : Wdf01000!FxIoQueue::ProcessCancelledRequestsOnQueue+0x12c
    0xffff8001d0ad5190 : 0xfffff808481e46c0 : Wdf01000!WPP_FxIoQueue_cpp_Traceguids
    0xffff8001d0ad51f8 : 0xfffff808481dfe10 : Wdf01000!FxPowerIdleMachine::m_StateTable
    0xffff8001d0ad5218 : 0xfffff808481e3290 : Wdf01000!FxPkgPnp::m_WdfPnpStates
    0xffff8001d0ad5238 : 0xfffff8084814a386 : Wdf01000!FxIFR+0x156
    0xffff8001d0ad5270 : 0xfffff808481e4610 : Wdf01000!WPP_PnpStateMachine_cpp_Traceguids
    0xffff8001d0ad52a0 : 0xfffff808481e4600 : Wdf01000!WPP_PowerStateMachine_cpp_Traceguids
    0xffff8001d0ad52a8 : 0xfffff8084815220c : Wdf01000!FxIoQueue::CancelForQueue+0xdc
    0xffff8001d0ad52b8 : 0xfffff808481e4600 : Wdf01000!WPP_PowerStateMachine_cpp_Traceguids
    0xffff8001d0ad5308 : 0xfffff8084815243c : Wdf01000!FxIoQueue::QueuePurge+0x1b8
    0xffff8001d0ad5318 : 0xfffff808481e46c0 : Wdf01000!WPP_FxIoQueue_cpp_Traceguids
    0xffff8001d0ad5330 : 0xfffff808481e46c0 : Wdf01000!WPP_FxIoQueue_cpp_Traceguids
    0xffff8001d0ad5348 : 0xfffff8084814ccbf : Wdf01000!FxNonPagedObject::Lock+0x1f
    0xffff8001d0ad53b8 : 0xfffff8084815cc48 : Wdf01000!FxPkgIo::StopProcessingForPower+0x138
    0xffff8001d0ad53f8 : 0xfffff808481b8fc5 : Wdf01000!FxDevice::DeleteSymbolicLink+0x39
    0xffff8001d0ad5410 : 0xfffff808481e3290 : Wdf01000!FxPkgPnp::m_WdfPnpStates
    0xffff8001d0ad5428 : 0xfffff808481d28d4 : Wdf01000!FxPkgPnp::PnpCleanupForRemove+0x90
    0xffff8001d0ad5458 : 0xfffff808481d2960 : Wdf01000!FxPkgPnp::PnpEventFailed+0x10
    0xffff8001d0ad5488 : 0xfffff80848166a79 : Wdf01000!FxPkgPnp::PnpProcessEventInner+0x1c9
    0xffff8001d0ad54a8 : 0xfffff808481e3290 : Wdf01000!FxPkgPnp::m_WdfPnpStates
    0xffff8001d0ad54b0 : 0xfffff808481e4610 : Wdf01000!WPP_PnpStateMachine_cpp_Traceguids
    0xffff8001d0ad5538 : 0xfffff808481641a8 : Wdf01000!FxPkgPnp::PnpProcessEvent+0x158
    0xffff8001d0ad5578 : 0xfffff808481743ef : Wdf01000!WPP_IFR_SF_qqcq+0xdb
    0xffff8001d0ad55d8 : 0xfffff808481d7aa5 : Wdf01000!FxPkgPnp::PnpSurpriseRemoval+0x25
    0xffff8001d0ad5608 : 0xfffff80848143e7f : Wdf01000!FxPkgPnp::Dispatch+0xef
    0xffff8001d0ad5630 : 0xfffff808481e45c0 : Wdf01000!WPP_FxPkgPnp_cpp_Traceguids
    0xffff8001d0ad5688 : 0xfffff803db0f3f40 : nt!DEVPKEY_Device_DevNodeStatusStarted
    0xffff8001d0ad56a8 : 0xfffff808481434f5 : Wdf01000!FxDevice::DispatchWithLock+0x155
    0xffff8001d0ad56d8 : 0xfffff803db28d34d : nt!PnpNotifyDerivedKeys+0xc9
    0xffff8001d0ad5728 : 0xfffff803db28d019 : nt!PnpDeviceRaisePropertyChangeEventWorker+0x135
    0xffff8001d0ad5730 : 0xfffff803db0f3f40 : nt!DEVPKEY_Device_DevNodeStatusStarted
    0xffff8001d0ad5740 : 0xfffff803db28bf58 : nt!PiPnpRtlObjectEventCallback
    0xffff8001d0ad5750 : 0xfffff803db0dcc70 : nt!PlugPlayHandlerTable+0x710
    0xffff8001d0ad5798 : 0xfffff8084bca7458 : serenum!Serenum_FDO_PnP+0x218
    0xffff8001d0ad57b0 : 0xfffff803db1a9e20 : nt!PiPnpRtlActiveOperationsLock
    0xffff8001d0ad57b8 : 0xfffff803daf716d4 : nt!ExAcquireResourceSharedLite+0x394
    0xffff8001d0ad57c8 : 0xfffff803daef958b : nt!IopAllocateIrpPrivate+0x19b
    0xffff8001d0ad57e8 : 0xfffff803db1a9e80 : nt!PiPnpRtlActiveOperationsLock+0x60
    0xffff8001d0ad57f8 : 0xfffff803db1a9e80 : nt!PiPnpRtlActiveOperationsLock+0x60
    0xffff8001d0ad5818 : 0xfffff8084bca722c : serenum!Serenum_PnP+0x3c
    0xffff8001d0ad5848 : 0xfffff803db28c7d0 : nt!IopSynchronousCall+0xd8
    0xffff8001d0ad5878 : 0xfffff803db2884aa : nt!PiPnpRtlBeginOperation+0x32
    0xffff8001d0ad58b8 : 0xfffff803db37d404 : nt!IopRemoveDevice+0xdc
    0xffff8001d0ad58e8 : 0xfffff803db0da29f : nt!ExAllocatePoolWithTag+0x85f
    0xffff8001d0ad5968 : 0xfffff803db2bf957 : nt!PnpSurpriseRemoveLockedDeviceNode+0xb3
    0xffff8001d0ad59c8 : 0xfffff803db37e99b : nt!PnpDeleteLockedDeviceNode+0x8b
    0xffff8001d0ad59f8 : 0xfffff803db37eb2b : nt!PnpAllocateCriticalMemory+0x2b
    0xffff8001d0ad5a08 : 0xfffff803db37e6be : nt!PnpDeleteLockedDeviceNodes+0xbe
    0xffff8001d0ad5a78 : 0xfffff803db37dbc9 : nt!PnpProcessQueryRemoveAndEject+0x1e5
    0xffff8001d0ad5ac0 : 0xfffff803db1a9e50 : nt!PiPnpRtlActiveOperationsLock+0x30
    0xffff8001d0ad5ae8 : 0xfffff803daf712ae : nt!ExAcquireResourceExclusiveLite+0x41e
    0xffff8001d0ad5b08 : 0xffff8001d0ad5c00 : 0xffff8001d0ad5c60 : 0xfffff803db24a100 : nt!ExNode0
    0xffff8001d0ad5ba8 : 0xfffff803db384cc9 : nt!PnpProcessTargetDeviceEvent+0xd9
    0xffff8001d0ad5bc0 : 0xffff8001d0ad5c00 : 0xffff8001d0ad5c60 : 0xfffff803db24a100 : nt!ExNode0
    0xffff8001d0ad5be8 : 0xfffff803db384f84 : nt!PnpDeviceEventWorker+0x294
    0xffff8001d0ad5c00 : 0xffff8001d0ad5c60 : 0xfffff803db24a100 : nt!ExNode0
    0xffff8001d0ad5c38 : 0xfffff803db24a100 : nt!ExNode0
    0xffff8001d0ad5c58 : 0xfffff803db24a280 : nt!ExNode0+0x180
    0xffff8001d0ad5c60 : 0xfffff803db24a100 : nt!ExNode0
    0xffff8001d0ad5c70 : 0xfffff803db384cf0 : nt!PnpDeviceEventWorker
    0xffff8001d0ad5c78 : 0xfffff803daf241b9 : nt!ExpWorkerThread+0xe9
    0xffff8001d0ad5c80 : 0xfffff803db24a100 : nt!ExNode0
    0xffff8001d0ad5c98 : 0xfffff803db24a280 : nt!ExNode0+0x180
    0xffff8001d0ad5cf8 : 0xfffff803db24a280 : nt!ExNode0+0x180
    0xffff8001d0ad5d00 : 0xfffff803daf240d0 : nt!ExpWorkerThread
    0xffff8001d0ad5d08 : 0xfffff803dae8f729 : nt!PspSystemThreadStartup+0x41
    0xffff8001d0ad5d58 : 0xfffff803dafdcbb6 : nt!KiStartSystemThread+0x16
    0xffff8001d0ad5d70 : 0xfffff803dae8f6e8 : nt!PspSystemThreadStartup
    
    *** WARNING: Unable to verify timestamp for ser2at64.sys
    *** ERROR: Module load completed but symbols could not be loaded for ser2at64.sys
      My Computer


  3. Posts : 3
    Windows 10 Pro 1607
    Thread Starter
       #3

    Hi,

    Thank you for the answer.

    I am afraid that Aten drivers is not the problem.
    In my previous debug i already think that Aten was the problem so i disable it and unplug the device but the problem was the same.

    After your post i update the driver but the same problem occur. I then uninstall completely Aten software and drivers but without success, the same problem occurs.

    The dump file you examine was from 2017 and maybe not related with this issue.

    In this post i send the dump from this last update try, see if that helps.

    Thank you.
      My Computer


  4. Posts : 1,538
    Windows 8.1 Enterprise x64
       #4

    This time the driver stnsport.sys is guilty (driver from the rs232 controller)
    Code:
    Microsoft (R) Windows Debugger Version 10.0.17763.132 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [F:\setupmem.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 16299 MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Machine Name:
    Kernel base = 0xfffff803`e0411000 PsLoadedModuleList = 0xfffff803`e077a110
    Debug session time: Wed May 22 17:51:50.429 2019 (UTC + 2:00)
    System Uptime: 0 days 0:02:30.230
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ................................................................
    ...............
    Loading User Symbols
    Loading unloaded module list
    ...................
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 50, {ffffc500007f2828, 0, fffff803e04f133a, 2}
    
    *** WARNING: Unable to verify timestamp for StnSport.sys
    *** ERROR: Module load completed but symbols could not be loaded for StnSport.sys
    
    Could not read faulting driver name
    Probably caused by : StnSport.sys ( StnSport+11d02 )
    
    Followup:     MachineOwner
    ---------
    
    0: 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: ffffc500007f2828, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff803e04f133a, If non-zero, the instruction address which referenced the bad memory
    	address.
    Arg4: 0000000000000002, (reserved)
    
    Debugging Details:
    ------------------
    
    
    Could not read faulting driver name
    
    KEY_VALUES_STRING: 1
    
    
    STACKHASH_ANALYSIS: 1
    
    TIMELINE_ANALYSIS: 1
    
    
    DUMP_CLASS: 1
    
    DUMP_QUALIFIER: 400
    
    BUILD_VERSION_STRING:  10.0.16299.1120 (WinBuild.160101.0800)
    
    SYSTEM_MANUFACTURER:  Hewlett-Packard
    
    SYSTEM_PRODUCT_NAME:  HP Pro 3400 Series MT
    
    SYSTEM_SKU:  LH128EA#AB9
    
    BIOS_VENDOR:  AMI
    
    BIOS_VERSION:  7.16
    
    BIOS_DATE:  03/23/2012
    
    BASEBOARD_MANUFACTURER:  Foxconn
    
    BASEBOARD_PRODUCT:  2ABF
    
    BASEBOARD_VERSION:  1.30
    
    DUMP_FILE_ATTRIBUTES: 0x8
      Kernel Generated Triage Dump
    
    DUMP_TYPE:  2
    
    BUGCHECK_P1: ffffc500007f2828
    
    BUGCHECK_P2: 0
    
    BUGCHECK_P3: fffff803e04f133a
    
    BUGCHECK_P4: 2
    
    READ_ADDRESS: fffff803e0810380: Unable to get MiVisibleState
    Unable to get NonPagedPoolStart
    Unable to get NonPagedPoolEnd
    Unable to get PagedPoolStart
    Unable to get PagedPoolEnd
     ffffc500007f2828 
    
    FAULTING_IP: 
    nt!MiMappingHasIoTracker+4e
    fffff803`e04f133a 488b03          mov     rax,qword ptr [rbx]
    
    MM_INTERNAL_CODE:  2
    
    CPU_COUNT: 2
    
    CPU_MHZ: a86
    
    CPU_VENDOR:  GenuineIntel
    
    CPU_FAMILY: 6
    
    CPU_MODEL: 2a
    
    CPU_STEPPING: 7
    
    CPU_MICROCODE: 6,2a,7,0 (F,M,S,R)  SIG: 29'00000000 (cache) 29'00000000 (init)
    
    BLACKBOXBSD: 1 (!blackboxbsd)
    
    
    BLACKBOXPNP: 1 (!blackboxpnp)
    
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    BUGCHECK_STR:  AV
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    ANALYSIS_SESSION_HOST:  MICHAL
    
    ANALYSIS_SESSION_TIME:  05-22-2019 20:01:22.0268
    
    ANALYSIS_VERSION: 10.0.17763.132 amd64fre
    
    TRAP_FRAME:  fffff0824e4bc090 -- (.trap 0xfffff0824e4bc090)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=f0a91599dbff0000
    rdx=ffffc562b158a000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff803e04f133a rsp=fffff0824e4bc220 rbp=00000000c000000e
     r8=ffffc562b158a000  r9=0000000000000001 r10=0000000000000002
    r11=ffffc562b158a7f8 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    nt!MiMappingHasIoTracker+0x4e:
    fffff803`e04f133a 488b03          mov     rax,qword ptr [rbx] ds:00000000`00000000=????????????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff803e0443689 to fffff803e0591940
    
    STACK_TEXT:  
    fffff082`4e4bbe08 fffff803`e0443689 : 00000000`00000050 ffffc500`007f2828 00000000`00000000 fffff082`4e4bc090 : nt!KeBugCheckEx
    fffff082`4e4bbe10 fffff803`e0464293 : 00000000`00000000 ffffdd09`1c5202dc ffffc500`007f2828 fffff803`e07997c0 : nt!MiSystemFault+0x1969
    fffff082`4e4bbeb0 fffff803`e059efda : 00000000`00000000 00000000`000ba6e3 ffffb401`ed9cf000 00000000`00020000 : nt!MmAccessFault+0x233
    fffff082`4e4bc090 fffff803`e04f133a : ffff0881`add4048e 00000000`80000000 00000000`000000ff fffff803`e39f20a1 : nt!KiPageFault+0x31a
    fffff082`4e4bc220 fffff803`e04f11d4 : 00000000`00000001 00000000`00001000 ffff0881`add404ce 00000000`c000000e : nt!MiMappingHasIoTracker+0x4e
    fffff082`4e4bc250 fffff803`e3a01d02 : ffffa30a`8971b724 00000000`c000000e 00000000`00000001 ffffdd09`1c5201c0 : nt!MmUnmapIoSpace+0x54
    fffff082`4e4bc280 ffffa30a`8971b724 : 00000000`c000000e 00000000`00000001 ffffdd09`1c5201c0 ffffffff`00000000 : StnSport+0x11d02
    fffff082`4e4bc288 00000000`c000000e : 00000000`00000001 ffffdd09`1c5201c0 ffffffff`00000000 ffffdd09`1c5202dd : 0xffffa30a`8971b724
    fffff082`4e4bc290 00000000`00000001 : ffffdd09`1c5201c0 ffffffff`00000000 ffffdd09`1c5202dd 00000001`00000001 : 0xc000000e
    fffff082`4e4bc298 ffffdd09`1c5201c0 : ffffffff`00000000 ffffdd09`1c5202dd 00000001`00000001 00000000`01000101 : 0x1
    fffff082`4e4bc2a0 ffffffff`00000000 : ffffdd09`1c5202dd 00000001`00000001 00000000`01000101 00000005`00000000 : 0xffffdd09`1c5201c0
    fffff082`4e4bc2a8 ffffdd09`1c5202dd : 00000001`00000001 00000000`01000101 00000005`00000000 00000000`00000000 : 0xffffffff`00000000
    fffff082`4e4bc2b0 00000001`00000001 : 00000000`01000101 00000005`00000000 00000000`00000000 00000000`ffffffff : 0xffffdd09`1c5202dd
    fffff082`4e4bc2b8 00000000`01000101 : 00000005`00000000 00000000`00000000 00000000`ffffffff ffffa30a`8971b6e0 : 0x00000001`00000001
    fffff082`4e4bc2c0 00000005`00000000 : 00000000`00000000 00000000`ffffffff ffffa30a`8971b6e0 fffff803`e39fe288 : 0x1000101
    fffff082`4e4bc2c8 00000000`00000000 : 00000000`ffffffff ffffa30a`8971b6e0 fffff803`e39fe288 ffffdd09`1d536128 : 0x00000005`00000000
    
    
    THREAD_SHA1_HASH_MOD_FUNC:  d3c21b66bcbee1cb2abb8594c083328a4b055dcb
    
    THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  4fbc1ef6b8f7aa49ddf5d54bf1541d6becac26fd
    
    THREAD_SHA1_HASH_MOD:  d7fee57a0510c7f7f9e3744e8c8f737d2267a427
    
    FOLLOWUP_IP: 
    StnSport+11d02
    fffff803`e3a01d02 ??              ???
    
    SYMBOL_STACK_INDEX:  6
    
    SYMBOL_NAME:  StnSport+11d02
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: StnSport
    
    IMAGE_NAME:  StnSport.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4c6e3f01
    
    STACK_COMMAND:  .thread ; .cxr ; kb
    
    BUCKET_ID_FUNC_OFFSET:  11d02
    
    FAILURE_BUCKET_ID:  AV_R_INVALID_StnSport!unknown_function
    
    BUCKET_ID:  AV_R_INVALID_StnSport!unknown_function
    
    PRIMARY_PROBLEM_CLASS:  AV_R_INVALID_StnSport!unknown_function
    
    TARGET_TIME:  2019-05-22T15:51:50.000Z
    
    OSBUILD:  16299
    
    OSSERVICEPACK:  1120
    
    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-04-06 07:08:50
    
    BUILDDATESTAMP_STR:  160101.0800
    
    BUILDLAB_STR:  WinBuild
    
    BUILDOSVER_STR:  10.0.16299.1120
    
    ANALYSIS_SESSION_ELAPSED_TIME:  14c4
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:av_r_invalid_stnsport!unknown_function
    
    FAILURE_ID_HASH:  {111fb85b-4475-a644-5154-220e6404d92a}
    
    Followup:     MachineOwner
    ---------
    
    0: kd> lmvm StnSport
    Browse full module list
    start             end                 module name
    fffff803`e39f0000 fffff803`e3a16000   StnSport T (no symbols)           
        Loaded symbol image file: StnSport.sys
        Image path: StnSport.sys
        Image name: StnSport.sys
        Browse all global symbols  functions  data
        Timestamp:        Fri Aug 20 01:38:25 2010 (4C6E3F01)
        CheckSum:         0002C6D5
        ImageSize:        00026000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
        Information from resource tables:
    0: kd> !blackboxpnp
        PnpActivityId      : {00000000-0000-0000-0000-000000000000}
        PnpActivityTime    : 132030139104294738
        PnpEventInformation: 0
        PnpEventInProgress : 0
        PnpProblemCode     : 22
        PnpVetoType        : 0
        DeviceId           : MF\PCI#VEN_9710&DEV_9912&SUBSYS_1000A000&REV_00\5&2cc9dc49&0&00E2#Child0000
        VetoString         : 
    
    0: kd> .load pde
    =========================================================================================
     PDE v11.3 - Copyright 2017 Andrew Richards
    =========================================================================================
    0: kd> !dpx
    Start memory scan  : 0xfffff0824e4bbe08 ($csp)
    End memory scan    : 0xfffff0824e4bd000 (Kernel Stack Base)
    
    0xfffff0824e4bbe38 : 0xfffff803e0455964 : nt!MiTradePage+0x554
    0xfffff0824e4bbe48 : 0xfffff803e058d274 : nt!MiMakeDemandZeroPte+0x10
    0xfffff0824e4bbe78 : 0xfffff803e058d1b1 : nt!MiGetPageFileHigh+0x9
    0xfffff0824e4bbea8 : 0xfffff803e0464293 : nt!MmAccessFault+0x233
    0xfffff0824e4bbef8 : 0xfffff803e0455268 : nt!MiFindContiguousPages+0x598
    0xfffff0824e4bbfc8 : 0xfffff803e04ed459 : nt!ExpAllocateBigPool+0x1b9
    *** WARNING: Unable to verify timestamp for StnSport.sys
    *** ERROR: Module load completed but symbols could not be loaded for StnSport.sys
    0xfffff0824e4bc088 : 0xfffff803e059efda : nt!KiPageFault+0x31a
    0xfffff0824e4bc090 : 0x0000000000000000 :  Trap @ fffff0824e4bc090
    0xfffff0824e4bc0f8 : 0xfffff803e04919c2 : nt!MI_IS_PHYSICAL_ADDRESS+0xd2
    0xfffff0824e4bc198 : 0xfffff803e058cca8 : nt!MiReadPteShadow+0xc
    0xfffff0824e4bc1a8 : 0xfffff803e06c3aa9 : nt!ExFreePoolWithTag+0x8d9
    0xfffff0824e4bc1c8 : 0xfffff803e04919c2 : nt!MI_IS_PHYSICAL_ADDRESS+0xd2
    0xfffff0824e4bc1f8 : 0xfffff803e04f133a : nt!MiMappingHasIoTracker+0x4e
    0xfffff0824e4bc248 : 0xfffff803e04f11d4 : nt!MmUnmapIoSpace+0x54
    0xfffff0824e4bc418 : 0xfffff803e04b7e97 : nt!IofCompleteRequest+0x17
    *** ERROR: Module load completed but symbols could not be loaded for mf.sys
    0xfffff0824e4bc478 : 0xfffff803e0437839 : nt!IofCallDriver+0x59
    0xfffff0824e4bc550 : 0xfffff803e0893680 : nt!PiPnpRtlObjectEventCallback
    0xfffff0824e4bc598 : 0xfffff0824e4bc650 : 0xfffff803e0500950 : nt!PnpDeviceCompletionRoutine
    0xfffff0824e4bc5a8 : 0xfffff803e0437839 : nt!IofCallDriver+0x59
    0xfffff0824e4bc5d0 : 0xfffff803e06d1218 : nt!DEVPKEY_Device_DevNodeStatusStarted
    0xfffff0824e4bc5e8 : 0xfffff803e3a27608 : serenum!Serenum_FDO_PnP+0x3a4
    0xfffff0824e4bc650 : 0xfffff803e0500950 : nt!PnpDeviceCompletionRoutine
    0xfffff0824e4bc668 : 0xfffff803e3a2724c : serenum!Serenum_PnP+0x3c
    0xfffff0824e4bc698 : 0xfffff803e0437839 : nt!IofCallDriver+0x59
    0xfffff0824e4bc6a8 : 0xfffff803e0439c13 : nt!IoAllocateIrp+0x23
    0xfffff0824e4bc6c8 : 0xfffff803e0500bd9 : nt!PnpSetDeviceAffinityThread+0x4d
    0xfffff0824e4bc6d8 : 0xfffff803e092630e : nt!PnpAsynchronousCall+0xea
    0xfffff0824e4bc708 : 0xfffff803e0500950 : nt!PnpDeviceCompletionRoutine
    0xfffff0824e4bc718 : 0xfffff803e0500b75 : nt!PnpSendIrp+0x91
    0xfffff0824e4bc788 : 0xfffff803e05114c8 : nt!PnpStartDevice+0x88
    0xfffff0824e4bc7a0 : 0xfffff803e0500950 : nt!PnpDeviceCompletionRoutine
    0xfffff0824e4bc7b8 : 0xfffff803e06cd268 : nt!KMPnPEvt_DeviceStart_Start
    0xfffff0824e4bc818 : 0xfffff803e0957ea7 : nt!PnpStartDeviceNode+0xdb
    0xfffff0824e4bc848 : 0xfffff803e09582ba : nt!IopUncacheInterfaceInformation+0xca
    0xfffff0824e4bc8a8 : 0xfffff803e0957d8f : nt!PipProcessStartPhase1+0x5b
    0xfffff0824e4bc8e8 : 0xfffff803e08966b9 : nt!PipProcessDevNodeTree+0x42d
    0xfffff0824e4bc978 : 0xfffff803e0991508 : nt!PiDcCompareUpdateProperties+0x18
    0xfffff0824e4bca28 : 0xfffff803e04b5512 : nt!KiSearchForNewThread+0x32
    0xfffff0824e4bca88 : 0xfffff803e04b4e7f : nt!KiSwapThread+0x1df
    0xfffff0824e4bcae8 : 0xfffff803e07940a0 : nt!IopDeviceTreeLock+0x60
    0xfffff0824e4bcaf0 : 0xfffff803e07940c0 : nt!PiEngineLock
    0xfffff0824e4bcaf8 : 0xfffff803e044f5e1 : nt!ExAcquireResourceExclusiveLite+0xe1
    0xfffff0824e4bcb20 : 0xfffff803e082b200 : nt!ExNode0
    0xfffff0824e4bcb68 : 0xfffff803e0860e4f : nt!PiRestartDevice+0xa7
    0xfffff0824e4bcb78 : 0xfffff803e044b4f9 : nt!ExAcquirePushLockExclusiveEx+0xe9
    0xfffff0824e4bcbb8 : 0xfffff803e0512a6a : nt!PnpDeviceActionWorker+0x43a
    0xfffff0824e4bcbe8 : 0xfffff803e043bfc4 : nt!KeRemovePriQueue+0x1e4
    0xfffff0824e4bcc38 : 0xfffff803e082b200 : nt!ExNode0
    0xfffff0824e4bcc50 : 0xfffff803e082b200 : nt!ExNode0
    0xfffff0824e4bcc70 : 0xfffff803e0512630 : nt!PnpDeviceActionWorker
    0xfffff0824e4bcc78 : 0xfffff803e043bbf5 : nt!ExpWorkerThread+0xf5
    0xfffff0824e4bcc90 : 0xfffff803e0792aa0 : nt!PnpDeviceEnumerationWorkItem
    0xfffff0824e4bccd8 : 0xfffff803e090b573 : nt!PspDisablePrimaryTokenExchange+0x3b
    0xfffff0824e4bcd00 : 0xfffff803e043bb00 : nt!ExpWorkerThread
    0xfffff0824e4bcd08 : 0xfffff803e04f6807 : nt!PspSystemThreadStartup+0x47
    0xfffff0824e4bcd40 : 0x526d65747379535c :  !da "\SystemR"
    0xfffff0824e4bcd50 : 0xfffff803e082c380 : nt!KiInitialThread
    0xfffff0824e4bcd58 : 0xfffff803e0598d96 : nt!KiStartSystemThread+0x16
    0xfffff0824e4bcd70 : 0xfffff803e04f67c0 : nt!PspSystemThreadStartup
    You can try to update these drivers (also look for them in the Snappy Driver linked above)
      My Computer


  5. Posts : 3
    Windows 10 Pro 1607
    Thread Starter
       #5

    Drivers where previous all updated with Snappy Driver. What i think is that in this case "stnsport.sys" don't have an updated driver. This driver is from 2010 and doesn't have any update.

    Uninstalled the drivers and already doing the update, later i will post the result.

    Thank you.

    - - - Updated - - -

    Hi,

    Even after disable and uninstalling the drivers it not worked. I have to remove physically the Comm Card and then the Windows was updated with success.

    All ok now, thank you for the help
      My Computer


  6. Posts : 41,462
    windows 10 professional version 1607 build 14393.969 64 bit
       #6

    Please post a new V2.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 18:03.
Find Us




Windows 10 Forums