Windows 10 2004 update fails to install - Memory Management?

Windows 10 ver 1909.

After the downloading and rebooting the OS crashes and has to be hard booted. It does it a second time and then after another hard reset it rolls back. The BSOD that pops up says "Memory Management". After I get back into windows (after the rollback) I find this in the event log.
Installation Failure: Windows failed to install the following update with error 0x800704C7: Feature update to Windows 10, version 2004.
While the above error usually indicates corrupted files the system is clean. I have run DSIM and Scannow. Both report no problems.
I've tried downloading and manually installing but get the same results. Any suggestions...

Macboatmaster said:

I know your computer spec says it is using Windows Defender but please confirm that to be the case
Also which if any other AV apps are in use even if only scan on demandWhat is connected USB apart from mouse and keyboardWhat third party apps are installed if any that have any relevance to the system - maintenance, disk cleaning, encryption etc.

Only Windows Defender, no other AV apps are installed.
USB connections include a logtec web cam, Intuos Pen Tablet, SpyderX, Mouse and Keyboard. All other USB devices are removed when not in use. I have tried removing all but keyboard/mouse for the update and that didn't work either.
No third party apps are installed for system mainenance, disk cleaning or encryption.
I do have Partition Magic and EaseUS Partition Master installed. These however are on demand apps...

Run these and upload results directly into this thread.

For any difficulty uploading use share links: one drive, drop box, or google drive


BSOD - Posting Instructions

Tuneup.bat - Click here to go to the BSOD batch repository to download and run this batch file.

LOGS.bat - Click here to go to the BSOD batch repository to download and run this batch file.

GetMemoryConfiguration.bat - Click here to go to the BSOD batch repository to download and run this batch file.

zbook said:

Run these and upload results directly into this thread.
For any difficulty uploading use share links: one drive, drop box, or google drive

BSOD - Posting Instructions

Results of running log collector: Dropbox - SOUTHONE-(2020-10-03_11-31-00).zip - Simplify your life

zbook said:

Tuneup.bat - Click here to go to the BSOD batch repository to download and run this batch file.

Results of Tuneup.bat:

Code:

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>dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.900

Image Version: 10.0.18363.1082

[==========================100.0%==========================] No component store corruption detected.
The operation completed successfully.

C:\windows\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.900

Image Version: 10.0.18363.1082

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

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>chkdsk /scan
The type of the file system is NTFS.
Volume label is Drive.

Stage 1: Examining basic file system structure ...
  1275936 file records processed.
File verification completed.
  16091 large file records processed.
  0 bad file records processed.

Stage 2: Examining file name linkage ...
  87556 reparse records processed.
  1551032 index entries processed.
Index verification completed.
  0 unindexed files scanned.
  0 unindexed files recovered to lost and found.
  87556 reparse records processed.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
  137549 data files processed.
CHKDSK is verifying Usn Journal...
  34683088 USN bytes processed.
Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

1950906364 KB total disk space.
1122261004 KB in 818290 files.
    527264 KB in 137550 indexes.
         0 KB in bad sectors.
   1458816 KB in use by the system.
     65536 KB occupied by the log file.
 826659280 KB available on disk.

      4096 bytes in each allocation unit.
 487726591 total allocation units on disk.
 206664820 allocation units available on disk.

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


C:\windows\system32>wmic recoveros set autoreboot = false
Updating property(s) of '\\SOUTHONE\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\windows|\\Device\\Harddisk0\\Partition3"'
Property(s) update successful.

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


C:\windows\system32>wmic recoveros get DebugInfoType
DebugInfoType
7


C:\windows\system32>wmic recoveros set DebugInfoType = 7
Updating property(s) of '\\SOUTHONE\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\windows|\\Device\\Harddisk0\\Partition3"'
Property(s) update successful.

C:\windows\system32>wmic recoveros get DebugInfoType
DebugInfoType
7


C:\windows\system32>wmic pagefile list /format:list


AllocatedBaseSize=4864
CurrentUsage=3
Description=C:\pagefile.sys
InstallDate=20200928154909.781608-420
Name=C:\pagefile.sys
PeakUsage=4
Status=
TempPageFile=FALSE




C:\windows\system32>wmic Computersystem where name="SOUTHONE" get AutomaticManagedPagefile
AutomaticManagedPagefile
TRUE


C:\windows\system32>wmic Computersystem where name="SOUTHONE" set AutomaticManagedPagefile=True
Updating property(s) of '\\SOUTHONE\ROOT\CIMV2:Win32_ComputerSystem.Name="SOUTHONE"'
Property(s) update successful.

C:\windows\system32>wmic Computersystem where name="SOUTHONE" get AutomaticManagedPagefile
AutomaticManagedPagefile
TRUE


C:\windows\system32>bcdedit /enum {badmemory}

RAM Defects
-----------
identifier              {badmemory}
A device which does not exist was specified.

zbook said:

LOGS.bat - Click here to go to the BSOD batch repository to download and run this batch file.

Results of LOGS.bat:
Dropbox - LOGS - Simplify your life
(All of the log files generated are located at this share.)

zbook said:

GetMemoryConfiguration.bat - Click here to go to the BSOD batch repository to download and run this batch file.

Results of GetMemoryConfiguration.bat:

Code:

Memory Modules:

Tag               BankLabel Capacity(GB) Manufacturer PartNumber           Speed
---               --------- ------------ ------------ ----------           -----
Physical Memory 0 BANK 0              16 859B         BLS16G4D240FSC.16FBD  2400
Physical Memory 2 BANK 2              16 859B         BLS16G4D240FSC.16FBD  2400


Total Memory:
32GB

Total Memory Slots:
4

Used Memory Slots:
2

Run:
DiskParInfo.bat - Click here to go to the BSOD batch repository to download and run this batch file.


List any:
a) cleaning software (Ccleaner, Wise cleaner, Glary utilities, etc.)
b) non-Microsoft
antivirus software
firewall software
encryption software


The computer has had recent BSODs.


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


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


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


Read these links on Windows driver verifier:

a) learn how to use the Windows Recovery Environment (RE) commands: reset and bootmode to turn off the tool

b) do not use the tool until it is communicated in the thread


Enable and Disable Driver Verifier in Windows 10
https://answers.microsoft.com/en-us/...3-c48669e4c983

zbook said:

Run:
DiskParInfo.bat - Click here to go to the BSOD batch repository to download and run this batch file.

Here are the results:
---PASTE--- Disk 0 is an SSD. It has 4 partition(s). Model: NVMe Samsung SSD 970

This computer has the above 1 fixed storage device(s) in total.
=======================================================================

Microsoft DiskPart version 10.0.18362.1

Copyright (C) Microsoft Corporation.
On computer: SOUTHONE

Disk ### Status Size Free Dyn Gpt
-------- ------------- ------- ------- --- ---
Disk 0 Online 1863 GB 2048 KB *
Disk 1 Online 1863 GB 1024 KB

Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
Volume 0 D DVD-ROM 0 B No Media
Volume 1 C Drive NTFS Partition 1860 GB Healthy Boot
Volume 2 FAT32 Partition 500 MB Healthy System
Volume 3 E Seagate Bac NTFS Partition 1863 GB Healthy

Disk 0 is now the selected disk.

Samsung SSD 970 EVO 2TB
Disk ID: {E684534D-80D9-11E9-9F15-F83441A99A6A}
Type : NVMe
Status : Online
Path : 0
Target : 0
LUN ID : 0
Location Path : PCIROOT(0)#PCI(1B00)#PCI(0000)#NVME(P00T00L00)
Current Read-only State : No
Read-only : No
Boot Disk : Yes
Pagefile Disk : Yes
Hibernation File Disk : No
Crashdump Disk : Yes
Clustered Disk : No

Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
Volume 1 C Drive NTFS Partition 1860 GB Healthy Boot
Volume 2 FAT32 Partition 500 MB Healthy System

Partition ### Type Size Offset
------------- ---------------- ------- -------
Partition 2 System 500 MB 1024 KB
Partition 1 Reserved 1020 MB 501 MB
Partition 3 Primary 1860 GB 1521 MB
Partition 4 Recovery 1024 MB 1862 GB

Partition 2 is now the selected partition.

Partition 2
Type : c12a7328-f81f-11d2-ba4b-00a0c93ec93b
Hidden : Yes
Required: No
Attrib : 0X8000000000000000
Offset in Bytes: 1048576

Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
* Volume 2 FAT32 Partition 500 MB Healthy System

Partition 1 is now the selected partition.

Partition 1
Type : e3c9e316-0b5c-4db8-817d-f92df00215ae
Hidden : Yes
Required: No
Attrib : 0000000000000000
Offset in Bytes: 525336576

There is no volume associated with this partition.

Partition 3 is now the selected partition.

Partition 3
Type : ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
Hidden : No
Required: No
Attrib : 0000000000000000
Offset in Bytes: 1594884096

Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
* Volume 1 C Drive NTFS Partition 1860 GB Healthy Boot

Partition 4 is now the selected partition.

Partition 4
Type : de94bba4-06d1-4d40-a16a-bfd50179d6ac
Hidden : No
Required: Yes
Attrib : 0X0000000000000001
Offset in Bytes: 1999323004928

Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
* Volume 4 NTFS Partition 1024 MB Healthy Hidden

===============================================================================

Windows Recovery Environment (Windows RE) and system reset configuration
Information:

Windows RE status: Enabled
Windows RE location: \\?\GLOBALROOT\device\harddisk0\partition3\Recovery\WindowsRE
Boot Configuration Data (BCD) identifier: 4ac41890-a113-11ea-9f8b-f83441a99a6a
Recovery image location:
Recovery image index: 1
Custom image location:
Custom image index: 0

===============================================================================

Firmware Boot Manager
---------------------
identifier {fwbootmgr}
displayorder {32560902-9cc1-11ea-9f66-806e6f6e6963}
{32560904-9cc1-11ea-9f66-806e6f6e6963}
{d2c6854b-f394-11ea-a023-806e6f6e6963}
{ddd42c77-04ee-11eb-a035-806e6f6e6963}
{bootmgr}
timeout 1

Windows Boot Manager
--------------------
identifier {bootmgr}
device unknown
path \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI
description Windows Boot Manager
locale en-us
inherit {globalsettings}
default {current}
resumeobject {5aa4b12a-e56d-11e9-a174-efebd649fcc7}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30

Firmware Application (101fffff)
-------------------------------
identifier {32560902-9cc1-11ea-9f66-806e6f6e6963}
device partition=\Device\HarddiskVolume1
path \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI
description Windows Boot Manager

Firmware Application (101fffff)
-------------------------------
identifier {32560904-9cc1-11ea-9f66-806e6f6e6963}
description ASUS BW-12B1ST

Firmware Application (101fffff)
-------------------------------
identifier {d2c6854b-f394-11ea-a023-806e6f6e6963}
description Samsung SSD 970 EVO 2TB

Firmware Application (101fffff)
-------------------------------
identifier {ddd42c77-04ee-11eb-a035-806e6f6e6963}
description Seagate BUP Slim BL 0304

Windows Boot Loader
-------------------
identifier {0cb3b571-2f2e-4343-a879-d86a476d7215}
device partition=\Device\HarddiskVolume1
path \EFI\Microsoft\Boot\SecConfig.efi
description DGOptOut
loadoptions DISABLE-LSA-ISO,DISABLE-VBS

Windows Boot Loader
-------------------
identifier {4ac41890-a113-11ea-9f8b-f83441a99a6a}
device ramdisk=[C:]\Recovery\WindowsRE\Winre.wim,{4ac41891-a113-11ea-9f8b-f83441a99a6a}
path \windows\system32\winload.efi
description Windows Recovery Environment
locale en-us
inherit {bootloadersettings}
displaymessage Recovery
osdevice ramdisk=[C:]\Recovery\WindowsRE\Winre.wim,{4ac41891-a113-11ea-9f8b-f83441a99a6a}
systemroot \windows
nx OptIn
bootmenupolicy Standard
winpe Yes

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \windows\system32\winload.efi
description Windows 10
locale en-us
inherit {bootloadersettings}
recoverysequence {4ac41890-a113-11ea-9f8b-f83441a99a6a}
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \windows
resumeobject {5aa4b12a-e56d-11e9-a174-efebd649fcc7}
nx OptIn
bootmenupolicy Legacy
hypervisorlaunchtype Auto

Resume from Hibernate
---------------------
identifier {5aa4b12a-e56d-11e9-a174-efebd649fcc7}
device partition=C:
path \windows\system32\winresume.efi
description Windows Resume Application
locale en-us
inherit {resumeloadersettings}
recoverysequence {4ac41890-a113-11ea-9f8b-f83441a99a6a}
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
filedevice partition=C:
filepath \hiberfil.sys
bootmenupolicy Standard
debugoptionenabled No

Windows Memory Tester
---------------------
identifier {memdiag}
device unknown
path \EFI\Microsoft\Boot\memtest.efi
description Windows Memory Diagnostic
locale en-us
inherit {globalsettings}
badmemoryaccess Yes

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

Debugger Settings
-----------------
identifier {dbgsettings}
debugtype Local

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 {4ac41891-a113-11ea-9f8b-f83441a99a6a}
description Windows Recovery
ramdisksdidevice partition=C:
ramdisksdipath \Recovery\WindowsRE\boot.sdi
A device which does not exist was specified.
---END PASTE---

Note the last line above...

zbook said:

List any:
a) cleaning software (Ccleaner, Wise cleaner, Glary utilities, etc.)
b) non-Microsoft
antivirus software
firewall software
encryption software

I have CCleaner installed. Screen shot of the requested section is below - NOTE: I have not run it in a while (since long before trying the upgrade). I also have DiskCryptor installed but it's only use is for a USB. Nothing on the computer is encrypted. No non-MS Anti-Virus or Firewall software is installed.

zbook said:

The computer has had recent BSODs.

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

zbook said:

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

zbook said:

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

zbook said:

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

There is no dump file, despite the two BSOD's while running the upgrade.

zbook said:

Read these links on Windows driver verifier:
a) learn how to use the Windows Recovery Environment (RE) commands: reset and bootmode to turn off the tool
b) do not use the tool until it is communicated in the thread

Enable and Disable Driver Verifier in Windows 10
https://answers.microsoft.com/en-us/...3-c48669e4c983

Reviewing these now...
Thanks for your help.

For Ccleaner uncheck:
a) Memory Dumps
b) Windows Log Files
c) Windows Error Reporting
d) Windows Event Logs




Windows driver verifier is designed to stress test drivers.

If there are misbehaving drivers the computer will crash.

If dump files are created they can be debugged.

Misbehaving drivers are then uninstalled or uninstalled and reinstalled.

The tool is run for approximately 48 hours and then an additional 36 hours after the last BSOD.

If there are no further BSOD this concludes the use of the tool.

After each BSOD you must turn off the tool in order to return to the desktop.

Learn the Windows RE commands reset and bootmode.

These are ran in safe mode or safe mode with command prompt.

In case these fail the next option is system restore.

If system restore fails you can restore a backup image or use registry commands.

Start the tool with the 3 customized test settings in the Ten Forums link.

Increase the simultaneous customized test settings by 3 - 5 / hour up to the 19 customized test settings in the Microsoft link.

There can be performance problems and / or slow boot while using the tool.

If necessary the customized test settings can be modified.

Summary:
a) make a new restore point
b) test all non-Microsoft drivers
c) test no Microsoft drivers
d) after each BSOD use the reset command to turn off the tool
e) if the reset command does not work then use the bootmode command
f) only if both reset and bootmode command fail to turn off the tool then use restore
g) start with the 3 customized test settings in the Ten Forums link
h) increase the customized test settings up to the 19 customized test settings in the Microsoft link
i) report any performance problems or very slow boot so that the customized settings can be modified