BSoD, Ntoskrnl.exe+14a6f0, BAD_POOL_HEADER, Error 0x019/154/12b

Hello!

I have been getting BSoD time to time for a 3 months or so... I have tried to track down what is causing it with no luck. I have sfc disks, ran few passes of memtest (Should do few more later on), updated drivers, if needed, uninstalled programs what might have caused crashes and so on.

Now I am asking helping from people who can really analyze dumps and stuff.
I added my computer info when registered, but here are those again:

CPU: FX-8350@stock
MB: Asus M5A97 Pro
GPU: Asus 780GTX
RAM: Corsair Ven. LP 2x4GB 1600MHz
SSD: Samsung 830 pro
HDD: Seagate 2TB green

Also I have been OCing my cpu and gpu in past, with care. No overheating or such has happened in the past. Now everything is stock and bios is on default settings.

Thank you in advance. Sincerely, Miksu

Edit: I tried to analyze dumps, seems that once my GPU drivers went haywire, but most important point I noticed corrupted memory part, so I should ran memtest once more for longer, right?

Two dumpfiles point to memory faults, one even hardware related FAULTY_HARDWARE_CORRUPTED_PAGE (12b)
This bugcheck indicates that a single bit error was found in this page. This is a hardware memory error.


Please start with diagnosing the system RAM first. You can use the free tool "Memtest86+" to stress test the RAM.

How to run "Memtest"
MemTest86+ - Test RAM - Windows 10 BSOD Tutorials
Make sure you are using the latest version 5.01 - Memtest86+ - Advanced Memory Diagnostic Tool

You can stop the test even if a single error is found during the test. Otherwise continue the test for 8-10 passes and post a screenshot with next reply. 8 passes is the recommended bare minimum but more passes will give better result.

The latest dumpfile is

Code:

 BugCheck 19, {22, 8000000000000000, 0, 0}

Probably caused by : dxgmms2.sys ( dxgmms2!VIDMM_RECYCLE_MULTIRANGE::Decommit+32726 )

Followup: MachineOwner
---------

5: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000022, 
Arg2: 8000000000000000
Arg3: 0000000000000000
Arg4: 0000000000000000

Stat with updating your Nvdia driver your driver is from nvlddmkm Mon Dec 26 00:58:48 2016