• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

help w/ OC'ing new rig... 2500+, A7N8X-DX, BuffaloTech PC3200 (2x512), ...

S

stech4u

Member
just got my new rig setup. specs are:

AMD Barton 2500+ w/ TT Silent Boost & AS3
ASUS A7N8X-Deluxe
Buffalo Technology 1GB (2x512MB) 6 Layer PC3200 CL 2.5 32X8 (Winbond Module)
Antec SONATA w/ optional YS-Tech 120mm fan
80GB (2x40GB) Maxtor 7600rpm HDDs
Sapphire Atlantis ATI Radeon 9600pro 128MB BULK


currently, i have: 11x166 (1.833GHz).

to anyone (almost) w/ the same setup, if you could please run it over me step-by-step how to safely OC this bad boy to 2.2GHz (and beyond if possible). thanks in advance.
 
Set everything to "user define" in bios. Set FSB at 200, multi at 11, vcore 1.7V, vdimm, 2.7V, Cas 2.3.3.7.
Run memtest86 through a few loops then run prime95 overnight. If you get errors experiment with raising vcore and vdimm. If you don't get errors experiment with lowering vcore.
 
doh, seems like i need a floppy for memtest86... didn't know i'd be needing it so i just installed a cdrw. ok, i'ma pull my old floppy and try your suggestion. thanks.
 
oh sweet...let me know which one so i don't have to do the extra work putting in the floppy and taking it out later. i was also wondering, for the long run, i heard that asus now has a utility to flash bios w/o using a floppy.... is this true?
 
Wouldn't it be easier to make the FSB like 300(don't know if your mobo can do that) and multiply by less, or is they more strenuous on the processor then with less FSB and more multiplying.
 
Originally posted by: pelikan
Set everything to "user define" in bios. Set FSB at 200, multi at 11, vcore 1.7V, vdimm, 2.7V, Cas 2.3.3.7.
Run memtest86 through a few loops then run prime95 overnight. If you get errors experiment with raising vcore and vdimm. If you don't get errors experiment with lowering vcore.
Click to expand...

hey pel... would that cas setting work w/ the buffalo tech cl2.5 pc3200?
 
Originally posted by: stech4u
Originally posted by: pelikan
Set everything to "user define" in bios. Set FSB at 200, multi at 11, vcore 1.7V, vdimm, 2.7V, Cas 2.3.3.7.
Run memtest86 through a few loops then run prime95 overnight. If you get errors experiment with raising vcore and vdimm. If you don't get errors experiment with lowering vcore.
Click to expand...

hey pel... would that cas setting work w/ the buffalo tech cl2.5 pc3200?
Click to expand...

Yes, if your buffalo has Winbond CH-5 on it then 2-3-3-7 or 2-2-3-7.
 
this is what i got from newegg...

(2x) Buffalo Technology 512MB 6 Layer PC3200 DDR Memory Module CL 2.5 32X8 (Winbond Module), Part# DD4002-512 - OEM

is that CH-5? is there a util to check the specs of the RAM?

thanks in advance.
 
If you're gonna have a problem with Prime95, it'll usually show up in the first couple of hours. Like Pelikan, I usually let it run overnight, since I once had an issue that only showed up after 10 hours and change!
 
memtest86 was 100% ok.

i've copy&pasted my results (below) from prime95 for 200x11, 1.7V, 2.7Vdimm, Cas @ 2-3-3-7 ...temp at 41/51 (idle/load). what should i do next?

-------------------
[Sun Oct 12 07:00:34 2003]
Compare your results to other computers at http://www.mersenne.org/bench.htm
That web page also contains instructions on how your results can be included.

AMD Athlon(tm) XP 3200+
CPU speed: 2204.81 MHz
CPU features: RDTSC, CMOV, PREFETCH, MMX, SSE
L1 cache size: 64 KB
L2 cache size: 512 KB
L1 cache line size: 64 bytes
L2 cache line size: 64 bytes
L1 TLBS: 32
L2 TLBS: 256
Prime95 version 22.12, RdtscTiming=1
Best time for 256K FFT length: 16.470 ms.
Best time for 320K FFT length: 21.102 ms.
Best time for 384K FFT length: 26.723 ms.
Best time for 448K FFT length: 30.880 ms.
Best time for 512K FFT length: 33.481 ms.
Best time for 640K FFT length: 43.941 ms.
Best time for 768K FFT length: 54.203 ms.
Best time for 896K FFT length: 63.266 ms.
Best time for 1024K FFT length: 72.359 ms.
Best time for 1280K FFT length: 93.859 ms.
Best time for 1536K FFT length: 113.236 ms.
Best time for 1792K FFT length: 138.083 ms.
[Sun Oct 12 07:20:22 2003]
Self-test 1024K passed!
[Sun Oct 12 07:35:22 2003]
Self-test 8K passed!
[Sun Oct 12 07:50:22 2003]
Self-test 10K passed!
[Sun Oct 12 08:05:32 2003]
Self-test 896K passed!
[Sun Oct 12 08:20:45 2003]
Self-test 768K passed!
[Sun Oct 12 08:35:45 2003]
Self-test 12K passed!
[Sun Oct 12 08:50:45 2003]
Self-test 14K passed!
[Sun Oct 12 09:06:02 2003]
Self-test 640K passed!
[Sun Oct 12 09:21:07 2003]
Self-test 512K passed!
[Sun Oct 12 09:36:07 2003]
Self-test 16K passed!
[Sun Oct 12 09:51:07 2003]
Self-test 20K passed!
[Sun Oct 12 10:06:15 2003]
Self-test 448K passed!
[Sun Oct 12 10:21:25 2003]
Self-test 384K passed!
[Sun Oct 12 10:36:26 2003]
Self-test 24K passed!
[Sun Oct 12 10:51:27 2003]
Self-test 28K passed!
[Sun Oct 12 11:06:29 2003]
Self-test 320K passed!
[Sun Oct 12 11:21:35 2003]
Self-test 256K passed!
[Sun Oct 12 11:36:36 2003]
Self-test 32K passed!
[Sun Oct 12 11:51:36 2003]
Self-test 40K passed!
[Sun Oct 12 12:06:36 2003]
Self-test 224K passed!
[Sun Oct 12 12:21:40 2003]
Self-test 192K passed!
[Sun Oct 12 12:35:42 2003]
FATAL ERROR: Final result was 2666F07E, expected: B2095F04.
Hardware failure detected, consult stress.txt file.
 
You must log in or register to reply here.
Back
Top