Memory Errors in Memtest86 - Please Help

IamJJJ

Honorable
Oct 8, 2012
81
0
10,630
Hello all! I'm having a problem here and I'm hoping someone can guide me to find a solution. First off, I will include my system specs.

System Specs:

CPU: AMD A10-5800K 3.8Ghz/ 4.2Ghz (Stock Cooler)
GPU: IGP - AMD Radeon HD 7660D
PSU: Antec Earthwatts 500W Bronze rated PSU
MB: ASRock FM2A55-DGS
RAM: G.Skill Ares Series DDR3-1866 2x4GB
HDD: WD Blue 500GB
HDD: WD Green 1TB
OS: Windows 7 Ultimate 64-bit
Additional Fans: 1 Antec Case Fan

--------------------------------------------------------------------------------------

Summary of the Problem: Due to a different issue I was having (at the end of this post I provided some background info) I ran Memtest86 last night and this morning to check my memory for bad sections/errors. Now the results I got were a bit odd...

First run of Memtest, I let it run overnight so it made multiple passes of the memory. Results:
http://s14.postimg.org/j7xaw9xg1/test1.jpg
--------------------------------------------------------------------------------------
So, obviously something is wrong with the memory if it had errors after 7 passes. I then used some logic and decided to test each 4GB module of memory individually to see which one had the errors. I left 1 module in the A slot and removed the one from the B slot. I then proceeded to run memtest. I let it run for 2 passes. Results:
http://s14.postimg.org/6f96wclu9/test3.jpg
--------------------------------------------------------------------------------------
Alright, that's some good news. At least one module is performing correctly. So after I rebooted and shut down my PC, I removed the previously tested memory module from Slot A and replaced it with the other memory module originally from Slot B that I removed for the previous memtest. This is where I ran into more errors. I let it run for only 1 pass because I believed that 1 pass was sufficient. Results:
http://s14.postimg.org/jyq121ztd/test2.jpg
--------------------------------------------------------------------------------------
So apparently only 1 memory module is bad. Right now, I'm running off the single memory module that procured no errors to prevent system instability. Now that I am at this point, I'm not sure what to do. Should I replace the damaged memory module? Should I call G.Skill to see if it can be replaced by warranty? What exactly should I do? I think I should use http://downloadmoreram.com/ (That was a joke)

Anyway in case it matters, I will provide you guys with some background information as to why I decided to run memtest:

I recently bought Total War: Rome 2 and installed it on my machine but I ran into a lot of problems trying to play it. It kept crashing and freezing completely so I decided to search for a solution. First off, my CPU was overheating. Well, I fixed that problem by reseating the heatsink. Second of all, my graphics drivers were all messed up. I replaced them with AMD's latest driver package (9.5.2013) as well as replaced atikmdag.sys and atikmpag.sys (I was getting BSOD's from those drivers) with stable versions. So I fixed 2 of the most obvious problems. Although those problems were fixed, the game kept freezing my computer and causing BSODs. I ran Whocrashed to discover the source of the BSOD:
--------------------------------------------------------------------------------------
On Sat 9/14/2013 10:41:45 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091413-26722-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xA (0x200000000000, 0x2, 0x1, 0xFFFFF80002EB3CF2)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
--------------------------------------------------------------------------------------

I did a lot of digging on the internet and figured out that this could be a possible memory problem so I downloaded memtest86 and the results are above.

Please help me I want to play Rome 2 :p

Thanks in Advance

 
Memtest86+ is the gold standard for testing ram.
Since you have identified a bad stick, you need to RMA it.
Now, here it gets a bit tricky.
A ram vendor will only support multiple sticks of ram that come in the same kit.

Contact g.skil support and see what they will do. They will want to send you a new complete kit. They only support kits, not individual sticks. There are good reasons for that since parts can change over time.
They might be understanding and have you give them a credit card deposit on a new kit. They it would be cancelled when they get your old kit.

If you can't do without any ram for a while, just order a new kit and plan on selling the rma kit when it arrives.