Originally posted by: Angerisagift
Originally posted by: nullpointerus
FSB
-- Put CPU/RAM at stock, and raise FSB. Test with Prime95 Blend overnight.
-- If you get errors here, raise MCH/FSB voltage, and possibly RAM voltage and retest FSB
When you say this are you saying that I should raise the FSB to the speed I plan on using for my OC then set CPU and RAM to stock/normal voltages also with this I'm assuming it means I need to lower my multiplier get as close to stock CPU speed as possible?
because if I'm understanding this right I would need to setup for say 7x333 for 2331Mhz
or 8x333 for 2664Mhz, because I'm assuming we're trying to rule out the FSB of the board as being at fault, so we would want the other components to run at manufacturer rated settings to verify they aren't the cause.
, as a Technician that troubleshoots a variety of technical issues on a daily basis, I understand your school of thought, ruling out each component one by one as a possible point of failure. However I'm having some difficulty understanding how I'd setup the test for myself.
Yes, exactly. Set everything to stock except the single component to be tested, and then eliminate them one-by-one.
(Generally speaking, the problem with CPU o/c-ing is that everything is "linked" to the FSB: we do not have perfect flexibility, but we do have some flexibility.)
FSB --> test with CPU/RAM as close to (or under, if need be) stock clocks
RAM --> test with previously-tested FSB, but with CPU as close to stock clocks
CPU --> test with previously-tested FSB/RAM, and CPU at desired settings
So, with your rig, you've already picked a good target FSB. Your CPU should easily hit the desired speed. Your MB/RAM should be able to support the target FSB with little to no excess voltage and at factory recommended settings. That's ideal!
Your Target OC
FSB --> 333 mhz
RAM --> 333 x 2.4 = 799 mhz
CPU --> 333 x 9.0 = 2997 mhz
The only thing to remember when lowering your CPU multiplier is that you must disable C1E and EIST because they'll just automatically set it to its maximum.
Step 1: FSB
OC Test Settings #1
FSB --> 333 mhz ......................... <-- desired
RAM --> 333 x 2.4 = _800 mhz ..... <-- at or below stock
CPU --> 333 x 7.0 = 2331 mhz ..... <-- at or below stock
Now run Prime95 Blend overnight. This test mode will stress CPU, cache, and RAM evenly. Since the motherboard's northbridge (NB) coordinates transfers between cache and RAM, this will also test the NB. So we are verifying that the board operates correctly at 333 mhz.
If you get errors/lockups of any kind, raise MCH and FSB by 0.1v and retest at step 1.
When this testing passes without errors, proceed to step 2 w/ same settings, except we now raise RAM to target speed.
Step 2: RAM
OC Test Settings #2
FSB --> 333 mhz ......................... <-- desired,
tested OK
RAM --> 333 x 2.4 = _800 mhz ..... <-- desired
CPU --> 333 x 7.0 = 2331 mhz ..... <-- at or below stock
(The numbers happen to be the same as step #1, but that's just a coincidence.)
Now run Memtest86+ 2.00 overnight. This test mode will place most of the stress on RAM. it will catch most (but not all) errors in memory, due to either defective RAM or RAM being run at unsupported timings/clocks and/or with insufficient voltage.
If you get errors/lockups of any kind, raise VDIMM by 0.1v and retest at step 2.
When this testing passes without errors, proceed to step 3 w/ same settings, except we know raise CPU to target speed.
Step 3: CPU
OC Test Settings #3
FSB --> 333 mhz ......................... <-- desired,
tested OK
RAM --> 333 x 2.4 = _800 mhz ..... <-- desired,
tested OK
CPU --> 333 x 9.0 = 2997 mhz ..... <-- desired
Now run Prime95 Blend overnight. This test mode is a mixture of Small FFT (which tests heat) and Large FFT (which tests voltage), so it's perfect for overnight CPU testing of all fundamentally important CPU functions.
If you get errors/lockups of any kind, raise VCORE by a small amount (varies by board) and retest at step 3.
When this testing passes without errors, proceed to step 4 w/ same settings.
Step 4: Full System
Target OC Settings
FSB --> 333 mhz ......................... <-- desired,
tested OK
RAM --> 333 x 2.4 = _800 mhz ..... <-- desired,
tested OK
CPU --> 333 x 9.0 = 2997 mhz ..... <-- desired,
tested OK
(By now, all components have tested fine individually, and stressing all of them through multi-tasking should (in theory) (via step 4) produce no errors. But in practice, you can pass steps 1-3 with a given target OC and still have problems in step 4.)
Now run the Folding @ Home client constantly in the background for one week. If you get no errors or EUEs, you can be sure your o/c is *very* stable.
If not, then you must get expert advice diagnosing the errors. Once a particular problem is pinpointed, you must go back and retest at step 1, 2, or 3. You wouldn't have to do them all in a series *by this point*, so just try to fix FSB, RAM, or CPU settings individually and then retry step 4 to verify that your fix worked.
(For your particular OC and parts, a failure at step 4 almost certainly means you need a slight bump in VCORE -- nothing more.)