Upgrade from Win7 Results in Safe_OS Phase Replicate_OC Error

Page 1 of 6 123 ... LastLast

  1. Posts : 117
    Windows 10
       #1

    Upgrade from Win7 Results in Safe_OS Phase Replicate_OC Error


    I am trying to upgrade my win7 SP1 x64 to win10 but it starts going, and then quits after a couple restarts and rolls back with the error code:

    0x8007001F 0x20006 Failed in the Safe_OS Phase with an error during Replicate_OC operation.

    I uninstalled my anti-virus because it told me that MS Security Essential was not supported. The install media is an ISO file that I just downloaded from Microsoft and mounted. I also tried doing a clean boot prior to install. Also, all win 7 updates are in, there's plenty of HD space. Nothing seems to work.
      My Computers


  2. Posts : 43,289
    Win 10 Pro (22H2) (2nd PC is 22H2)
       #2

    Hi, some basics before @zbook comes along and asks for a mass of data..

    Please note that trying to resolve upgrade problems can be exceptionally time consuming and may not succeed.

    1. What is the exact model of your laptop?
    2. Please post a screenshot of your partitions using a 3rd party partition manager ensuring all text is visible.
    To post a screenshot please use the icon above your post 'Insert Image'
    3. Have you ever been offered an upgrade to Win 10 via Windows update? If not, MS deems your PC to be incompatible,
    4. Normal preparation -see
    Upgrade to Windows 10
    sections
    Important notes
    and
    Here's How:

    Then see sections:
    Get help with Windows 10 upgrade and installation errors - Windows Support
    Resolve Windows 10 upgrade errors


    These contain links leading to futher links- a lot of information.

    5. Please make sure your BIOS is fully up to date

    6. It is likely " the extend code 0x20006 correctly the error means there is a failure to Move/Copy the WIM files to recovery file location." 0x8007001F could point to 3rd party program or driver incompatibility.

    A detailed examination of the upgrade logs is needed.

    Please run this MS tool and report the result: SetupDiag

    Example thread - where you can see an example of some of the data to be collected:
    Windows 10 Update keeps failing 0x8007001F - 0x20006
      My Computers


  3. Posts : 117
    Windows 10
    Thread Starter
       #3

    First off, the computer I am trying to upgrade is not my laptop as it says in my profile. My laptop already came with win10. My desktop has win7 and I need to upgrade ASAP for one main reason - my cloud backup service ended support for 7 when MS did so my files are not being backed up after that date.

    I ran the upgrade advisor back in 2016 and it said my system was ok so I did it, back when you could get it for free and then roll back to 7 and have the win10 activation already for when you want to move for good. That time, it worked without a problem and I actually ran win10, and then rolled back. I have not made any significant changes to the system since then. I figured this time it would be just as easy.

    My partitions are pretty simple: Upgrade from Win7 Results in Safe_OS Phase Replicate_OC Error-partitions.jpg

    Here are the specs of my desktop courtesy of speccy: Upgrade from Win7 Results in Safe_OS Phase Replicate_OC Error-speccy.jpg

    There is no update for my BIOS (its 6 years old now).

    I ran the setupdiag tool but the txt file was just blank.
      My Computers


  4. Posts : 43,289
    Win 10 Pro (22H2) (2nd PC is 22H2)
       #4

    Thank you for your reply.
    I figured this time it would be just as easy.
    Bear in mind this is now a different build of Win 10, and the drivers delivered with a particular build may differ.

    It is possible your PC may only be upgradable to a particular build of Win 10. There is no guarantee that any particular arbitrary older PC can be updated to any particular build of Win 10 - effectively millions use their PCs out of specification.

    Please specify the make and model of your desktop.
    Please post a link to its driver page.

    How much free space do you have on C: ?

    You have lots more in my previous post for you to work with. e.g. see the Example thread dealing with the same error message.

    Your complete error code does not appear here:
    https://docs.microsoft.com/en-us/win...res#0x800xxxxx

    Please upload the relevant log files:
    https://docs.microsoft.com/en-us/win...rade/log-files
      My Computers


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

    In Ten Forums there are commands that are commonly used in Windows 10 that do not work in Windows 7.
    Most of the tutorials in this post are specific to Windows 7.

    Troubleshooting logs is tedious and time consuming.
    The computer will be tuned up.
    After the tune up the first upgrade attempt will be made to generate new logs for troubleshooting.
    Then there will likely be many trial and error steps to identify problems related to failed migration.

    These are additional options:
    Windows 10 - Test & Try with No Risk, No Install - Windows 7 Help Forums
    Upgrade to Windows 10 from Windows 7 for Free
    Clean Install Windows 10 Directly without having to Upgrade First


    For all steps / test please post images into the thread.
    In case there are any problems posting images please use share links (one drive, drop box, or google drive).

    1) Update the specs in the "My Computer" section:

    System Specs - Fill in at Ten Forums
    In the left corner below in your post you find 'My System Specs'.
    After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.
    System Info - See Your System Specs - Windows 7 Help Forums

    Include PSU. cooler, case, peripherals and anything attached to the computer by wired or wireless (mouse, keyboard, headset, printer, xbox, USB wireless network card, etc.)

    2) Open administrative command prompt and type or copy and paste:
    3) sfc /scannow
    4) wmic recoveros set autoreboot = false
    5) wmic recoveros set DebugInfoType = 2
    6) wmic recoveros get autoreboot
    7) wmic recoveros get DebugInfoType
    8) bcdedit /enum all

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

    10) Make sure that there is no over clocking while troubleshooting

    11) Run the DM log collector > upload results into this thread
    BSOD - Posting Instructions

    12) 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
    Disk Check - Windows 7 Help Forums

    13) Copy and paste the results into the thread:
    Check Disk (chkdsk) - Read Event Viewer Log - Windows 7 Help Forums

    14) Create a new restore point:
    Restore Point - Add "Create Restore Point" to Context Menu in Windows - Windows 7 Help Forums

    15) Make a backup image and save the backup image to another disk drive:
    Imaging with free Macrium - Windows 7 Help Forums
    https://www.sevenforums.com/tutorial...usb-drive.html

    16) 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
    https://www.sevenforums.com/tutorial...ure-image.html

    17) Download and install Minitool Partition Wizard > post an image of the results into this thread
    https://download.cnet.com/MiniTool-P...-10962200.html

    18) If the computer has Ccleaner (do not install the software if it is not already installed) > click windows tab or custom clean > scroll down to system and advanced > post an image into the thread

    19) When setupdiag was clicked did it run or flash and not produce a text file?

    20) Download and install: https://www.voidtools.com/

    21) Use the application to find any of these folders or files (limit to the latest upgrade failure date)

    Code:
    C:\Windows\Panther
    
    folders:
    \$Windows.~bt\sources\panther
    \$Windows.~bt\Sources\Rollback
    \Windows\Panther
    \Windows\Panther\NewOS
    
    Setupmem.dmp may be found in either (depending on when the bugcheck occurs)
    %SystemDrive%$Windows.~bt\Sources\Rollback
    %WinDir%\Panther\NewOS\Rollback
    
    setuperr.log
    setupact.log
    Setupmem.dmp
    setupapi.dev.log
    BlueBox.log
    Event logs (*.evtx)
    C:\$Windows.~BT\Sources\Rollback
    $Windows.~bt\Sources\Rollback\setupmem.dmp
    $Windows.~bt\Sources\Rollback\setupapi\setupapi.dev.log
    $Windows.~bt\Sources\Rollback*.evtx
    $Windows.~BT\Sources\Panther\UnattendGC
    miglog.xml
    Windows\Logs\Mosetup
    Setupapi.offline.log



    22) 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 uninstalled)

    23) List and uninstall all non-Microsoft firewall software

    24) List all Microsoft and non-Microsoft drive encryption software.
    Uninstall all non-Microsoft disk encryption software
      My Computer


  6. Posts : 117
    Windows 10
    Thread Starter
       #6

    dalchina said:
    Thank you for your reply.

    Bear in mind this is now a different build of Win 10, and the drivers delivered with a particular build may differ.

    It is possible your PC may only be upgradable to a particular build of Win 10. There is no guarantee that any particular arbitrary older PC can be updated to any particular build of Win 10 - effectively millions use their PCs out of specification.

    Please specify the make and model of your desktop.
    Please post a link to its driver page.

    How much free space do you have on C: ?

    You have lots more in my previous post for you to work with. e.g. see the Example thread dealing with the same error message.

    Your complete error code does not appear here:
    https://docs.microsoft.com/en-us/win...res#0x800xxxxx

    Please upload the relevant log files:
    https://docs.microsoft.com/en-us/win...rade/log-files
    My desktop is a self-build. Win7 was installed on a bare SSD drive at the time so there is no manufacturer's bloatware or anything like that.

    The C: drive now has around 7gb free after the install attempt; I was able to gain back to 11gb free before each attempt by deleting the temp files from the last attempt. I won't delete those folders just yet so I can grab the error logs:

    The setupact is too big for an attachment. 25mb. Looks like I'm going to have to upload it to google drive and share the link: setupact.log - Google Drive

    - - - Updated - - -

    zbook said:

    2) Open administrative command prompt and type or copy and paste:
    3) sfc /scannow
    4) wmic recoveros set autoreboot = false
    5) wmic recoveros set DebugInfoType = 2
    6) wmic recoveros get autoreboot
    7) wmic recoveros get DebugInfoType
    8) bcdedit /enum all

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

    10) Make sure that there is no over clocking while troubleshooting
    For the first part, no overclocking and here's the cmd prompt:
    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation. All rights reserved.

    C:\Windows\system32>sfc /scannow

    Beginning system scan. This process will take some time.

    Beginning verification phase of system scan.
    Verification 100% complete.

    Windows Resource Protection did not find any integrity violations.

    C:\Windows\system32>wmic recoveros set autoreboot=false
    Updating property(s) of '\\BRUCE-1\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name
    ="Microsoft Windows 7 Professional |C:\\Windows|\\Device\\Harddisk0\\Partition2"
    '
    Property(s) update successful.

    C:\Windows\system32>wmic recoveros set DebugInfoType=2
    Updating property(s) of '\\BRUCE-1\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name
    ="Microsoft Windows 7 Professional |C:\\Windows|\\Device\\Harddisk0\\Partition2"
    '
    Property(s) update successful.

    C:\Windows\system32>wmic recoveros get autoreboot
    AutoReboot
    FALSE


    C:\Windows\system32>wmic recoveros get DebugInfoType
    DebugInfoType
    2


    C:\Windows\system32>bcdedit /enum all

    Windows Boot Manager
    --------------------
    identifier {bootmgr}
    device partition=\Device\HarddiskVolume1
    description Windows Boot Manager
    locale en-US
    inherit {globalsettings}
    default {current}
    resumeobject {b8c21753-9635-11e3-b126-946c1622aa88}
    displayorder {current}
    toolsdisplayorder {memdiag}
    timeout 15

    Windows Boot Loader
    -------------------
    identifier {current}
    device partition=C:
    path \Windows\system32\winload.exe
    description Windows 7
    locale en-US
    inherit {bootloadersettings}
    recoverysequence {b8c21755-9635-11e3-b126-946c1622aa88}
    recoveryenabled Yes
    osdevice partition=C:
    systemroot \Windows
    resumeobject {b8c21753-9635-11e3-b126-946c1622aa88}
    nx OptIn

    Windows Boot Loader
    -------------------
    identifier {b8c21755-9635-11e3-b126-946c1622aa88}
    device ramdisk=[C:]\Recovery\b8c21755-9635-11e3-b126-946c1622aa
    88\Winre.wim,{b8c21756-9635-11e3-b126-946c1622aa88}
    path \windows\system32\winload.exe
    description Windows Recovery Environment
    inherit {bootloadersettings}
    osdevice ramdisk=[C:]\Recovery\b8c21755-9635-11e3-b126-946c1622aa
    88\Winre.wim,{b8c21756-9635-11e3-b126-946c1622aa88}
    systemroot \windows
    nx OptIn
    winpe Yes

    Resume from Hibernate
    ---------------------
    identifier {b8c21753-9635-11e3-b126-946c1622aa88}
    device partition=C:
    path \Windows\system32\winresume.exe
    description Windows Resume Application
    locale en-US
    inherit {resumeloadersettings}
    filedevice partition=C:
    filepath \hiberfil.sys
    debugoptionenabled No

    Windows Memory Tester
    ---------------------
    identifier {memdiag}
    device partition=\Device\HarddiskVolume1
    path \boot\memtest.exe
    description Windows Memory Diagnostic
    locale en-US
    inherit {globalsettings}
    badmemoryaccess Yes

    EMS Settings
    ------------
    identifier {emssettings}
    bootems Yes

    Debugger Settings
    -----------------
    identifier {dbgsettings}
    debugtype Serial
    debugport 1
    baudrate 115200

    RAM Defects
    -----------
    identifier {badmemory}

    Global Settings
    ---------------
    identifier {globalsettings}
    inherit {dbgsettings}
    {emssettings}
    {badmemory}

    Boot Loader Settings
    --------------------
    identifier {bootloadersettings}
    inherit {globalsettings}
    {hypervisorsettings}

    Hypervisor Settings
    -------------------
    identifier {hypervisorsettings}
    hypervisordebugtype Serial
    hypervisordebugport 1
    hypervisorbaudrate 115200

    Resume Loader Settings
    ----------------------
    identifier {resumeloadersettings}
    inherit {globalsettings}

    Device options
    --------------
    identifier {b8c21756-9635-11e3-b126-946c1622aa88}
    description Ramdisk Options
    ramdisksdidevice partition=C:
    ramdisksdipath \Recovery\b8c21755-9635-11e3-b126-946c1622aa88\boot.sdi

    C:\Windows\system32>
    Upgrade from Win7 Results in Safe_OS Phase Replicate_OC Error Attached Files
      My Computers


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

    Please increase the free space on the Windows drive to > 30 GB.
      My Computer


  8. Posts : 117
    Windows 10
    Thread Starter
       #8

    zbook said:
    11) Run the DM log collector > upload results into this thread
    BSOD - Posting Instructions
    the generated file is attached.

    - - - Updated - - -

    zbook said:
    Please increase the free space on the Windows drive to > 30 GB.
    I'm not sure I can do that. I'd have to get rid of the temp folders from the last install attempt, plus how else can I find things to get rid of? I've used disk cleanup and CC Cleaner - temp folder was cleared, recycle bin cleared. The win10 install files live on the D: drive so that's not taking up space. Seems to me that the last time several months ago that I tried to make space I was able to get up into the 20gb range but I don't know what is taking it up now.

    Edit: One idea I thought of is the most important folder for me to save on the C: drive (for which I can't update my cloud backup anymore) is the C:\users\.... My folder under "users" (I'm the only user) contains around 35gb alone. If I moved that to the D: drive it could give me around 40gb free but some files in there are used by programs for example my email client, passwords, etc so it would throw off the data location for these things. Maybe if I moved it when attempting a win10 install and then move it back if it fails and rolls back? Its a lot of work though.
    Upgrade from Win7 Results in Safe_OS Phase Replicate_OC Error Attached Files
      My Computers


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

    1) To increase the likelihood of a successful upgrade the free space is important.

    2) Files can be temporarily transferred to the cloud and restored after a successful upgrade.

    Free Up Drive Space in Windows 10


    Code:
    ------------------------
    Disk & DVD/CD-ROM Drives
    ------------------------
          Drive: C:
     Free Space: 7.5 GB
    Total Space: 114.4 GB
    File System: NTFS
          Model: Samsung SSD 840 EVO 120GB ATA Device
    
          Drive: D:
     Free Space: 1066.3 GB
    Total Space: 1907.7 GB
    File System: NTFS
          Model: ST2000DX002-2DV164 ATA Device


    3) During the upgrade only the Windows drive should be connected to the computer.
    The cables can be detached or drives removed.


    4) The logs reported problems corruption of the drive file system and BSOD.
    There were no dump files collected by the log collector.

    5) Update the specs in the "My Computer" section:
    System Specs - Fill in at Ten Forums
    In the left corner below in your post you find 'My System Specs'.
    After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.
    System Info - See Your System Specs - Windows 7 Help Forums

    Include PSU. cooler, case, peripherals and anything attached to the computer by wired or wireless (mouse, keyboard, headset, printer, xbox, USB wireless network card, etc.)

    6) If the computer has Ccleaner (do not install the software if it is not already installed) > click windows tab or custom clean > scroll down to system and advanced > post an image into the thread

    7) Move the paging file from D: to C:

    8) Post images of startup an recovery system failure and Virtual Memory / paging file

    9) Run memtest86+ version 5.01 for at least 8 passes.
    Memtest86+ - Advanced Memory Diagnostic Tool
    This may take hours so plan to run it overnight.

    a) Please make sure you use the Memtest86+ version 5.01 with the link below.
    Memtest86+ - Advanced Memory Diagnostic Tool

    The testing is done not by time but by passes.
    The more passes the better the testing conditions.
    There are a significant number of false negatives if fewer than 8 passes are made.
    A false negative is a test pass when there is malfunctioning RAM.
    There is 8 GB of RAM on the computer.
    Memtest86+ version 5.01 testing takes approximately 1 - 2 hours /GB RAM
    Just 1 error is a fail and you can abort testing.
    Then test 1 RAM module at a time in the same DIMM each for 8 or more passes.

    b) When Memtest86+ version 5.01 has completed 8 or more passes use a camera or smart phone camera to take a picture and post an image into the thread.
    https://answers.microsoft.com/en-us/...f-ecc7b7ff6461
    MemTest86+ - Test RAM

    10) Run HD Tune (free version) (all drives)
    HD Tune website
    Post images into the thread for results on these tabs:
    a) Health
    b) Benchmark
    c) Full error scan


    11) Run Sea Tools for Windows
    long generic test
    Post an image of the test result into the thread
    SeaTools for Windows |
    Seagate

    How to use SeaTools for Windows | Seagate Support US

    12) For any BSOD:

    a) run the DM 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

    13) Please do not perform windows upgrade attempts until the computer has been tuned up

    14) Immediately before the next upgrade attempt please uninstall:
    a) Microsoft security essentials
    b) Gopro

    15) For any encrypted drives please plan to decrypt before the next upgrade attempt

    16) Upgrade the BIOS: F14 > F15
    https://www.gigabyte.com/us/Motherbo...upport-dl-bios



    Code:
    Event[1184]:
      Log Name: System
      Source: Microsoft-Windows-WER-SystemErrorReporting
      Date: 2019-12-02T01:50:46.000
      Event ID: 1001
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Bruce-1
      Description: 
    The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000024 (0x00000000001904fb, 0xfffff8800c6f05a8, 0xfffff8800c6efe10, 0xfffff800034d8ac9). A dump was saved in: C:\Windows\Minidump\120219-12714-01.dmp. Report Id: 120219-12714-01.
    
    
    
    Event[1654]:
      Log Name: System
      Source: Microsoft-Windows-WER-SystemErrorReporting
      Date: 2019-12-04T12:39:43.000
      Event ID: 1001
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Bruce-1
      Description: 
    The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000001e (0xffffffffc0000005, 0xfffff8000350e5ec, 0x0000000000000000, 0xffffffffffffffff). A dump was saved in: C:\Windows\Minidump\120419-8143-01.dmp. Report Id: 120419-8143-01.
    
    
    
    Event[4336]:
      Log Name: System
      Source: Microsoft-Windows-WER-SystemErrorReporting
      Date: 2019-12-19T11:14:30.000
      Event ID: 1001
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: BRUCE-1
      Description: 
    The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000000a (0x0000000000000137, 0x0000000000000002, 0x0000000000000000, 0xfffff80003464aa4). A dump was saved in: C:\Windows\Minidump\121919-13026-01.dmp. Report Id: 121919-13026-01.
    
    
    
    Event[4850]:
      Log Name: System
      Source: Microsoft-Windows-WER-SystemErrorReporting
      Date: 2019-12-21T11:58:11.000
      Event ID: 1001
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: BRUCE-1
      Description: 
    The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000001e (0x0000000000000000, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\Minidump\122119-13821-01.dmp. Report Id: 122119-13821-01.
    
    
    
    Event[7365]:
      Log Name: System
      Source: Microsoft-Windows-WER-SystemErrorReporting
      Date: 2020-01-11T03:03:08.000
      Event ID: 1001
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Bruce-1
      Description: 
    The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff800037538d8, 0xfffff8801f3b2ee0, 0x0000000000000000). A dump was saved in: C:\Windows\Minidump\011120-17628-01.dmp. Report Id: 011120-17628-01.

    Code:
    Event[7897]:
      Log Name: System
      Source: Ntfs
      Date: 2020-01-13T18:56:24.177
      Event ID: 55
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Bruce-1
      Description: 
    The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume \Device\HarddiskVolume2.
    
    Event[7898]:
      Log Name: System
      Source: Ntfs
      Date: 2020-01-13T18:56:24.177
      Event ID: 55
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Bruce-1
      Description: 
    The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume \Device\HarddiskVolume2.

    Code:
    1/11/2020 9:04 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: &#x000d;&#x000a;P2: &#x000d;&#x000a;P3: &#x000d;&#x000a;P4: &#x000d;&#x000a;P5: &#x000d;&#x000a;P6: &#x000d;&#x000a;P7: &#x000d;&#x000a;P8: &#x000d;&#x000a;P9: &#x000d;&#x000a;P10: &#x000d;&#x000a;&#x000d;&#x000a;Attached files:&#x000d;&#x000a;C:\Windows\Minidump\011120-17628-01.dmp&#x000d;&#x000a;C:\Users\Bruce\AppData\Local\Temp\WER-48875-0.sysdata.xml&#x000d;&#x000a;&#x000d;&#x000a;These files may be available here:&#x000d;&#x000a;C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_0ec56814&#x000d;&#x000a;&#x000d;&#x000a;Analysis symbol: &#x000d;&#x000a;Rechecking for solution: 0&#x000d;&#x000a;Report Id: 011120-17628-01&#x000d;&#x000a;Report Status: 0
    12/2/2019 7:51 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: &#x000d;&#x000a;P2: &#x000d;&#x000a;P3: &#x000d;&#x000a;P4: &#x000d;&#x000a;P5: &#x000d;&#x000a;P6: &#x000d;&#x000a;P7: &#x000d;&#x000a;P8: &#x000d;&#x000a;P9: &#x000d;&#x000a;P10: &#x000d;&#x000a;&#x000d;&#x000a;Attached files:&#x000d;&#x000a;C:\Windows\Minidump\120219-12714-01.dmp&#x000d;&#x000a;C:\Users\Bruce\AppData\Local\Temp\WER-18782-0.sysdata.xml&#x000d;&#x000a;&#x000d;&#x000a;These files may be available here:&#x000d;&#x000a;C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_0dd871a6&#x000d;&#x000a;&#x000d;&#x000a;Analysis symbol: &#x000d;&#x000a;Rechecking for solution: 0&#x000d;&#x000a;Report Id: 120219-12714-01&#x000d;&#x000a;Report Status: 0
    12/4/2019 6:40 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: &#x000d;&#x000a;P2: &#x000d;&#x000a;P3: &#x000d;&#x000a;P4: &#x000d;&#x000a;P5: &#x000d;&#x000a;P6: &#x000d;&#x000a;P7: &#x000d;&#x000a;P8: &#x000d;&#x000a;P9: &#x000d;&#x000a;P10: &#x000d;&#x000a;&#x000d;&#x000a;Attached files:&#x000d;&#x000a;C:\Windows\Minidump\120419-8143-01.dmp&#x000d;&#x000a;C:\Users\Bruce\AppData\Local\Temp\WER-32292-0.sysdata.xml&#x000d;&#x000a;&#x000d;&#x000a;These files may be available here:&#x000d;&#x000a;C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_0e20a5df&#x000d;&#x000a;&#x000d;&#x000a;Analysis symbol: &#x000d;&#x000a;Rechecking for solution: 0&#x000d;&#x000a;Report Id: 120419-8143-01&#x000d;&#x000a;Report Status: 0
    12/19/2019 5:17 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: &#x000d;&#x000a;P2: &#x000d;&#x000a;P3: &#x000d;&#x000a;P4: &#x000d;&#x000a;P5: &#x000d;&#x000a;P6: &#x000d;&#x000a;P7: &#x000d;&#x000a;P8: &#x000d;&#x000a;P9: &#x000d;&#x000a;P10: &#x000d;&#x000a;&#x000d;&#x000a;Attached files:&#x000d;&#x000a;C:\Windows\Minidump\121919-13026-01.dmp&#x000d;&#x000a;C:\Users\Bruce\AppData\Local\Temp\WER-44382-0.sysdata.xml&#x000d;&#x000a;&#x000d;&#x000a;These files may be available here:&#x000d;&#x000a;C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_0c2a8813&#x000d;&#x000a;&#x000d;&#x000a;Analysis symbol: &#x000d;&#x000a;Rechecking for solution: 0&#x000d;&#x000a;Report Id: 121919-13026-01&#x000d;&#x000a;Report Status: 0
    12/21/2019 6:02 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: &#x000d;&#x000a;P2: &#x000d;&#x000a;P3: &#x000d;&#x000a;P4: &#x000d;&#x000a;P5: &#x000d;&#x000a;P6: &#x000d;&#x000a;P7: &#x000d;&#x000a;P8: &#x000d;&#x000a;P9: &#x000d;&#x000a;P10: &#x000d;&#x000a;&#x000d;&#x000a;Attached files:&#x000d;&#x000a;C:\Windows\Minidump\122119-13821-01.dmp&#x000d;&#x000a;C:\Users\Bruce\AppData\Local\Temp\WER-51558-0.sysdata.xml&#x000d;&#x000a;&#x000d;&#x000a;These files may be available here:&#x000d;&#x000a;C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_0d8c5263&#x000d;&#x000a;&#x000d;&#x000a;Analysis symbol: &#x000d;&#x000a;Rechecking for solution: 0&#x000d;&#x000a;Report Id: 122119-13821-01&#x000d;&#x000a;Report Status: 0
    Last edited by zbook; 14 Jan 2020 at 12:42.
      My Computer


  10. Posts : 43,289
    Win 10 Pro (22H2) (2nd PC is 22H2)
       #10

    Yes, >30Gb free, say- Windows.old will be created- that's about as big as Windows is now.

    Just some odd observations from setupact.log
    CONX Failed to add driver ....motfilt.sys - appears to be related to some Motorola program. Suggest you investigate and uninstall that

    motoandroid.sys - another motorola related program- maybe connected with a Motorola phone somehow?
    - looks like some Motorola program is incompatible - more moto refs. exist.

    lgvzandnetbus64.sys:
    What is LG VZW United Drivers?

    This is the software package that includes the required drivers, configuration and management utilities to support the LG VZW.
    An LG driver?
    LG VZW United Drivers by LG Electronics - Should I Remove It?

    kpvnmbze.sys - Google- no results. Rt click, properties, identify it and deal with the relevant program

    That's just 3 ideas on things to remove...
      My Computers


 

  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 01:31.
Find Us




Windows 10 Forums