Windows 10: Windows 10 BSOD after upgrading from 1703 to 1809

Discus and support Windows 10 BSOD after upgrading from 1703 to 1809 in Windows 10 BSOD Crashes and Debugging to solve the problem; I am testing the Win 10 upgrade from 1703 to 1809. The update is successful, however, I find that BSOD occurs every time when I do a Windows Update.... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by Elvis_382, Jul 15, 2019.

  1. ELVIS_382
    Elvis_382 Win User

    Windows 10 BSOD after upgrading from 1703 to 1809


    I am testing the Win 10 upgrade from 1703 to 1809.


    The update is successful, however, I find that BSOD occurs every time when I do a Windows Update.


    Here is the dump file.


    Microsoft (R) Windows Debugger Version 10.0.18362.1 AMD64

    Copyright (c) Microsoft Corporation. All rights reserved.




    Loading Dump File [C:\Windows\MEMORY.DMP]

    Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.





    ************* Path validation summary **************

    Response Time (ms) Location

    Deferred SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols

    Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols

    Executable search path is:

    Windows 10 Kernel Version 17763 MP (4 procs) Free x64

    Product: WinNt, suite: TerminalServer SingleUserTS

    Built by: 17763.1.amd64fre.rs5_release.180914-1434

    Machine Name:

    Kernel base = 0xfffff802`7c4b1000 PsLoadedModuleList = 0xfffff802`7c8cc9f0

    Debug session time: Thu Jul 11 11:57:45.817 2019 (UTC + 8:00)

    System Uptime: 0 days 0:05:44.668

    Loading Kernel Symbols

    ......................................Page 2001cf026 too large to be in the dump file.

    Page 2001cf925 too large to be in the dump file.

    .........................

    .............Page 20040575b too large to be in the dump file.

    ...................................................

    ................................................................

    .......

    Loading User Symbols

    PEB is paged out (Peb.Ldr = 0000002c`cc83d018). Type ".hh dbgerr001" for details

    Loading unloaded module list

    ............

    For analysis of this file, run !analyze -v

    1: kd> !analyze -v

    *******************************************************************************

    * *

    * Bugcheck Analysis *

    * *

    *******************************************************************************



    SYSTEM_SERVICE_EXCEPTION (3b)

    An exception happened while executing a system service routine.

    Arguments:

    Arg1: 00000000c0000005, Exception code that caused the bugcheck

    Arg2: fffff80d0bdfe99d, Address of the instruction which caused the bugcheck

    Arg3: fffff980257ae680, Address of the context record for the exception that caused the bugcheck

    Arg4: 0000000000000000, zero.



    Debugging Details:

    ------------------





    KEY_VALUES_STRING: 1





    PROCESSES_ANALYSIS: 1



    SERVICE_ANALYSIS: 1



    STACKHASH_ANALYSIS: 1



    TIMELINE_ANALYSIS: 1





    DUMP_CLASS: 1



    DUMP_QUALIFIER: 401



    BUILD_VERSION_STRING: 17763.1.amd64fre.rs5_release.180914-1434



    SYSTEM_MANUFACTURER: HP



    SYSTEM_PRODUCT_NAME: HP ProDesk 600 G3 SFF



    SYSTEM_SKU: Y3F34AV



    BIOS_VENDOR: HP



    BIOS_VERSION: P07 Ver. 02.06



    BIOS_DATE: 06/09/2017



    BASEBOARD_MANUFACTURER: HP



    BASEBOARD_PRODUCT: 82B4



    BASEBOARD_VERSION: KBC Version 06.15



    DUMP_TYPE: 1



    BUGCHECK_P1: c0000005



    BUGCHECK_P2: fffff80d0bdfe99d



    BUGCHECK_P3: fffff980257ae680



    BUGCHECK_P4: 0



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



    FAULTING_IP:

    Ntfs!NtfsDecodeFileObject+5d

    fffff80d`0bdfe99d 8b4804 mov ecx,dword ptr [rax+4]



    CONTEXT: fffff980257ae680 -- (.cxr 0xfffff980257ae680)

    rax=0000000000000000 rbx=ffff9403586b0d18 rcx=ffff9403586b0d18

    rdx=0000000000000000 rsi=ffffdf0621a947b0 rdi=ffff9403672820e0

    rip=fffff80d0bdfe99d rsp=fffff980257af070 rbp=0000000000000000

    r8=fffff980257af128 r9=fffff980257af0f0 r10=fffff980257af2b8

    r11=fffff980257af2a8 r12=ffffdf0620685d58 r13=ffffdf0620685a70

    r14=fffff980257af2b8 r15=ffffdf0620685cd0

    iopl=0 nv up ei pl nz na pe nc

    cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202

    Ntfs!NtfsDecodeFileObject+0x5d:

    fffff80d`0bdfe99d 8b4804 mov ecx,dword ptr [rax+4] ds:002b:00000000`00000004=????????

    Resetting default scope



    BUGCHECK_STR: 0x3B_c0000005



    CPU_COUNT: 4



    CPU_MHZ: db0



    CPU_VENDOR: GenuineIntel



    CPU_FAMILY: 6



    CPU_MODEL: 9e



    CPU_STEPPING: 9



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



    BLACKBOXBSD: 1 (!blackboxbsd)





    BLACKBOXPNP: 1 (!blackboxpnp)





    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT



    PROCESS_NAME: TiWorker.exe



    CURRENT_IRQL: 0



    ANALYSIS_SESSION_HOST: PC1198



    ANALYSIS_SESSION_TIME: 07-11-2019 16:30:42.0223



    ANALYSIS_VERSION: 10.0.18362.1 amd64fre



    LAST_CONTROL_TRANSFER: from fffff80d0bed01e0 to fffff80d0bdfe99d



    STACK_TEXT:

    fffff980`257af070 fffff80d`0bed01e0 : ffff9403`4ffa8030 ffff9403`44c02340 ffffdf05`f5800d80 00000000`000002a4 : Ntfs!NtfsDecodeFileObject+0x5d

    fffff980`257af0b0 fffff80d`0bed2ddc : ffff9403`672820e0 00000000`00000000 00000000`00000000 ffff9403`00000030 : Ntfs!NtfsFindTargetElements+0x48

    fffff980`257af120 fffff80d`0bec1c33 : ffff9403`586b0d18 ffffdf06`20685cd0 ffffdf06`20685a70 00000000`00000001 : Ntfs!NtfsSetLinkInfo+0x24c

    fffff980`257af3b0 fffff80d`0bec0e77 : ffff9403`586b0d18 ffff9403`66f5da90 ffff9403`66f5da00 ffffdf06`20685c60 : Ntfs!NtfsCommonSetInformation+0xc83

    fffff980`257af490 fffff802`7c5690d9 : ffff9403`4ae435b0 ffff9403`66f5da90 ffff9403`586b0d18 fffff980`257b0000 : Ntfs!NtfsFsdSetInformation+0x107

    fffff980`257af540 fffff80d`0a8f6219 : ffff9403`67002050 00000000`10000000 ffff9403`66f5da90 00000000`00000000 : nt!IofCallDriver+0x59

    fffff980`257af580 fffff80d`0a8f4a36 : fffff980`257af610 ffff9403`52bf2760 94036728`20b00000 00000000`00100002 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x289

    fffff980`257af5f0 fffff802`7c5690d9 : ffff9403`66f5da90 fffff802`7cb4e73e ffff9403`5431c080 fffff802`00000002 : FLTMGR!FltpDispatch+0xb6

    fffff980`257af650 fffff80d`0bdc67a3 : fffff980`257af780 ffffdf05`f5e04ac0 00000000`00000000 fffff802`7cb006ce : nt!IofCallDriver+0x59

    fffff980`257af690 fffff802`7c5690d9 : 00000000`00000000 ffff9403`6727b1f0 00000000`00000001 ffff9403`66f5da90 : fsh+0x67a3

    fffff980`257af7a0 fffff802`7c567d43 : 01d532d2`e6957c4e 00000000`00000020 fffffcbd`c0c19102 00000000`00000048 : nt!IofCallDriver+0x59

    fffff980`257af7e0 fffff802`7c5dcd7c : ffff9403`66f5da90 fffff980`00000000 00000000`00000000 ffff9403`00020000 : nt!IopCallDriverReference+0xd3

    fffff980`257af850 fffff802`7c675785 : 00000000`00000a94 0000002c`cccfe020 0000013a`32438420 00000000`000000f2 : nt!NtSetInformationFile+0x72c

    fffff980`257af990 00007ffc`1d4ffb54 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25

    0000002c`cccfdbf8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`1d4ffb54





    THREAD_SHA1_HASH_MOD_FUNC: b2c8719a9b3e2aec3712bb20f1afa93cfb44c1d8



    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: d6fa3a59a509da5501449b15e3c394f922de6cb9



    THREAD_SHA1_HASH_MOD: 7db717144f7a8482d43daf954a7434841bce7d9f



    FOLLOWUP_IP:

    fsh+67a3

    fffff80d`0bdc67a3 4c8bb424f0000000 mov r14,qword ptr [rsp+0F0h]



    FAULT_INSTR_CODE: 24b48b4c



    SYMBOL_STACK_INDEX: 9



    SYMBOL_NAME: fsh+67a3



    FOLLOWUP_NAME: MachineOwner



    MODULE_NAME: fsh



    IMAGE_NAME: fsh.sys



    DEBUG_FLR_IMAGE_TIMESTAMP: 4e5e0a74



    STACK_COMMAND: .cxr 0xfffff980257ae680 ; kb



    BUCKET_ID_FUNC_OFFSET: 67a3



    FAILURE_BUCKET_ID: 0x3B_c0000005_fsh!unknown_function



    BUCKET_ID: 0x3B_c0000005_fsh!unknown_function



    PRIMARY_PROBLEM_CLASS: 0x3B_c0000005_fsh!unknown_function



    TARGET_TIME: 2019-07-11T03:57:45.000Z



    OSBUILD: 17763



    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: unknown_date



    BUILDDATESTAMP_STR: 180914-1434



    BUILDLAB_STR: rs5_release



    BUILDOSVER_STR: 10.0.17763.1.amd64fre.rs5_release.180914-1434



    ANALYSIS_SESSION_ELAPSED_TIME: 7152



    ANALYSIS_SOURCE: KM



    FAILURE_ID_HASH_STRING: km:0x3b_c0000005_fsh!unknown_function



    FAILURE_ID_HASH: {dbc433b8-cd68-56e9-ff76-e055aeb40b56}



    Followup: MachineOwner

    :)
     
    Elvis_382, Jul 15, 2019
    #1
  2. KEEPITSIMPLEENGR
    keepitsimpleengr Win User

    Windows 10 ver 1607 will not upgrade to 1703

    • How are you performing the upgrade from Windows 10 Version 1607 to 1703
    Windows10Upgrade9252 (2).exe

    • What troubleshooting steps have you performed to address the issue?
    Retry
     
    keepitsimpleengr, Jul 15, 2019
    #2
  3. ROLANDO VIL
    Rolando Vil Win User
    Windows 10 ver 1607 will not upgrade to 1703

    Hi,

    We would like to ask you some questions in order to assist you properly:

    • How are you performing the upgrade from Windows 10 Version 1607 to 1703?
    • What troubleshooting steps have you performed to address the issue?
    While waiting for your reply, we suggest that perform the following and check if it resolves your concern:

    • Perform a clean boot using this
      link      . This helps eliminate software conflicts that occur when you install a program, update, or when you run a program in Windows 10.
    • Download and run the
      Windows Update troubleshooter       for your version of Windows.
    • Once you've performed the suggested steps, perform the upgrade again and check the results.

    Please post the results for us to assist you further.
     
    Rolando Vil, Jul 15, 2019
    #3
  4. NORDIC
    Nordic Win User

    Windows 10 BSOD after upgrading from 1703 to 1809

    Windows 10 upgrade problem, no input accepted

    I really hate having to come here and ask for help, but I really am stumped. It hurts my geek pride. I have a PC with fairly modern hardware in it. It has a p8p67 pro in it. I have tried upgrading windows 10 on it twice now. Both times I have had the same result.

    After windows finishes upgrading it goes to the log in/set up screen. I can't do anything. No keyboard or mouse input is accepted.

    I will list some, or hopefully all, of the troubleshooting steps I have tried:
    • Move keyboard and mouse to different USB ports.
    • Try different keyboard or mouse.
    • Restart computer, repeatedly.
    • Google for related issues.
    • Update Bios, because why not.
    • Create boot media and revert to windows 7.
    The windows 10 system restore boot media works fine with keyboard and mouse. All USB ports work in windows 7. I don't know what is wrong. I suspect that windows 10 is lacking a driver of some sort, but since the computer accepts no input I have no way of checking for which driver let alone installing it.

    Please help me figure this out. If I have to revert back to windows 7 again, I am not going to get it upgraded to windows 10. Thank you in advanced.
     
    Nordic, Jul 15, 2019
    #4
Thema:

Windows 10 BSOD after upgrading from 1703 to 1809

Loading...

  1. Windows 10 BSOD after upgrading from 1703 to 1809 - Similar Threads - BSOD upgrading 1703

  2. BSOD after Windows 10 1703 - 1903

    in Windows 10 BSOD Crashes and Debugging
    BSOD after Windows 10 1703 - 1903: i have a issue of BSOD DRIVER PNP WATCHDOG ,dosent even boot, it will stuck at boot screen with windows 10 logo for 5 min and display BSOD tried every method Microsoft recommend i reached out to dell, the technical support said its software problem i tried every single...

  3. Your PC will automatically restart in one minute after in-place upgrade from 1703 - 1809

    in Windows 10 Customization
    Your PC will automatically restart in one minute after in-place upgrade from 1703 - 1809: Hi, We faced with issue related restart loop after In-place upgrade Computer is updated across SCCM Task Sequence to 1809. When user trying to enter to their profile it shows message about : [ATTACH] Your PC will automatically restart in one minute Recreate user profile...

  4. Cannot update my desktop from 1703 to 1809

    in Windows 10 Installation and Upgrade
    Cannot update my desktop from 1703 to 1809: I have been neglecting updates as I had them turned off due to Windows updating without my consent, so this week I finally wanted to bring my PC running Windows 10 up to date. I ran through all of regular windows update, rebooted a couple times but was met with the popup...

  5. Cannot update my desktop from 1703 to 1809

    in Windows 10 Installation and Upgrade
    Cannot update my desktop from 1703 to 1809: I have been neglecting updates as I had them turned off due to Windows updating without my consent, so this week I finally wanted to bring my PC running Windows 10 up to date. I ran through all of regular windows update, rebooted a couple times but was met with the popup...

  6. update from Windows 10 version 1703 to 1809 failed

    in Windows 10 Installation and Upgrade
    update from Windows 10 version 1703 to 1809 failed: I literally only just realized that my HP Pavilion 10 laptop is really behind on updates and when I try to update to a newer version of Windows 10, I have tried updating through my laptop's "Window's update" feature in the settings and it comes up with "Feature update to...

  7. After upgrade to Windows 10 1809, printing from MS Access result in a BSOD

    in Windows 10 BSOD Crashes and Debugging
    After upgrade to Windows 10 1809, printing from MS Access result in a BSOD: Hello, After upgrading Windows 10 pc's from 1803 to 1809, colleagues began to print from MS Access which result in a Windows Stop Error (BSOD) Stopcode: SYSTEM_SERVICE_EXCEPTION win32kfull.sys. Returning back to Windows 10 1803 solved the problem. Is there a fix available?...

  8. Updating from 1703 to 1809.

    in Windows 10 Installation and Upgrade
    Updating from 1703 to 1809.: I have a Surface Pro 4 still on 1703 and have a bunch of updates available to download including a cumulative update for 1703 and Malicious Software Removal Tool along with a Feature Update for 1803 and I was wondering if it was okay for me to bypass them all and install the...

  9. User master after upgrade from 1607 to 1703

    in User Accounts and Family Safety
    User master after upgrade from 1607 to 1703: Hi, after i upgraded my notebook from 1607 to 1703 i asks for the password of the user master after every boot/reboot. i can't find this user in the user database. How can i delete this user account? Thanks, Peter 94841

  10. Windows 10 1703 Upgrade Failing

    in Windows 10 Installation and Upgrade
    Windows 10 1703 Upgrade Failing: For a few weeks now I've been trying to install the new Windows 10 1703 upgrade and it keeps failing. It goes through the whole check the system thing, everything is ok and then proceeds to download the 2.9gb update esd file. Following that it goes through the install...