Was working fine and then it just died loading a game (Guild Wars 2, loaded every day). It then repeatedly BSoD until it asked me if I wanted to go back to an earlier option.

Did that, it came back up and into Windows, few seconds later another BSod and then repeat BSoDs again.

Any ideas of what's going wrong?

The BSOD message is pretty vital to diagnosing it, e.g. was it something like IRQL_NOT_LESS_OR_EQUAL, PAGE_FAULT_IN_NON_PAGED_AREA, etc?

Google either that message or the stop code, e.g 0x00000001

Also you should go into system settings and turn off automatic restarts, that gives you chance to note the error or look it up from your phone.

My money is on the GPU, if you can remove it or swap with another then do that..

Could be the SSD/HDD..

Sounds too quick to be RAM

Quote from: XEntity on December 18, 2020, 17:45:55 PM
My money is on the GPU, if you can remove it or swap with another then do that..
Could be the SSD/HDD..
Sounds too quick to be RAM

what he said :-o

So I finally got to checking this, not been well.

Stop code: IRQL NOT LESS OR EQUAL

Lots of possible issues, one of which is a memory fault so I pulled out a pair of memory modules and tried that. It got to windows and crashed again with a driver issue which I didn't have time to record. Not installed anything new so will have to keep plugging at it when I can.

If you've swapped the memory, my money is on the graphics card.

Quote from: Clock'd 0Ne on January 31, 2021, 12:55:08 PM
If you've swapped the memory, my money is on the graphics card.

Been busy doing other things and ignoring this issue, but finally got around to trying a different graphics card, seems not.

Then found a thread elsewhere on an old Corsair mouse driver. Tried one years ago, didn't like it so just put the mouse in storage. Found the driver, deleted, computer back up and working... 

We were all wrong...

I've never known a mouse driver cause that big an issue, good job on getting it sorted though!

The actual item is CorsairVBusDriver.sys, which combines badly with the December 2020 Windows update, which is why it happened in December. I don't know the exact reason for this but deleting worked.

Might still come back but I can hopefully sort that if it happens.