Anyone think they know why I've hit a wall?

HotKetchup

Member
Apr 30, 2003
80
0
0
Specs:
Abit NF7-S bios 2.x
Athlon 2100+ (T-bred B DUT3C AIUHB 0301)
Corsair TWINX 1GB 3200 CL2 in dual channel
SK-7 + Vantec Tornado (temp never gets higher than 39 C)
Memory is always syncronized with FSB
AGP always locked at 66mhz (can't find settings for PCI freq.)
WinXP pro

I have my FSB from 133 to 166 running stable at 1.65v (.05 higher than default). At 185mhz Windows won't boot (tried all voltages up to 1.85v).

So I took it a step slower and upped the FSB up to 171 from 166 and it only ran stable some of the time. I tried increasing the voltage in .025 increments all the way up to 1.825. Often, right after I started Windows, I would get a blue screen with a bunch of mumbo jumbo (I can't understand what it's telling me) and would restart my machine automatically. Upon restarting I would get a warning that drive C: needed to be checked for errors and it would do it. Once it boots into Windows I would get a notice saying that it recovered from a serious error and that I should report it to M$. Sometimes the desktop just froze up before I could do anything. But sometimes none of that would happen. I even tried all these things with the multiplier knocked down to 11.0 (from 13.0 default) to see if that helped but nope.

When I try running 3Dmark2001SE at those settings it would sometimes crash to the desktop in the first loop. The strange thing is that I can run CPU Burn-in for half an hour and not get a problem. What does that mean? That my cpu is fine but the memory can't keep up? The memory is at the default voltage (2.6v) for it's default speed (200mhz - DDR400) and I'm not running it anywhere near it's limit. Should I mess with any other voltages like the chipset's?

I'm only getting 2.158Ghz out of this proc. Shouldn't I be getting more? I will be highly disappointed if I bought this expensive DDR400 for nothing.
 

Soulkeeper

Diamond Member
Nov 23, 2001
6,740
156
106
I have the same problem i think the fsb limitations are a weakness of the nforce2 chipset
some do it while others don't, just sounds buggy to me
i've tryed 3 nforce2 boards with similar limitations below 200mhz
i can't even run my mem at 200 and fsb at 166 for a stable setup

that's why i got an ic7 max3 P4 motherboard
heh

 

HotKetchup

Member
Apr 30, 2003
80
0
0
Maybe. But it's the v2.0 board that supports 400mhz. I can run the mem at 400 and FSB at 133 and it works fine.
 

Jeff7181

Lifer
Aug 21, 2002
18,368
11
81
Maybe if you solder some resistors to your motherboard and drill a hole or maybe two in it, you'll be able to run a higher FSB ;)
 

nick1985

Lifer
Dec 29, 2002
27,153
6
81
Originally posted by: Jeff7181
Maybe if you solder some resistors to your motherboard and drill a hole or maybe two in it, you'll be able to run a higher FSB ;)

yeah, it worked for soulkeeper. oh wait, it went terribly wrong and now he wonders why his nforce2 was unstable.
rolleye.gif
 

rgreen83

Senior member
Feb 5, 2003
766
0
0
Maybe try running the memory a-sync with loose timings to see just how far the cpu will go on its own. The error that causes the corruption is usually from data lost somewhere in the NF2 northbridge when overclocking. The NB performs differently depending on what the cpu's default fsb is, it works best with the stock fsb and slightly worse with other fsb, so maybe mod the cpu to run at 166 default then try from there. Also try giving the NB a little bit more voltage.

*edit* I know the mod to run the chip at 166fsb sounds bass ackwards, but this is how it works on the 2.0. Here are some linkys for support>
http://www.liquidninjas.com/bbs/showthread.php?s=&threadid=3936</a>
http://www.amdforums.com/showthread.php?s=&threadid=219508 *edit*
 

Soulkeeper

Diamond Member
Nov 23, 2001
6,740
156
106
Originally posted by: nick1985
Originally posted by: Jeff7181
Maybe if you solder some resistors to your motherboard and drill a hole or maybe two in it, you'll be able to run a higher FSB ;)

yeah, it worked for soulkeeper. oh wait, it went terribly wrong and now he wonders why his nforce2 was unstable.
rolleye.gif

no.

just relax you trolls and stop trying to act smart, cause yur not


the board is stable just not with any fsb speed anywhere near 200mhz with any voltages/timings
the voltage mod's i've done work and aren't a problem, i've modded a few boards in my time
the chipset must just be a bad stepping or something
it is a C1 rev ultra-400 nforce2 chipset

guess i wasn't lucky in picking my nforce2 motherboards. But i got an ic7 max3 coming so i'll leave this thing at like 1.9ghz and call it a day



but as far as this thread is concerned i suggest running the memory as a lower ratio to the fsb speed
if you are running dual channel mode then this won't hurt performance much
changing memory timings did nothing for my overclocks


good luck