Question Diagnosing Memory_Management BSOD

[Don__Kamikaze]

Hello
I have been experiencing blue screens for the past few months that are becoming more and more common. During this period I have replaced my RAM as well, but the errors are occurring before and after the RAM replacement.

The most common blue screen error is memory_management. memtest86 and Windows memory diagnostics have not shown any errors. Other crashes I have updated my BIOS and done an in place reinstallation of Windows without much success. I have also used Seatools to check my hard drive and found no issues. I have also used SFC and chkdsk which repaired a few files but the issue persists. The issue mostly occurs when I am playing a game or streaming /recording via OBS, although in one instance I was just watching a video on Firefox.

I have kept an eye on the temperature as well but it the crash happens even at normal operating temperatures.

CPU: i7-8700K
RAM: 32 (16x2) GB 3600MHz (previous one was 8x2GB at 3200MHz)
GPU: GTX 1080
Motherboard: Prime z370-p

I ran driver verifier and this is my latest dump from the crash. https://www.mediafire.com/file/vdokxxmyu9ia3ug/041124-29343-01.dmp/file



Any help would be appreciated

 

[Ralston18]

PSU: make, model, wattage, age, condition (orginal to build, new, refurbished, used)?

History of heavy gaming?

Disk drive(s): make, model, capacity, how full?

 

[Don__Kamikaze]

PSU: make, model, wattage, age, condition (orginal to build, new, refurbished, used)?

History of heavy gaming?

Disk drive(s): make, model, capacity, how full?

PSU: Corsair RM750x 80+ Gold. 750 Watts. New to build (10/2017)

I have used it quite often for games, although typically not at the highest settings or the latest. Most recent crashes were with Jigsaw puzzle dreams, Bayonetta, and Darksiders Warmastered.

HDD: 2TB Seagate SATA-III 6Gb/s 7200rpm. st2000dm005-2cw102. Free space: 311 GB
SSD: Crucial CT500MX200SSD3 MX200 500GB. Free space 351 GB. (connected using mSATA to M2 adapter)

 

[Ralston18]

PSU - 6 1/2 years old. May be at or nearing its' designed in EOL (End of Life).

Look in Reliability History/Monitor and Event Viewer for error codes, warnings, and even informational events just before or at the time of the crashes.

Reliability History/Monitor is much more end user friendly and the timeline format may reveal patterns.

Event Viewer requires more time and effort to navigate and understand. To help:

How To - How to use Windows 10 Event Viewer | Tom's Hardware Forum (tomshardware.com)

My general rule of thumb is that increasing numbers of errors and/or varying errors is a sign of a faulty or failing PSU. Caveat being some catastrophic failure....

Is it possible for you to swap in another known working PSU for testing? (Be sure to use only the cables that come with the test PSU.)

Also. Be sure (as you always should be doing) to back up all important data at least 2 x to locations other than the host computer. Verify that the backups are both recoverable and readable.

 

[Don__Kamikaze]

PSU - 6 1/2 years old. May be at or nearing its' designed in EOL (End of Life).

Look in Reliability History/Monitor and Event Viewer for error codes, warnings, and even informational events just before or at the time of the crashes.

Reliability History/Monitor is much more end user friendly and the timeline format may reveal patterns.

Event Viewer requires more time and effort to navigate and understand. To help:

How To - How to use Windows 10 Event Viewer | Tom's Hardware Forum (tomshardware.com)

My general rule of thumb is that increasing numbers of errors and/or varying errors is a sign of a faulty or failing PSU. Caveat being some catastrophic failure....

Is it possible for you to swap in another known working PSU for testing? (Be sure to use only the cables that come with the test PSU.)

Also. Be sure (as you always should be doing) to back up all important data at least 2 x to locations other than the host computer. Verify that the backups are both recoverable and readable.

Thank you.
I have taken a look at the reliability history and there isn't much info there. As for event viewer, I am not noticing any particular pattern, but I have seen a countless number of event 51 "An error was detected on device during a paging operation".

I tried installing a large game now and it crashed with a Kernel_data_inpage_error after it really slowed down. Not the first time I encountered that BSOD. When restarting Windows was checking and fixing the SSD. Could it be the culprit despite all those checks?

Unfortunately, I don't have an alternative PSU, but I can always get one and return it if it is unneeded.

 

[Don__Kamikaze]

And now it crashed with a SYSTEM_SERVICE_EXCEPTION installing the same game. Windows is attempting to fix the SSD again.

Edit: upon starting Windows did not show any text (only icons) and I had to restart it for text to show. Also noticed that the CPU temperature was spiking very high before the crash (100 C-ish)

 

[ubuysa]

The dump you uploaded indicates that this may be a syatem drive problem...

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 000000000000003f, An inpage operation failed with a CRC error. Parameter 2 contains
    the pagefile offset. Parameter 3 contains the page CRC value.
    Parameter 4 contains the expected CRC value.
Arg2: 0000000000046d07
Arg3: 0000000000000003
Arg4: 000000004a1b00f7

.....

ADDITIONAL_DEBUG_TEXT:  Memory Manager detected corruption of a pagefile page while performing an in-page operation.
The data read from storage does not match the original data written.
This indicates the data was corrupted by the storage stack, or device hardware.

.....

 *** Memory manager detected 1 instance(s) of corrupted pagefile page(s) while performing in-page operations.

I suggest you look at your system drive, since this appears to be a paging file error. I would download the Crucial Storage Executive Tool and display the drive status and health from there. Also check for a firmware and/or driver update.

If that's all good then set Windows to use no paging file, reboot and then set 'automatic page file for all drives' to re-create a pagefile.

 

[Don__Kamikaze]

The dump you uploaded indicates that this may be a syatem drive problem...

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 000000000000003f, An inpage operation failed with a CRC error. Parameter 2 contains
    the pagefile offset. Parameter 3 contains the page CRC value.
    Parameter 4 contains the expected CRC value.
Arg2: 0000000000046d07
Arg3: 0000000000000003
Arg4: 000000004a1b00f7

.....

ADDITIONAL_DEBUG_TEXT:  Memory Manager detected corruption of a pagefile page while performing an in-page operation.
The data read from storage does not match the original data written.
This indicates the data was corrupted by the storage stack, or device hardware.

.....

 *** Memory manager detected 1 instance(s) of corrupted pagefile page(s) while performing in-page operations.

I suggest you look at your system drive, since this appears to be a paging file error. I would download the Crucial Storage Executive Tool and display the drive status and health from there. Also check for a firmware and/or driver update.

If that's all good then set Windows to use no paging file, reboot and then set 'automatic page file for all drives' to re-create a pagefile.

I forgot to mention that I have previously attempted to change the paging file to be on the HDD but the problem still happened.

I updated the firmware of the SSD (had to do it manually because the storage executive failed.

I also followed your suggestion for the pagefile. It rebooted and set the pagefile to be on the HDD. I will keep monitoring to see if the issue persists and update accordingly.

No event 51 is showing in the event viewer so far and managed to perform the installation of the same game that failed earlier.

Thank you for your suggestions.

 

[ubuysa]

Update the chipset drivers then. The dump doesn't lie, there was a CRC error in a page-in operation. If it's not the drive the pagefile is on, then it's either RAM or the motherboard.