Sys-USB causing immidiate shutdown once it is manually initiated

I was reading this article, How to use block storage device, which was quite informative because I wanted to mount a thumb drive.

Let me start by saying my keyboard and mouse are both USB connection, and have worked flawlessly from the initial install.

Now when I insert the thumb drive. Nothing, literally nothing happens. So I search for explanations and found said article.

So I open dom0 Terminal

$ lsusb
Bus 009 Device 002: ID 26ce:01a2 ASRock LED Controller
Bus 009 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 010 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 007 Device 002: ID 046b:c52b Logitech, Inc. Unifying Receiver  <-- Mouse
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 413c:2105 Dell Computer Corp. Model L100 Keyboard  <-- Keyboars
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
bus 001 Device 002: ID 05dc:a81d Lexar Media, Inc. LJDTT16G [JumpDrive 16GB]  <-- Trying to mount
Bus 001 Device 003: ID  0e8d:0616 MediaTek Inc. Wireless_Device
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

So the system sees the USB drive. So I proceed:

$ lsblk
< I will spare you all the qube vm pools and loopbacks>
<Point is there was no "/dev/sda" to  mount>

I open my qube manager, and discover the my Sys-USB is not running. I highlight Sys-USB and hit “Start/Resume” in the ribbon bar at the top. Instantly, the system SHUTS DOWN. No prompt, no warning, no “Qubes Status…” in the top right corner. Instant blackout, board and all. The kind of sudden thing that you are left saying, “What just happened!”

So of course I had to do it again, to make sure is was not something else, and sure enough, same thing! Ok Sys-USB clearly has an ISSUE.

I go into System Setting, and that is when I realize my Keyboard and Mouse is working, and they are USB.

So the system sees, and initiates the USB for the keyboard and mouse, but fails completely otherwise. The system see the Lexar JumpDrive but fails to initiate a udev and the dev/sda allocation.

So I need some assistance diagnosing this one. I read a few post, by a few I mean a lot, but none seem to jump out at me similar to this particular problem. Mouse and Keyboard if not lagging, It might be causing my system to boot-loop but not sure. See my only other post. Which was fixed by adding “qubes.skip_autostart” to grub. It is not “malfunctioning” as some others have said, it is straight up not starting and crashes the system.

By default only input USB devices are initialized in dom0:

You should also add the usbcore.authorized_default=0 option, which prevents the initialization of non-input devices. (Qubes ships with a USBGuard configuration that allows only input devices when usbcore.authorized_default=0 is set.)

USB qubes | Qubes OS

Check the PCI devices connected to sys-usb in its Settings-> Devices tab.
Make sure that only USB controllers are present in the right column.
Maybe some other critical PCI device is selected in the right column like GPU and your system reboots once it’s trying to remove it from dom0 and passthrough it to sys-usb.
Or try to remove all devices from the right column and then add them back one by one until you find the device that is causing the issue.