Difficulty Diagnosing Memory Issues

[bowsting]

Introduction

I have recently run into some difficulties with my year and a half old system (specs below). It started as some odd issues with Windows the search function where it would close after a few seconds of being open. I tried the suggestions online but got nowhere so I refreshed my machine. This actually caused more problems, mainly with the graphics, so I completely reinstalled windows drivers etc. Now all of those issues are gone but now I am getting various bluescreens all of which appear to be tied to memory and I am getting random program crashes for various programs.

 

However, the odd part of this, and the reason I haven't just gone out and replaced my memory, is that Memtest86+ has not picked up any issues with my RAM with over a dozen passes. Because of this, I am somewhat concerned that the issue is actually some alternate hardware issue (say the motherboard) and I am looking for some guidance on how I should go about moving forward.

 

The System

Operating System: Windows 10

Motherboard: MSI x99s SLI Plus

CPU: i7-5820k

Memory: G.Skill DDR4 3000 8GBx2

GPU: MSI 980ti

HDD: WD Black 2TB

SSD: Samsung 850 EVO 250GB

PSU: EVGA SuperNOVA 750 G2

 

The BSODs

The BSODs I have been getting are varied but all appear to be memory related. I have attached the minidump files below. These are never BSOD loops and only occur about once every 2 days but that's regular enough to cause serious concern obviously.

 

Windows Memory Diagnostic

Unlike Memtest86, WMD has returned that there are hardware issues both times I have run it. However, I do not know how to read the information so any assistance in that regard would be appreciated:

Log Name:      System
Source:        Microsoft-Windows-MemoryDiagnostics-Results
Date:          9/30/2017 16:24:13
Event ID:      1102
Task Category: None
Level:         Error
Keywords:      
User:          SYSTEM
Computer:      DESKTOP-1CFA8QE
Description:
The Windows Memory Diagnostic tested the computer's memory and detected hardware errors. To identify and repair these problems, contact the computer manufacturer
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-MemoryDiagnostics-Results" Guid="{5F92BC59-248F-4111-86A9-E393E12C6139}" />
    <EventID>1102</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2017-09-30T23:24:13.623379300Z" />
    <EventRecordID>3644</EventRecordID>
    <Correlation />
    <Execution ProcessID="4996" ThreadID="5024" />
    <Channel>System</Channel>
    <Computer>DESKTOP-1CFA8QE</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <UserData>
    <Results xmlns="http://manifests.microsoft.com/win/2005/08/windows/Reliability/Postboot/Events">
      <LaunchType>Manual</LaunchType>
      <CompletionType>Fail</CompletionType>
      <MemorySize>16284</MemorySize>
      <TestType>10</TestType>
      <TestDuration>78</TestDuration>
      <TestCount>12</TestCount>
      <NumPagesTested>4167370</NumPagesTested>
      <NumPagesUnTested>1230</NumPagesUnTested>
      <NumBadPages>1</NumBadPages>
      <T1NumBadPages>0</T1NumBadPages>
      <T2NumBadPages>0</T2NumBadPages>
      <T3NumBadPages>0</T3NumBadPages>
      <T4NumBadPages>0</T4NumBadPages>
      <T5NumBadPages>1</T5NumBadPages>
      <T6NumBadPages>0</T6NumBadPages>
      <T7NumBadPages>0</T7NumBadPages>
      <T8NumBadPages>0</T8NumBadPages>
      <T9NumBadPages>0</T9NumBadPages>
      <T10NumBadPages>0</T10NumBadPages>
      <T11NumBadPages>0</T11NumBadPages>
      <T12NumBadPages>0</T12NumBadPages>
      <T13NumBadPages>0</T13NumBadPages>
      <T14NumBadPages>0</T14NumBadPages>
      <T15NumBadPages>0</T15NumBadPages>
      <T16NumBadPages>0</T16NumBadPages>
    </Results>
  </UserData>
</Event>

 

092217-8328-01.dmp

092617-7328-01.dmp

092717-7281-01.dmp

092917-5281-01.dmp

093017-8281-01.dmp

[Skiiwee29]

So with memory, its usually 1 or 2 things, the RAM itself, or the CPU, since it houses the memory controller. Very very rarely is it ever the motherboard that is the problem in these instances. What I would recommend doing is try removing your overclock on your CPU and testing for an extended period of time to see if you get the errors or crashes. 

[bowsting]

Quote

What I would recommend doing is try removing your overclock on your CPU and testing for an extended period of time to see if you get the errors or crashes.

So I have no overclock on my CPU currently though I am using XMP on the memory. Would it be worthwhile running without that for a while to see what happens?

[Skiiwee29]

18 minutes ago, bowsting said:

So I have no overclock on my CPU currently though I am using XMP on the memory. Would it be worthwhile running without that for a while to see what happens?

definitely.