SlayerOfHellWyrm

It doesn't look like the Wiim Ultra supports 32-bit, which is probably why you aren't seeing it: So, 32-bit is out of the question. Now, why is it seeing only 16-bit? Not sure. Where are you being told it's 16-bit? The device itself?

Odd, I just tested and didn't get that.

I would check for the installed apps, nuke either that's installed, reboot, then try and do a manual driver update for everything off Asus' site. You can use Armory crate, but I generally recommend doing things manually.

Tried digging around some, and I don't see reference to this anywhere. All I have see reference to, is a game/chat balance which can be changed. There's some pre-done EQs in the software, but none called "game". Sorry, I wanted to try and help but I can't find where you're seeing this mode referenced.

Sounds like you need larger ear tips. For best sealing, I always recommend memory foam since you squeeze them down, then insert them and as they expand they conform to your ear. They are more expensive than normal tips and get worn out so that you have to replace them way more frequently, but imo, they are worth it. I would see if Comply makes them for those earbuds, or some other brand, perhaps? Now, with that said, is this a new issue, or your first time using them?

Looking at the crashes, you've got an issue with the network driver. Do you have both Armory crate and the Intel Driver & Assistant Support installed? I've seen this before with both software trying to upgrade drivers to different versions and causing conflicts.

I'm referring to a DRAM cache. Let me use an analogy: You have a dirt pile to move, and you can load the dirt into the transport vessel with a backhoe, so your speed limit is how fast you can carry the buckets to where you need the dirt to go. With a DRAM cache, it's like having a wheelbarrow alongside the buckets. If you only have to move an mount of dirt equal to or less than what the wheelbarrow can carry, it's way faster than a bucket. However, once you need to move more, you still have to use some buckets as well because you can only empty the wheelbarrow so fast. It's not the best analogy, but it gets across what a DRAM cache kinda does. Makes the drive go fast, but if you start moving way more data than the cache, or the drive is nearing full it starts to slow. Without a DRAM cache, that just happens from the get-go, and the fuller the drive gets the slower it gets. It can definitely explain the speed jumping around some.

So, that's a HikSemi WAVE(S) SSD. They are known to be very low-quality drives. Odds are, that thing has 0 cache and writing the patch has filled it, then with poor quality/tier NAND, it's just slowing to a freaking crawl. You can use something like CrystalDiskMark, Atto, HD Sentinel, and other similar tools to benchmark the drive, but make sure you do large file size tests too. I don't have faith in that drive at all.

If it's a one off, I wouldn't dig into things honestly. Only if it becomes a frequent problem. Many things can cause Windows to halt itself but that doesn't mean anything is broken. You could've had an unlucky bit flip in RAM, and that could be enough. Has this happened more than once?

What displays are already connected? What's the TV you are trying to add? How are you connecting each display to the GPU? You will need to be pretty specific about what cable is used, as in DP to DP, HDMI to DP, DP to HDMI or HDMI to DP and so on.

It could be to do with you nesting .rar files with the .iso that you're then trying to compress. You shouldn't really nest compressed files/folders, it usually results in a larger file, and can cause other issues. Most notably, if you nest too many times, you'll flag some A/Vs for creating a RAR/TAR/ZIP bomb, aka, one compressed file that expands out to something massive and eats your CPU as you do it. Side note, what in the hell is this ISO that's 40GB? That's a chonky boi.

Make sure the Bluetooth services are also running. Windows has a nasty habit of shutting them off when you are doing things like uninstalling/installing/updating BT drivers. I've seen it quite a few times over my years. Might not be the issue in your case, but if the Bluetooth Support Service is off (which controls pairing) it won't let you nuke devices you've previously paired (it should, but Windows is Windows and sometimes does dumb things).

It's not a bad idea. I don't like doing part recommendations, only because I don't want any responsibility.

Yeah, not on the QVL so that could be part of the issue.

So, long shot as that memory kit is NOT on the QVL for that board, but try matching the timings of the below, validated RAM kit. I can't guarantee that'll work, but it might help to loosen the timings based on that. As a note, whenever you build a new rig, this is a good lesson for why you should ideally stick to the QVL. I know this is an old rig and it's in the past, and hopefully you do it now, but when you gotta do funky shit in the past and don't record what you had to do you get this sort of issue