[SOLVED] Win Server 2012 R2 Windows Update / Component Store Corruption

A

adamjw

Well-known member
Joined
Mar 6, 2018
Posts
59
Hi, I have the following problem:

Windows Update returns error code 80073712

Things I have tried:

Windows Update troubleshooter
same problem

Manually resetting Windows Update components
same problem

Uninstalling the last windows update
error - both through the GUI and through DISM

sfc /scannow
Windows Resouce Protection could not perform the requested operation

DISM.exe /Online /Cleanup-image /RestoreHealth
Error: 14098
The component store has been corrupted.

DISM using offline image
same result

While SFCFix was running it displayed a message that due to the nature of corruptions scan times have been extended, but when it finished it said it found no corruptions.

Following is the SFCFix log:

SFCFix version 3.0.2.1 by niemiro.
Start time: 2021-07-12 13:11:16.667
Microsoft Windows Server 2012 R2 Update 3 - amd64
Not using a script file.




AutoAnalysis::
SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2021-07-12 14:33:14.874
----------------------EOF-----------------------

Here is the CBS file:

CBS.zip

Thanks!
 
Hello,

As you will know some of our helpers have increased workloads professionally, and this has resulted in a slower response time for Windows Update threads.

I am checking to see if you still need help with this thread. If so please respond and this will bring your thread to our attention again. Thank you for your patience.
 
Hi, yes I do still need help, thanks!

I've been able to uninstall some windows updates that showed as corrupt, and now certain things are slightly better, but the overall problem remains.

I'm unable to uninstall KB2966826 - I get error 14098 Component Store Corrupted.

I can now install some windows updates, though others fail.

sfc /scannow will now run, and it reports:

"Windows Resource Protection found corrupt files but was unable to fix some of them."

DISM.exe /Online /Cleanup-Image /RestoreHealth
and
DISM.exe /Online /Cleanup-Image /StartComponentCleanup
both still return error 14098

I ran SFCFix again and it was unable to create a logfile, but it reported that it found 3 corruptions and fixed 0.

Here is the new CBS folder:

CBS Folder

Thanks!
 
I've looked through your latest CBS folder and can see the three possible corruptions which were being referenced. The following should help to correct these.

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Attach this SFCFix.txt file into your next post for me to analyse please.
 

Attachments

Thanks for the file. It completed successfully.

Please try the following:

DISM /RestoreHealth Scan
  1. Open an Admin Command Prompt and copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, then press Enter
    Dism /Online /Cleanup-Image /RestoreHealth
  2. Let me know if it finishes this time and once again provide the CBS folder as you did before.
 
Deployment Image Servicing and Management tool
Version: 6.3.9600.17031

Image Version: 6.3.9600.17031

[==========================100.0%==========================]

Error: 0x80240021

DISM failed. No operation was performed.
For more information, review the log file.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
 

Attachments

I'll be looking into this over the weekend. Although DISM completed it is not able to automatically fix the missing/corrupted files.
 
I have a fix for about 85% of the missing/corrupt files. I think it would be good to apply this fix and make sure that things are going in the right direction while I continue to search for the remaining ones.

Step 1: SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.


  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the file, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script. This may take a while.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt
  8. Attach this file into your next post for me to check please.

Step 2: Rerun SFC /scannow

Step 3: Provide the latest CBS Folder
 
Thank you. Following is the output of SFC /scannow, and attached are the files:

Beginning system scan. This process will take some time.

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

Windows Resource Protection found corrupt files but was unable to fix some
of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios.
 

Attachments

Hello adamjw,

Great work!

I'm trying to find the remaining files - to help me with this please can you provide me with a copy of your COMPONENTS hive.

Retrieve Components Hive
1. Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
2. Please copy this file to your desktop.
Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
3. Right-click on this file on your desktop and select Send To...Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
4. The file will likely be too large to upload here so please upload to a file sharing service. Examples of services to upload to are Dropbox or OneDrive or SendSpace and then just provide the link in your reply.
 
I have looked at your Components hive and can see that there are four cases of corrupt data in the file. I can repair this data but the type of error is a single bit error which is most commonly associated with hardware malfunction such as memory or disk failure. This could explain a lot of the reasons for the corruptions which seem to be appearing on your system. It would make sense to look into this before continuing. To start with I would suggest you provide the logfiles which we would normally request for a blue screen of death (BSOD) problem and these will provide me with a set of files that can help determine if you have been having any issues with the hardware. There may be more tests I can ask you to run later on. Follow the instructions below to create the logfiles which you can upload into your next post here (no need to create a BSOD thread).

Blue Screen of Death (BSOD) Posting Instructions - Windows 10, 8.1, 8, 7 + Vista
 
The first thing to note is that there is a history of many BSOD crashes, they occur from Feb 2016 to 31 Jan 2020. The crashes have many references to one-bit memory corruption and pool corruption. Did you do anything from Feb 2020 onwards which has caused these crashes to stop? My guess is that the earlier crashes have contributed to system file corruption.

Code: 
BugCheck 1E, {ffffffffc0000005, fffff8034896f761, 0, ffffffffffffffff}
Probably caused by: ntkrnlmp.exe ( nt!SwapContext_PatchLdMxCsr+f4 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 109, {a3a01f59b59545e4, 0, c0129d4765ce0069, 101}
Probably caused by: Unknown_Image ( ANALYSIS_INCONCLUSIVE )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1A, {41792, fffff6bffdaac080, 4000000000000, 0}
Probably caused by: memory_corruption ( ONE_BIT )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 139, {3, ffffd00022586390, ffffd000225862e8, 0}
Probably caused by: ntkrnlmp.exe ( nt!KiFastFailDispatch+d0 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1000007E, {ffffffffc0000005, fffff801fb66f9e9, ffffd0004b4547e8, ffffd0004b453ff0}
Probably caused by: ntkrnlmp.exe ( nt!CmpCleanUpKcbCacheWithLock+1b9 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 24, {b500190645, ffffd000e6c30408, ffffd000e6c2fc10, fffff800488162aa}
Probably caused by: Ntfs.sys ( Ntfs+1cf2aa )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1A, {41792, fffff6bffdb33098, 4000000000000, 0}
Probably caused by: memory_corruption ( ONE_BIT )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1A, {41793, fffff6801553b8b8, 8, 7}
Probably caused by: ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+1decf )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1A, {41792, fffff6806e342008, 4000000000000, 0}
Probably caused by: memory_corruption ( ONE_BIT )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck BE, {ffffc001b5110008, 8000000064d1b121, ffffd00022d13f70, b}
Probably caused by: ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+a85a )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 3B, {c0000005, fffff80368499507, ffffd00023e38d40, 0}
Probably caused by: memory_corruption ( nt!MiQueryAddressState+1d7 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 24, {b500190645, ffffd00021ea9c58, ffffd00021ea9460, fffff8017d230918}
Probably caused by: Ntfs.sys ( Ntfs+1a918 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 109, {a3a01f5a71fcc81a, 0, c0543ad7e6cf2e0f, 101}
Probably caused by: Unknown_Image ( ANALYSIS_INCONCLUSIVE )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 139, {3, ffffd001f08fdf10, ffffd001f08fde68, 0}
Probably caused by: ntkrnlmp.exe ( nt!KiFastFailDispatch+d0 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 109, {a3a01f58c359d9c2, 0, 76b61aa8d6681136, 101}
Probably caused by: Unknown_Image ( ANALYSIS_INCONCLUSIVE )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1A, {5002, fffff58010804000, 9042, 209041ffffffe}
Probably caused by: ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+20755 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 19, {d, ffffc000c761b000, fbfe5d8ada79345b, fbfa5d8ada79345b}
Probably caused by: Pool_Corruption ( nt!ExDeferredFreePool+1036 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1A, {41792, fffff68065769fe0, 2000000000000, 0}
Probably caused by: memory_corruption ( ONE_BIT )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1A, {41792, fffff6bffef5f080, 4000000000000, 0}
Probably caused by: memory_corruption ( ONE_BIT )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1A, {41792, fffff68051d7e0b8, 2000000000000, 0}
Probably caused by: memory_corruption ( ONE_BIT )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1A, {5002, fffff79940000000, 143a9, 4143aaffffffe}
Probably caused by: ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+20755 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 24, {b500190645, ffffd00022b46908, ffffd00022b46110, fffff801fc770cea}
Probably caused by: Ntfs.sys ( Ntfs+dbcea )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1A, {5002, fffff58010804000, 6799, 20679effffffe}
Probably caused by: ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+20755 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1000007E, {ffffffffc0000005, fffff8023531d033, ffffd000b3b206c8, ffffd000b3b1fed0}
Probably caused by: ntkrnlmp.exe ( nt!ExFreePoolWithTag+33 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 19, {3, ffffe0001c0e19d0, fffde0001c0e19d0, ffffe0001c0e19d0}
Probably caused by: Pool_Corruption ( nt!ExDeferredFreePool+ebb )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 34, {51157, ffffd000228fe4f8, ffffd000228fdd00, fffff8026615bb9b}
Probably caused by: ntkrnlmp.exe ( nt!CcAcquireByteRangeForWrite+2f3 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 139, {3, ffffd0004edf1530, ffffd0004edf1488, 0}
Probably caused by: ntkrnlmp.exe ( nt!KiFastFailDispatch+d0 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 4A, {7ffd82c5072a, 2, 0, ffffd000f5747b80}
Probably caused by: ntkrnlmp.exe ( nt!KiSystemServiceExit+24b )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1A, {41792, fffff6bffe100180, 4000000000000, 0}
Probably caused by: memory_corruption ( ONE_BIT )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1A, {5200, ffffe000e797c000, bbf87553dd33c2e0, bbfc7553dd33c2e0}
Probably caused by: ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+3008f )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 34, {51157, ffffd0002056b2a8, ffffd0002056aab0, fffff8027109e6fd}
Probably caused by: memory_corruption ( nt!MiUnlockMdlWritePages+79 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1E, {ffffffffc0000005, fffff803ebeb6ef1, 0, ffffffffffffffff}
Probably caused by: memory_corruption ( nt!MiDereferenceControlAreaPfn+1d )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1A, {41792, fffff6bffef0cfc8, 4000000000000, 0}
Probably caused by: memory_corruption ( ONE_BIT )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 3B, {c0000005, fffff8014b7ab9ea, ffffd0002235eeb0, 0}
Probably caused by: memory_corruption ( nt!MmQueryVirtualMemory+1da )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1A, {41792, fffff6bffe1b7100, 4000000000000, 0}
Probably caused by: memory_corruption ( ONE_BIT )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 24, {b500190645, ffffd00020ea7488, ffffd00020ea6c90, fffff801da770a1f}
Probably caused by: ntkrnlmp.exe ( nt!ExReinitializeResourceLite+157 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 50, {fffff58012816a88, 0, fffff80312ae1c74, 2}
Probably caused by: memory_corruption ( nt!MiUpdateWsle+6d4 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 7F, {8, fffff801614a4e70, ffffd00021cae000, fffff8016012d2ae}
Probably caused by: win32k.sys ( win32k!DwmAsyncActivationChange+85 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1A, {41793, fffff68009c42fe0, 10d, 10c}
Probably caused by: ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+a5bf )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 139, {3, ffffd0002330d3b0, ffffd0002330d308, 0}
Probably caused by: Pool_Corruption ( nt!ExDeferredFreePool+100d )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1A, {41793, fffff6bfff8bbfb8, b, a}
Probably caused by: ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+a5bf )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1E, {ffffffffc0000005, fffff803afdcf66a, 0, ffffffffffffffff}
Probably caused by: ntkrnlmp.exe ( nt!SwapContext_PatchXRstor+0 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 24, {b500190645, ffffd001f91b08f8, ffffd001f91b0100, fffff8004c96d65f}
Probably caused by: Ntfs.sys ( Ntfs+de65f )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 19, {3, ffffc00179359500, 3a34303a34302035, ffffc00179359500}
Probably caused by: Pool_Corruption ( nt!ExDeferredFreePool+ebb )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 19, {e, ffffc0010fca1720, 0, 29a3f8e3b55a9659}
Probably caused by: Pool_Corruption ( nt!ExDeferredFreePool+dac )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 19, {d, ffffc00088842a40, e8cf8b49d28b41c6, 518fe124fd620b34}
Probably caused by: Pool_Corruption ( nt!ExDeferredFreePool+1036 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 3B, {c0000005, fffff802d731205f, ffffd0012fd14b60, 0}
Probably caused by: ntkrnlmp.exe ( nt!ExAllocatePoolWithTag+5ff )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1A, {5003, fffff79940000000, 38fb, 0}
Probably caused by: ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+15a99 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 50, {ffffc000d3891000, 0, fffff802ffe21a13, 2}
Probably caused by: ntkrnlmp.exe ( nt!HvpSetRangeProtection+67 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck D1, {0, 2, 8, 0}
Probably caused by: Unknown_Image ( ANALYSIS_INCONCLUSIVE )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

You do not appear to have had any BSOD problems since 31 Jan 2020. Did you make any changes to the system such as replacing components or changing BIOS settings?
 
This is a VM running on the same hardware as a similar VM that hasn't had similar problems so it's a bit strange. There may have been a change in January 2020 that corrected the problem but I'm not certain. But at least the BSOD problems are not continuing to occur - that seems like good news. Is there anything else we should do before repairing the component hive corruption?
 
Thanks for the background. We can hopefully assume that with over 12 months of no crashes the problem has gone away and perhaps a change was made to the host machine back in Jan 2020. This leaves us with the corruptions to sort out and any associated WU file errors.

I will send you the corrected Components file and here are the instructions:

Step 1 - Replace Components Hive Manually

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

  1. Download COMPONENTS.ZIP and save to your desktop.
  2. Right-click on it and select Extract all.... Make sure the "Show extracted files when complete" is checked and click Extract.
  3. Now we have the COMPONENTS file that we will be using to replace your current one.
  4. Navigate to C:\Windows\System32\config
  5. Right-click on the current COMPONENTS file and select rename. Rename it to COMPONENTS.bad.
    Note: If you get an error that the file is in use, reboot your computer and then try again.
  6. Take the file from the Components folder on your desktop and paste it into C:\Windows\System32\config
Step 2: Please run another DISM after this and provide the latest CBS Folder so that we can assess what is left to fix.
 
Great, thank you. Following and attached are the results.

Deployment Image Servicing and Management tool
Version: 6.3.9600.17031

Image Version: 6.3.9600.17031

[==========================100.0%==========================]

Error: 0x80240021

DISM failed. No operation was performed.
For more information, review the log file.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
 

Attachments

Thank you for the LOGS, I am concerned about the high numbers of corrupt files and want to explore other possible corruptions in the registry. If you are comfortable working in the registry please do the following, if you would rather not mess in the registry let me know and I'll send another way to do it.

Step#1 - Export CBS hive
  • Click on the Start button and in the search box, type regedit
  • When you see regedit on the list, right-click on it and select Run as administrator.
  • When regedit opens, using the left pane, navigate to the following registry key and select it by clicking on it once.

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing
  • Once selected, click File > Export....
  • Change the Save as type: to Registry Hive Files (.).
  • Name this file ComponentBasedServicing (with no file extension) and save it to your Desktop.
  • Right-click on the saved file and choose Send To -> Compressed (zipped) Folder.
  • Attach the .ZIP file to your next post.
  • If the file is too large to upload here, upload to Dropbox or OneDrive or SendSpace and just provide the link here.

Step#2 - Export SideBySide
  1. Click on the Start button and in the search box, type regedit
  2. When you see regedit on the list, right-click on it and select Run as administrator
  3. When regedit opens, using the left pane, navigate to the following registry key and select it by clicking on it once.

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide
  4. Once selected, click File > Export....
  5. Change the Save as type: to Registry Hive Files (.)
  6. Name this file SxS (with no file extension) and save it to your Desktop.
  7. Once done please upload this file via Dropbox or OneDrive or SendSpace.
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top