Question Windows 10 Kernel 41 Crashes

[TimorousTurtle]

Windows 10 updates (cumulative and security) started consistently failing to install on my computer (error 0x80070643), Microsoft tech support helpfully told me that it was a known issue and that I should just restore my computer as that might solve the problem. It didn't and now my computer crashes randomly and I have no idea what to do.

Computer Specifications:
Processor AMD Ryzen 7 3700X 8-Core Processor 3.59 GHz
Installed RAM 16.0 GB
System type 64-bit operating system, x64-based processor

Windows Specifications:
Edition Windows 10 Home
Version 22H2
Installed on ‎11/‎16/‎2022
OS build 19045.4170
Experience Windows Feature Experience Pack 1000.19054.1000.0

This link is for the Event Log
This link is for the Sysnative Zip File

 

[Ralston18]

[Note: above links download a .zip file and a .evtx file]

PSU: make, model, wattage, age, condition (original to build, new, used, refurbished)?

Disk drive(s): make, model, capacity, how full?

= = = =

Open Reliability History/Monitor and take a couple of representative screenshots showing as many critical (red) errors and error codes as possible. Show the full window.

Post the screenshots here via imgur (www.imgur.com).

 

[TimorousTurtle]

The links are the native formats for the Event Log and the SysnativeZip, should I have posted them as different formats?

The PSU is a now 4 year old (but I bought it new and clean everything every 6 months), and has always been run off of a surge protected UPS:
KRATOS P1-650G

AC Input: 100-240V / 10A / 47-63Hz
DC Output: +3.3V / +5V / +12V / -12V / +5Vsb
Max. Output Current: 20A / 20A / 54.2A / 0.3A / 2.5A
Max. Output Power: 100W / 650W / 3.6W / 12.5W
Total Power: 650W
Protection: OVP / UVP / OPP / OCP / SCP / SP / ICP

I have three drives:
I boot and store everything non-gaming related on my C drive which is a PNY CS900 1TB SSD that has 476GB free.
All my gaming files on a portable external WD-Black 2TB SSD drive via a USB-C to 3.0 USB-A port and it has 788GB free
Lastly I have a STEL8000100 Backup Plus Hub 8TB External Desktop magnetic disk backup via 3.0 USB-A to 3.0 USB-A that has 7427GB free.

Here are the screencapture links from oldest to most recent:

https://imgur.com/nwH8Aqw

View: https://imgur.com/nwH8Aqw

https://imgur.com/QevROh7

View: https://imgur.com/QevROh7

https://imgur.com/JyUWEft

View: https://imgur.com/JyUWEft

https://imgur.com/HzuZ6Po

View: https://imgur.com/HzuZ6Po

https://imgur.com/c1zkseD

View: https://imgur.com/c1zkseD

https://imgur.com/2JVzw1o

View: https://imgur.com/2JVzw1o

 

[ubuysa]

It's a known problem, I ran into it. It's related to the UEFI recovery partition needing to be resized. See the Microsoft post link below and follow the instructions to increase the size of the WinRE (AKA Recovery) partition.

https://answers.microsoft.com/en-us...80070643/e6473fa4-f2d4-42c3-b4be-266b43454306

 

[TimorousTurtle]

I followed the directions from the link provided, and I encountered a problem in that even though I set the execution policy to "remotesigned" it would not run the script supplied from Windows. Does anyone know what is going wrong?

https://imgur.com/OpWKyWd

View: https://imgur.com/OpWKyWd

 

[ubuysa]

I'm not sure the script is signed. Since it's a Microsoft script I set the execution policy to unrestricted, ran the script, and then set it back to restricted.

 

[TimorousTurtle]

That is what is confusing me; I'm running Powershell as an administrator, and I ran "set-executionpolicy remotesigned" which should set the execution policy to unrestricted. But even then I get an error in Powershell that it won't run the script from the link.
I even tried seeing if changing the execution policy with only "Yes" vs "Yes to All" would change the result, and if you look at the linked image, both have the same error.
I've even tried restarting and performing every step again from the beginning, but I run into the same problem.

 

[TimorousTurtle]

OK, so...
I had to track down the documentation, in my talk with the Microsoft IT they had me run some other scripts before restoring my computer. I looked into things and apparently this messed with my computer's Windows PowerShell (x32) execution policies, and disabled WinRe. I've since enabled WinRe with Command Prompt, set my execution policies to unrestricted, followed the links steps to run the supplied script (I used the "-bypass" to force Powershell to execute the script), restarted, and... my windows update went through!
I'm pretty ecstatic since it was quite the investigative journey to get here, and would like to thank everyone who helped me!