Ram Incompatibility issue?

Relatyvity

Distinguished
Jul 1, 2015
12
0
18,520
Hi everyone! I'm new here so please forgive me if i make a mistake!

First of all here is my config: Asrock fm2a88X+killer mobo, AMD a10-7850k apu 16gB of G.Skill trident X 2400MHz ram (2 sticks) Be.Quiet dark power pro p6 650w psu and a coolermaser elite something case. I bought the mobo, ram and apu from a guy who wanted to build a new pc, but he got pissed off before the assembly and decide to sell it. The mobo and apu weren't used and still has warranty but the ram were in his previous config for about half a year. Now the problem is that i'm having BSoD and unexpected shutdown issues since i assembled it. I'm not an IT pro but i'm not a dummy, so i don't think i made a mistake during the assembly and there is no visible damage on any of the components. The stop codes refers to driver and/or ram related issues, and according to asrcok's and G.Skill's site the ram modules doesn't seem to be compatible. I mean it supports ddr3 modules and these are ddr3 modules, it supports modules with 2400Mhz clockspeed and it is, and it even supports 8GB stick wit 2400Mhz clockspeed but only 2 types, and this is not one of those 2. So is it possible that the problem i facing is an incompatibility issue or is it a damaged/faulty hardware? (yep i tested the ram with memtest, and first it found so many errors, the counter was unable to display, but after i swapped the modules out and placed them into the other slot, i was able to run it for 12 hours without a single error) I have already asked G.Skill and they were kinda helpful but, they said it should work with no problem, i should use them at 1866Mhz but that doesn't seem to be a solution. I tried to contact with asrock but i received the ordinary reply.

Please help me, I'm exhausted from fighting with this machine, i just want to make it work.
 
Solution
I would try setting them all the way down to 1333 or 1600 just for testing. CAS Timings of 10-10-10-30, and try the voltage at 1.5v. These settings are standard for value ram and won't hurt your ram at all.
If you are able to run your computer without issues with these settings, it's possible that the CPU doesn't like the 1.65v ram. CPU's that have the Ram controller integrated (like yours) typically supply power to the Ram modules directly. Higher voltage modules can cause instabilities because of this.

Just something to try in your testing.

Relatyvity

Distinguished
Jul 1, 2015
12
0
18,520


It's on default settings, meaning 1.65V. The support from G.Skill said it should be ok. That's the lowest setting and i didn't wanted to burn it so i haven't tried higher voltage settings yet.
 

budgetbuilds760

Reputable
Nov 1, 2015
42
0
4,540


good idea- Have u changed anything in bios regarding the CPU?
 

Pat Flynn

Distinguished
Aug 8, 2013
238
16
18,815
I would try setting them all the way down to 1333 or 1600 just for testing. CAS Timings of 10-10-10-30, and try the voltage at 1.5v. These settings are standard for value ram and won't hurt your ram at all.
If you are able to run your computer without issues with these settings, it's possible that the CPU doesn't like the 1.65v ram. CPU's that have the Ram controller integrated (like yours) typically supply power to the Ram modules directly. Higher voltage modules can cause instabilities because of this.

Just something to try in your testing.
 
Solution

Relatyvity

Distinguished
Jul 1, 2015
12
0
18,520


I pressed the wrong button can i undo this? :D I selected it as a solution... damn it. Nevermind thank you for the reply. I can lower the clockspeed and set the timing but i cannot lower the voltage this is the lowest setting, I cannot go under 1.65V
 

Relatyvity

Distinguished
Jul 1, 2015
12
0
18,520


Sure i did. A lot. But i have never risked anything since i payed all my pocket money on this machine. So all the safety functions are enabled, and everithing that has an auto setting is set on automatic. I overclocked it with the built in overclocker that sets up the whole system to be suitable for overclocking but it didn't make any difference so i tuned it off. It's working on factory speed now.