seeing a rash (3 out of the last 5 memory dumps i looked at yesterday and today) of these bugchecks all from the same CPU series
AMD64 Family 23 Model 113 Stepping 0
You are the only one who had the most current bios patch. the bugcheck occured when a driver attempted to disable something too many times.
this ended in the count going to a -1 value which windows called a bugcheck for. You would have to provide a kernel memory dump in order to get a chance to see what was causing this problem. the debugger only shows what was running on the active core at the time of the bugcheck and you were running
WhoCrashedEx.exe
when the system crashed (made me laugh since it was so ironic)
for debugging set the memory dump type to kernel, reboot and wait for the next crash and provide the memory.dmp file
and I will see if i can find out what was going on with the other cpu cores at the time of the crash.
you might also try to avoid the crash by going into bios and turning off special functions of the cpu like some of the sleep functions.
(or go into control panel power management and set the machine to run in a high performance mode)
you might also go to the motherboard vendors website and update any custom drivers. They would contain "fixes" for known bugs in the chipset and various AMD cpu versions.
I will look at the drivers listed in the debugger for anything useful.
edit: looks like you have only the generic microsoft provided drivers. These will not have fixes for known problems with just your motherboard. (you would have to get the fixes from the motherboard vendors website)
-two other systems I looked at yesterday also only had the microsoft generic drivers installed.
note: I will look at your other bugchecks to see if one happened to catch a active core that caused the problem.
second bugcheck was due to a stack overflow in the graphics subsystem.
the debugger does not like some of your microsoft core system files.
you should start cmd.exe as an admin and run
DISM.exe /Online /Cleanup-Image /Restorehealth
DISM.exe /Online /Cleanup-Image /Restorehealth Explained (itechguides.com)
then reboot.
--------
third bugcheck was in windows winsock provider code (network code)
while you were running
qbittorrent.exe
generally you would look to update your network driver for this error:
most likely this driver:
\SystemRoot\System32\drivers\rt640x64.sys Mon Nov 18 01:14:08 2019
look for a update on your motherboard vendors website.
------------
forth bugcheck was in the windows desktop manager.
looks like a malware infection the code that was running outside of kernel drivers like it was injected and ran.
I would guess your system has malware on it.
you should run the dism.exe command, turn off virtual memory to delete your pagefile.sys, run a malware scan
and check your task scheduler for 3rd party tasks running (often every 15 minutes)
then reboot and turn your virtual memory back on to get a new clean pagefile.sys
-------
last bugcheck was in the system windows kernel driver while running
qbittorrent.exe
the system was up for only 32 seconds, you need to make sure this tool is not set to run on start up.
if you want to use it make sure it gets turned off after each use.
the debugger thinks your afd.sys is bogus. the dism.exe command should fix the binaries.
be sure to change the default settings on your app so it does not share files and make sure it does not start when the system starts.
2: kd> !SYSINFO machineid
Machine ID Information [From Smbios 3.3, DMIVersion 0, Size=2382]
BiosMajorRelease = 5
BiosMinorRelease = 17
BiosVendor = American Megatrends Inc.
BiosVersion = F60c
BiosReleaseDate = 10/29/2020
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = B450M GAMING
SystemFamily = Default string
SystemVersion = Default string
SystemSKU = Default string
BaseBoardManufacturer = Gigabyte Technology Co., Ltd.
BaseBoardProduct = B450M GAMING
BaseBoardVersion = x.x
2: kd> !SYSINFO cpuinfo
[CPU Information]
~MHz = REG_DWORD 3593
Component Information = REG_BINARY 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
Configuration Data = REG_FULL_RESOURCE_DESCRIPTOR ff,ff,ff,ff,ff,ff,ff,ff,0,0,0,0,0,0,0,0
Identifier = REG_SZ AMD64 Family 23 Model 113 Stepping 0
ProcessorNameString = REG_SZ AMD Ryzen 5 3500X 6-Core Processor
Update Status = REG_DWORD 1
VendorIdentifier = REG_SZ AuthenticAMD
2: kd> !sysinfo cpumicrocode
sysinfo: unknown error 80004005
2: kd> !sysinfo gbl
[ACPI Good Bios List]
[MCFG - 1195787085 bytes]
AcpiOemID="MCFG","MCFG<"
AcpiOemTableId="MCFG","MCFG<"
AcpiOemRevision=">=","MCFG",1195787085
AcpiRevision=">=","MCFG",77
AcpiCreatorRevision=">=","MCFG",1195787085