- Jan 16, 2001
- 31,528
- 3
- 76
Originally posted by: TerryMathews
Originally posted by: MichaelD
I'm overclocking and running a 150FSB. This doesn't have an effect b/c the NCCH-DL has a working AGP/PCI lock. CPU-Z shows AGP/PCI speeds of 66.6MHz and 33.3MHz exactly, so that's not it.
I cannot run a 200FSB b/c these particular Xeons can't take it. The way it works is that for a split second, the bios powers up the CPUs at DEFAULT multiplier (16x) times whatever FSB you've set. THEN pending a successful boot, it lowers/raises speeds to whatever you've set in the bios.
I cannot post at 12x200 which is the same 2.40GHz I'm running now b/c of the above stated problem.![]()
Did you swap around the CPUs? I've got one that can POST at 16x200 and one that can't. As long as the one that can is in CPU0, you're golden.
Also, did you make sure you were using the 1:1 memory setting and not the faster one? When you jumper and POST at 133FSB, you need to set the memory to 333 to get the proper 1:1 setting at 200. ASUS = stupid BIOS when it comes to that.
And yes, just because you've utilized a PCI lock doesn't mean it's not adversely affecting performance. Running the bus at 66.6MHz and the FSB at 150MHz means they're no longer synchronized - for large transfers the processor is going to have to wait for a 66.6MHz clock cycle to transmit data to/from the SCSI card. It'd be more of a latency issue than a transfer bandwidth one - but it still might be causing some other gremlins.
If you really want to check if it's a hardware problem or software one, download a Knoppix LiveCD that supports your SCSI card and try one of the Linux HD benchmarking programs.
Hmm. I AM running a 4:5 mem/sys ratio. Let me see if I can toy aroudn in the bios w/o killing it. BRB.
*edit*
Well, I changed the memory setting in the bios from Auto to DDR333. No diff. I may try for 200FSB again.