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

Looking at your recent crash dumps I see two drivers that are causing problems:

rzudd.sys Wed Oct 26 01:12:19 2016
nvlddmkm.sys Fri Oct 27 08:49:39 2017

Code:

BugCheck D5, {ffff880834ff6fa0, 0, fffff80b3aed8b70, 0}

*** WARNING: Unable to verify timestamp for rzudd.sys
*** ERROR: Module load completed but symbols could not be loaded for rzudd.sys

Could not read faulting driver name
Probably caused by : rzudd.sys ( rzudd+28b70 )

BugCheck 139, {3, ffffba0a1a6d0ac0, ffffba0a1a6d0a18, 0}

Probably caused by : dxgmms2.sys ( dxgmms2!VIDMM_LINEAR_POOL::Free+343f2 )

Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_ref_pubwu.inf_amd64_2e7fa54192fe16d0\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys

Please update the NVidia driver. The best way to do this is to uninstall everything of Nvidia using Display Driver Uninstaller and install new drivers from your Graphics card manufacturer or from the NVidia website. When you do this be sure the "clean install" box is checked and only install the Graphics driver and the PhysX driver.

The other driver is for the Razor Mouse and you need to search for updated drivers from the manufacturer.

For anyone that stumbles upon this months later - I had bad RAM.

I had already, multiple times, cleanly installed my Nvidia driver and Razer drivers as I too could see they were being flagged sporadically by BlueScreenView.
I completely reinstalled Windows fresh, after wiping and formatting my drives, as I said in my post, and then the errors started pointing to the ntoskrnl.exe driver.

so...

I ignored this thread once the only reply was to reinstall drivers on a completely fresh installation of Windows and something I had already done...

I ended up replacing my RAM and all the issues went away. RAM passed Memtest86+ (I ran it again overnight with 9 passes) but was clearly the issue as I put the sticks on another desktop computer and it too started crashing immediately.

Don't always trust Memtest86+.....