Long time random BSOD problem

[Killmeplsnow]

Just another small update, couldn’t hit Edit so had to post again, but I did a system restore and first thing on reboot, artifacting. All the MSI afterburner -500 settings were reverted too, so I had to restart a few more times but got the -500 core/memory setting back in there and it’s stable at the desktop again, lol. I’ll prob just leave it like this for now and use 365 day deferred windows updates.

[Killmeplsnow]

One more update, sorry again, I was able to get OCCT to start working by using DirectX 9 instead of DirectX 11. The test is running at 95% gpu usage, 250 fps but limited to 30% power through MSI and -500 core/memory. I want to remove these settings but I’m 99% sure the artifacting and system crash will follow, lol. The test has been running on the PSU tab for about 10 minutes but I’m going to leave this on for a few hours if possible to try to rule out the PSU… do you think OCCT would be a good determination of PSU working if it’s going for a while on DirectX9 with 250FPS?

[Killmeplsnow]

One picture with 12V and other PSU info w/ HWINFO
[MEDIA=imgur]9KHN1iP[/MEDIA]
Tons of results from OCCT
[MEDIA=imgur]a/3QOgXSL[/MEDIA]

[phillpower2]

Hmm I think that’s kind of the whole point of OOSU10. My main reasoning for getting it was to stop all the spying Windows 10 likes to do. I may have to reconsider if this is what is causing these issues.

At this time there is no way of knowing what is causing you issues but it makes no sense in troubleshooting while all the while knowing that there is dubious software present, reasons why you shouldnt use such programs are well documented on various forums with one no nonsense explanation here

I would stick to what has been previously suggested tbh.

You may need to start from scratch with this, clean install of Windows, clean install of the chipset drivers, using earlier drivers for the GPU that were proven to be stable and no OCing, if you get the same issue with this set up it would go some way to suggesting a hardware issue but atm it still looks like being software related.

[phillpower2]

Any update for us?

[phillpower2]

Thread closed due to lack of feedback from the OP.