StopError - Kernal Security Check Failure (fresh OS install W10 x64)

Note; this request for assistance is not being made on the afflicted machine. The attached zip is however from the relevant unit.

The stop error problem (kernel security check failure) seems to be a recent development having only become an issue within the past few weeks. There have not been any hardware changes in this time.

The problem seems to occur when my friend is playing the game "Overwatch" but I have witnessed the stop error simply when BattleNet is attempting to install something; be it Overwatch or another Blizzard title.

I have already done a drive reformat and full fresh operating system install to rule out any possibility of this being an issue with the previous upgrade from 7 to 10. I also performed a basic memory test. The first port of call upon installing the GPU and audio driver was to Install battle.net and then allow battle.net to install Overwatch. The issue repeated during this Overwatch installation. This was literally our first maneuver. We haven't even bothered to run windows activation yet and have not installed anything else.

With no reliable way to view the crash dump file I decided it was best to turn this over to you guys to see if you can highlight the culprit. My only current theory is that the SE is caused by one of the more recent Crimson drivers for the GPU.
Attachment 110242

We are all having problems analysing BSOD events at the moment because the Microsoft symbol servers are not being updated to allow us to do the analysis. This seems to affect some more than others and the one file you have does not analyse.

philc43 said:

We are all having problems analysing bsod events at the moment because the microsoft symbol servers are not being updated to allow us to do the analysis. this seems to affect some more than others and the one file you have does not analyse.

Thanks for the response. Is this a permanent impediment for this support request then and should I abandon it here? Or could the situation there change and I should then leave it open and continue to monitor?

If you get further BSOD events please post them here and we will continue to try and find the cause.