New
#1
3 x BSOD in a row pointing to ntoskrnl.exe (while playing games)
Hi everyone,
A couple of weeks ago I had a string of BSOD's with differing bug check/stop codes.
All while playing games (Civ V mostly and Overwatch).
Just prior to this I updated my graphics card and my RAM.
Some things I did back then:
I ran memtest86+ and stopped after 5 passes.
I checked and doubled checked and triple checked my display drivers.
I ran chkdsk and sfc/ scannow,
Unplugged every hard drive from my computer that wasn't the boot drive.
Eventually... I wiped ALL of my drives clean and reinstalled Windows FRESH.
The problem went away. Until today/yesterday.
I had a BSOD yesterday but truly.. I don't know why. I wasn't in the room or using my computer, I had gone downstairs and left it on. I only know this happened because of the minidump file.
Today I had a BSOD while playing Overwatch. First the game crashed with an "unidentified error" and I couldn't get it to start up again so I restarted the computer. After that, I got a BSOD mid game... (thank you blizzard for suspending me from competitive play thanks to said crashes!)
Googling around.. I discovered Driver Verifier so I started it and after I rebooted.. another BSOD... which I believe is the intended behaviour of this utility? To identify the problematic drivers?
All three errors (according to BlueScreeView) point to the ntoskrnl.exe driver.
I stopped it rebooted and now here I am, in these forums. I have attached the ZIP folder from your DM log utility.
I have also attached a zip folder (new-xxx.zip) with my OLD minidump files (that I had previously uploaded to the Windows help forums which provided little help).
Any help would be monumentally appreciated.
I am able to swap out the new RAM for the old RAM if need be, I haven't because... the memtest passes.
And I don't know how useful that would be when it's so sporadic and frankly hard to recreate without a few stacked hours of game play.
And this was a BSOD out of nowhere, I've been playing Overwatch and the computer has been fine since my OS reinstall a few weeks ago.
Attachment 181300
Attachment 181301