NF7-S Rev 2.0 / Kingston Hyper X

**~~Shroomalistic~~** · 04-21-2003, 09:40 PM

Well just my luck. I get a new nf7-s rev 2.0 and what do i find out. There is an incompatibility issue with the two. Kingston Hyper X does not work good in the third ( single ) slot. Abit says there working with kingston to fix the problem..

Its always something......................................... ...

**Hallowed** · 04-21-2003, 10:30 PM

A BIOS fix later and all is well. I'll bet its just SPD timings anyway, and those are changeable.

**Dissolved** · 04-22-2003, 03:27 AM

Would this affect the rev1.2 by any chance?

**Jen** · 04-22-2003, 04:52 AM

Originally posted by Dissolved
Would this affect the rev1.2 by any chance?

My understanding it affects only Rev 2.0's

**~~Shroomalistic~~** · 04-22-2003, 01:15 PM

Is just on the 2.0 on my 1.2 it was ok. After vdd mod i am able to get 225 @ 2,2,2,4 settings with one stick. Still no luck with two. I hope a fix comes out for this soon.

**glock19owner** · 04-22-2003, 01:32 PM

This is why I always wait a month or so before buying a newly released MB...adn Abit will get a fix out soon...at least its not as bad as the Corsiar issue when the 8RDA+'s came out...its taken Epox how long now to finally get a half-as*ed working BIOS for Corsiar memory...

**muzz** · 04-22-2003, 02:25 PM

Well it wasn't ALL Corsair memory, I have had 0 issues with my XMS 3500 sticks.
Both of my 8RDA+ boards have done over 230fsb dual with it in.

I will admit the problem there is just stupid though.

**deathstar13** · 04-22-2003, 08:56 PM

hmmm odd,i run a stick of each. 256 xms 3500 and 256 hyperx 3500
the hyperx is in slot3 closest to the edge of the mobo and xms is slot1 closest to the cpu.
ive had no issues what so ever with my rev2 nor did i either in the rev 1.2
i didnt see any revision number on the hyperx tho.

**ri3eboi** · 04-22-2003, 09:22 PM

The incompatibility is between the HyperX and the new nForce2 northbridge chip! Because people experienced the same problems with other nforce2 boards that are released recently. Also the problem seems to exist only when running RAM in Dual channel! So if you use one stick of HyperX, you can go as high as the board will go. Hope that helped.

**glock19owner** · 04-22-2003, 10:17 PM

Originally posted by muzz
Well it wasn't ALL Corsair memory, I have had 0 issues with my XMS 3500 sticks.
Both of my 8RDA+ boards have done over 230fsb dual with it in.

I will admit the problem there is just stupid though.

I agree with both of your comments Muzz...but a sh*t load of people including myself got the famous C1 error when they installed the XMS3500...this is also why I have 3 extra BIOS chips around now...and I don't run XMS3500 anymore either...not until I know there is a definet fix for it...

that's for being one of the luck one...lol...

**xtreme** · 04-23-2003, 08:26 AM

yup.. nf7-s 1.2 + 2x khx = 227FSB 3-2-2-2
nf7-s 2.0 + 2x kxh = 190FSB 3-2-2-2

LOL :>

**Boogotop** · 04-23-2003, 06:31 PM

on my nf7-s 2.0 and my hyperx (4.2.2.2) my systems reboot after 10-15min of gaming...lol

i think i will change my hyperx for other memory...on my 8rda+ i need to set memory@5.3.3.2 to run it @215 and more

**SAE** · 04-24-2003, 04:43 AM

Anyone here thinking this could be fixed?

Maybe I will try out some Twinmos 3200 BH5...

On my 1.1 (was back immediately in my sys) I am at least going 227MHz 2,0-3-2-2 dual channel. The striking 2.0 hardly manages 200.

P.S. nVidia's fault cause kingston was there and kickin' ass before new NB rev

**~~Shroomalistic~~** · 04-24-2003, 05:53 PM

Well i am now able to get to 484 on a single stick. The highest i could get before was 450. PC ICE gave me a little tip.

With the 333 athlons you had to cut the 3rd L12 bridge to get them to clock higher. So on my 2100 i connected that same bridge and made it a 333/2700. After that i could clock higher.

Very odd but it worked.

I havent tried with two sticks yet. But i doubt it will make a difference with these kingston sticks.

**SAE** · 04-25-2003, 04:09 AM

Who cares about single channel

If the boards would run dual like single :smileysex

Infact abit, nvidia or kingston have to solve this problem satisfiing all concerned users...

Deinstalled my 2.0 because I could not see any light at the end of the tunnel... at least 220 ... no!

Not even single channel... with bios ver. 11

**~~Shroomalistic~~** · 04-29-2003, 12:21 AM

Anybody come up with anything on this matter yet

NF7-S Rev2.0 / HyperX

**SAE** · 04-29-2003, 01:32 AM

Originally posted by Shroomalistic
Anybody come up with anything on this matter yet

NF7-S Rev2.0 / HyperX

No. Did not read anything.

Very interested in progress on this prob though

If there is no solution...

Hope that helps

**xgman** · 04-29-2003, 09:11 AM

Originally posted by Shroomalistic
Anybody come up with anything on this matter yet

NF7-S Rev2.0 / HyperX

Yes, I went out and bought some Mushkin 3500 ram at 228 52221 and moved the HyperX to a ver. 1.2 board.

**~~Shroomalistic~~** · 05-05-2003, 08:41 AM

Anyone know of a store that sells mushkin 3500 ( walkin store )
I wont order online. Dont believe in it. Im in the Los Angeles area if that helps.

**shimmishim** · 05-05-2003, 09:09 PM

i dunno why i didn't follow these threads carefully

i have a stick of hyperx 512 megs pc3500 and prime stopped on the 3rd test while running only at a fsb of 200 mhz @ 2-3-3-6!!!

and the speed was slower than my highest speed i could run...

sucks huh?

**~~Shroomalistic~~** · 05-11-2003, 11:06 AM

Anyone find any kind of fix yet. I dont have money for new ram right now. I did talk to fry's electronics and they said they were getting the mushkin 3500 real soon. Hopefully i can come up with some money by then. Or get a new freaking board.

Thread: NF7-S Rev 2.0 / Kingston Hyper X

Thread Tools

Search Thread

Rate This Thread

Display

NF7-S Rev 2.0 / Kingston Hyper X

Think it has been nVidia's fault if it's a question of fault indeed.

Bookmarks

Bookmarks

Posting Permissions