{"version":"1.0","provider_name":"Ami Sapphire's Notices","provider_url":"http:\/\/cwcyrix.nsupdate.info\/gnu-social\/public\/","type":"link","title":"Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Monday, 30-Oct-2023 17:41:11 EDT","author_name":"Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)","author_url":"http:\/\/cwcyrix.nsupdate.info\/gnu-social\/public\/index.php\/amisapphire","url":"http:\/\/cwcyrix.nsupdate.info\/gnu-social\/public\/notice\/182","html":"And the update: Sis's laptop seems to be fine now. Some settings seem to be working properly now (though that was done after DISM and SFC twice).<br \/>\n<br \/>\nOriginally, the unit BSODed, then it was brought to me. Unit also had a delay powering on, then it started checking the disk for errors. Then it booted to the Windows desktop.<br \/>\n<br \/>\nThen part of the AMD GPU drivers were corrupt. This prompted me to scan the disk twice: \/f, then \/r. Noticed the Date\/Time Settings would crash, but pretty much everything else was fine.<br \/>\n<br \/>\nSadly, DISM was pretty much useless, but sfc \/scannow was not so. This was run twice. Eventually, the Date\/Time Settings worked.<br \/>\n<br \/>\nAlso noticed after DISM, the build number discrepancy showed. <br \/>\n<br \/>\n<br \/>\nReference:<br \/>\n<a href=\"http:\/\/cwcyrix.nsupdate.info\/gnu-social\/public\/notice\/179\" title=\"http:\/\/cwcyrix.nsupdate.info\/gnu-social\/public\/notice\/179\" rel=\"nofollow noreferrer\" class=\"attachment\">http:\/\/cwcyrix.nsupdate.info\/gnu-social\/public\/notice\/179<\/a>","thumbnail_url":"http:\/\/cwcyrix.nsupdate.info\/gnu-social\/public\/thumbnail\/45?w=96&h=96"}