Dump inspection for BSOD on brand new Windows 10 PC

I'm sorry I thought that the dump contained all the info about the pc main components:

Motherboard: Asrock Z370 extreme4, the bios is up to date, and I've installed the drivers provided by Asrock, of course I'm not currently doing any overclock
Ram: G.Skill 2x8GB ddr4 3200MHz dual channel
Cpu: Intel Core i7 8086k
Gpu: nvidia geforce rtx 2080 <-that's where the nvidia usb c is from
1 SATA3 ssd Samsung 860evo (with windows)
1 hdd

running Windows 10 Pro, a weeks-old installation, as I accidentally installed Intel optane drivers on the first one, and after seeing the condition of the os after their removal, i decided to re-do a clean install to avoid eventual complications (how funny).
As I said the system was running perfectly fine before the installation of the wireless card, I used and configured it for at least a week.

Potentially useful things worth to mention:
-The gpu drivers updated probably hours before I proceeded to install the wifi card, then, I didn't use the pc until the card installation was complete.
So, I can't tell if they where running correctly before since I simply didn't use the pc enough
-The BSOD appears *minutes* after the boot of windows. Not during the process. Up to 10 minutes after, if the pc is unused
-It *never* appeared during normal use of the pc, even after being on for hours
-I could probably say that it happens only if the pc is left untouched after windows' boot, but I'm not sure.
-It doesn't happen at every boot, maybe one every three times, or even four. But after the crash, it's unable to reboot automatically and it stucks at 100%
-I actually had an xbox 360 usb controller attached to an usb port the first two times, but not the third.

I'm going to send a more detailed dump but I didn't understand if I should select "full memory" or "kernel", or if one contains the other, I'll upload as soon as it occurs again.
I'd really really like to solve this by the "nice" way instead of going brute force with dism.
Reinstalling windows a third time is out of discussion, as I'm studying at the University and I don't have even closely enough time to rebuild everything from scratch.
I doubt something broke by itself alone anyway, It didn't even have to perform the October's update as it was already up to date.
The same installation media was succesfully used on other pcs as well.

Ok I just ran into a bsod again (i had to voluntarily turn off and on again windows, no "reboot"), I've uploaded the kernel memory dump as well as the new miniDump.
Here they are

Thank you!

..Oh
It seems it's falling all apart
How could all of that happen? I've never seen anything like that before.
Kernel modified? what could have been? And everything just broke together from one day to another..
I really haven't a clue about that usb driver, my bios is up to date, and I've installed everything relevant the motherboard's vendor
provided me, it has even an automatic driver version checker. If I uninstall it, what should take it's place exactly?
I ran all the hardware tests I could think of, everything passed correctly, both ssd and hdd. The ssd came from Amazon with the latest
firmware, I checked. All I know is that they're not running in AHCI mode, but instead in some "Intel rst premium".
The system is new and still almost empty! It has barely two weeks
I'll run dism but What the ..? All of a sudden!
I'll probably stick with those bsod for a while, I really don't that much time to look after a self-destructing pc.
If the pc is'n left alone after boot, it runs perfectly for an undetermined amount of time, good enough for me for now.

Just when I needed it the most, it just keeps going better it seems.

Thank You

I've run dism and an sfc/scannow, but they didn't found anything. Disabling xusb22 seemed to work, windows did three successful boots.
And now I can say almost for sure that the error occurs only if the pc is left untouched for a while after windows boots.
If I do something before the "timeout", then it's safe to use it until power off.
Resets performed after the bsod and reboots (via start->reboot) seem to prevent the error from appearing as well.
But now that it's disabled there's a problem: the xbox controllers aren't recognized anymore, nor the usb one, nor the "virtual" one used by the nvidia shield controller.
That's interesting

Edit 1: Oh, you've found some of reHips' files! It's a sandboxing solution I've been using lately.
It's main key point is that it shouldn't use kernel hacks, but only windows built-in features. I excluded it at the beginning because it's one of the first programs i have installed, and it didn't cause errors (well, till now at least). I uninstalled it anyway before running dism and nfc.
The asmedia drivers have been happily installed together with the other motherboard drivers

Mistery solved! Yaaaay!!
After you mentioning the xusb22 driver, known to be associated with the xbox 360 controller, I drove my attention on the Nvidia Shield controller. You see, that device is an Android usb/Bluetooth controller that works on Windows via GeForce Now, by creating a twin virtual "Xbox 360 controller", that somehow is mapped to the "Nvidia controller".
Before installing the wireless card I used it with the USB cable only, I needed the card to use Bluetooth. Well it turns out that the Nvidia controller causes bsods if used through Bluetooth.
Weird combination of conditions.
By reading the forum I was almost laughing by seeing everyone accusing the same identical symptoms but in a context so different.
Well, it seem that's it's up to Nvidia from now on, thank you all!

Thanks for the driver tools and asmedia tips too, it could be that I've accidentally connected the case's USB ports to a connector reserved to asmedia ports, I'll check on the manual