[SOLVED] 22H2 | .NET update | BSOD | DISM 0x800f081f

Race4803 · Jul 31, 2023

Greetings,

And sorry for the messy thread title, I didn't really know what to put in there since a few things happened, in order as follows :

updates KB5028937 and KB5028412 have been applied in the last 2 days (pretty sure Windows update broke something when doing those)
got a BSOD
tried running sfc and DISM (check, restore, with external source from win10 iso and all, tried many things I could ever find before arriving here)
- sfc always saying things are broken but can't fix them, and each time seems to fix a new thing
- DISM either saying it successfully restored or giving a 0x800f081f
got a second BSOD
tried a few sfc&DISM again, always same results
no BSOD since but it'll probably happen again somehow...

Minidumps of both BSOD are joined,
ComponentsScanner seemed to say things were broken with red text, but log doesn't say much
CBS only had the one log file, and joined dism log even if not asked because why not, maybe can help...

Thanks forward !

x BlueRobot · Aug 9, 2023

Are you running Driver Verifier at all? You can check with the following command if you're not sure:

Rich (BB code):

verifier /querysettings

Additionally, could you please check that you have kernel memory dump, it should be available here:

Code:

%systemroot%\MEMORY.DMP

If so, then please place it inside .zip folder and then upload it to a file sharing site such as WeTransfer as it will be too large to attach to a forum post.

Race4803 · Aug 15, 2023

Thanks for the reply, sorry I just came back but I'll be more reactive from now on !

so I just checked and nothing in Driver Verifier is enabled on my side.

Here's the memory dump.

Thanks forward !

x BlueRobot · Aug 16, 2023

Thanks, the issue doesn't seem to be hardware-related in my opinion which what usually causes Stop 0xEFs. I would suggest running Driver Verifier for now with the recommended settings as suggested here:

Driver Verifier - BSOD related - Windows 11, 10, 8.1 and 8

Rich (BB code):

3: kd> .exr ffff8c0a14b3fa18
ExceptionAddress: 00007ffcf18833c6 (ntdll!RtlpGetActivationContextData+0x0000000000000052)
   ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
  ExceptionFlags: 00000001
NumberParameters: 1
   Parameter[0]: 0000000000000039
Subcode: 0x39 FAST_FAIL_CONTROL_INVALID_RETURN_ADDRESS Shadow stack violation

Race4803 · Aug 16, 2023

Alright thanks a lot,
Driver Verifier is running,
guess I keep it on until I get another potential BSOD ?

Do I need to pause Windows Updates for now or it shouldn't pose problem to apply newer ones ? (KB5029649 and KB5029244 are awaiting installation)

x BlueRobot · Aug 17, 2023

Race4803 said:
guess I keep it on until I get another potential BSOD ?

Yes, if you don't get any additional crashes within the next few days then I would disable it.

Race4803 said:
Do I need to pause Windows Updates for now or it shouldn't pose problem to apply newer ones ?

I would just pause updates for now until we have resolved your other errors otherwise it will just fail again.

Race4803 · Aug 17, 2023

OK so it just happened that tonight trying to boot my computer :
it's in a BSOD loop at boot (triggered by Driver Verifier)
and it only goes to the auto repair mode on which it asks the Microsoft account password I'm using on the computer which I can't find because I always use pin code

...
I'm so dumb...

I seemingly can't trigger the standard safe mode to go disable the verifier...

any insight on what would be the easiest solution to get out of this?

Thanks forward again!

Race4803 · Aug 17, 2023

alright I've been able to make a windows installer usb and I've been able to access the restoration point thing,

trying it, and hoping I'll be able to boot again after this...

Race4803 · Aug 17, 2023

alright,

booted again,
here's the latest fresh memdump (guessing you'll be interested in it since it's bigger and newer)...

the big red text mentioning System Restore Point on the driver verifier guide is really needed

getting offline for now, at least the thing boots and probably still has the same problems, but we got new dumps !

Thanks a lot again for your patience !

Race4803 · Aug 17, 2023

(also here's the related minidump which I realized I forgot!)

x BlueRobot · Aug 18, 2023

Thanks, it looks like Riot Vanguard (vgk.sys) is causing issues so I would suggest that you remove it or try and find an updated version. It is plagued with bugs and security issues, much like BEDaisy.sys which is the BattleEye anti-cheat driver.

Race4803 · Aug 18, 2023

Alright,
It's weird it's still showing in dumps and things because I had disabled its load at boot through Sysinternals' Autoruns...maybe some leftover part of some part of it was messing things...

Now it's uninstalled, what do you suggest I try next ?
things that come in mind are trying again a cycle of SFC and DISM to see if now they can fix things ?
or should I reenable Driver Verifier to see if it flags another thing ?

What do you think would be best ?

Thanks forward

x BlueRobot · Aug 21, 2023

Let's focus on repairing that corrupted payload file first of all, otherwise any update attempts will simply fail again.

Rich (BB code):

2023-08-01 04:24:24, Info                  CBS    =================================
2023-08-01 04:24:24, Info                  CBS    Checking System Update Readiness.
2023-08-01 04:24:24, Info                  CBS    
2023-08-01 04:24:24, Info                  CBS    (p)    CSI Payload Corrupt    (n)            x86_netfx4-csc_exe_b03f5f7f11d50a3a_4.0.15840.3_none_be934e5d4d003cf9\csc.exe
2023-08-01 04:24:24, Info                  CBS    Repair failed: Missing replacement payload.

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 WeTransfer and then just provide the link in your reply.

Race4803 · Aug 21, 2023

thanks !
here's the file

x BlueRobot · Aug 23, 2023

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.

Download SFCFix.exe (by niemiro) and save this to your Desktop.
Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
Save any open documents and close all open windows.
On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
SFCFix will now process the script.
Upon completion, a file should be created on your Desktop: SFCFix.txt.
Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

Afterwards, please run DISM again and then le me know if it was successful or not. If it reports any errors, then please provide your CBS logs as you did before. Otherwise, please try and update the system.

Race4803 · Aug 25, 2023

Thanks, here's the log

Code:

SFCFix version 3.0.2.1 by niemiro.
Start time: 2023-08-25 19:59:19.229
Microsoft Windows 10 Build 19045 - amd64
Using .zip script file at C:\Users\olivi\Downloads\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\Windows\WinSxS\x86_netfx4-csc_exe_b03f5f7f11d50a3a_4.0.15840.3_none_be934e5d4d003cf9\csc.exe

Successfully copied file C:\Users\olivi\AppData\Local\niemiro\Archive\x86_netfx4-csc_exe_b03f5f7f11d50a3a_4.0.15840.3_none_be934e5d4d003cf9\csc.exe to C:\Windows\WinSxS\x86_netfx4-csc_exe_b03f5f7f11d50a3a_4.0.15840.3_none_be934e5d4d003cf9\csc.exe.

Successfully restored ownership for C:\Windows\WinSxS\x86_netfx4-csc_exe_b03f5f7f11d50a3a_4.0.15840.3_none_be934e5d4d003cf9\csc.exe
Successfully restored permissions on C:\Windows\WinSxS\x86_netfx4-csc_exe_b03f5f7f11d50a3a_4.0.15840.3_none_be934e5d4d003cf9\csc.exe
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2023-08-25 19:59:19.546
Script hash: ISpNxG1vCykC7MM8KljNdz8HF4j8qEB5YMroink9SdU=
----------------------EOF-----------------------

I did run DISM /Online /Cleanup-image /Restorehealth afterwards, and it did say the restoration is successful, thanks !

Should run some SFC before trying to get latest Windows Updates, or SFC isn't needed ?

x BlueRobot · Aug 26, 2023

I wouldn't worry about SFC for now, please attempt to update again and then post the CBS logs if it fails.

Race4803 · Aug 26, 2023

It just found and installed KB4023057 and KB5029847, nothing seems to have gone wrong, and no other BSOD occured since the Driver Verifier one.

x BlueRobot · Aug 27, 2023

I would do a quick check for any additional updates otherwise I think we can mark this thread as solved.

Race4803 · Aug 27, 2023

alright thanks a lot,
I'll repost here if any other problem occurs !

Marking it as solved for now

[SOLVED] 22H2 | .NET update | BSOD | DISM 0x800f081f

Member

Attachments

Administrator

Member

Administrator

Member

Administrator

Member

Member

Member

Member

Attachments

Administrator

Member

Administrator

Member

Administrator

Attachments

Member

Administrator

Member

Administrator

Member