I don't know if this means anything, but hardware acceleration was never on in Chrome, apparently.
Update: I've got everything on my SSD with Windows on it copied to externals, for a possible future fresh-install of Windows (should it come to it). I'm waiting on my brother to return the USB flash drive I lent him, so I can create a windows installer/ISO on it, and a backup of windows.
For now, I found an HDMI long enough to replace the DisplayPort cable for my second monitor, and my extra DVI cable should be arriving soon to test it with that.
I don't think I ever mentioned this, and if I didn't, I meant to! I had upgraded my second monitor (previously a standard ASUS monitor) to a 144hz ASUS "gaming" monitor. I didn't know I needed a DisplayPort cable to get the full usage out of the 144hz monitor, so I'd ordered one and plugged it in, and that was only a week or so before I started getting BSODs (late August/early Sept).
This might just be my mind rambling, but could there be a conflict with the DisplayPort cable, the new 144hz monitor, or the fact that it's my second monitor and I'm using an extended windows display setting? Should I be testing everything with my previous second monitor? with DVI, HDMI, or Display Port connectors?
I don't think I've actually spent more than a few hours without my second monitor on, because I *absolutely* need it for work, but when I'm gaming I could try just using only one monitor and attempting to trigger the BSODs using Chrome, which might confirm a conflict with the second monitor?.. idk.
If you think there could be a conflict with any of the above, what should I be testing for first/second? (I'm planning on testing the driver verifier today, when I get my USB flash drive back and some time to test it)