piece of **** windows crashing Game Input reconfigure

Yeah, the consensus seems to be, it's a needle in a haystack chase for solutions and these error codes are just pretty useless.

Am on a laptop, so should I unplug the PC and see if it BSODs on battery power? Not gonna go out and buy a new power adapter just to test this hypothesis.
Was it caused be an ASUS BIOS update around the time the issues arose? Possible. Was it caused by a trackpad replacement I got for my machine during warranty (and possible USB driver errors)? Maybe.

Am trying now a fresh install with a Win ISO over the existing system (so to keep my apps and setting). But not sure if that might be a waste of time as it might or might not reinstall all drivers?

Ideas welcome ¯\_ (ツ)_/

"I didn't do proper science and try one at a time so I don't know which fixed it."

Sometimes even then lol.

Much of the info on ntkrnlmp.exe via links is non-explaining really. They don't say why or how its involved in a good way.

But, I see Microsoft docs can slowly help make a connection between c-states, CPU, and ntkrnlmp.exe at least eg (don't view this as a fix here. Its just used to link the 3 mentioned points) "The Ntkrnlmp.exe file that is included in hotfix 840987 includes a sequence of instructions that reveal this bug.", "when a processor resumes from a C1 idle state" https://learn.microsoft.com/en-us/troubleshoot/windows-server/performance/stop-0x0000000a-error-processor-c1-idle-state

I know from my last motherboard with this computer I'm on that c-states and older PSU's with newer CPUs can be used in disabling the low power state that will render the computer with an issue randomly. The motherboard I'm on now deals with all that automatically though while the other one didn't which is quite amazing. But, that certainly can apparently cause an issue with ntkrnlmp.exe.

That's far more likely than the power cable and outlets :)

But, it goes to show sometimes people wrongly view problems. If the problem is with the computer actually working improperly then the software isn't to be done for a fix (most times). There can be exceptions.

That's actually showing the same error as mine "ntkrnlmp.exe." Where if you google it shows the primary sources are bad power supply/adapters.

To fix my own I obtained a new power cable, switched outlets and disabled C states in my Bios. I didn't do proper science and try one at a time so I don't know which fixed it.

Keep getting HYPERVISOR_ERROR about twice a day, although I have turned the Hyper-V off long time already.
Running a AMD Ryzen 7 5700U with integrated Radeon Graphics. Did reinstall the AMD driver suggested/needed by my ASUS laptop (from their site).

Guess I can spend another two days reinstalling/configuring the whole OS and apps (which takes most of my time).

WinDbg resulted in following:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

HYPERVISOR_ERROR (20001)
The hypervisor has encountered a fatal error.

IMAGE_NAME:  ntkrnlmp.exe

   Information from resource tables:
        CompanyName:      Microsoft Corporation
        ProductName:      Microsoft® Windows® Operating System
        InternalName:     ntkrnlmp.exe
        OriginalFilename: ntkrnlmp.exe
        ProductVersion:   10.0.22000.978
        FileVersion:      10.0.22000.978 (WinBuild.160101.0800)
        FileDescription:  NT Kernel & System
        LegalCopyright:   © Microsoft Corporation. All rights reserved.

PS C:\WINDOWS\system32> sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files and successfully repaired them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.
PS C:\WINDOWS\system32> sfc /scannow

Alright! So far no success with all the above.

Also ran sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth. No errors.
Just got two restarts one with Problem Event Name: BlueScreen, Code: 20001, and just 5 minutes ago a BSOD with a hissing sound and irql_not_less_or_equal message. W11 turned into a total unreliable mess for me, after running without a SINGLE crash for months after installation.

Edit: I just got another BSOD with KMODE_EXCEPTION_NOT_HANDLED and WdFilter.sys listed as reason.

Edit: Now stop code: HYPERVISOR ERROR during video call.

Maddening that it's not clear what causes all this ****.