Originally posted by: GNY
Thanks Xeon I will probably go for the Best OCZ I can lay my hands on !!!
Originally posted by: GNY
Thanks for the heads up Xeon, I will call them on Monday and give them my specs and see what they recommend. 1 other thing Xeon, I"m thinking about buying the Heatsink you also recommended, What is the best Thermol compond to use on this puppy.
Originally posted by: GNY
Thanks for the heads up Xeon, I will call them on Monday and give them my specs and see what they recommend. 1 other thing Xeon, I"m thinking about buying the Heatsink you also recommended, What is the best Thermol compond to use on this puppy.
Originally posted by: computer
So Michael, we are still waiting on what fixed the Memtest problems! What was it, what did you do to fix them?
I got rid of them on mine by DISABLING the Promise controller. With in enabled, over 25,000 (TWENTY FIVE THOUSAND) error on the M$ RAM diagnostics and a bunch on Memtest. With it disabled, NO errors on the M$ test on the first pass and maybe one or two there after. Same with Memtest.
GNY, Nanotherm PCM+ is currently the best. See my post on it on this thread. Do a "find" on ....PCM+......not on this page or the last, but starting from the 3rd page back then go back. It's there somewhere.
Originally posted by: computer
(DAMN SCREWED UP WEBSITE!!)
?????????????????????????????????? 😕 :disgust: :frown:As for the Memtest issue and how I solved it, I can't reveal that at the moment, you'll understand why real soon, but I will say, It was a much different problem than the one you were having.
Originally posted by: jhites
Set the vdimm to 2.85v and leave it there. Set the Performance Mode under the Jumper Free Config to Standard. Set the vcore on the cpu to 1.5875v and reboot using the MemTest floppy to check stability after above settings. If you get errors, go into the chipset settings and change the Ras to Cas Delay to 3. Reboot to Memtest and check it again. You will have to play with the fsb settings and the memory timings to find your sweet spot. All cpu's and memory modules are different, so it may take you a while to achieve your maximum stable settings.Originally posted by: CannibalisticH0b0
Timings: 2-2-2-5
vdimm, tried a few, but none made a difference.
Originally posted by: jhites
I did some a while back when I had first put thisOriginally posted by: Xeon
PCMark2002 Scores
CPU score: 7630
Memory score: 8641
HDD score: 1099
If you have some scores please post them.
system together that is in my sig.
CPU Score . . . . . 7882 . . . 8702
Memory Score . 10462 . . 10142
HDD Score . . . . . 1146 . . . 1191
The first set was running 3110Mhz @ DDR490 1:1 ratio and
the second set was running 3430Mhz @ DDR432 5:4 ratio.
FutureMark Link
Take it off the AI Overclock and use manual settings for cpu and memory. You will most likely get better results and better overall performance.Oriiginally posted by: sillious
My question is: the mobo is 800MHz FSB, but the FSB showing here is way lower. It is correct, if so, how can I raise the FSB? And could someone also say by the result, can I go any higher based on my configuration? I can't set it to 30% oc, it crashes. Another thing is the system has DX 9.1a, but it's showing 8.1, is it because PCMark2002 is older, or is it norm?
Wow! Huge difference. Mine with the BIOS set to 1.585v in bios will show up to 1.60 in XP idle but will drop to between 1.500-1.525 under full load. These boards do have a pretty wide fluctuation range for most ppl.Originally posted by: shoman94
Yea...might be a good idea...
One thing I did notice though is the board overvolts the vcore up to 1.600 then at 1.625 it under volts..... 1.650 and 1.600 in bios are the same once booted into windows...load and Idle.....
My board is set at 1.585 in bios...in XP idle is 1.65 and full load brings it down as low as 1.555..... THIS SUCKS. How can I get a stable overclock with those fluctuations????
Originally posted by: CannibalisticH0b0
Originally posted by: jhites
Set the vdimm to 2.85v and leave it there. Set the Performance Mode under the Jumper Free Config to Standard. Set the vcore on the cpu to 1.5875v and reboot using the MemTest floppy to check stability after above settings. If you get errors, go into the chipset settings and change the Ras to Cas Delay to 3. Reboot to Memtest and check it again. You will have to play with the fsb settings and the memory timings to find your sweet spot. All cpu's and memory modules are different, so it may take you a while to achieve your maximum stable settings.Originally posted by: CannibalisticH0b0
Timings: 2-2-2-5
vdimm, tried a few, but none made a difference.
Hmm... well this sure is strange. I finally got around to doing this, but except for 2-2-2-5 @ 200MHz with PAT enabled, they all froze either @ 56% or 98%... Then, I did 2-2-3-5 @ 217MHz with PAT enabled, and that got like 135 errors, and then froze, but to my surprise, Windows actually managed to boot with this. Also, the 3DMark03 score improved a bit! I dunno whether I should keep this, go back to 2-2-2-5 PAT 200MHz (since that's nice and stable and has no errors with MemTest and doesn't freeze while running the program), or keep trying different timings... Suggestions? The timings that have frozen in Memtest or just don't boot up in Windows without the comp restarting right away are:
2-2-2-5 w/o PAT @ 217MHz
2-2-2-5 w/ PAT @ 217MHz
2-2-3-5 w/o PAT @ 217MHz
2-3-3-7 w/o PAT @ 217MHz