Kingston HyperX and 8RDA+ Issues Update Thread

Quote:

---

Originally posted by janko10


Yes, the 2 sticks is the issue. Like I said a few people with single 512mb sticks are doing fine and then others aren't. Could be bad batches of ram produced by Kingston, who knows. Hopefully Epox will be able to reproduce the issues in the lab.

---

It's OBVIOUSLY not just a bad batch of ram. Other wise with the A3 stepping my pc 3000 would not get past 180 in dual ddr form. THE SAME EXACT SETUP with A3 stepping board...ram is identical just swapped it all out...it hits a brick wall at 180 20+ mhz less than i know the ram is capable.

kirkyg

Quote:

---

Originally posted by kirkyg


It's OBVIOUSLY not just a bad batch of ram. Other wise with the A3 stepping my pc 3000 would not get past 180 in dual ddr form. THE SAME EXACT SETUP with A3 stepping board...ram is identical just swapped it all out...it hits a brick wall at 180 20+ mhz less than i know the ram is capable.

kirkyg

---

Good point.

I also have had 512 MB HyperX PC3000 issues. Very similar results - CPU OC's fine to 2.5 GHz, but under no cpu speed or Vdimm/Vcore can I get the memory clock above 180ish. I'm running an Abit NF7-S V2.0 w/an A1 stepping, and 2 stcicks of 512 MB HyperX 3000. Currently nice and stable at 12x200 w/ memory at 5/6 (166 MHz). Bump the mem clock up, and the system won't even boot all the way into windows.

I have not been too overly concerned, just figured I had some bad RAM and would try Corsair 3500 in a bit, but now I'm curious. If everyone is having these issues, there may be more to it...

Is it possible it's an A1 stepping issue? Is anyone w/o the A1 having problems?

Quote:

---

Originally posted by s1203372
I also have had 512 MB HyperX PC3000 issues. Very similar results - CPU OC's fine to 2.5 GHz, but under no cpu speed or Vdimm/Vcore can I get the memory clock above 180ish. I'm running an Abit NF7-S V2.0 w/an A1 stepping, and 2 stcicks of 512 MB HyperX 3000. Currently nice and stable at 12x200 w/ memory at 5/6 (166 MHz). Bump the mem clock up, and the system won't even boot all the way into windows.

I have not been too overly concerned, just figured I had some bad RAM and would try Corsair 3500 in a bit, but now I'm curious. If everyone is having these issues, there may be more to it...

Is it possible it's an A1 stepping issue? Is anyone w/o the A1 having problems?

---

Nope its definitely related to the change in stepping. But it may just be with kingston. I hope the corsair works if it doesn't then im in a pickle.

kirkyg

Hey janko just to let you know that i only have 1 512 stick of KHX and can't get above 180 either so its not an issue of 1 or 2 sticks. I hope this gets resolved or else it looks like i may hafta buy new ram cos 180 fsb is definetely not high enough for me. Hell the only reason i went with the Hyper-X is because i saw that everyone was easily hitting 200+ fsb.

Quote:

---

Originally posted by f4t4bb0t
Hey janko just to let you know that i only have 1 512 stick of KHX and can't get above 180 either so its not an issue of 1 or 2 sticks. I hope this gets resolved or else it looks like i may hafta buy new ram cos 180 fsb is definetely not high enough for me. Hell the only reason i went with the Hyper-X is because i saw that everyone was easily hitting 200+ fsb.

---

Thanks, I'll update the op :cool:

MONSTER UPDATE:

Thanks to gplracer @ amdforums.com for PM'ing me this info...

Well guys it looks like it's official, HyperX is incompatible with the new Rev A1 stepping of the NForce2. Found this out at a thread in the Abit USA forums. It seems their NF7-S 2.0 with the A1 is crapping out with the HyperX as well. Looks like they're more advanced in the resolution issue though. Here's a statement from Abit directly on the problem in the thread:

Quote:

---

We are working closely with Kingston regarding this issue. So far, the problem seems to be a incompatible issue between the Hyper X and the newer stepping of the North Bridge. I can run ANY other PC3500 modules up to 217Mhz FSB =434Mhz DDR @ 2-3-3-6 without any problems on the NF7-S v2.0.

Kingston is working on this issue with NVIDIA right now and we are waiting for a fix from them.

AFAIK, Hyper X has the same issue with other motherboard manufactures as well.

---

The full thread can be found here:

http://forum.abit-usa.com/showthread...0&pagenumber=1

I suggest everybody read through it, I'm in the midst of doing that now. I'm gonna email Epox the thread as well to let them know that Abit seems to think it's the A1 revision as well so they can get right on it.

I'm gonna keep reading and post any more info...

ahh sh1t thas not good news. What will generally happen in occasions like this?? Will epox fix it later on with newer bios release or is it something beyond that. Good to know its not the mobo at least but i still don't wanna sell off this 1 stick and get some other brand memory. Can ya gimmie a summary of that post on the other forums. Don't have the time right now to read thru all of it.

NOT SO GOOD UPDATE:

Well in reading more of the thread, Abit seems to think the fix will have to come from Kingston since other brands of PC3200 and PC3500 memory work ok in their boards. Let's hope Epox doesn't take that stance as well, otherwise I'll race you all to www.ebay.com :cool: :(


Here's Abit's quote:

Quote:

---

A fix might have to come from Kingston instead of ABIT, because we do not see a problem running the NF7-S 2.0 with any other PC3200-PC3500 memory. There are other nForce 2 chipset motherboard users reporting the same problem with the Hyper X as wel.

---

UPDATE:

Here's my latest email to Epox, btw:

Quote:

---

Mr. Hutton, I've found some more information pertaining to the Kingston HyperX issues. I was browsing the Abit USA forums and noticed a thread there where people with the Abit NF7-S 2.0 (an NForce2 motherboard with the A1 stepping of the north bridge as well) are also having incompatibility issues with the ram as well. Abit has officially acknowledged that Kingston is currently working with NVIDIA to try and resolve the issue, so I just wanted to give you guys a heads-up and maybe that way you can jump start this and get in contact with Kingston about it (if you haven't already, of course). Here's a direct quote from the Abit Representative in the thread:

"We are working closely with Kingston regarding this issue. So far, the problem seems to be a incompatible issue between the Hyper X and the newer stepping of the North Bridge. I can run ANY other PC3500 modules up to 217Mhz FSB =434Mhz DDR @ 2-3-3-6 without any problems on the NF7-S v2.0.

Kingston is working on this issue with NVIDIA right now and we are waiting for a fix from them.

AFAIK, Hyper X has the same issue with other motherboard manufactures as well."

So it doesn't seem that it's an Epox related issue at all, just and NForce2 A1/C1 and Kingston issue. The rest of the thread can be found here:

http://forum.abit-usa.com/showthread.php?
threadid=8216&perpage=15&highlight=hyperx%203500&pagenumber= 1

So let me know what you guys think/find when you get a chance. Perhaps you'll be able to come up with some kinda fix in the bios for the 8RDA+? Thanks again for all your help and quick response to this issue.

Thanks again,

---

It's weird though, crapping out at 180mhz, just hitting a wall there. Hmm...I hope kingston recognizes the issue and ppl can RMA their sticks for a new revision.

OMG THIS OFFICIALLY SUCKS UPDATE:

Well at least the_nut_man at Abit forums has heard back from Kingston, they never sent me anything.

This is not encouraging :(

Quote:

---

Guys

I like to do my research before I jump in to anything so I contacted Kingston support and got the following response. Hope this helps.

Hi Steve,

Thank you for contacting Kingston Technical Support. This Abit NF7-S board
uses Nvidia nForce2 SPP chipset, and from our testings done in lab, Hyper X may
not be compatible with nVidia nForce2 SPP chipset , when 2 pieces are installed.
One piece should work, 2 pieces will mostly likley fail. You may consider using
our regular parts that are compatible with this board: KVR266X64C25/256
(DDR266), KVR333X64C25/256(DDR333), and KVR400X64C25/256(DDR400).

Please let me know if I can be of further assist.

Regards,

Jane Cheng
Kingston Technology Far East Co.
+886-3-5666860 direct
+886-3-5789502 fax
[email protected] or
[email protected]

---

That message was posted on 4/18. If that's goona be Kingston's official stance, then I think we're all gonna be SOL, which sucks a fat you know what.

I'm still reading through the thread...

well damn this just sucks. What other brand of Memory can o/c to 200+ cos i'm not really up to date on memory besides the Hyper-X. Didn't the Crucial RAM have a problem with the 8rda+ also or was it the Corsair?

I don't believe Corsair XMS 3500 has a problem with the 8rda+. I atleast hope not because I was planning to go with 2 sticks of 512 mb XMS 3500

LOL UPDATE:

Well I FINALLY got a response from Kingston....

Quote:

---

Thank you for using Kingston on-line technical support. If you would kindly contact our technical support group via telephone at (800) 435-0640, we will be able to assist you better. Thank you for using Kingston on-line technical support.

Best Regards,
Tawan Robinson
Technical Support
Kingston Technology Company

---

Well that helps a bunch (insert ol' Mr. Rooleyes right here).

I don't have the time to call then right now, but I will later or tommorrow. I'll be PLEASANTLY surprised if that does anybody any good, but hey, you never know.

If any of you guys have the time right now, give 'em a call and see what they have to say. Make sure you note that it's NOT about overclocking. The ram is rated to run at 200mhz+ (for you people with PC3200+ obviously), so it should be able to run that high- i.e. that's NOT overclocking. It seems that all the tech support people love to throw in the obigatory 'Oh, we don't support overclocking' when we're not overclocking the ram damnit :mad: