Sign in with
Sign up | Sign in
Your question

Memtest86 errors on two sticks only.

Tags:
  • Asus
  • G.SKILL
  • RAM
  • Memtest86
  • Memory
Last response: in Memory
Share
March 25, 2014 10:16:31 PM

3 months ago I rebuilt my desktop, new everything except tower, PSU and optical drive. I started noticing once a day or sometimes every other day it would shutdown or BSOD out of the blue. I have been busy and unable to troubleshoot it until recently and I've started with memtest and got some errors when running Memtest86+ 5.01.

Here is my setup:
Mobo: Asus Z87-A
CPU: Intel Core i7-4770K Haswell 3.5GHz
Ram: G.SKILL Ares Series 16GB (2 x 8GB) 240-Pin DDR3 SDRAM DDR3 2400
HDD: Seagate 600 Series ST240HM000 2.5" 240GB SATA III MLC
Video Card: GIGABYTE GV-R929D5-4GD-B Radeon R9 290 4GB 512-bit GDDR5 PCI Express 3.0
PSU: Corsair TX850
I've also got the old optical drive, and 4 1TB HDDS.

The first time I ran Memtest all the BIOS settings were set to auto, and I had both ram sticks in. I pressed F2 on Memtest to force multi-threading. I got 32 errors.


The second time I ran Memtest I adjusted in the BIOS the DRAM Voltage to 1.65 and the Timings to 11-13-13-31. I ran the first stick by itself. I did not force multi-threading. No errors.


The third time I ran Memtest I took the first stick out and put the second stick into the same channel the first stick was in. No multi-threading, same BIOS settings as test 2. No errors.


The fourth time I ran Memtest I moved the second stick back to its original channel to test that channel. Again no multi-threading and same BIOS settings as test 2 and 3. No errors.


The fifth time I ran memtest I put the first stick back into its slot and left the second stick in its slot as well. I enabled multi-threading and had the same BIOS settings as test 2,3, and 4. I got the same 32 errors on the first pass.


The sixth time I ran memtest in the BIOS I changed the XMP to enabled and it said that it would change in the advance settings Command Rate from Auto to 2. I have multi-threading enabled. I got even more errors this time.


I'm running it a seventh time now with just one stick in and with multi-threading enabled to make sure that isn't the issue.

I am a bit confused with what could be wrong here. I read the MOBO manual and it said to use slots A2 and B2 which I am using. Should my next step be to update the BIOS? I haven't updated it yet or changed any defaults other then the ones I mentioned above.

Update: I scratched the seventh test, and instead grabbed two sticks of G.SKILL Ripjaw F3-14900CL9D8GBXL which is also XMP so I let that change the BIOS settings automatically for the Ripjaw ram. I ran both sticks in the same spots as the previous ram together and got the same errors.


I am going to try a few different configurations for which two slots they occupy when both are in and testing and see if I get the same errors again. I would rather not have to RMA the MOBO, that is a lot of work so I am going to try other options first.

More about : memtest86 errors sticks

a b } Memory
March 25, 2014 10:23:53 PM

Potentially a bad slot on the motherboard, or damaged RAM is more impacted at the higher speed settings.

RMA the RAM and go from there.
m
0
l
a b Ĉ ASUS
a c 117 } Memory
March 26, 2014 3:06:52 PM

Do you have the latest BIOS?

Do you have any other DDR3 RAM you can test with?

Thank you
GSKILL SUPPORT

m
0
l
Related resources
September 8, 2014 5:53:30 AM

Hi tomblits,

Were you ever able to resolve this? I have a similar problem (memtest errors with both RAM sticks installed, but not individually).

Thanks.

m
0
l
a b } Memory
September 10, 2014 7:34:40 AM

TobyD said:
Hi tomblits,

Were you ever able to resolve this? I have a similar problem (memtest errors with both RAM sticks installed, but not individually).

Thanks.



Create a new thread for a new problem.
m
0
l
September 10, 2014 8:12:04 AM

Alec Mowat said:
TobyD said:
Hi tomblits,

Were you ever able to resolve this? I have a similar problem (memtest errors with both RAM sticks installed, but not individually).

Thanks.



Create a new thread for a new problem.


OK; thanks Alec. Here's the thread for my problem: http://
m
0
l
!