This is getting a bump because, unfortunately, not only that this BSOD problem persists, I have ANOTHER BSOD (this one came out of the blue, no game was opened. It pointed out to win32k.sys).
Attaching NEW BSOD dumb, see last post for the one I get after exiting a game (or, for example, closing the process on a game that's not responding).
LE: Please note that the 2 dumps have the same name
Sorry about that, forgot.