Windows 10: BSOD after Overwatch crashed, caused by win32kbase.sys

I just built a new PC with and it's been error free for the last few days. However today after installing the new Nvidia drivers for my 1070 I had Overwatch crash on me and then shortly after that the PC BSOD. The only thing that has changed on my PC since the last time I played Overwatch(lasy night) was those drivers so I'm thinking they may be the cause and I will DDU and reinstall after I post this and try the game again.

Since I restarted from the BSOD I haven't been able to cause another BSOD however Overwatch has crashed several times, normally 5-10 minutes after I start playing.

Temps are all fine, the i7 6700k is being cooled by a Cryorig H5 Universal max temp 62c and my EVGA 1070SC hit 75c(stock fan curve is a little low).

I did manage to look at the minidump and see that WinDbg seems to be pointing the cause at win32kbase.sys but I've got no idea what to even make of that.

I'll update this post after I reinstall the drivers and maybe roll back if they continue.

EDIT: Yeah, BSOD after I shut down Battle.net and a few other programs before I planned to DDU. This time the cause is being pointed at ntkrnlmp.exe. Went ahead and disabled a few things from startup as well.

:)

 

Recurring BSOD crashes after using specific software (Axure RP Pro)

The causes of the BSOD's are related to BAD_POOL_CALLER and SYSTEM_SERVICE_EXCEPTION related to the drivers; ntoskrnl.exe+16c560 and win32kbase.sys

 

Windows BSOD issues - Have DMP files

The driver verifier is not the issue here.... The whole point of that command is to BSOD your system and to see which drivers are acting up, that is the reason I posted the .dmp file for that BSOD. Of course I would have disabled that after successfully
getting the system to crash...

My BIOS is the latest version (American Megatrends Inc. 1.I0, 25-Apr-17), that is the reason the .nfo file is included with the dumps so people are able to see that.

The SYSTEM_SERVICE_EXCEPTION is indeed the main BSOD caused by main things over the past few weeks, which is what I am trying to fix.

29JUL - SYSTEM_SERVICE_EXCEPTION (win32kfull.sys)

26JUL - SYSTEM_SERVICE_EXCEPTION (win32kbase.sys)

24JUL - SYSTEM_SERVICE_EXCEPTION (ntoskrnl.exe)

23JUL - SYSTEM_SERVICE_EXCEPTION (win32kbase.sys)

22JUL - SYSTEM_SERVICE_EXCEPTION (ntoskrnl.exe)

18JUL - SYSTEM_SERVICE_EXCEPTION (win32kbase.sys)

ect, ect...

If older .dmp files are necessary I can always provide.

Thanks.

 

Have you tried rolling back the Nvidia driver to the previous version via Device Manager?

 

Not yet, I am about to try that after I update Windows, I just tested another game and it too crashed to desktop after some time. I'm not seeing any reports of BSOD on the forums with these new drivers but maybe I'm just really unlucky. All I know is ever BSOD has a different error code.

UPDATE: Soooo I could not install the new KB3206632 Win10 Update without removing the new Nvidia drivers first. It would just throw errors when starting the update and then get stuck on the "Preparing Files" screen. After removing the Nvidia drivers it installed and updated in 1 try.

UPDATE 2: Ended up rolling back to 376.19 Nvidia drivers, games are still crashing.

 

On my phone right but since nothing I've tried has fixed anything I decided to download and run Memtest86. Because the BSOD are random and the crashing od games is also random. I've never used Memtest86 before but it's not even done with Pass 2 and there have already been 18,000 errors.... Is that a clear sign my RAM is bad?

 

Alright, I ended up running Memtest86 again with the RAM individually and 1 of the sticks failed Test 6 immediately the other one I can't get to fail alone. However after putting them back together again they didn't fail any test immeditaly so ended up lettings them run all through the night and surely enough Test 6 and Test 8 had failures. So once again I separated the RAM and the one that failed alone failed once more on Test 6.

I'm gonna have Amazon replace the RAM since I just bought it and I guess I'll be doing another run of Memtest86 when I get them in.

 

Any single failure is enough to indicate the ram is bad and needs to be replaced.

Hope this fixes it for you.