In this day and age, any hardware causing a BSOD or freeze, I will assume faulty and remove.
I can't honestly remember the last time I saw one that wasn't caused by that.
The last BSOD I saw was 3 years ago while building a set of IBM BladeCenter blades. Their RAID card crashes if the default MS driver loads on 2012R2. 2012R2 wasn't officially supported at that point, so it was fair enough, but even then all I had to do was create an install disk with the IBM-supplied drivers (many YEARS ahead of the default MS ones) and it's worked flawlessly for years since on a number of BladeCenters without a problem under 2012R2 and heavy load.
As a programmer, I can justify that - literally the MS driver is so out of date it can't have been written when that hardware was made, and it's not as "compatible" as the 2012 driver, or the 2008 driver but advertises itself to be and the vanilla Windows Setup (which has nothing else compatible with that hardware) tries to load it but BSOD because the hardware isn't what it was expecting. It was instant (on loading the driver via Windows Setup), reproducible, and obvious.
Slipstream the Windows install and supplement the MS driver with anything written SINCE then and it picks the better driver and just works. That's fine by me. And an issue you'd only experience when doing major system upgrades or first-installs.
But a BSOD other than that? I can't even remember. Had a couple of client drive failures and still no BSOD (wouldn't boot, but you'd expect problems beforehand). I would have to say it's been probably 8-9 years since any BSOD that wasn't obviously explainable (hardware obviously failing, computer overheating, or problems like the above).
But a BSOD just because you updated a driver and reboot? No way. Why would you tolerate that on even a personal machine? That's data loss just waiting to happen.
BSOD my machine without an obvious reason why (and not just "it's a new driver" or "it's not the latest driver") and your hardware will be replaced.
I have a gaming laptop. I update the nVidia drivers precisely "when required" (i.e. a new game literally won't load without an update). That means I'm miles behind on versions. I kill all the taskbar apps and get rid of the dual-driver junk and whatever else, in any way I can. Still no BSOD. And when I update, the worst I expect is - very briefly - running on the internal Intel graphics until the new driver kicks in after a reboot.
BSOD died with Windows XP, and those were mainly because it was hard to isolate processes from each other etc. If you have ANY piece of kit that still gives you them in anything even approaching a reproducible or frequent way, ditch it and buy something else.
Same for kernel dumps (unless you've been fiddling with the kernel, they shouldn't happen) or whatever equivalent on Mac.