Originally posted by: AznBoi36
Just got my NF7-S v2.0 today!
I will be installing it in later tonight...
Just a quick FYI, I was about to ask the clerk at my local computer store if I can look at the board to see the revision number, but while it was bringing it to me, the side sticker on the box said "NF7-S 2.0" so that pretty much says everything
I will post a follow up with my experiences once I have everything installed.
Current rig info @ http://aznv.net/mypc.gif[/q
don't use the SATA RAID... you'll get corruptions out the butt..
- Status
Alright, I got this baby in!
After getting everything installed O/S, drivers, games, etc etc I started my OC journey on this new baby
Right off the bat, after reading many peoples posts about their experiences, I decided to set the FSB from 133 -> 217 (217 is the highest rated speed my memory can run. They're ocz pc3500 basic series), set vcore to 1.75, vdimm to 2.8, vcc to 1.7, memory to cas2.5 6-3-3.
Everything ran fine, pretty much, except the memory kept crapping out. I was getting too many application errors, and such. Thus I went back into the bios, and decided to keep my fsb at 200, left the memory timings the same. I wanted to keep the fsb:memory in sync. It's been about 2 hours now, stability seems rock solid so far. Only did one run of 3dmark. Will do more later...
Only complaint I have so far is that I'm using the onboard ethernet (realtek chipset) and I'm behind a ICS server. Everything I boot into windows, my whole computer would freeze for about 10-20 seconds (only my mouse would move, nothing else responds), and I think it's trying to get my IP settings and etc, from the ICS dhcp server
For now, my experiences were good
After getting everything installed O/S, drivers, games, etc etc I started my OC journey on this new baby
Right off the bat, after reading many peoples posts about their experiences, I decided to set the FSB from 133 -> 217 (217 is the highest rated speed my memory can run. They're ocz pc3500 basic series), set vcore to 1.75, vdimm to 2.8, vcc to 1.7, memory to cas2.5 6-3-3.
Everything ran fine, pretty much, except the memory kept crapping out. I was getting too many application errors, and such. Thus I went back into the bios, and decided to keep my fsb at 200, left the memory timings the same. I wanted to keep the fsb:memory in sync. It's been about 2 hours now, stability seems rock solid so far. Only did one run of 3dmark. Will do more later...
Only complaint I have so far is that I'm using the onboard ethernet (realtek chipset) and I'm behind a ICS server. Everything I boot into windows, my whole computer would freeze for about 10-20 seconds (only my mouse would move, nothing else responds), and I think it's trying to get my IP settings and etc, from the ICS dhcp server
For now, my experiences were good
I don't think I will try to go over a fsb of 220, as many here are saying it'd require a chipset vmod, since 1.7v isin't enough juice for it..
Right now, I'm thinking of picking up a pair of those corsair low latency modules..
Even though I'm at 200fsb in dual channel mode, it only feels a little faster than when I was using a 166fsb with cas2-2-2-5 1t timings on my AT7... that's now made me realize that very high quality is very important..
Right now, I'm thinking of picking up a pair of those corsair low latency modules..
Even though I'm at 200fsb in dual channel mode, it only feels a little faster than when I was using a 166fsb with cas2-2-2-5 1t timings on my AT7... that's now made me realize that very high quality is very important..
You know what's cool about the 2.0?
At the bottom right of the board there are 2 leds: 1 green and 1 red. Only the red one spews out a sweet red glow to my case (I have a side panel window)
The glow is very nice.. althought it's nowhere near the brightness of a CCFL tube, it makes for a nice errie red glow
Although I don't know if it's only related to the 2.0, even the rev1->1.2 might have them too.. but I don't see it mentioned on any reviews.. and I haven't seen a review of any rev2 yet..
At the bottom right of the board there are 2 leds: 1 green and 1 red. Only the red one spews out a sweet red glow to my case (I have a side panel window)
The glow is very nice.. althought it's nowhere near the brightness of a CCFL tube, it makes for a nice errie red glow
Although I don't know if it's only related to the 2.0, even the rev1->1.2 might have them too.. but I don't see it mentioned on any reviews.. and I haven't seen a review of any rev2 yet..
Noid
Platinum Member
- Sep 20, 2000
- 2,390
- 193
- 106
yes, the 1.2's have the leads.
And your right about the glow. I have a nice ANTEC case with a window.
It just has enough luminescence to put a red glow on the wall.
On your memory note,,, I experienced a similar situation with the memory also,,,
All I had to do was back off 0.5 on the multiplier on the CPU.
Seems the combination of Dual and the higher FSB, stressed my cache.
Now that we had a 80 degree day here in Chicago, I backed off my FSB to 215.5 (dropped chipset v to ~1.85v) and lowered my multiplier to 10.
(see my previous post on my pencil trick volt mod)
This allowed 1.775 volts on the CPU, which lowered my temps alot. (1.75v actual)
Today I'm going to see if I can go even lower on the CPU voltage, (and keep Prime95 running)
My XP2600+ (333) is just sightly oc'd now. And I only lost 60 points in 3dM03.
---------- EDIT --------
Dropped to 1.70v CPU - Prime95 stable with 3dM01 Demo LOOP mode on Non-Defualt with sound on (and Hardware doctor).
And your right about the glow. I have a nice ANTEC case with a window.
It just has enough luminescence to put a red glow on the wall.
On your memory note,,, I experienced a similar situation with the memory also,,,
All I had to do was back off 0.5 on the multiplier on the CPU.
Seems the combination of Dual and the higher FSB, stressed my cache.
Now that we had a 80 degree day here in Chicago, I backed off my FSB to 215.5 (dropped chipset v to ~1.85v) and lowered my multiplier to 10.
(see my previous post on my pencil trick volt mod)
This allowed 1.775 volts on the CPU, which lowered my temps alot. (1.75v actual)
Today I'm going to see if I can go even lower on the CPU voltage, (and keep Prime95 running)
My XP2600+ (333) is just sightly oc'd now. And I only lost 60 points in 3dM03.
---------- EDIT --------
Dropped to 1.70v CPU - Prime95 stable with 3dM01 Demo LOOP mode on Non-Defualt with sound on (and Hardware doctor).
From my thoughts of it, being the 2.0 uses a NB Nforce2 chip that officially supports 200fsb, hitting 200fsb and beyond is easy as long as you have a cpu that can do it
I just got an NF7 v2 board and was wondering what those 2 LEDs signify. It seems like the green one tells when the computer is on and the red when the board has power going to it. Is that all or is there something more?
Also, Sandra2003 and WCPUID identify my board as a 1.x revision but on the box and on the board it says v2.0. I just wanted to make sure I did get a v2.0 board, I don't know why there'd be a discrepency.
Also, Sandra2003 and WCPUID identify my board as a 1.x revision but on the box and on the board it says v2.0. I just wanted to make sure I did get a v2.0 board, I don't know why there'd be a discrepency.
there is a new bios update that should address that issue..
if the box and board say v 2.0, it's a 2.0
beatle
Diamond Member
- Apr 2, 2001
- 5,661
- 5
- 81
There is a new bios out for the NF7/NF7-S v2.0. You can pick it up here. Here's a list of the changes:
1. Please use AWDFLASH 8.23D or later to update NF7 series BIOS. With incorrect AWDFLASH version, the GUID will be erased, and leads to IEEE1394 peer to peer function failed. AWDFLASH 8.23D is included in this BIOS package.
2. Fixes incorrectly detect Thorton 2600+(166x12.5)CPU in SoftmenuIII.
3. Fixes DRAM hang up at POST code EFh for specific memory module.
4. Fix the problem that if used CPU 400FSB without User Define,it would not show DDR xxx (xxx=200,266,333,400).
5. The default value of CPU FSB/DRAM freq revises to "Auto".
6. Adds "CPU Disconnect Function" to adjust C1 disconnects. The Chipset does not support C2 disconnect; thus, disable C2 function.
7. Fixes DMI Pool data to be Socket A, Product Name: NF7-S/NF7 (nVidia- nForce2), Version: 2X.
8. The frequency of CPU 1917Mhz revised to 1916MHz.
9. Update SIP table to solve systems crashed issue while using 400FSB CPU+DDR 333, and revise the SIP Table of 266FSB CPU.
10. The default value of "Memory Timings" revises to "Optimal".
11. Updates BPL to be 2.94.
12. Fix system can not show fan speed in PC Health Status while using lower speed FAN.
13. Add "IDE Bus Master"function to improve transfer speed of GHOST, and default value set up to disabled.
14. Fix the problem that systems can not detect USB Drvice under WinME resume from S3,S4 mode, and lead to usb connector failed.
15. Fine tune the OC ability of 333FSB CPU.
16. BIOS Compile Date: 3/27/2003.
Unfortunately, they mention nothing about fixing incorrect temperature readings, which I suspect my board of. I'll go flash to newest anyway and see if it helps.
1. Please use AWDFLASH 8.23D or later to update NF7 series BIOS. With incorrect AWDFLASH version, the GUID will be erased, and leads to IEEE1394 peer to peer function failed. AWDFLASH 8.23D is included in this BIOS package.
2. Fixes incorrectly detect Thorton 2600+(166x12.5)CPU in SoftmenuIII.
3. Fixes DRAM hang up at POST code EFh for specific memory module.
4. Fix the problem that if used CPU 400FSB without User Define,it would not show DDR xxx (xxx=200,266,333,400).
5. The default value of CPU FSB/DRAM freq revises to "Auto".
6. Adds "CPU Disconnect Function" to adjust C1 disconnects. The Chipset does not support C2 disconnect; thus, disable C2 function.
7. Fixes DMI Pool data to be Socket A, Product Name: NF7-S/NF7 (nVidia- nForce2), Version: 2X.
8. The frequency of CPU 1917Mhz revised to 1916MHz.
9. Update SIP table to solve systems crashed issue while using 400FSB CPU+DDR 333, and revise the SIP Table of 266FSB CPU.
10. The default value of "Memory Timings" revises to "Optimal".
11. Updates BPL to be 2.94.
12. Fix system can not show fan speed in PC Health Status while using lower speed FAN.
13. Add "IDE Bus Master"function to improve transfer speed of GHOST, and default value set up to disabled.
14. Fix the problem that systems can not detect USB Drvice under WinME resume from S3,S4 mode, and lead to usb connector failed.
15. Fine tune the OC ability of 333FSB CPU.
16. BIOS Compile Date: 3/27/2003.
Unfortunately, they mention nothing about fixing incorrect temperature readings, which I suspect my board of.
I'll go flash to newest anyway and see if it helps.Originally posted by: beatle
There is a new bios out for the NF7/NF7-S v2.0. You can pick it up here. Here's a list of the changes:
1. Please use AWDFLASH 8.23D or later to update NF7 series BIOS. With incorrect AWDFLASH version, the GUID will be erased, and leads to IEEE1394 peer to peer function failed. AWDFLASH 8.23D is included in this BIOS package.
2. Fixes incorrectly detect Thorton 2600+(166x12.5)CPU in SoftmenuIII.
3. Fixes DRAM hang up at POST code EFh for specific memory module.
4. Fix the problem that if used CPU 400FSB without User Define,it would not show DDR xxx (xxx=200,266,333,400).
5. The default value of CPU FSB/DRAM freq revises to "Auto".
6. Adds "CPU Disconnect Function" to adjust C1 disconnects. The Chipset does not support C2 disconnect; thus, disable C2 function.
7. Fixes DMI Pool data to be Socket A, Product Name: NF7-S/NF7 (nVidia- nForce2), Version: 2X.
8. The frequency of CPU 1917Mhz revised to 1916MHz.
9. Update SIP table to solve systems crashed issue while using 400FSB CPU+DDR 333, and revise the SIP Table of 266FSB CPU.
10. The default value of "Memory Timings" revises to "Optimal".
11. Updates BPL to be 2.94.
12. Fix system can not show fan speed in PC Health Status while using lower speed FAN.
13. Add "IDE Bus Master"function to improve transfer speed of GHOST, and default value set up to disabled.
14. Fix the problem that systems can not detect USB Drvice under WinME resume from S3,S4 mode, and lead to usb connector failed.
15. Fine tune the OC ability of 333FSB CPU.
16. BIOS Compile Date: 3/27/2003.
Unfortunately, they mention nothing about fixing incorrect temperature readings, which I suspect my board of.
So anybody install this?? Good or bad for use 2.0 boards
This issue has been known for A LONG TIME!!!
It's just sad that Abit won't do anything about it. Board works well without using SATA RAID so i can't complain...
but since i do have 2 x 60 gig hard drives i should try to get an IDE raid card or something
Originally posted by: MARMADUKE
Shimm..
My old 8RDA+ buddy, you have had bad luck
I'm not complaining!!!
this is a great board despite the flakey sata raid setup...
i can do 218 mhz on my fsb as i couldn't even do over 195 with my 8rda+
i killed my board trying to do the mod... so, i can't complain about this board at all
running 2.5 ghz on this board so... no complaints....
I've had my NF7-S 1.1 running for about a month now at 2Ghz with a 2100+ on a 166fsb and 12 multiplier. Recently, I upped the fsb to 200 and lowered the multiplier to 10. The weird thing is that everytime I come home from work to turn it on, it boots with a 100fsb. I have to go into the bios and just do the save and exit option to get it to run at 200fsb again. It also did this while running at 166fsb and at default fsb. I have no idea why this is happening. It's not a big deal since I just go into the bios and make the change without a problem. It's annoying at worst. Anyways, any ideas on this or how it could be solved would be greatly appreciated. I posted this at amdmb.com a few weeks ago, but noone responded. I hope to get more insight here.
Thanks
Rod
NF7-S 1.1 bios 16
2100+@2ghz, 200fsb, 1.625v, Speeze hsf (verrry happy with this hsf)
2 256mb PC2700 samsung, 2.6v, running at speed defaults and in sync with cpu fsb
antec SL350 ps
maxtor 60gb
52x cdrom
52x24x52 cdrw
1.44 floppy
Thanks
Rod
NF7-S 1.1 bios 16
2100+@2ghz, 200fsb, 1.625v, Speeze hsf (verrry happy with this hsf)
2 256mb PC2700 samsung, 2.6v, running at speed defaults and in sync with cpu fsb
antec SL350 ps
maxtor 60gb
52x cdrom
52x24x52 cdrw
1.44 floppy
218 is great!..
I have a new 8RDA+ with C1 chip coming from egg tomorrow, some are doing 243 fsb with no mods at all!
I have build about 7 so far l
I have a new 8RDA+ with C1 chip coming from egg tomorrow, some are doing 243 fsb with no mods at all!
I have build about 7 so far l
I recently got and NF7 board and have two questions:
1) Does anyone know what the jumper near the AGP port does? I posted a thread in this forum about how with this board the LED on my optical mouse doesn't turn off at shutdown and there is no BIOS setting to adjust this. Someone suggested changing the jumper by the AGP slot, but since the manual doesn't say what it does I don't want to mess with it until I know what I'm getting into.
2) I've noticed with this board there is no way to manually adjust the PCI divider (relative to the FSB) like my last board. So does the board automatically ajdust it so the PCI clock is at 33 MHz or does it use a series of ratios based on what the FSB is (like 1/4 for 133, 1/5 for 166 etc). I'm wondering because if if overclock the board to an odd FSB (say 175, etc) I'm wondering what the PCI clock will default to since there's no way of changing it manually and I don't know of a software program that will let you monitor it.
1) Does anyone know what the jumper near the AGP port does? I posted a thread in this forum about how with this board the LED on my optical mouse doesn't turn off at shutdown and there is no BIOS setting to adjust this. Someone suggested changing the jumper by the AGP slot, but since the manual doesn't say what it does I don't want to mess with it until I know what I'm getting into.
2) I've noticed with this board there is no way to manually adjust the PCI divider (relative to the FSB) like my last board. So does the board automatically ajdust it so the PCI clock is at 33 MHz or does it use a series of ratios based on what the FSB is (like 1/4 for 133, 1/5 for 166 etc). I'm wondering because if if overclock the board to an odd FSB (say 175, etc) I'm wondering what the PCI clock will default to since there's no way of changing it manually and I don't know of a software program that will let you monitor it.
I have no idea about the first part of your question but for question 2, it locks the pci frequency to 33 so overclock to your hearts desire... you'll have no problems!
and someone help this man out with his first question
- Status
TRENDING THREADS
-
Discussion Zen 5 Speculation (EPYC Turin and Strix Point/Granite Ridge - Ryzen 9000)- Started by DisEnchantment
- Replies: 25K
-
Discussion Intel Meteor, Arrow, Lunar & Panther Lakes Discussion Threads
- Started by Tigerick
- Replies: 21K
-
Discussion Intel current and future Lakes & Rapids thread- Started by TheF34RChannel
- Replies: 23K
-
-
Facebook
Twitter