*** Official ABIT NF7/S (nForce2) Thread ***

[pelikan]

First I'd use a low multiplier for the cpu, like 9, and see what the memory will do. I would give the memory 2.9V and test it at Cas 2-2-2-6 to see how high it goes stable. Then benchmark with Sandra, Aida32, UT2003 and 3DMark01. Then back off to more conservative timings, 2-3-3-7 or 2.5-3-3-7 and see how high that will go and do the same benchmarks.
When you've found optimal FSB and timings for the memory start raising the multi.
I test stability with memtest86 and prime95.

 

[Booyah]

Great board! Upgraded to the ver2 runs rock stable.

 

[Noid]

New BIOS ....

v1.x = 21
v2.0 = 1.8

NF7-S 1.x

NF7 / NF7-S 2.0

NF7-M

For NF7-S 1.x ....

1 Updated BPL to v3.09 according to NVidia's recommendation.
2 Fixed the problem that system hangs up with POST code 01 while resuming from STR mode with user defined DRAM timings. With default SPD setting, no problem at all and doesn't need this update.
3 Fixed the problem that system hangs up at POST code FF with over clocking setting- change the multiplier factor from CPU default to 19.
4 Fixed the problem that Barton 2500+ CPU is occasionally detected as Barton 3200+.
BIOS Compile date: 7/24/2003.

 

[PUNKtotalled]

Is that bios running fine?

 

[paladinhost]

Text

07/20/2003 7:43 PM


I am going to order this board to use the Sata Raid Does the NF7s use a good chip for sata that give better performance than IDE???

-------------------------
Heat My Rig Ars/Evals


SATA Boost pretty good no lost data on copy or transmitting....got problem on first timer ....but all work fine i use my dvd rom with sata too,

maxtor SATA 8Mb 7200 Diamond max plus

 

[pelikan]

I'm using bios 18 on my rev. 2 board and no problems so far. I'm also using the new nvidia nforce2 drivers without problems.
I've been updating the bios with the Abit flash utility, using the "one click" option. It's very easy and has worked for two bios flashes.

 

[t4t3r]

I'm on 1.8 now, flashed using the floppy method, running just fine. I'm also using the 2.45 nforce drivers without any problems.

 

[Noid]

I dumped the 2.45's. I got the same sound issues as the other releases.

I will be trying a custom install next time. (skipping sound driver)

 

[pelikan]

When I first tried the 2.45's I also had sound issues. But it was because my operating system was all messed up from finding the overclocked limits of my board. That always happens to me with a new board, and is expected. After reformatting and clean installing XP, the 2.45's work great.

 

[nlh]

Any suggestions on the precise method of software installation?

Also, before I go scour the manual, is there a quick way to keep the BIOS from searching for a RAID setup upon boot? It happens to lengthen the boot process greatly and I don't wish to use RAID yet.

Thanks, time to go read.

 

[beatle]

nlh, I'm not sure what you mean by "precise method of software installation," but under integrated peripherals, there is an option to disable the onboard SATA.

 

[nlh]

Is the onboard SATA what causes a slight delay at boot? I'll do that then, thanks.

By software installation I mean the order of driver installs, etc. (Nforce2 chipset drivers, directx, video drivers and so on).

I have SP1 and the chipset and video drivers installed, but not directx9 yet. I assume that's the last and only step. Just wanted to be precautious - thanks.

 

[nlh]

Another question in general -

I use the Swiftech MCX462+ heatsink, but a weak, quiet fan (vantec stealth). The Hardware Monitor reads my CPU as idling around 40c, then it will move up and down quickly upon little activity. Does the software just estimate what might be happening, or is my CPU usage higher than normal? I don't mind the higher temperatures since I don't overclock, but I'm a little crazy and would like it to stay low/accurate.

 

[eliteramen]

Anybody know or try an Athlon XP "Mobile" (specifically Barton 2500+) in the NF7-S v2.0? I've heard of success using an XP Mobile in other nforce2/ultra boards.

Thanks,
[eR]

 

[spikemike]

i'm getting a Vio minimum voltage warning from the hardware monitor and when I checked it is varying rapidly, but always floating around the built in minimum (3.1V-3.2V) is this a problem, anyway to make it higher?

Thanks

 

[DKlein]

I just bought a NF7-S v2.0 the other day and started overclocking it. Everything was working fine, I got the bus up to 180 before my DDR333 couldn't keep in sync anymore, but then when I turned my computer off and back on nothing happened - there was a blank screen and a long beep. I cleared the CMOS and started over again. Basically, I can't go any higher than 168 or else the computer won't start (but it WILL restart). Anyone else having this problem or have any ideas?

Specs:
Abit NF7-S v2.0 (BIOS v1.8)
AMD Athlon XP 2500+ (Barton)
512MB Kingston VRAM DDR333
GeForce3 Ti 200
Other stuff...

I tried upping the voltages and fooling around with RAM settings, but it was of no use.

 

[Shimmishim]

Originally posted by: DKlein
I just bought a NF7-S v2.0 the other day and started overclocking it. Everything was working fine, I got the bus up to 180 before my DDR333 couldn't keep in sync anymore, but then when I turned my computer off and back on nothing happened - there was a blank screen and a long beep. I cleared the CMOS and started over again. Basically, I can't go any higher than 168 or else the computer won't start (but it WILL restart). Anyone else having this problem or have any ideas?

Specs:
Abit NF7-S v2.0 (BIOS v1.8)
AMD Athlon XP 2500+ (Barton)
512MB Kingston VRAM DDR333
GeForce3 Ti 200
Other stuff...

I tried upping the voltages and fooling around with RAM settings, but it was of no use.

its a good chance taht it is your RAM...

if you have another stick... try it out in your system

 

[BDSM]

have you tried to run the ram async?

 

[DKlein]

I switched the RAM (wonder why I didn't do that earlier) and it worked.... somewhat. There were still some problems though. I went up from 166 to 183 with no problem, just I had to do it one by one. Then I tried lowering the timings and had to clear the CMOS. When I tried to put it back to 183 again (just in one shot though) it didn't work. I'm thinking perhaps the BIOS could have something to do with this...

 

[Soulkeeper]

i'm at 211 fsb right now
what about the rest of you ??

 

[BDSM]

220 mhz is max for me.

 

[pelikan]

Originally posted by: spikemike
i'm getting a Vio minimum voltage warning from the hardware monitor and when I checked it is varying rapidly, but always floating around the built in minimum (3.1V-3.2V) is this a problem, anyway to make it higher?

Thanks

You should check it at a molex with a digital multi meter. If it really is too low then there are options. If your psu is low quality or just doesn't have enough power, of course get a new one. If the psu is good then you can mod it to get more juice on that rail. The mod is pretty easy and can be done to by putting a pot on one of the wires leading to your mb (the one that tells your psu how high the 3.3V rail is).

 

[Links4me]

Originally posted by: Soulkeeper
i'm at 211 fsb right now
what about the rest of you ??

Still where I was a couple of months ago, running stable w/ win2k. Prime95 no errors for 20hrs+, memtest no errors for 20hrs. WinXP is a different story.....with the same specs cpu 1.8v, mem 1.8, chipset 1.7v, prime95 ran 20hrs no errors one day and the next, failed after a few hours, then another time after 20mins....then the blue screens.....I looked up the error (it says it is a memory error) and lots of others have had the same problem and they all pretty much said, "I just lowered the fsb on the memory and it was fine" or something like that. I personally am not going to run pc3200 memory at anything less than pc3200. I tried various mem settings in the bios, voltage settings etc.....still the same. Weird tho', sometimes it took a whole day after a fresh install of winXP (this is pro I'm talking about), before the blue screens came. (also, I always load the OS at default settings for cpu,mem etc...then overclock) Anyway, back to win2k w/ no problems after a month.....Oh well....

 

[Mustanggt]

Originally posted by: Soulkeeper
i'm at 211 fsb right now
what about the rest of you ??

Mine is at 227 fsb wish I knew how to copy pics of benchmarks to show my Mem scores and FSB. this is a great board

 

[Megatomic]

I just got my NF7-S R2 today. I thought it was going to be a dead board (the NB and SB coolers were loose and had bent caps over and such) but right out the box I got 200MHz FSB. My 8RDA+ was incapable of this. And I'll be honest with you all, this system is so snappy at 200MHz FSB. I just can't believe how responsive it is; memory benchmark results are so much higher than they were at 185MHz. But I know it can be better... Where can I go for a good BIOS tweaking guide? The one at MotherboardFAQ.com is geared mostly for Epox boards. Thanks for any links.

Oh and one thing I saw today. I flashed to BIOS 18 and suffered from warm reboot lockups when the system was detecting the RAM during POST. I flashed back to BIOS 17 and this problem was gone. Did anyone else experience this? Or is this maybe a product of the loose heatsinks bending the caps? Opinions? Thanks once again.