BSODs from hal.dll and ntoskrnl.exe shows up during gameplay

I know it isn't both, I tried both seperately and I can enter the bios to place the usb first in boot order using delete, I've been able to do that from the beginning. The problem is that for some reason it doesn't seem to matter, after I save and restart, windows simply opens and after checking the bios again, the main hdd is in first place again. I'll try it on a different flash drive or temporarily unplug the hdd next.

Britton, i never would have thought of that :). Also thank you for going to the trouble of taking the picture of the boot screen and everything, it's really helpful.

Yeah I got it to work, running right now on the computer. Thanks for telling me to put it in a usb 2.0; it still showed up only as a uefi but when I used the boot menu at the bottom (which i never saw????), and sorry for the late response I was on a vacation.

I ran the test but then after coming back around 3 hours later the computer was at the windows login screen... I'm so lost at this point, what even happened? Because of it returning to the login screen I couldn't determine the results, but there were no bluescreens logged so I'm clueless as to what actually happened. If anyone could get back to me with what I should do at this point it would be very appreciated.

I wasn't running windows memory diagnostic, I ran memtest from this site Memtest86+ - Advanced Memory Diagnostic Tool. Or maybe I'm just misinterpreting what you're saying Britton. I will try the test again to see if the same results occur, but I fear that the problem the whole time was the motherboard since we've ruled out the hard drive and processor, and the passes that memtest did on the memory were fine when I left (still only 1-2 passes though). I'll run it again later on.