Windows 10: Windows 10 Update 1809 Fails: 0xc1900101 CRITICAL_PROCESS_DIED ntfs.sys

Discus and support Windows 10 Update 1809 Fails: 0xc1900101 CRITICAL_PROCESS_DIED ntfs.sys in Windows 10 Installation and Upgrade to solve the problem; I have a fully up to date Windows 10 Pro computer. Aside from 1809, Windows Update works normally. I have tried updating within Windows Update (when... Discussion in 'Windows 10 Installation and Upgrade' started by WesleyGr, May 23, 2019.

  1. WesleyGr Win User

    Windows 10 Update 1809 Fails: 0xc1900101 CRITICAL_PROCESS_DIED ntfs.sys


    I have a fully up to date Windows 10 Pro computer. Aside from 1809, Windows Update works normally.


    I have tried updating within Windows Update (when it was offered), the Update Assistant tool and a Windows 10 1809 ISO image. The result is always the same.


    I have updated every driver one at a time, via Device Manager.

    I've run chkdsk. I've run "/sfc scannow".

    I've removed every USB drive. I've removed every mapped drive.


    I've run SetupDiag.exe but I cannot make sense of the results (see log output below). I also cannot find any other person with the same problem.


    Is there anyone out there that has any other ideas of how to solve the problem?



    Matching Profile found: DebugSetupMemoryDump - C7C63D8A-C5F6-4255-8031-74597773C3C6
    System Information:
    Machine Name = <removed>
    Manufacturer = Dell Inc.
    Model = Latitude E5570
    HostOSArchitecture = x64
    FirmwareType = UEFI
    BiosReleaseDate = 20180820000000.000000+000
    BiosVendor = 1.19.3
    BiosVersion = 1.19.3
    HostOSVersion = 10.0.17134
    HostOSBuildString = 17134.1.amd64fre.rs4_release.180410-1804
    TargetOSBuildString = 10.0.17763.190 (rs5_release_svc_prod1.181114-1827)
    HostOSLanguageId = 1033
    HostOSEdition = Professional
    RegisteredAV = Windows Defender,Windows Defender,Windows Defender,Windows Defender,Windows Defender,Windows Defender,Windows Defender,Windows Defender,
    FilterDrivers = wcnfs,WdFilter,wcifs,CldFlt,luafv,Wof,FileInfo,
    UpgradeStartTime = 5/22/2019 3:55:51 PM
    FinalizeStartTime = 5/22/2019 5:07:36 PM
    UpgradeEndTime = 5/22/2019 7:13:58 PM
    UpgradeElapsedTime = 03:18:07
    CV = hRVZWHtfBUmgoqW3
    ReportId = A385185A-D7DD-4F9A-8BC4-9A0BAF8548D8

    DebugSetupMemoryDump: DirectiveDebugMemoryDump - C:\$WINDOWS.~BT\Sources\Rollback\setupmem.dmp -
    Microsoft (R) Windows Debugger Version 10.0.18362.1 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\$WINDOWS.~BT\Sources\Rollback\setupmem.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*
    Deferred *http://symweb
    Symbol search path is: SRV*;*http://symweb
    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 = 0xfffff807`2fa11000 PsLoadedModuleList = 0xfffff807`2fe2ba50
    Debug session time: Wed May 22 19:13:58.621 2019 (UTC - 4:00)
    System Uptime: 0 days 0:02:56.460
    Loading Kernel Symbols
    ........................................Page 20041a0ed too large to be in the dump file.
    .......................
    ............Page 20040ee5d too large to be in the dump file.
    ....................................................
    ................................................................
    ............................
    Loading User Symbols
    .............................
    Loading unloaded module list
    ....................
    For analysis of this file, run !analyze -v
    0: kd> *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    CRITICAL_PROCESS_DIED (ef)
    A critical system process died
    Arguments:
    Arg1: ffffac887314f480, Process object or thread object
    Arg2: 0000000000000000, If this is 0, a process died. If this is 1, a thread died.
    Arg3: 0000000000000000
    Arg4: 0000000000000000

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

    Page 20041a0ed too large to be in the dump file.
    Page 20040ee5d too large to be in the dump file.

    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: Dell Inc.

    SYSTEM_PRODUCT_NAME: Latitude E5570

    SYSTEM_SKU: 06DF

    BIOS_VENDOR: Dell Inc.

    BIOS_VERSION: 1.19.3

    BIOS_DATE: 08/20/2018

    BASEBOARD_MANUFACTURER: Dell Inc.

    BASEBOARD_PRODUCT:

    BASEBOARD_VERSION:

    DUMP_TYPE: 1

    BUGCHECK_P1: ffffac887314f480

    BUGCHECK_P2: 0

    BUGCHECK_P3: 0

    BUGCHECK_P4: 0

    PROCESS_NAME: services.exe

    CRITICAL_PROCESS: services.exe

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

    ERROR_CODE: (NTSTATUS) 0x784c2080 - <Unable to get error code text>

    CRITICAL_PROCESS_REPORTGUID: {edf33d86-23ed-4a74-9c47-1ee55f03b7b6}

    IMAGE_NAME: ntdll.dll

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    MODULE_NAME: ntdll

    FAULTING_MODULE: 00007ff642240000 services

    CPU_COUNT: 4

    CPU_MHZ: af8

    CPU_VENDOR: GenuineIntel

    CPU_FAMILY: 6

    CPU_MODEL: 4e

    CPU_STEPPING: 3

    CPU_MICROCODE: 6,4e,3,0 (F,M,S,R) SIG: C6'00000000 (cache) C6'00000000 (init)

    BLACKBOXBSD: 1 (!blackboxbsd)


    BLACKBOXPNP: 1 (!blackboxpnp)


    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

    BUGCHECK_STR: 0xEF

    CURRENT_IRQL: 0

    ANALYSIS_SESSION_HOST: <removed>

    ANALYSIS_SESSION_TIME: 05-23-2019 10:36:50.0714

    ANALYSIS_VERSION: 10.0.18362.1 amd64fre

    CONTEXT: 000000000006001a -- (.cxr 0x6001a)
    Unable to read context, NTSTATUS 0xC0000147

    LAST_CONTROL_TRANSFER: from fffff8073029bedd to fffff8072fbc2b40

    STACK_TEXT:
    ffffaa03`d16b7838 fffff807`3029bedd : 00000000`000000ef ffffac88`7314f480 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
    ffffaa03`d16b7840 fffff807`30199a99 : 00000000`00000000 fffff807`2fa5c6b5 ffffac88`7314f480 fffff807`2fa5c5b4 : nt!PspCatchCriticalBreak+0xfd
    ffffaa03`d16b78e0 fffff807`3000172c : ffffac88`00000000 00000000`00000000 ffffac88`7314f480 ffffac88`7314f758 : nt!PspTerminateAllThreads+0x1994e5
    ffffaa03`d16b7950 fffff807`30003269 : ffffffff`ffffffff ffffaa03`d16b7a80 ffffac88`7314f480 fffff807`2ffc3a01 : nt!PspTerminateProcess+0xe0
    ffffaa03`d16b7990 fffff807`2fbd3d85 : ffffac88`0000032c ffffac88`784c2080 ffffac88`7314f480 000000b0`002ff60c : nt!NtTerminateProcess+0xa9
    ffffaa03`d16b7a00 00007ffe`1e74fbe4 : 00007ffe`1e7c0d4b 00007ffe`1e7f111c 000000b0`002ff5d0 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
    000000b0`002fd748 00007ffe`1e7c0d4b : 00007ffe`1e7f111c 000000b0`002ff5d0 00000000`00000000 00000000`00000009 : ntdll!NtTerminateProcess+0x14
    000000b0`002fd750 00007ffe`1e7577ae : 00007ffe`1e7f111c 00000000`0000000a 000001e1`bf48a440 00000000`beef8600 : ntdll!TppWorkerpInnerExceptionFilter+0x5b
    000000b0`002fd780 00007ffe`1e73fd26 : 00000000`00000001 00000000`00000c70 000000b8`6e4f1000 00000000`000011c0 : ntdll!TppWorkerThread$filt$5+0x19
    000000b0`002fd7c0 00007ffe`1e74f242 : 00007ffe`1e7f11cc 000000b0`002fe4b0 000000b0`002ff5d0 00000000`00000000 : ntdll!_C_specific_handler+0x96
    000000b0`002fd830 00007ffe`1e75467f : 00000000`00000000 000000b0`002fddd0 00000000`00000000 00007ffe`1e6b0000 : ntdll!_GSHandlerCheck_SEH+0x6a
    000000b0`002fd860 00007ffe`1e6b4bef : 000000b0`002fddd0 00000000`00000000 00007ffe`1e81dc54 00007ffe`1e6b0000 : ntdll!RtlpExecuteHandlerForException+0xf
    000000b0`002fd890 00007ffe`1e7533ee : 00000000`00000000 00000000`0006001a 00000000`0000042d 00000000`00000001 : ntdll!RtlDispatchException+0x40f
    000000b0`002fdfc0 00007ff6`42246dd3 : 00007ff6`422d8000 00007ff6`422c1a18 00007ff6`422c1a18 00007ff6`422473b7 : ntdll!KiUserExceptionDispatch+0x2e
    000000b0`002fe760 00007ff6`422494a8 : 000001e1`bf068ae0 000000b0`002fe950 000001e1`bf4fa400 000000b0`00000001 : services!ScLogonService+0x21f
    000000b0`002fe850 00007ff6`4224bd35 : 00000000`00000000 000000b0`002fed40 00000000`00000000 000001e1`bf3ab720 : services!CWin32ServiceRecord::LogonAndStartImage+0x2bc
    000000b0`002fec40 00007ff6`422490e5 : 000000b0`00000000 000001e1`bf2c9900 000000b0`002fef90 00000000`00000001 : services!CWin32ServiceRecord::StartInternal+0x2a5
    000000b0`002fef40 00007ff6`42248d60 : 00000000`00000000 000001e1`bf2c9900 000000b0`002feff0 00007ff6`422d8000 : services!CServiceRecord::Start+0x95
    000000b0`002fefa0 00007ff6`4224d4fd : 00007ff6`422bf898 000001e1`00000000 00000000`00000000 00000000`00000000 : services!ScStartMarkedServicesInServiceSet+0x17c
    000000b0`002ff030 00007ff6`4225503e : 000001e1`bf06e890 000000b0`002ff148 00007ff6`00000080 000001e1`00000000 : services!ScStartServicesInStartList+0x28d
    000000b0`002ff110 00007ff6`42256636 : 00000000`00000000 000001e1`00000000 00000000`00000000 00000000`00000024 : services!ScStartServiceAndDependencies+0x1be
    000000b0`002ff1e0 00007ffe`1e72835b : 000001e1`bf506c50 000001e1`bf506c50 00000000`7ffe0386 00000000`00000000 : services!CDelayStartContext:Windows 10 Update 1809 Fails: 0xc1900101 CRITICAL_PROCESS_DIED ntfs.sys :perform+0x326
    000000b0`002ff510 00007ffe`1e72527c : 000001e1`bf505a80 000001e1`bf506c50 00000000`00000000 00000000`00000102 : ntdll!RtlpTpWaitCallback+0x9b
    000000b0`002ff580 00007ffe`1e7005c4 : 000001e1`bf002458 000001e1`bf4597c0 00000000`00000000 000001e1`bf002458 : ntdll!TppExecuteWaitCallback+0xa4
    000000b0`002ff5d0 00007ffe`1ba47e94 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!TppWorkerThread+0x644
    000000b0`002ff8c0 00007ffe`1e71a251 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : KERNEL32!BaseThreadInitThunk+0x14
    000000b0`002ff8f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x21


    THREAD_SHA1_HASH_MOD_FUNC: 577b658ba21128f54c1a9a5848bea60644e0a62a

    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: f1a9817ee76f2564a64f8bbc4812e90a661ada73

    THREAD_SHA1_HASH_MOD: 1b5ee7059e0165cbb2715ad60f28b36db6172a45

    FOLLOWUP_IP:
    ntdll!NtTerminateProcess+14
    00007ffe`1e74fbe4 c3 ret

    FAULT_INSTR_CODE: c32ecdc3

    SYMBOL_STACK_INDEX: 6

    SYMBOL_NAME: ntdll!NtTerminateProcess+14

    FOLLOWUP_NAME: MachineOwner

    STACK_COMMAND: .cxr 0x6001a ; kb

    BUCKET_ID_FUNC_OFFSET: 14

    FAILURE_BUCKET_ID: 0xEF_services.exe_BUGCHECK_CRITICAL_PROCESS_784c2080_services.exe!ScLogonService_ntdll!NtTerminateProcess

    BUCKET_ID: 0xEF_services.exe_BUGCHECK_CRITICAL_PROCESS_784c2080_services.exe!ScLogonService_ntdll!NtTerminateProcess

    PRIMARY_PROBLEM_CLASS: 0xEF_services.exe_BUGCHECK_CRITICAL_PROCESS_784c2080_services.exe!ScLogonService_ntdll!NtTerminateProcess

    TARGET_TIME: 2019-05-22T23:13:58.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: 1979-02-20 19:36:42

    BUILDDATESTAMP_STR: 180914-1434

    BUILDLAB_STR: rs5_release

    BUILDOSVER_STR: 10.0.17763.1.amd64fre.rs5_release.180914-1434

    ANALYSIS_SESSION_ELAPSED_TIME: 2477

    ANALYSIS_SOURCE: KM

    FAILURE_ID_HASH_STRING: km:0xef_services.exe_bugcheck_critical_process_784c2080_services.exe!sclogonservice_ntdll!ntterminateprocess

    FAILURE_ID_HASH: {822399f6-6f4f-70d5-1207-38746fee0ddb}

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

    lmv m ntfs - 0: kd> start end module name
    fffff807`3cb40000 fffff807`3cdcd000 Ntfs (deferred)
    Image path: \SystemRoot\System32\Drivers\Ntfs.sys
    Image name: Ntfs.sys
    Image was built with /Brepro flag.
    Timestamp: E2059A47 (This is a reproducible build file hash, not a timestamp)
    CheckSum: 0028E511
    ImageSize: 0028D000
    File version: 10.0.17763.168
    Product version: 10.0.17763.168
    File flags: 0 (Mask 3F)
    File OS: 40004 NT Win32
    File type: 3.7 Driver
    File date: 00000000.00000000
    Translations: 0409.04b0
    Information from resource tables:
    CompanyName: Microsoft Corporation
    ProductName: Microsoft« Windows« Operating System
    InternalName: ntfs.sys
    OriginalFilename: ntfs.sys
    ProductVersion: 10.0.17763.168
    FileVersion: 10.0.17763.168 (WinBuild.160101.0800)
    FileDescription: NT File System Driver
    LegalCopyright: ⌐ Microsoft Corporation. All rights reserved.
    ||. - 0: kd> . 0 64-bit Kernel bitmap dump: C:\$WINDOWS.~BT\Sources\Rollback\setupmem.dmp

    :)
     
    WesleyGr, May 23, 2019
    #1

  2. Windows 10 1809 update fails with message 0xc1900101.

    When running the update for Windows 10 1809 it fails and submits this message 0xc1900101. How do I repair this issue,.
     
    MichaelManlove1, May 23, 2019
    #2
  3. Windows 10 1809 update fails with message 0xc1900101.

    I first tried to install Windows 10 update Version 1809 twice on 4th October 2018 with message 0xc1900101.

    A couple of days after my failed second attempt I learned of issues with this update so I stopped trying until mid-December.

    I have lost track of the number of failed attempts since then.

    Windows Update does not recognise that Version 1809 exists. I then tried using Windows 10 update assistant. Downloading V 1809 was fine but when it came to installing the update it failed at 42% of installation and would begin to undo the changes and bring
    me back to V 1803.

    As stated, I tried many times without Windows 10 update assistant. I tried many times with the assistant as well but come the dreaded figure of 42% installation completion it would fail and begin to undo the changes and back to V 1803.

    In my Update history the following is written:

    Feature Updates (1)

    ˅ Feature update to Windows 10, version 1809 (2)

    Last failed install attempt on 04/10/2018 - 0xc1900101

    See what's new in this update

    Help!!!!
     
    RemoCostantini, May 23, 2019
    #3
  4. Windows 10 Update 1809 Fails: 0xc1900101 CRITICAL_PROCESS_DIED ntfs.sys

    Unable to upgrade one of the system to Windows 10 Update Error 0xC1900101 - 0x20004

    Thank you for the reply. I read both of those threads already.

    1. Resetting BIOS. I flashed BIOS to the latest version. Currently running default settings. No change.

    2. Andre da Costa brings up a list of reasons. For error 0xC1900101-0x20017 he says refer to error 0xc000021a.

    2a. Regarding his troubleshooting steps for error 0xc000021a. He says to wipe the drive and switch from NTFS to GPT. This is incorrect. If this was true, then no one could update from Windows 7 to Windows 10 without a clean install. Beyond which, I updated
    my first desktop from Windows 7 to Windows 10 when it was running Windows 7 on NTFS.

    2b. Regarding his additional troubleshooting steps for error 0xC1900101-0x20017. He has a number of suggestions, such as disabling peripherals. I tried all of these for both .iso and USB installs. No luck.

    Any other suggestions?
     
    Patrick M. Nagel, May 23, 2019
    #4
Thema:

Windows 10 Update 1809 Fails: 0xc1900101 CRITICAL_PROCESS_DIED ntfs.sys

Loading...
  1. Windows 10 Update 1809 Fails: 0xc1900101 CRITICAL_PROCESS_DIED ntfs.sys - Similar Threads - Update 1809 Fails

  2. Windows 10 update from 1809 to 1903 fails with 0xc1900101

    in Windows 10 Installation and Upgrade
    Windows 10 update from 1809 to 1903 fails with 0xc1900101: I have a dual boot system with Opensuse Tumbleweed and Windows 10 Pro. During the previous feature update from 1803 to 1809 I could not get it to work and resorted to a clean reinstall. I would like to avoid that if possible. The error code 0xc1900101 seems to suggest a...
  3. Windows 10 1809 update fails with message 0xc1900101.

    in Windows 10 Installation and Upgrade
    Windows 10 1809 update fails with message 0xc1900101.: Windows Update does not recognise that Version 1809 exists. I then tried using Windows 10 update assistant. Downloading V 1809 was fine but when it came to installing the update it failed at 42% of installation and would begin to undo the changes and bring me back to V 1803....
  4. Windows 10 version 1809 update always fail (0xc1900101)

    in Windows 10 Installation and Upgrade
    Windows 10 version 1809 update always fail (0xc1900101): Hi everyone, Per subject title, my computer has always failed with Windows 10 version 1809 update (0xc1900101). I would really appreciate if someone can help look at the following from the setuperr.log from my most recent failed install and see what might be the possible...
  5. Feature update to Windows 10, version 1809 failed to install - 0xc1900101

    in Windows 10 Installation and Upgrade
    Feature update to Windows 10, version 1809 failed to install - 0xc1900101: This huge update, which I have now twice tried to install, effectively renders my PC unbootable. Midway through the installation, after a few planned reboots, it leaves me with a blank screen and a movable mouse pointer. The power button is not working and it takes two or...
  6. Windows 10 1809 Update Failure 0xc1900101

    in Windows 10 Installation and Upgrade
    Windows 10 1809 Update Failure 0xc1900101: I'm looking for help installing Windows 10 1809. MY PC is custom built, about a year old and has i7-6850 processor with 32 GB memory and Windows 10 Pro x64 v1803 build 17134.472 installed on 5/24/2018. 1809 install has failed twice to install. I was present during the second...
  7. Windows 10 1809 update fails with message 0xc1900101.

    in Windows 10 Installation and Upgrade
    Windows 10 1809 update fails with message 0xc1900101.: I first tried to install Windows 10 update Version 1809 twice on 4th October 2018 with message 0xc1900101. A couple of days after my failed second attempt I learned of issues with this update so I stopped trying until mid-December. I have lost track of the number of failed...
  8. Windows 10 Updates 1803 and 1809 Fail to install - Error 0xC1900101 0x30017

    in Windows 10 Installation and Upgrade
    Windows 10 Updates 1803 and 1809 Fail to install - Error 0xC1900101 0x30017: I have tried everything recommended in similar threads to install updates 1803 and 1809 (my PC is still stuck at 1709): PC is Dell XPS 8700 with i7-4790, 24GB of RAM, 64-bit processor, 64-bit Windows 10 OS, Latest BIOS A13 Deleted all old installation directories There is...
  9. Windows 10 Update 1809 Failed 0xc1900101

    in Windows 10 Installation and Upgrade
    Windows 10 Update 1809 Failed 0xc1900101: I'm getting the above error code when trying to update to Windows 10 version 1809. I've tried updating through both Windows Update and the Media Creation Tool, but get the same error at the time of the first reboot. Ideas?...
  10. 1809 update Failed to install on ‎04-‎Oct-‎2018 - 0xc1900101

    in Windows 10 Installation and Upgrade
    1809 update Failed to install on ‎04-‎Oct-‎2018 - 0xc1900101: The 1809 update Failed to install on ‎04-‎Oct-‎2018 - 0xc1900101 Any idea what this code means? https://answers.microsoft.com/en-us/windows/forum/windows_10-update/1809-update-failed-to-install-on-04-oct-2018/5a211fd2-d209-4e53-890d-37d6ed31c27e

Users found this page by searching for:

  1. 0xc190101 0x30017 C3/C6

    ,
  2. windows 10 upgrade setupmem.dmp arg1: ffffa30f3900d080 a critical process died