Sign-in / Sign-up
Your question

DDR3 RAM confusion. need help

Tags:
  • DDR3
  • RAM
  • Memory
Last response: in Memory
October 23, 2013 7:46:02 AM

ok after reading up on stuff for ages now, I can't really find a solution to my problem, so I try to post here and hopefully somebody can help me.

so here is my setup:
CPU Intel i5 3570k
MB: Gigabyte GA-B75-D3V
RAM 2x 4GB A-DATA AX3U1600GC4G9-2G, Game-Series
Windows 7 64bit

I am having issues with my DDR3 RAM, either I have bluescreens with various memory related messages or I am having frequent (random?) "APPCRASH" of various applications (incl. microsoft ones, like explorer, windows services ect.).

I am doing troubleshooting for weeks now and the issue must be related to the Memory in some way. So I played around with timings and voltages, but it doesn't seem to change much of my problem.
It must be hardware related, bc I ruled out everything else, I did a fresh install of Windows on a empty harddrive, updated BIOS and set to default before doing anything.

So here is my actual question, I can even really categorize my memory. It says it's supposed to be DDR3 1600G memory and the advertised specs are 9-9-9-24 @800mhz, @1.5V , which is also the included XMP Profile. But when I activate said profile in BIOS the described problems above become more frequent. When I set the setting to "auto" it clocks at 665mhz and timings are unchanged, which seems more stable (at least bluescreens are gone) but APPCRASH still happens. So apparently my MOBO can't stably run the XMP or the AUTO profile.

So if I were to loosen timings to get a stable system, what would you recommend? CPU-Z confused me, bc it says max. bandwith is 667mhz and it also says it's PC3-10700 memory.. shouldn't it be PC3-12800 considering the XMP profile and advertised specs? Have I bought DDR3-1333 memory that is overclocked by default? And why is tRAS so low? I've read it should always be at least CL+tRCD+tRP, but the "default" specs from the manufacturer are contrary to that.

Also worth to mention: the system runs perfectly stable with just one RAM stick. As soon as I put in the second one the problems begin (no matter which channel). And memtest runs 14passes without any errors btw.

here are 2 screens of what CPU-Z shows.

More about : ddr3 ram confusion

October 23, 2013 8:21:08 AM

A-Data memory modules are known to be complete garbage.
They do not undergo effective QA, and never have as far as I'm concerned.

They may also mismatch the SPD and RAM chips, making a product that is completely useless to the consumer.

Sure it lets them sell QA FAIL (at a normal company) inventory at a profit, but it's illegal and unethical.


Bin that shit and buy RAM that meets it's published specifications from Kingston (or any other reputable memory manufacturer).
m
0
l
October 23, 2013 9:08:02 AM

TheLastDoomguy said:
A-Data memory modules are known to be complete garbage.
They do not undergo effective QA, and never have as far as I'm concerned.

They may also mismatch the SPD and RAM chips, making a product that is completely useless to the consumer.

Sure it lets them sell QA FAIL (at a normal company) inventory at a profit, but it's illegal and unethical.


Bin that shit and buy RAM that meets it's published specifications from Kingston (or any other reputable memory manufacturer).


great -.- , I didn't know that. Buying new ones is not an option atm tho, bc I don't have the money. So I need to find a solution.. at least temporary one so that my system runs stable even if it requires to run the RAM at lower speccs. But I am noob when it comes to that, so I don't really know how I figure out these speccs.
m
0
l
Related resources
a c 5396 } Memory
October 23, 2013 5:09:11 PM

Try changing CR (Command Rate) to 2T - currently it's at 1T, these aren't made to run that tight, if problems persist, raise DRAM voltage + 0.05 and all should be good
m
0
l
October 28, 2013 6:15:55 PM

Tradesman1 said:
Try changing CR (Command Rate) to 2T - currently it's at 1T, these aren't made to run that tight, if problems persist, raise DRAM voltage + 0.05 and all should be good


Didn't work. Although appcrashes and BSODs became less frequent I think.
m
0
l
a c 5396 } Memory
October 28, 2013 6:40:33 PM

Do you have the latest BIOS, if not get that, then enable XMP, select profile 1 and try it...It should set to 2T and 1600, 9-9-9-24.....If still problems raise the DRAM voltage to 1.55... if still problems raise the CPUVTT voltage to 1.1

There are many misconceptions from CPU-Z - might look at my info thread here:

http://www.gskill.us/forum/showthread.php?t=10565
m
0
l
October 29, 2013 9:39:14 AM

Tradesman1 said:
Do you have the latest BIOS, if not get that, then enable XMP, select profile 1 and try it...It should set to 2T and 1600, 9-9-9-24.....If still problems raise the DRAM voltage to 1.55... if still problems raise the CPUVTT voltage to 1.1

There are many misconceptions from CPU-Z - might look at my info thread here:

http://www.gskill.us/forum/showthread.php?t=10565


Yes I have the latest BIOS. Updating BIOS was one of the first things I did when BSODs appeared.
And yes, as written above, I already tried the XMP profile, it sets the RAM to 9-9-9-24 1T @800mhz, but this makes the problems worse.

Currently I am running the RAM at 9-9-9-27 2T @665mhz and 1.55V like you suggested before, but I had a BSOD yesterday and now I am trying the same thing on different RAM slots.

What is CPUVTT voltage? Is that what CPU-Z shows as Core Voltage in the CPU tab?

m
0
l
a c 5396 } Memory
October 29, 2013 3:51:03 PM

CPUVTT is the memory controller voltage
m
0
l
October 29, 2013 11:29:22 PM

Tradesman1 said:
CPUVTT is the memory controller voltage


My BIOS doesn't let me change this. It's at 1.05V and greyed out no matter what settings I use.
m
0
l
a c 5396 } Memory
October 30, 2013 8:01:01 AM

My drop them a note asking about why voltages can't be adjusted
m
0
l
November 1, 2013 9:05:49 AM

Because the motherboard needs to support voltage changes to VDIMM?
This is hardly uncommon.

If you have been running with bad memory for an extended period of time then you can't just swap in good memory and have the problems go away, there will be executable files and libraries on the hard drive that have become corrupt.

Google: sfc /scannow, do that, then re-install all drivers and software that is 'required' to be stable.

Alternatively, once you have the memory stable, re-install the Operating System and all drivers and software.

m
0
l
a c 5396 } Memory
November 1, 2013 3:41:41 PM

The RAM itself doesn't isn't going to change Executables it reads them from the harddrive and does what they say, I don't ever remember having to reinstall the system due to a stick going bad
m
0
l
November 4, 2013 5:35:23 PM

No matter what I've tried I couldn't get it to run stable with both RAM sticks. So I removed one stick and the problems persisted, but then I switched the sticks and I haven't had a BSOD or APPCRASH for 2 or 3 days now. Appearently only one module is broken, bc I can run this one at 9-9-9-27 @800mhz @1.5V when the other showed problems within a couple of hours with much lower specs. I'll keep it this way for now and If problems return, I'll be back otherwise this might be the solution.
m
0
l
a c 5396 } Memory
November 4, 2013 5:40:19 PM

Sounds like RMA/return time
m
0
l