Radium_Angel

Can't say I know him

There's one more reason I drive an old 308GT4...none of this electronic/tracking/pay me forever BS to impede the drive experience.

And that's a good thing. We don't need more "info/edu/taiment" with shoddy testing, half-accurate reporting and really bad videography (the latter is why I don't watch the channel videos, they give me a headache)

BIOS updating is not generally an automatic thing. With a pre-built the trick is to find the right BIOS, as flashing a wrong BIOS wil brick the PC

Honestly, a better PSU would do, there is a nice thread here on which PSUs are good and which are not good, I'd bounce around there for a bit and read, and if it was my system, I'd go for something in the 700 watt range, but I"m a firm believer in overkill (my main system runs a 1300watt PSU)

Ok, if the connectors on the PSU to mobo are standard (24pin for the main, and 4 for CPU) then swapping of the PSU should be an easy task. Then you could add a GPU to the system and a fresh PSU and you'd be good to go. This is assuming you are happy overall with the PC.

use memtest to check RAM

Only one way to find out, and that's by looking at it and taking measurements to compare against a standard ATX PSU

That won't support a better video card, do you know if the PSU is standard, or one of HP's infamous proprietary designs?

sigh...irritating. Ok, is the computer set to capture only mini crash dumps? Also, I need the bluetooth driver date please. It may need to be updated. When was the last time the BIOS firmware was updated?

That's far too many, sounds like the hub cannot handle all that power draw, or it's got an electrical short somewhere. I'd suggest playing with your system with the absolute bare minimum to function (dump the usb hub and all the usb devices except the keyboard and mouse) and see if your system returns to stability.

Ok, powered is good, because too many USB devices on one that is unpowered can be very bad. How many, and what kind, are the USB devices plugged into the powered hub?

I can't find anything out, which is generally not a great sign. It's *possible* the PSU is failing, there are a number of people on Amazon complaining about that issue, but before we go chucking new parts at this, I'd like to resolve the bluetooth crash and the virualbox mouse driver issue first. BTW, your USB splitter, is it powered or unpowered?

Sorry, was driving home, I am not familiar with "casting", you may wish to start a different thread on how to make that work, someone else better suited to answering that can help. I don't see anything either, that's generally not a great sign, but let me do some more research. It;'s possible you have a failing power supply, but I'm not ready to say that just yet

Let us know how it works out.

The rest of the crash files are all identical with the VirtualBox mouse driver causing the issue.

If the computer is a pre-built, the manual may tell you, otherwise it's a label printed on the side of the PSU itself

Check to ensure the VM services are not trying to autostart

Look into the driver section, it'll tell you how old the driver install date it, tho the error about "status device power failure" says perhaps your PSU is failing and cannot provide power to all your devices. What's the specs on your PSU?

Next Crash DUmp ___ DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If kernel debugger is available get stack backtrace. Arguments: Arg1: 0000000000000000, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000001, value 0 = read operation, 1 = write operation Arg4: fffff801b236265c, address which referenced memory BUGCHECK_CODE: d1 BUGCHECK_P1: 0 BUGCHECK_P2: 2 BUGCHECK_P3: 1 BUGCHECK_P4: fffff801b236265c SYMBOL_NAME: VBoxMouse+265c MODULE_NAME: VBoxMouse IMAGE_NAME: VBoxMouse.sys STACK_COMMAND: .thread ; .cxr ; kb BUCKET_ID_FUNC_OFFSET: 265c FAILURE_BUCKET_ID: AV_VBoxMouse!unknown_function OS_VERSION: 10.0.22621.1928 BUILDLAB_STR: ni_release_svc_prod3 OSPLATFORM_TYPE: x64 OSNAME: Windows 10 VirtualBox mouse driver crashed...unusual....I will keep looking at issues

ok, I'm going to post some relevant bits from the crash dumps here, so perhaps they will help others as well. This is from the first crash dump: SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff8057c3b1c49, Address of the instruction which caused the bugcheck Arg3: ffff97058e1710d0, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. BUGCHECK_CODE: 3b BUGCHECK_P1: c0000005 BUGCHECK_P2: fffff8057c3b1c49 BUGCHECK_P3: ffff97058e1710d0 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: audiodg.exe SYMBOL_NAME: BthA2dp!Em_AacLc_Enc_sInitializeSF+12d MODULE_NAME: BthA2dp IMAGE_NAME: BthA2dp.sys IMAGE_VERSION: 10.0.22621.1125 STACK_COMMAND: .cxr 0xffff97058e1710d0 ; kb BUCKET_ID_FUNC_OFFSET: 12d FAILURE_BUCKET_ID: 0x3B_c0000005_BthA2dp!Em_AacLc_Enc_sInitializeSF OS_VERSION: 10.0.22621.1928 BUILDLAB_STR: ni_release_svc_prod3 OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {c1b03926-a3b1-fae1-7f86-37c1b4dfd72d} ____ Now, this is only the first crash, and others may show something different, but it looks like your audio driver went stupid, specifically the Bluetooth module. Is that driver up to date? I will keep looking at the other crash files and post as I discover things.

Is the rain on the wallpaper supposed to be there? Also, the system is configured to automatically reboot, that needs to be changed. https://www.lifewire.com/how-do-i-disable-automatic-restart-on-system-failure-in-windows-2626067#:~:text=Go to Control Panel and,box next to Automatically restart.

Thx, I"m actually at work right now (shhhh! dun tell no one) so I can't discord

hmmm... Ok, when the system crashes, can you take a cellphone screen shot of what it's doing at the moment of Blue Screening?