Here's a relatively cheap new stuff upgrade option you can chew on.
CPU -
AMD A10-7860K
Board - AsRock FM2A68M
RAM - 8GB Kingston
SSD - Corsair Force LE 240GB
You'd actually be dropping the 8800 GT in this case and using the onboard graphics from the A10, it's faster.
$330 pre-shipping/tax.
Sniper, I know this may seem strange, but is it possible with all these items for me to still use my old 8800GT with this setup and overrule the R7(Or somehow disable it?) and the R5?
Some kind of bullcrap incompatibility with Crimson drivers with Windows going on the past while. I see zillions of people with the same problem as me (Stop code: thread stuck in driver device) and the fixes people swear by don't work for me. Only happens when I am running project Zomboid. Its awful annoying. But it is definitely some kind of driver issue getting looped.
I have tried completely DDU removing all graphics drivers and fresh installing. Nope. Getting rid of all programs that might be...nope don't have any extra programs yet on this fresh install and I already disabled the Xbox app and checked for Raptr. Disabling a bunch of stuff.....Nope. Updating drivers for everything else(Audio)......Nope.
Right now its beyond annoying. Will the 8800GT PCI E card work fine on this Mobo? I think so, but I am not sure how to go about uninstalling the radeons to default to the Geforce old card. I just want to see if the problem persists with the old video card, because then at least I can isolate that its probably a motherboard issue or possibly the sound drivers getting stuck in a loop and not the graphics drivers.
Bios/UEFI is already updated to the most recent Win10 supporting version.
I considered trying catalyst beta drivers, but it says right on the downloads that those are for dedicated memory cards, not APU's Integrated.
But I am tired and just spent 10 hours trying to fix this problem. Zomboid is not exactly a demanding game on video cards, so my guess is anything I play will crash.
I wish there was some damn way it would tell me WHICH driver is getting caught in a loop so I can figure out the problem. In Vista I knew my way around this stuff, but I am lost in win 10 and Tom's hardware guys and such are not responding