• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Barton 2500+ OC problem... Please help

M

Mr.Pig

n00b
Joined
Jun 12, 2004
Messages
28
Machine specs:

2500+ (AQZFA0347XPMW)
Abit NF7-S rev. 2
Kingston KVR400X64C25/512 (x2): 2.5 - 3 - 3 - 7 (I think, but not sure on the last one)
9800 Pro (flashed to 9800 XT)
SLK-947 w/ Cooler Master Aero blower
Antec Sonata (stock PSU)


Behavior:
Though locked, the processor seems more or less OK at 3200+. (I think the stepping is actually pretty good.) When I try anything that uses serious system memory (MemTest), I get a crash. Also video apps like 3DMark (any) crash shortly after starting.

Upping the voltage on the CPU (as high as 1.8V), memory (2.8V), AGP (1.6V?) and chipset (as high as the board can go, but don't remember exactly), the system is more stable, but eventually crashes running both apps mentioned above.

Thinking I had a memory issue, I ran the CPU at 400 and the RAM at 333. The system was completely stable in that case with minimal voltage increases, if any. Tried relaxing the timings across the board (3 - 4 - 4 - 8) and the system wouldn't boot. =/ Also tried running the memory is single-channel mode and even taking out one DIMM, to no avail.


Questions:
Is my north bridge having problems or my RAM? My guess is RAM, in which case is there anything I can do short of buying better stuff? Is it worth while to run the CPU at 400 and the RAM at 333? My preliminary benchmarks suggest not.

And what's with my machine not booting with relaxed memory timings?

Thanks for any input you guys/gals might have
 
I experianced this problem before on a A7N8x-E Deluxe. The problem only seemed to manifest itself if the FSB was exactly 200mhz. After screwing around for awhile and getting it to work at 232FSB with a memory divider I gave up on figuring out the anomoly. I did later try one of the UBER bios's though and the problem seemed to go away
 
Thanks for the input BigT. I will look into your solution. Now if only my CPU was unlocked... :)
 
You must log in or register to reply here.
Back
Top