Kingston hyperx savage 2400 - did I get a faulty RAM?

Toggle sidebar Toggle sidebar
N

Narhim

Reputable
Apr 6, 2015
9
0
4,510
Hi everyone,

I have an issue with my new RAM from kingston (savage 2x8 GB 2400mhz). Did a cmos reset. After installing the ram, I got 4 beeps, the pc rebooted 3x and started. I went into bios and saw that the ram is running at 1600mhz, 1,55V.
I activated xmp profile 2 (2133mhz), saved and rebooted. again 4 beeps, two reboots and boot. in bios I saw that the ram was again running 1600mhz.
When activating xmp1 (2400) the pc booted and 2400 was indeed running. I accepted the initial hiccups and went on working with my pc.
tested the ram with memtest for 2h and it ran stable.

However, after round 8 days the pc suddenly beeped 4x at boot and after 3 reboots booted. I went into bios and I saw that the ram voltage is at 1,425 while running at 2400. That was weird so I tested the jedec and the xmp profiles again.
I managed to boot into bios with 2133mhz running and was shocked to see that instead of 1,6V dramv was as high as 1,725V. When I booted back into 2400 the dramv was at 1,875V, after reboot at 1,425V and 1600mhz ran at 1,55V.

I have no clue what is going on, either the ram is not compatible with my motherboard, the 8 days fried my memory controller (which is unlikely) or the ram is broken.

I removed the ram for now. can you help me please?

my rig:
asrock z77 fatality performance
i73770k
Gigabyte gtx 980g1
antec hcg 620m
 
Sort by date Sort by votes
Hi Narhim,
I'm Jewel with Kingston US Technical Support and would like to offer our assistance. Not sure why but it seems that even setting the XMP profile is not setting the voltage of the memory properly. When running on 1600 it should be 1.5V, at 2133 1.6V and at 2400 1.65V as programmed in the XMP profiles. One thing you can try is to manually set the timings and voltage according to the proper specifications to make sure the memory is properly set. Also, by default the memory should run at 1600 1.5V so when it was first installed it was running the way it should have been. Here is the datasheet of the memory showing the timing settings for the two XMP profiles: http://www.kingston.com/datasheets/HX324C11SRK2_16.pdf

When going into the DRAM timing settings the only timings that would need to be change are the first three as indicated in the datasheet. Outside of that only the frequency and DRAM Voltage would need to be changed for the specification. Before making any changes make sure to restore the BIOS to defaults to avoid any conflicts with other changes that may have occurred.

For further assistance, please contact our support in your area. Contact information found here: http://www.kingston.com/company/contacts#tech

Thank you for using HyperX Savage memory!
 
Upvote 0 Downvote
hi,
I have the latest bios available for this mobo installed. when I set the values manually, I ended up with 2400mhz and 1.85V. Even after a uefi default restore, no change. never had an issue with kingston ram before.
will likely do a rma and may try the 1866mhz savage.
 
Upvote 0 Downvote

I tried it on stock and at 4.2ghz, still no difference. The ram just needs too high voltage to run stable.
 
Upvote 0 Downvote
yes, that is the version 2.10p from 31.1.2013
I had 16gb khx1866cl10 before and they ran very well. sold them to a friend and got the savage. why? because I thought it will give my pc an edge... it did :/
 
Upvote 0 Downvote


I just found out that the savage 1866 pulls my CPU PLL voltage up to 1.834V, I can't even override it in BIOS.
Interestingly the PLL voltage seems to set the DRAMV up to the same value and even when I set it to 1.5V it still shows 1.834V. Again that is WAY TOO HIGH for DRAMV. I could not find anything regarding this issue anywhere.
I got a set of old crucial 1600cl9 RAM today and was able to set the CPU PLL voltage to 1.584V and that set the DRAMV to 1.584V. the VTT I set to 1.094 to be in the 0.5V range...
The PC runs and it seems stable (for now) but I have the bad feeling that the Kingston RAM somehow fracked up my IMC or messed up the MoBo somehow.
I tried to fix things with CMOS-reset, even BIOS reflash in case there would be some faulty bytes floating around and messing up the settings, but no change. The PLL still sets the minimum of the DRAMV in BIOS.
Any thoughts?
I hope I won't need to get a new CPU/Mobo, wanted to wait for skylake... :/ Should have remembered the "don't touch the running system" and just leave things the way they were.
 
Upvote 0 Downvote


Tried in the black (A2, B2) the ones that are reccomended to use by ASrock and then tried the red ones... no difference :/
 
Upvote 0 Downvote
Hi, Narhim : )

I have exactly the same problem.
Saves me from creating another thread like this.

I have the same CPU (OCed to 4.2)
Different mobo, but same manufacturer. (AsRock Z77 Extreme4)
same RAM

I bought the HyperX Savage 2400 and it is only running at 1600.
I've tried changing the XMP profile like you and manually setting it to 2400, but it only shows as 800 (so effectively 1600) in CPU-Z.
I manually set it to DDR3-2400, to no avail. Also tried it on auto, to no avail again.

14csoeg.jpg

The PC restarts itself 2 times before it manages to finally load windows, everytime.
This message appears before it finally loads up:
zofg8x.jpg


I don't want to confuse or get in the way of everything here, so I could create another thread if you want me to, but since it's exactly the same issue, I though it'd be best to post here.

2nv3zb5.jpg


kd042e.jpg
 
Upvote 0 Downvote


Ok that did not come to my mind... will do!
 
Upvote 0 Downvote
Ok, the CPU PLL voltage still defines the DRAMV, which was not the case before I tried the savage... Even after cmos reset and battery removal for 1h.
Is this issue hardware-related? Can it be that the savage screwed something in my CPU / IMC? Or something in the Motherboard?
Damn it!
@JaredzzC the very same thing. With 1866 it was the same. Savage is not compatible with wither some of the Motherboards from ASrock z77 chipsets and/or the i7 3770ks. How are the voltages?
 
Upvote 0 Downvote
Could be that the savage somehow screwed things up,seems to be that way.The only thing possible is the bios chip itself,don't understand how though.
Another try at flashing the bios maybe?
You don't have some kind of overclocking tool at work in windows?
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom