FenX2024
Member
- Oct 5, 2024
- 22
For quite some time, I have not been able to update Windows 8.1 because of the error "80073712". Because of the irresponsible person I am, that didn't really bother me until Roblox broke and I couldn't launch it anymore. I've since fixed Roblox with the help of their support team (by uninstalling it and deleting the folder using "rmdir /s Roblox" through the command prompt), but now launching it causes my computer to give me the blue screen of death with the error "IRQL_NOT_LESS_OR_EQUAL", which is a whole different issue - I'd like to tackle this one first. I have a slight suspicion that the blue screens of death when launching Roblox are because of system corruptions (I copied my old hard drive that was failing using Clonezilla, which might've transferred some corrupted files). Because of that, I went on a whole journey and here it is:
- I've run DISM (with /checkhealth, /scanhealth, and /restorehealth) numerous times, the latter parameter of which is giving me the "0x800f0906" error, but I did find out that there are 72 corruptions, which is many! I've also tried using a Windows 8.1 .iso image as /source (with /limitaccess), which didn't help at all (most likely since the versions didn't match),
- I've run SFC with /scannow, which doesn't find any corruptions,
- I've tried using SFCFix, which didn't help by itself. I did use the "Trace::" script (the example of which I saw in another thread while trying to find solutions) to find the source of the corrupted files - it seems to be just three updates: KB4503276, KB4578953, and KB3124275. I've included the "SFCFix.txt" file with those results. Also, now SFCFix doesn't find any errors for whatever reason (maybe because of the messing described below) - I've included the "SFCFixNow.txt" file with these results,
- I also, being desperate when trying to avoid making a thread, used an example of one of another user's solution (the "PowerCopy::" SFCFix.zip file) to try to fix a single corruption by installing the same file (but an earlier version of it) to replace the corrupted one, and then later putting the earlier-version file into the same-name-as-corrupted-file folder, which thankfully didn't work. I will not do that again,
- In the middle of me writing this message, my computer crashed because of "MEMORY_MANAGEMENT" (fun), so now you can have my "components"! :)