Windows Update 1809 Fails - Error 0xc00000fd

Page 3 of 4 FirstFirst 1234 LastLast

  1. Posts : 41,474
    windows 10 professional version 1607 build 14393.969 64 bit
       #21

    See this link or customized test settings:
    Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community

    All non-Microsoft drivers are tested simultaneously with approximately nineteen simultaneous test settings.

    Currently there are three customized test settings. Increase the number of simultaneous tests by 4 - 6 per hour so that there are a total of 19 simultaneous tests. If the computer becomes suffers too much or if the boot becomes too slow the settings can be recustomized.
      My Computer


  2. Posts : 1,345
    Windows 10 Pro 64-bit
       #22

    [QUOTE=otronics;1588440]* Thanks for the RAM details. I wonder if taking out the 4GB I added would make the update work? I don't think contacting Crucial will work now - out of warranty. /QUOTE]
    You can use either set but I wouldn't make any changes w/o zbook's advice during the troubleshooting procedures.
      My Computer


  3. Posts : 41,474
    windows 10 professional version 1607 build 14393.969 64 bit
       #23

    Mismatched RAM can cause unexpected shutowns/restarts with or without BSOD.
    This is with a test pass using Memtest as the algorithm is not testing for this type of problem.

    At this time the tool Windows driver verifier is testing all of the drivers.
    If there are computer problems (stability versus instability including freezing/hangs) then one of the newer RAM module will be uninstalled to evaluate the computer environment.
      My Computer


  4. Posts : 67
    Windows 10 Home 64-bit
    Thread Starter
       #24

    Driver Verifier now switched off. It was for about 48 hours.

    Blue screen error was:

    Driver detected violation iusb3hcs.sys
      My Computer


  5. Posts : 41,474
    windows 10 professional version 1607 build 14393.969 64 bit
       #25

    See post #14 and step #14:

    14) After any BSOD:
    a) Run the BETA log collector and post a new zip into the thread
    b) Open file explorer > this PC > C: > in the right upper corner search for: C:\windows\memory.dmp > if the file size is < 1.5 GB then zip and post a separate share link into the thread using one drive, drop box, or google drive


    Please restart Windows driver verifier so that it runs an additional 36 hours after the last BSOD.

    Use the nineteen customized simultaneous settings in this link:
    Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community

    The goal while using the tool is to create dump files.
    The dump files are then debugged to find misbehaving drivers and hardware.

    Immediately after each BSOD run the BETA log collector and upload the memory.dmp so that the files do not disappear and are not overwritten.
      My Computer


  6. Posts : 67
    Windows 10 Home 64-bit
    Thread Starter
       #26

    Got it.

    Will keep trying.

    I had a look for dump files after the BSOD but there were none.

    BETA log collector files attached if they are of any use though.
    Windows Update 1809 Fails - Error 0xc00000fd Attached Files
      My Computer


  7. Posts : 41,474
    windows 10 professional version 1607 build 14393.969 64 bit
       #27

    1) Repeat the chkdsk scan:

    Open administrative command prompt and type or copy and paste: chkdsk /r /v C:
    This may take many hours so plan to run overnight


    C:\WINDOWS\system32>chkdsk /r /v C:
    The type of the file system is NTFS.
    Cannot lock current drive.

    Chkdsk cannot run because the volume is in use by another
    process. Would you like to schedule this volume to be
    checked the next time the system restarts? (Y/N)

    Type: Y
    reboot

    2) Use the text and images in this link to find the chkdsk report in the event viewer > copy and paste > notepad > post a share link into the thread using one drive, drop box, or google drive

    Read Chkdsk Log in Event Viewer in Windows 10 | Tutorials


    3) Open control panel > category > programs > add remove programs > post images into the thread

    4) Open device manager > click view > click show hidden devices > manually expand all rows > look for any row displaying a yellow triangle with black exclamation mark or unknown device > post images into the thread

    5) Open Ccleaner > click windows tab > scroll down to system and advanced > post an image into the thread

    6) During the troubleshooting process please do not use disk cleanup

    7) The logs displayed that Windows driver verifier was off.

    Please use the customized settings in this link to run Windows driver verifier continuously for 48 hours:

    Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community

    8) Run HD Sentinel (free or trial version) > post images into the thread for results on these tabs:
    a) overview
    b) temperature
    c) SMART
    For the smart results please widen the columns so that the characters in each row are in full view

    9) Open administrative command prompt and type or copy and paste:
    10) sfc /scannow
    11) dism /online /cleanup-image /restorehealth
    12) bcdedit /enum all
    13) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread


    Code:
    Event[23288]:
      Log Name: System
      Source: Microsoft-Windows-StartupRepair
      Date: 2019-03-06T20:40:38.604
      Event ID: 1002
      Task: N/A
      Level: Information
      Opcode: Info
      Keyword: N/A
      User: S-1-5-18
      User Name: NT AUTHORITY\SYSTEM
      Computer: Server
      Description: 
    Start-up Repair failed.
    
    Event[23289]:
      Log Name: System
      Source: Microsoft-Windows-StartupRepair
      Date: 2019-03-06T20:40:38.604
      Event ID: 1121
      Task: N/A
      Level: Information
      Opcode: Info
      Keyword: N/A
      User: S-1-5-18
      User Name: NT AUTHORITY\SYSTEM
      Computer: Server
      Description: 
    The following file necessary for Windows start-up was corrupt: e:\boot\resources\custom\bootres.dll
    Code:
    Event[21798]:
      Log Name: System
      Source: Microsoft-Windows-Kernel-General
      Date: 2019-03-04T15:38:27.480
      Event ID: 5
      Task: N/A
      Level: Error
      Opcode: Info
      Keyword: N/A
      User: S-1-5-18
      User Name: NT AUTHORITY\SYSTEM
      Computer: Server
      Description: 
    {Registry Hive Recovered} Registry hive (file): '\??\Volume{303b50c8-f0eb-11e1-b98c-806e6f6e6963}\System Volume Information\SPP\SppCbsHiveStore\{cd42efe1-f6f1-427c-b004-033192c625a4}{4ABADABD-63D0-4F45-B6CA-6B4A88F31F44}' was corrupted and it has been recovered. Some data might have been lost.
    Code:
    Event[21759]:
      Log Name: System
      Source: Microsoft-Windows-Kernel-General
      Date: 2019-03-04T15:23:14.301
      Event ID: 5
      Task: N/A
      Level: Error
      Opcode: Info
      Keyword: N/A
      User: S-1-5-18
      User Name: NT AUTHORITY\SYSTEM
      Computer: Server
      Description: 
    {Registry Hive Recovered} Registry hive (file): '\SystemRoot\System32\Config\SOFTWARE' was corrupted and it has been recovered. Some data might have been lost.
    Last edited by zbook; 07 Mar 2019 at 13:22.
      My Computer


  8. Posts : 67
    Windows 10 Home 64-bit
    Thread Starter
       #28

    Chkdsk hangs at 10%.

    I'm going to have to go the reset route and will try and upgrade from there.

    A huge pain but I get the feeling that will take slightly less time than troubleshooting.

    Will let you know how I get on as there will be problems I'm sure.
      My Computer


  9. Posts : 41,474
    windows 10 professional version 1607 build 14393.969 64 bit
       #29

    It is normal behavior for chkdsk to:
    a) have the % counter rise to a low number in the teens while completing the fix and restore.
    b) this may take many hours.

    If you want to run the tool and view the ETA (estimated time) then it can be run in Windows RE.
    This is accomplished using a bootable Windows 10 iso > command prompt > chkdsk /r /v with the applicable partition drive letter.

    Running chkdsk /r /v overnight on current drives typically is an overnight process allowing 6 - 8 hours for the tool to run.
    With older drives or drives that had major problems the tool could take days to run. This rarely happens with current drives.
    See if you can run the chkdsk /r /v overnight and if necessary a portion of the following day.
      My Computer


  10. Posts : 67
    Windows 10 Home 64-bit
    Thread Starter
       #30

    This thread can be closed now - resetting the PC and then updating has (surprisingly) solved the problem.

    Thanks for your help but this seemed the 'quickest' way to go in the end.
      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 22:55.
Find Us




Windows 10 Forums