Win 10 (22H2) DISM Corruptions - Error: 0x800f081f with 621 CBS Manifest Corruptions

RafaMGam

Member
Joined
Dec 17, 2024
Posts
5
Hey there!

So I've been down this rabbit hole and I ended up here. Sorry for my ignorance, as I don't know a lot about computers!

For the last year or so I've been getting BSOD crashes pointing to system drivers, often nothing specific at all. I tried repairing my Windows installation the usual ways, but it kept crashing during the repair and reverting the changes back. Same for, Windows Update - it crashes when I try to update, so I've been stuck on build 19045.3803 for a while now. So naturally I tried doing all the SFC and DISM commands the various internet results told me to, and I ended up falling on the "Source files not found" error when trying to repair my Windows image. Then I learned about SFCFix, which also failed, but then I saw a lot of people having success here, and how the CBS.log would tell me what was missing/corrupted.

Well, to my surprise I opened the CBS.log and I was surprised to see the staggering amount of 617 CBS Manifest Corruptions (working hard to one-up the thread before me). Oddly enough, a lot of those missing files are for older Windows builds, so I'm not sure at all what's happening here. I read the guide teaching how to fix those corruptions by grabbing the files from a VM install, but it's such a huge number of files that I'm not even sure how to start tackling that, or if I have the willpower to.

My system is fairly stable during normal use, though it crashes a bunch when booting (it gets there eventually) and when running more demanding games/software. Considering how it's been failing to repair Windows, I'm afraid of attempting a Clean Install and ending up with no OS at all. Since I use this computer for work, I'm trying as much as possible to avoid having to send it to repair, so any help I can get here would be immensely appreciated!

The requested files are attached below. Thanks!
 

Attachments

Hi @RafaMGam,

Welcome to Sysnative Forums!

If you haven't already, please review the posting instructions here, and attach the requested log files. Without log files, our helpers will not be able to assist, and this will slow down fixing your machine.

If logs have been already been provided, our team of volunteers will analyse the provided log files to build a fix for your system. Please be aware that this may take several days from your initial post, due to the high volume of threads that we receive.


- Sysnative Windows Update Team
 
Hi and welcome to Sysnative,

Download the
6092ba29b640f-SysnativeBSODCollectionApp_101-2.png
Sysnative BSOD Dump + System File Collection App to your desktop.
  • Right-click on SysnativeBSODCollectionApp.exe and select "Run as administrator".
  • When the tool is ready, it will open the directory: C:\Users\<username>\Documents.
  • Post the zipfile: SysnativeFileCollectionApp.zip as attachment in your next reply.
  • The textfile 'BSODPostingsInstructions' you may close.
 
Hi,

1. Some of the *.dmp files are corrupted, so I would suggest to start a new thread in the BSOD section after following the BSOD the BSOD posting instructions.
2. Please refer to this thread as well.
3. When the BSOD issue has been resolved we can pick-up this thread again to repair the corruptions.
 
Hi,

I believe that would be my fault, since I was impatient and pressed the restart button during my last BSOD. I got another couple BSODs and it seems to have generated proper *.dmp files this time around.

Just in case, I'm uploading a new zipfile with these *.dmp files included, so please let me know if they will be good enough, or if you still rather I start a new thread in the BSOD section. Thanks!
 

Attachments

Hi,

I believe that would be my fault, since I was impatient and pressed the restart button during my last BSOD. I got another couple BSODs and it seems to have generated proper *.dmp files this time around.

Just in case, I'm uploading a new zipfile with these *.dmp files included, so please let me know if they will be good enough, or if you still rather I start a new thread in the BSOD section. Thanks!
Your sysnative file collection is not in english, so I can't read it.
 
Cheers! Following the posting instructions, here's some extra info:
  • System Manufacturer: unknown
  • Laptop or Desktop: Desktop
  • Exact model number: unknown
  • OS: Windows 10 x64
  • What was original installed OS on system: Windows 10
  • Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer): unknown
  • Age of system? (hardware): nearly 2 years
  • Age of OS installation: nearly 2 years
  • Have you re-installed the OS: no
  • CPU: AMD Ryzen 5 4500, 6-Core, 12-Threads, 3.6GHz (4.1GHz Turbo), Cache 11MB, AM4, 100-100000644BOX
  • RAM: 2 x Team Group T-Force Vulcan Pichau, 8GB (1x8), DDR4, 3200MHz, C16, Branca RTB, TLPBD48G3200HC16F01
  • Video Card: Asus GeForce RTX 2060 Dual OC Edition 6GB GDDR6 192-bit, DUAL-RTX2060-O6G-EVO
  • MotherBoard: Asus PRIME A520M-E DDR4 Socket AM4 Chipset AMD, PRIME A520M-E
  • Power Supply: Corsair CV Series CV650 80 Plus Bronze 650W, CP-9020236-BR
  • Is driver verifier enabled or disabled? Disabled. I tried running it, but it immediately crashed my system.
  • What security software are you using? Default Windows one
  • Are you using proxy, vpn, ipfilters or similar software? No
  • Are you using Disk Image tools? (like daemon tools, alcohol 52% or 120%, virtual CloneDrive, roxio software) No
  • Are you currently under/overclocking? Are there overclocking software installed on your system? Not overclocking. MSI Afterburner installed for checking temperature.
Speccy snapshot: http://speccy.piriform.com/results/PY0JauG0YL1dO0lhGqJ0nqc

As for my sysnative file collection's language, I assume that's because of my system's language, which is not something I can easily change (or at all, I imagine). If there is a way to change the file collection's language that I missed, please advise me and I'll change it. Thanks!
 
Unfortunately you didn't change the system language, it's all still in Portuguese, which none of us read. For the future you need to temporarily change the system language to English (Settings > Time & Language > Language & Region, and make the preferred language English).

From the dumps however, this looks very much like bad RAM so in the first instance I suggest you test your RAM...
  1. Download Memtest86 (free)
  2. Use the imageUSB.exe tool extracted from the download to make a bootable USB drive containing Memtest86 (1GB is plenty big enough). Do this on a different PC if you can, because you can't fully trust yours at the moment.
  3. Then boot that USB drive on your PC, Memtest86 will start running as soon as it boots.
  4. If no errors have been found after the four iterations of the 13 different tests that the free version does, then restart Memtest86 and do another four iterations. Even a single bit error is a failure.
Let us know how that test goes.
 

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

Back
Top