New
#11
That BSOD can happen for a variety of reasons. I've had it myself in the past and in my case it was a driver issue. It's almost certainly a driver issue here too since it occurred after trying to uninstall the chipset drivers. I could be wrong but I would not expect the computer to boot properly without chipset drivers installed, and it's always been my understanding to update them by simply installing the new drivers, which uninstalls the old ones in the process... which you tried next with the same result, but maybe a kerfuffle there from uninstalling them the first time. Sometimes Windows "works in mysterious ways" and needs a couple reboots or a time out after "an event," then when you try the same thing later or the next day, it works. But that error is not an indication of bad hardware, imo, so if you have the time and are curious (like I would be in your place), I would do as you say and try from scratch with the system the way it is, before swapping out the mobo. That way, whether it works or not, you've added to your knowledge. Otherwise you'll never know.Does anyone think the BSOD indicates bad hardware and I should just skip right to the mobo swap though?
And it does happen on occasion that the latest drivers are not the best drivers for some particular hardware. I realize you're only trying to update them due to the mouse issue, but it might be the newer chipset drivers don't play nice with the hardware. Though it would be nice to find the update works now, and the mouse issue is resolved. Good luck.