Windows 10 Version 1803 update fails consistently (take 2)

Page 1 of 2 12 LastLast

  1. Posts : 6
    Windows 10 Pro
       #1

    Windows 10 Version 1803 update fails consistently (take 2)


    Hi TenForums,

    About a year and a half ago, I ran into issues attempting to update to Windows 10 Version 1709 from Version 1607. I reached out for help from the Microsoft community (answers.microsoft.com) with no luck. The saga is documented here. Ultimately, I resorted to backing up my data, reformatting my hard drives and reinstalling Windows 10 with the most up-to-date ISO - created using the Windows 10 Media Creation Tool on a USB drive.

    Fast forward to today, and I'm running into the same issues again trying to update to Windows 10 Version 1803 regardless of which installation path I take (Windows Update, Upgrade Assistant, ISO file, etc.).

    Feature update to Windows 10, version 1803 - Error 0x80240031
    Windows 10 Version 1803 update fails consistently (take 2)-screenshot-2019-08-31-09.18.52.png
    Windows 10 Version 1803 update fails consistently (take 2)-screenshot-2019-08-31-09.19.02.png

    This is the output from the Windows Update Troubleshooter:
    ElevatedDiagnostic.pdf

    Installation still fails with the same error message after all the "issues found" were "fixed":
    Windows 10 Version 1803 update fails consistently (take 2)-screenshot-2019-08-31-09.29.40.png

    The only thing unique about my Windows 10 installation is that I followed Kari's tutorial on moving the Users folder to another location using "Method One" (clean installation).

    It would be great if I could get some help with figuring out what is preventing me from upgrading my Windows version so that I can stay up-to-date with all the latest security patches as well as use programs that depend on the latest version of Windows 10 (ie. Docker). The last thing I want is to require needing to resort to a clean installation every time a new major Windows 10 version comes out.

    Happy to provide any information necessary to troubleshoot this issue.

    Thanks in advance for any help!
      My Computer


  2. Posts : 6,247
    Windows 11 Pro - Windows 7 HP - Lubuntu
       #2

    Welcome to the Forum

    I also have used Kari tutorial to move \Users to another disk and had no problem updating from 1803 to 1809 and 1903.
    I always do my updates by downloading the ISO, mounting it and run setup.

    Any reason you didn't use 1809 or 1903?
    As you have tried Windows Update, Upgrade Assistant, ISO file, etc. I can only think that it fails because 1803 is no longer supported.
    How did you blocked WU so id didn't do the update on the regular basics?
    Last edited by Megahertz; 31 Aug 2019 at 20:50.
      My Computers


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

    Sorry, that's my mistake - I didn't explicitly only try to update to 1803...I believe that maybe Windows Update was trying to install 1803, 1809 , and 1903 in sequential order and got held up with 1803.

    Most recently, I did try to use Windows 10 Update Assistant to install 1903, which also failed:
    Windows 10 Version 1803 update fails consistently (take 2)-screenshot-2019-08-31-20.03.11.png
    Windows 10 Version 1803 update fails consistently (take 2)-screenshot-2019-08-31-20.07.26.png

    I did block Windows Update for a while back when 1803 consistently failed to install, but I've since unblocked it and it still continues to error out even if I attempt to install the latest version.
      My Computer


  4. Posts : 41,413
    windows 10 professional version 1607 build 14393.969 64 bit
       #4

    0xc8007001f is only a result code.
    When troubleshooting upgrade failures all attempted upgrades should be performed with a bootable Windows 10 iso.

    0xc8007001f often can be related to problems with the registry or a device.

    For all tests / steps post images of commands and results into the thread.
    For any problems posting images please use share links (one drive, drop box, or google drive)

    1) There are log collectors used in another forum.
    Run each V2 and DM and upload results into this thread.
    BSOD - Posting Instructions

    2) Find two flash drives that you can format (> or = 8 GB)

    3) Create a bootable Windows 10 iso with the same version

    Windows Download - #1 Windows ISO Download Source
    Microsoft Windows and Office ISO Download Tool
    TechBench by WZT (v4.1.1)

    4) Create a bootable Windows 10 iso build 1903

    https://www.microsoft.com/en-us/soft...load/windows10
    Download Windows 10 ISO File
    Create Bootable USB Flash Drive to Install Windows 10

    5) Run through this Windows upgrade check list:

    Code:
    UPGRADE CHECK LIST:
    Run through this check list before the next upgrade attempt:
    
    1) remove nonessential hardware
    docks
    USB devices
    printers
    headset
    speakers
    joysticks
    projectors
    scanners
    plotters
    portable optical drives (CD, DVD)
    microphones
    cameras
    webcams
    smartphones
    bluetooth devices
    USB drives (other than a windows 10 iso if used for the upgrade)
    USB Wireless Mouse or Keyboard Receiver, USB Wireless Network Card
    secondary monitors
    
    
    2) These should be the only attached devices:
    wired mouse
    wired keyboard
    monitor
    
    Any of these that have been done in the past week are not necessary to repeat:
    
    
    3) open administrative command prompt and type or copy and paste: (repair file system)
    chkdsk /r /v 
    This may take many hours so plan to run overnight
    Find the chkdsk report in the event viewer using the information in this link and post into the thread:
    Read Chkdsk Log in Event Viewer in Windows 10 Performance Maintenance Tutorials
    https://www.tenforums.com/tutorials/40822-read-chkdsk-log-event-viewer-windows-10-a.html 
    
    4) open administrative command prompt and copy and paste: (repair operating system)
    sfc /scannow 
    dism /online /cleanup-image /restorehealth 
    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
    
    5) update windows (have all recommended updates installed) and reboot after updates
    
    6) List and uninstall all non-Microsoft antivirus software
    (This includes always on and manual software.)
    (This includes running the applicable antivirus uninstall tools for any AV that could have been incompletely unistalled)
    
    7) List and uninstall all non-Microsoft firewall software
    
    8) List all Microsoft and non-Microsoft drive encryption software. 
    Uninstall all non-Microsoft disk encryption software
    
    9) Run disk cleanup to clean temporary and system files
    
    10) Verify that the drive has > 30 GB free space (At least 25 GB is needed for creating dumps)
    
    11) Place the computer in clean boot:
    https://support.microsoft.com/en-us/help/929135/how-to-perform-a-clean-boot-in-windows
    How to perform a Clean Boot in Windows 10 - TechNet Articles - United States (English) - TechNet Wiki
    https://social.technet.microsoft.com/wiki/contents/articles/29876.how-to-perform-a-clean-boot-in-windows-10.aspx
    https://www.tenforums.com/tutorials/41804-perform-clean-boot-windows-10-troubleshoot-software-conflicts.html
    
    
    12) Detach all SATA devices other than the disk drive that has the Windows operating system
    (Make sure that the only disk drive that is attached to the computer at the time of the upgrade attempt is the disk drive containing Windows)
    (Other disk drives may be able to be detached by disconnecting cables or if necessary to remove the drive from the computer)
    
    13) Make sure that there is no metered connection:  https://support.microsoft.com/en-us/help/17452/windows-metered-internet-connections-faq


    6) Perform an in place upgrade repair with the identical iso.

    Repair Install Windows 10 with an In-place Upgrade

    7) If the in place upgrade repair is successful with the identical iso then repeat the in place upgrade repair with the 1903 iso.
      My Computer


  5. Posts : 6,247
    Windows 11 Pro - Windows 7 HP - Lubuntu
       #5

    Zbook,
    To do a Repair install on the current install (1803), would the OP need to make a USB boot able disk or he can download the iso, mount the iso and run setup?
    Once the 1803 is fixed , can he do the same with 1903 (download the iso, mount the iso and run setup)?
      My Computers


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

    The iso can be downloaded to either a flash drive or to the desktop.

    The flash drive is a better option if there is possible need for the Windows advanced troubleshooting menu.
    For example in case there is boot failure, corruption of the operating system, drive file system, etc. and the end user cannot open the windows advanced troubleshooting menu on the computer.
      My Computer


  7. Posts : 6
    Windows 10 Pro
    Thread Starter
       #7

    Here are the results from V2:
    GRAPHITE-780T-(2019-09-01_18-44-53).zip

    I get an error when trying to run DM:
    Windows 10 Version 1803 update fails consistently (take 2)-screenshot-2019-09-01-18.53.22.png

    In the process of finding the iso that matches my existing system, I learned that I actually still have 1607 installed and not 1709 :
    Windows 10 Version 1803 update fails consistently (take 2)-screenshot-2019-09-01-18.57.00.png

    Unfortunately, none of the tools you linked have 1607 available for download. What should I do in this case? Should I skip the in place repair for 1607 and follow your instructions doing the in place repair for 1903?
      My Computer


  8. Posts : 6,247
    Windows 11 Pro - Windows 7 HP - Lubuntu
       #8

    Something is strange: Build 14393.2214 is a April 17, 2018
    https://support.microsoft.com/en-us/...date-kb4093120

    The link for 1607 Win10_1607_English_x64.iso
      My Computers


  9. Posts : 6
    Windows 10 Pro
    Thread Starter
       #9

    zbook, I followed your instructions as best I could trying to do the in place repair with both 1607 as well as 1903 with all peripherals unplugged except for mouse, keyboard, and monitor.

    Installation failed again for both attempts.
      My Computer


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

    1) The computer has been having BSOD.
    2) The V2 log collector collected BSOD from 3/14 to 8/31.
    3) All bugchecks were 139:
    KERNEL_SECURITY_CHECK_FAILURE

    Code:
             Operating System: Windows 10 Pro 64-bit (10.0, Build 14393) (14393.rs1_release_1.180402-1758)
    Code:
    Installed Physical Memory (RAM)	128 GB

    4) For all steps / tests post images into the thread.

    5) If there are any problems posting images use share links (One drive, Drop box Google drive, or Amazon).

    6) All modifications, software and hardware can be modified after troubleshooting has been completed.

    7) The computer has 8 RAM modules that are 16 GB each.
    Remove all RAM modules.
    Label all modules and DIMM.
    Re-seat two modules.
    If the owners manual has a recommended DIMM when two modules are used please use these slots.

    8) Open administrative command prompt and type or copy and paste:
    9) sfc /scannow
    10) dism /online /cleanup-image /scanhealth
    11) dism /online /cleanup-image /restorehealth
    12) sfc /scannow
    13) chkdsk /scan
    14) wmic recoveros set autoreboot = false
    15) wmic recoveros set DebugInfoType = 7
    16) bcdedit /enum {badmemory}

    17) 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

    18) Make sure that there is no over clocking while troubleshooting.

    19) Sometimes there are problems in the bios that produce bsod.

    20) The BIOS: Version/Date American Megatrends Inc. 1003, 9/13/2016
    Upgrade the BIOS: 1003 > 1903
    This should be the most up to date non-beta BIOS

    Code:
    Improve system performance
    Improved DRAM stability
    Fix Logitech devices issue.
    Fix Intel I211 Lan issue*
    Fixed memtest86 issue
    Fixed Plextor device issue
    Improve system performance
    Add in turn-off function of LED under S3/S4/S5 status.
    Fixed Samsung device (SM961, printer) issues.
    Improve system stability

    ROG RAMPAGE V EDITION 10 Driver & Tools | Motherboards | ASUS USA


    21) To ensure that there are no improper bios settings please reset the bios.

    22) Sometimes there can be failure to boot after resetting the bios.

    23) Backup the computer files to another drive or to the cloud.

    24) Make a backup image using Macrium:
    Macrium Software | Macrium Reflect Free:
    Macrium Software | Macrium Reflect Free

    25) Create a brand new restore point.
    Create System Restore Point in Windows 10

    How to Clear Your Computers CMOS to Reset BIOS Settings:
    How to Clear Your Computer’s CMOS to Reset BIOS Settings
    3 Ways to Reset Your BIOS - wikiHow:
    3 Ways to Reset Your BIOS - wikiHow


    26) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings

    a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery window into the thread

    b) > on the advanced tab under performance > click on settings > on the performance options window > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory window into the thread

    27) Read this link on Windows driver verifier: (do not use the tool until it is communicated in the thread)
    Enable and Disable Driver Verifier in Windows 10

    28) Learn how to use the Windows advanced troubleshooting menu to turn off and recover from using the tool.

    29) For any BSOD:

    a) run the V2 log collector to collect new log files

    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 > post a separate share link into the thread using one drive, drop box, or google drive

    30) Run setupdiag > post a share link into the thread

    31) List and uninstall all non-Microsoft antivirus software
    (This includes always on and manual software.)
    (This includes running the applicable antivirus uninstall tools for any AV that could have been incompletely unistalled)

    32) List and uninstall all non-Microsoft firewall software

    33) List all Microsoft and non-Microsoft drive encryption software.
    Uninstall all non-Microsoft disk encryption software

    34) Open administrative command prompt and type or copy and paste:
    chkdsk /r /v
    This may take hours to run so plan to run overnight.
    Run on all drives using the syntax: chkdsk /r /v C: or chkdsk /r /v D: changing the drive letter to the applicable drive.

    C:\Windows\system32>chkdsk /r /v
    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


    35) Use the information in this link to find the chkdsk report in the event viewer. Copy and paste into notepad > save to desktop > post into the thread using one drive or drop box share link:
    Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials
    Read Chkdsk Log in Event Viewer in Windows 10

    36) Open disk management > by default some columns are compressed > widen each Status and Volume > make sure the contents within the parenthesis are in full view and that none of the characters are cutoff > view disk 0 > widen this row as needed so that all of the characters are in full view > post an image into the thread
    Disk Management - How to Post a Screenshot of

    37) Turn off Windows fast startup:
    Turn On or Off Fast Startup in Windows 10


    Code:
    8/31/2019 12:28 PM	Windows Error Reporting	Fault bucket , type 0&#x000d;&#x000a;Event Name: BlueScreen&#x000d;&#x000a;Response: Not available&#x000d;&#x000a;Cab Id: 0&#x000d;&#x000a;&#x000d;&#x000a;Problem signature:&#x000d;&#x000a;P1: 139&#x000d;&#x000a;P2: 3&#x000d;&#x000a;P3: ffff868189718ec0&#x000d;&#x000a;P4: ffff868189718e18&#x000d;&#x000a;P5: 0&#x000d;&#x000a;P6: 10_0_14393&#x000d;&#x000a;P7: 0_0&#x000d;&#x000a;P8: 256_1&#x000d;&#x000a;P9: &#x000d;&#x000a;P10: &#x000d;&#x000a;&#x000d;&#x000a;Attached files:&#x000d;&#x000a;\\?\C:\Windows\Minidump\083119-13312-01.dmp&#x000d;&#x000a;\\?\C:\Windows\TEMP\WER-15328-0.sysdata.xml&#x000d;&#x000a;\\?\C:\Windows\MEMORY.DMP&#x000d;&#x000a;&#x000d;&#x000a;These files may be available here:&#x000d;&#x000a;C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_139_1bd1463518e34089fbe377c87355e85305993_00000000_cab_128c7975&#x000d;&#x000a;&#x000d;&#x000a;Analysis symbol: &#x000d;&#x000a;Rechecking for solution: 0&#x000d;&#x000a;Report Id: 0d11362a-04be-461f-b685-89cdf064eca5&#x000d;&#x000a;Report Status: 2048&#x000d;&#x000a;Hashed bucket:
    8/31/2019 12:28 PM	Windows Error Reporting	Fault bucket , type 0&#x000d;&#x000a;Event Name: BlueScreen&#x000d;&#x000a;Response: Not available&#x000d;&#x000a;Cab Id: 0&#x000d;&#x000a;&#x000d;&#x000a;Problem signature:&#x000d;&#x000a;P1: 139&#x000d;&#x000a;P2: 3&#x000d;&#x000a;P3: ffff868189718ec0&#x000d;&#x000a;P4: ffff868189718e18&#x000d;&#x000a;P5: 0&#x000d;&#x000a;P6: 10_0_14393&#x000d;&#x000a;P7: 0_0&#x000d;&#x000a;P8: 256_1&#x000d;&#x000a;P9: &#x000d;&#x000a;P10: &#x000d;&#x000a;&#x000d;&#x000a;Attached files:&#x000d;&#x000a;\\?\C:\Windows\Minidump\083119-13312-01.dmp&#x000d;&#x000a;\\?\C:\Windows\TEMP\WER-15328-0.sysdata.xml&#x000d;&#x000a;\\?\C:\Windows\MEMORY.DMP&#x000d;&#x000a;&#x000d;&#x000a;These files may be available here:&#x000d;&#x000a;C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_139_1bd1463518e34089fbe377c87355e85305993_00000000_03dc48d0&#x000d;&#x000a;&#x000d;&#x000a;Analysis symbol: &#x000d;&#x000a;Rechecking for solution: 0&#x000d;&#x000a;Report Id: 0d11362a-04be-461f-b685-89cdf064eca5&#x000d;&#x000a;Report Status: 4&#x000d;&#x000a;Hashed bucket:
    8/29/2019 12:36 PM	Windows Error Reporting	Fault bucket , type 0&#x000d;&#x000a;Event Name: BlueScreen&#x000d;&#x000a;Response: Not available&#x000d;&#x000a;Cab Id: 0&#x000d;&#x000a;&#x000d;&#x000a;Problem signature:&#x000d;&#x000a;P1: 139&#x000d;&#x000a;P2: 3&#x000d;&#x000a;P3: ffff8a816e0aaec0&#x000d;&#x000a;P4: ffff8a816e0aae18&#x000d;&#x000a;P5: 0&#x000d;&#x000a;P6: 10_0_14393&#x000d;&#x000a;P7: 0_0&#x000d;&#x000a;P8: 256_1&#x000d;&#x000a;P9: &#x000d;&#x000a;P10: &#x000d;&#x000a;&#x000d;&#x000a;Attached files:&#x000d;&#x000a;\\?\C:\Windows\Minidump\082919-13406-01.dmp&#x000d;&#x000a;\\?\C:\Windows\TEMP\WER-20078-0.sysdata.xml&#x000d;&#x000a;\\?\C:\Windows\MEMORY.DMP&#x000d;&#x000a;&#x000d;&#x000a;These files may be available here:&#x000d;&#x000a;C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_139_93bc744d8af15f59b0d381f5dd3476df56c25d9c_00000000_cab_14587445&#x000d;&#x000a;&#x000d;&#x000a;Analysis symbol: &#x000d;&#x000a;Rechecking for solution: 0&#x000d;&#x000a;Report Id: 8b2d843a-2480-4e2e-98db-2344986a6335&#x000d;&#x000a;Report Status: 2048&#x000d;&#x000a;Hashed bucket:
    8/29/2019 12:35 PM	Windows Error Reporting	Fault bucket , type 0&#x000d;&#x000a;Event Name: BlueScreen&#x000d;&#x000a;Response: Not available&#x000d;&#x000a;Cab Id: 0&#x000d;&#x000a;&#x000d;&#x000a;Problem signature:&#x000d;&#x000a;P1: 139&#x000d;&#x000a;P2: 3&#x000d;&#x000a;P3: ffff8a816e0aaec0&#x000d;&#x000a;P4: ffff8a816e0aae18&#x000d;&#x000a;P5: 0&#x000d;&#x000a;P6: 10_0_14393&#x000d;&#x000a;P7: 0_0&#x000d;&#x000a;P8: 256_1&#x000d;&#x000a;P9: &#x000d;&#x000a;P10: &#x000d;&#x000a;&#x000d;&#x000a;Attached files:&#x000d;&#x000a;\\?\C:\Windows\Minidump\082919-13406-01.dmp&#x000d;&#x000a;\\?\C:\Windows\TEMP\WER-20078-0.sysdata.xml&#x000d;&#x000a;\\?\C:\Windows\MEMORY.DMP&#x000d;&#x000a;&#x000d;&#x000a;These files may be available here:&#x000d;&#x000a;C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_139_93bc744d8af15f59b0d381f5dd3476df56c25d9c_00000000_03dc5b9d&#x000d;&#x000a;&#x000d;&#x000a;Analysis symbol: &#x000d;&#x000a;Rechecking for solution: 0&#x000d;&#x000a;Report Id: 8b2d843a-2480-4e2e-98db-2344986a6335&#x000d;&#x000a;Report Status: 4&#x000d;&#x000a;Hashed bucket:
    3/13/2019 12:21 PM	Windows Error Reporting	Fault bucket , type 0&#x000d;&#x000a;Event Name: BlueScreen&#x000d;&#x000a;Response: Not available&#x000d;&#x000a;Cab Id: 0&#x000d;&#x000a;&#x000d;&#x000a;Problem signature:&#x000d;&#x000a;P1: 139&#x000d;&#x000a;P2: 3&#x000d;&#x000a;P3: ffffb0001ed7aec0&#x000d;&#x000a;P4: ffffb0001ed7ae18&#x000d;&#x000a;P5: 0&#x000d;&#x000a;P6: 10_0_14393&#x000d;&#x000a;P7: 0_0&#x000d;&#x000a;P8: 256_1&#x000d;&#x000a;P9: &#x000d;&#x000a;P10: &#x000d;&#x000a;&#x000d;&#x000a;Attached files:&#x000d;&#x000a;\\?\C:\Windows\Minidump\031319-16000-01.dmp&#x000d;&#x000a;\\?\C:\Windows\TEMP\WER-18109-0.sysdata.xml&#x000d;&#x000a;\\?\C:\Windows\MEMORY.DMP&#x000d;&#x000a;&#x000d;&#x000a;These files may be available here:&#x000d;&#x000a;C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_139_999a4d753fa6d387632abe4214dd2f2e1ddeab20_00000000_cab_14d08220&#x000d;&#x000a;&#x000d;&#x000a;Analysis symbol: &#x000d;&#x000a;Rechecking for solution: 0&#x000d;&#x000a;Report Id: 43be3051-1f2b-433f-99aa-4c35243bebc9&#x000d;&#x000a;Report Status: 2048&#x000d;&#x000a;Hashed bucket:
    3/13/2019 12:20 PM	Windows Error Reporting	Fault bucket , type 0&#x000d;&#x000a;Event Name: BlueScreen&#x000d;&#x000a;Response: Not available&#x000d;&#x000a;Cab Id: 0&#x000d;&#x000a;&#x000d;&#x000a;Problem signature:&#x000d;&#x000a;P1: 139&#x000d;&#x000a;P2: 3&#x000d;&#x000a;P3: ffffb0001ed7aec0&#x000d;&#x000a;P4: ffffb0001ed7ae18&#x000d;&#x000a;P5: 0&#x000d;&#x000a;P6: 10_0_14393&#x000d;&#x000a;P7: 0_0&#x000d;&#x000a;P8: 256_1&#x000d;&#x000a;P9: &#x000d;&#x000a;P10: &#x000d;&#x000a;&#x000d;&#x000a;Attached files:&#x000d;&#x000a;\\?\C:\Windows\Minidump\031319-16000-01.dmp&#x000d;&#x000a;\\?\C:\Windows\TEMP\WER-18109-0.sysdata.xml&#x000d;&#x000a;\\?\C:\Windows\MEMORY.DMP&#x000d;&#x000a;&#x000d;&#x000a;These files may be available here:&#x000d;&#x000a;C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_139_999a4d753fa6d387632abe4214dd2f2e1ddeab20_00000000_03385330&#x000d;&#x000a;&#x000d;&#x000a;Analysis symbol: &#x000d;&#x000a;Rechecking for solution: 0&#x000d;&#x000a;Report Id: 43be3051-1f2b-433f-99aa-4c35243bebc9&#x000d;&#x000a;Report Status: 4&#x000d;&#x000a;Hashed bucket:
    3/14/2019 12:01 PM	Windows Error Reporting	Fault bucket , type 0&#x000d;&#x000a;Event Name: BlueScreen&#x000d;&#x000a;Response: Not available&#x000d;&#x000a;Cab Id: 0&#x000d;&#x000a;&#x000d;&#x000a;Problem signature:&#x000d;&#x000a;P1: 139&#x000d;&#x000a;P2: 3&#x000d;&#x000a;P3: ffffb5000e36b320&#x000d;&#x000a;P4: ffffb5000e36b278&#x000d;&#x000a;P5: 0&#x000d;&#x000a;P6: 10_0_14393&#x000d;&#x000a;P7: 0_0&#x000d;&#x000a;P8: 256_1&#x000d;&#x000a;P9: &#x000d;&#x000a;P10: &#x000d;&#x000a;&#x000d;&#x000a;Attached files:&#x000d;&#x000a;\\?\C:\Windows\Minidump\031419-15484-01.dmp&#x000d;&#x000a;\\?\C:\Windows\TEMP\WER-17484-0.sysdata.xml&#x000d;&#x000a;\\?\C:\Windows\MEMORY.DMP&#x000d;&#x000a;&#x000d;&#x000a;These files may be available here:&#x000d;&#x000a;C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_139_29c475b222e743e6a73c22e2e67b7ec99adbbc8c_00000000_cab_15287937&#x000d;&#x000a;&#x000d;&#x000a;Analysis symbol: &#x000d;&#x000a;Rechecking for solution: 0&#x000d;&#x000a;Report Id: 7dc353b2-3414-4726-9155-75b3d09181f8&#x000d;&#x000a;Report Status: 2048&#x000d;&#x000a;Hashed bucket:
    3/14/2019 12:01 PM	Windows Error Reporting	Fault bucket , type 0&#x000d;&#x000a;Event Name: BlueScreen&#x000d;&#x000a;Response: Not available&#x000d;&#x000a;Cab Id: 0&#x000d;&#x000a;&#x000d;&#x000a;Problem signature:&#x000d;&#x000a;P1: 139&#x000d;&#x000a;P2: 3&#x000d;&#x000a;P3: ffffb5000e36b320&#x000d;&#x000a;P4: ffffb5000e36b278&#x000d;&#x000a;P5: 0&#x000d;&#x000a;P6: 10_0_14393&#x000d;&#x000a;P7: 0_0&#x000d;&#x000a;P8: 256_1&#x000d;&#x000a;P9: &#x000d;&#x000a;P10: &#x000d;&#x000a;&#x000d;&#x000a;Attached files:&#x000d;&#x000a;\\?\C:\Windows\Minidump\031419-15484-01.dmp&#x000d;&#x000a;\\?\C:\Windows\TEMP\WER-17484-0.sysdata.xml&#x000d;&#x000a;\\?\C:\Windows\MEMORY.DMP&#x000d;&#x000a;&#x000d;&#x000a;These files may be available here:&#x000d;&#x000a;C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_139_29c475b222e743e6a73c22e2e67b7ec99adbbc8c_00000000_03445023&#x000d;&#x000a;&#x000d;&#x000a;Analysis symbol: &#x000d;&#x000a;Rechecking for solution: 0&#x000d;&#x000a;Report Id: 7dc353b2-3414-4726-9155-75b3d09181f8&#x000d;&#x000a;Report Status: 4&#x000d;&#x000a;Hashed bucket:
    7/4/2019 6:17 AM	Windows Error Reporting	Fault bucket , type 0&#x000d;&#x000a;Event Name: BlueScreen&#x000d;&#x000a;Response: Not available&#x000d;&#x000a;Cab Id: 0&#x000d;&#x000a;&#x000d;&#x000a;Problem signature:&#x000d;&#x000a;P1: 139&#x000d;&#x000a;P2: 3&#x000d;&#x000a;P3: ffffb800153abdb0&#x000d;&#x000a;P4: ffffb800153abd08&#x000d;&#x000a;P5: 0&#x000d;&#x000a;P6: 10_0_14393&#x000d;&#x000a;P7: 0_0&#x000d;&#x000a;P8: 256_1&#x000d;&#x000a;P9: &#x000d;&#x000a;P10: &#x000d;&#x000a;&#x000d;&#x000a;Attached files:&#x000d;&#x000a;\\?\C:\Windows\Minidump\070419-25750-01.dmp&#x000d;&#x000a;\\?\C:\Windows\TEMP\WER-27796-0.sysdata.xml&#x000d;&#x000a;\\?\C:\Windows\MEMORY.DMP&#x000d;&#x000a;&#x000d;&#x000a;These files may be available here:&#x000d;&#x000a;C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_139_be9c04102e3bd54df8057737c1fe76dbea439_00000000_cab_169888e6&#x000d;&#x000a;&#x000d;&#x000a;Analysis symbol: &#x000d;&#x000a;Rechecking for solution: 0&#x000d;&#x000a;Report Id: 89dfbe5b-3855-43e2-809a-091e826e3c86&#x000d;&#x000a;Report Status: 2048&#x000d;&#x000a;Hashed bucket:
    7/4/2019 6:17 AM	Windows Error Reporting	Fault bucket , type 0&#x000d;&#x000a;Event Name: BlueScreen&#x000d;&#x000a;Response: Not available&#x000d;&#x000a;Cab Id: 0&#x000d;&#x000a;&#x000d;&#x000a;Problem signature:&#x000d;&#x000a;P1: 139&#x000d;&#x000a;P2: 3&#x000d;&#x000a;P3: ffffb800153abdb0&#x000d;&#x000a;P4: ffffb800153abd08&#x000d;&#x000a;P5: 0&#x000d;&#x000a;P6: 10_0_14393&#x000d;&#x000a;P7: 0_0&#x000d;&#x000a;P8: 256_1&#x000d;&#x000a;P9: &#x000d;&#x000a;P10: &#x000d;&#x000a;&#x000d;&#x000a;Attached files:&#x000d;&#x000a;\\?\C:\Windows\Minidump\070419-25750-01.dmp&#x000d;&#x000a;\\?\C:\Windows\TEMP\WER-27796-0.sysdata.xml&#x000d;&#x000a;\\?\C:\Windows\MEMORY.DMP&#x000d;&#x000a;&#x000d;&#x000a;These files may be available here:&#x000d;&#x000a;C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_139_be9c04102e3bd54df8057737c1fe76dbea439_00000000_02807927&#x000d;&#x000a;&#x000d;&#x000a;Analysis symbol: &#x000d;&#x000a;Rechecking for solution: 0&#x000d;&#x000a;Report Id: 89dfbe5b-3855-43e2-809a-091e826e3c86&#x000d;&#x000a;Report Status: 4&#x000d;&#x000a;Hashed bucket:
    5/19/2019 7:01 AM	Windows Error Reporting	Fault bucket , type 0&#x000d;&#x000a;Event Name: BlueScreen&#x000d;&#x000a;Response: Not available&#x000d;&#x000a;Cab Id: 0&#x000d;&#x000a;&#x000d;&#x000a;Problem signature:&#x000d;&#x000a;P1: 139&#x000d;&#x000a;P2: 3&#x000d;&#x000a;P3: ffffcd81e4e05ec0&#x000d;&#x000a;P4: ffffcd81e4e05e18&#x000d;&#x000a;P5: 0&#x000d;&#x000a;P6: 10_0_14393&#x000d;&#x000a;P7: 0_0&#x000d;&#x000a;P8: 256_1&#x000d;&#x000a;P9: &#x000d;&#x000a;P10: &#x000d;&#x000a;&#x000d;&#x000a;Attached files:&#x000d;&#x000a;\\?\C:\Windows\Minidump\051919-18062-01.dmp&#x000d;&#x000a;\\?\C:\Windows\TEMP\WER-20125-0.sysdata.xml&#x000d;&#x000a;\\?\C:\Windows\MEMORY.DMP&#x000d;&#x000a;&#x000d;&#x000a;These files may be available here:&#x000d;&#x000a;C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_139_23e1261f10bf8bbedafd74e2d5599761d27bdba_00000000_cab_15cc7a8f&#x000d;&#x000a;&#x000d;&#x000a;Analysis symbol: &#x000d;&#x000a;Rechecking for solution: 0&#x000d;&#x000a;Report Id: d14526fa-42b8-4df6-a8bc-b454be8e8a42&#x000d;&#x000a;Report Status: 2048&#x000d;&#x000a;Hashed bucket:
    5/19/2019 7:01 AM	Windows Error Reporting	Fault bucket , type 0&#x000d;&#x000a;Event Name: BlueScreen&#x000d;&#x000a;Response: Not available&#x000d;&#x000a;Cab Id: 0&#x000d;&#x000a;&#x000d;&#x000a;Problem signature:&#x000d;&#x000a;P1: 139&#x000d;&#x000a;P2: 3&#x000d;&#x000a;P3: ffffcd81e4e05ec0&#x000d;&#x000a;P4: ffffcd81e4e05e18&#x000d;&#x000a;P5: 0&#x000d;&#x000a;P6: 10_0_14393&#x000d;&#x000a;P7: 0_0&#x000d;&#x000a;P8: 256_1&#x000d;&#x000a;P9: &#x000d;&#x000a;P10: &#x000d;&#x000a;&#x000d;&#x000a;Attached files:&#x000d;&#x000a;\\?\C:\Windows\Minidump\051919-18062-01.dmp&#x000d;&#x000a;\\?\C:\Windows\TEMP\WER-20125-0.sysdata.xml&#x000d;&#x000a;\\?\C:\Windows\MEMORY.DMP&#x000d;&#x000a;&#x000d;&#x000a;These files may be available here:&#x000d;&#x000a;C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_139_23e1261f10bf8bbedafd74e2d5599761d27bdba_00000000_02785d14&#x000d;&#x000a;&#x000d;&#x000a;Analysis symbol: &#x000d;&#x000a;Rechecking for solution: 0&#x000d;&#x000a;Report Id: d14526fa-42b8-4df6-a8bc-b454be8e8a42&#x000d;&#x000a;Report Status: 4&#x000d;&#x000a;Hashed bucket:
    Code:
    Installation Failure: Windows failed to install the following update with error 0x8024200D: Feature update to Windows 10, version 1803.
    
    Installation Failure: Windows failed to install the following update with error 0x8007001F: Feature update to Windows 10, version 1803.
    
    Installation Failure: Windows failed to install the following update with error 0x8024200D: Feature update to Windows 10, version 1803.
    
    
    Installation Failure: Windows failed to install the following update with error 0x8007001F: Feature update to Windows 10, version 1803.
    Code:
    Windows failed fast startup with error status 0xC00000D4.
    Code:
    The embedded controller (EC) returned data when none was requested. The BIOS might be trying to access the EC without synchronizing with the operating system. This data will be ignored. No further action is necessary; however, you should check with your computer manufacturer for an upgraded BIOS.
      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 03:56.
Find Us




Windows 10 Forums