Constant blue screen crash- posting here as I THINK it's software?

[Roadkillv1]

So for the last few days I've been getting a blue screen crash and reset a couple of times a day- only whilst playing Destiny 2. I play No Mans Sky, hearthstone, valheim, various other games. Nothing. It's always during Destiny, and tbh, never during any chaotic shooting or fights...it's in a menu. Not the same menu, I could be looking at a map, or my inventory, but never mid fight. It isn't overheating as I've checked regularly and it goes between 60 to 80. NMS plays higher than Destiny does.

I did a reliability check and got the following, not sure if it helps-

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffff978c03098028, 0x00000000b2000000, 0x0000000000030005). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 6499742a-3a5e-4522-b6d7-5aaaf58dfbe9.


The only thing I can think of is MAYBE it started around the time nvidia did their last driver update, has anyone else noticed issues appearing since then? I don't know if it's related at all or if I have my days wrong. It's pretty frustrating.

 

[Roadkillv1]

update- not sure how coincidental it is but, I tested a theory to see if it was simple and I've gone from crashing twice a day playing it, to not crashing in 2 days. I noticed from the reliability report it started the day after nvidia released a new driver update, so I rolled back to the one before and it hasn't done it since. so...fingers crossed, it seemed that simple. I'll hold off on updating the card for a while I guess! thanks all anyway.

 

[Roadkillv1]

The GPU driver can be one of the most real time intensive parts of the system - which means it can expose edge case stability problems both in the underlying hardware (and not actually a driver/software issue) or can expose edge case stability issues in the driver/software.

What are your hardware specs BTW? on older Intel systems a 124 STOP could be caused due to some relationship between IMC, VTT (VCCSA) and VCORE voltages which had to be within a certain range of each other for some reason I don't think Intel ever explained the rules of (don't think it is true on 7 series or newer but not 100% on that).

EDIT: Not unusual in these cases to never get to the root of it and just have to avoid certain driver versions where it happens.

Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz 3.60 GHz
32.0 GB
Nvidia geforce gtx 1650