Bsod memory_management

I've had multiple BSOD's over the past month or so. I've updated all drivers and still had a BSOD today. I've tried using WinDBG but am not smart enough to use it properly. Any assistance would be appreciated.

Code:

BugCheck 12B, {ffffffffc00002c4, ab3, 2487a400, ffffd68010443000}

*** WARNING: Unable to verify checksum for win32k.sys
Probably caused by : memory_corruption

Code:

BugCheck 1A, {41793, ffff800163a89fd0, 11, 10}

Probably caused by : memory_corruption ( nt!MiDeleteVirtualAddresses+1337c2 )

Code:

BugCheck 12B, {ffffffffc00002c4, bda, ed4afc0, ffff9b8115be1000}

*** WARNING: Unable to verify checksum for win32k.sys
Probably caused by : memory_corruption

Code:

BugCheck 1A, {41793, fffff6000037ea40, 5d, 5c}

Probably caused by : memory_corruption ( nt!MiDeleteVirtualAddresses+1337c2 )

Code:

BugCheck 1A, {41793, ffff8880f0d33ff8, 2, 1}

Probably caused by : memory_corruption

Code:

BugCheck 1A, {41793, ffffb680f3890c00, 2, 1}

Probably caused by : memory_corruption ( nt!MiDeleteVirtualAddresses+1337c2 )

Code:

Crash dump initialization failed!

Code:

The driver \Driver\WudfRd failed to load for the device USB\VID_05AC&PID_12A8\0b803bf23a148dc662bd34ef09bd5e945f4a234e.

Code:

Installation Failure: Windows failed to install the following update with error 0x800F0841: 2017-05 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4016871).

Code:

The system failed to flush data to the transaction log. Corruption may occur in VolumeId: G:, DeviceName: \Device\HarddiskVolume6.
(A device which does not exist was specified.)

Code:

The system failed to flush data to the transaction log. Corruption may occur in VolumeId: G:, DeviceName: \Device\HarddiskVolume7.
(A device which does not exist was specified.)

Code:

Installation Failure: Windows failed to install the following update with error 0x80070643: Update for Microsoft Outlook 2010 (KB3191906) 64-Bit Edition.

Code:

The device, \Device\Harddisk3\DR3, has a bad block.

Code:

The device, \Device\Harddisk3\DR3, has a bad block.

There were 6 minidump files and all displayed memory corruption.

Run memtest86+ version 5.01 for at least 8 runs. This may take hours so plan to run it overnight.
Memtest86+ - Advanced Memory Diagnostic Tool

There is a bad block on one of your drives.

Run Sea Tools for Windows on all drives (SMART, short, and long generic)
Run HD Tune, HD Sentinel, or Crystal Disk on all drives and post images and data into the forum.

Open administrative command prompt and run chkdsk /x /f /r (this may take many hours so plan to run overnight)

When in administrative command prompt or with win + r type winver
In the pop up view the windows 10 version and build and post into the forum.
There were some failed windows updates (not new) but see if you can update to the latest build.

To post the chkdsk results:
Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials
CHKDSK: What is it and how do I run it? - Ask Leo!
How do I see the results of a CHKDSK that ran on boot? - Ask Leo!
How to find chkdsk results in Windows 10 - Winaero uses 26226 find

http://www.seagate.com/support/downl...ls-win-master/
How to use SeaTools for Windows
CrystalDiskInfo - Software - Crystal Dew World
http://www.hdtune.com/
Hard Disk Sentinel - HDD health and temperature monitoring

Last "bad block" for \Device\Harddisk4\DR6 was at 10.05.2017. So I think this was the drive which was defective.

All BSOD dumps show memory_corruption as cause. Since your disks seems to be ok u should to an memtest to thest your RAM:

Diagnostic Test

 RAM TEST

Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums

   Note

MemTest86+ needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

Make a photo of the result and post it.

So, when I ran Memtest, I got 100 errors within the first couple of minutes. Should I still run chkdsk? Or just try and see if its a defective DIMM slot or RAM stick? Either way I'm busy the rest of the week and will be continuing on the weekend.

There is/are problems with the RAM or the dim/motherboard connections. Now its process of elimination. Use one RAM at a time and check memory. Run overnight so that it can get information while you are sleeping. The same for chkdsk. It's best to run it overnight. With memory identified already lets work on that now.

Is there any news or did you fix the problem?

Sorry, I've been busier than I thought I would be, but I swapped my RAM sticks into different DIM slots and BSOD'd with MEMORY_MANAGEMENT while using it before I could even run the Memtest. Will get new RAM tomorrow and report back.

When you test the RAM using Memtest86+ version 5.01 please make 8 or more passes: Memtest86+ - Advanced Memory Diagnostic Tool

When the test has completed please make an image and post into the thread.