having trouble overclocking

Gaygle · 26 Mar 2006 at 17:20

ok, i have set my memclock/CPU ratio to 1:1 (DDR 200), but now that i have overclocked it, in CPU-z it is only showing my memory as running at 117mhz when it should be at 235mhz. but there was another option in the bios that said memclock/CPU ratio (2:1) (DDR 400).....is this the option i want instead? I got scared before cos when i did this, it wouldn't boot into windows and instead came up with "Windows has detected a corruption in Windows/system32/system, try repairing windows with the windows cd". and i was like NOOOO!!!, but i quickly threw everythin back to stock and it was ok, but now i'm scared to do it agian

Raikiri · 26 Mar 2006 at 17:23

How about you try something inbetween?

Most boards would consider 1:1 to be 200mhz (400ddr) but yours seems to be reading it as the DDR value. Is there a 5/3 option? that should run your ram at 166mhz and a little higher with the overclock.

Gaygle · 26 Mar 2006 at 17:30

ok, so does it matter more is the CPU reaches higher FSB or the memory? why do ppl run their RAM with a 1:1 ratio? I've got 1GB corsair XMS pro, so its more than capable of being overclocked quite a bit

Raikiri · 26 Mar 2006 at 17:36

1:1 offers a slight increase in performance (2:1 on yours)

Edit: This an AMD or P4? if it is p4 keeping the memory matching the CPU's FSB makes quite a large diference compared to AMD.

Gaygle · 26 Mar 2006 at 17:49

cheers for the speedy responses. ok, the CPU/RAM ratio is now at DDR333 (166mhz), but now, the stupid ram has changed its clocks to:

CAS 3.0
RAS-CAS 3
RAS PRECHARGE - 3
Tras - 8
TRC - 12

what can i do now? do i define my own timings?

Gaygle · 26 Mar 2006 at 17:59

ok i set the clocks to 2.5,3,3,7 but what i really need to know is how do i corrupt the boot up by doing this? cos thats one thing i'm not gona go through agian. i dont even know how i did it before.

thanks

Raikiri · 26 Mar 2006 at 18:03

If the memory is too clocked too high it will be unstable and the data it is storing will be corrupted... either that or you have not turned the PCI lock on and your HDs were getting corrupted.

Gaygle · 26 Mar 2006 at 19:14

ok, yeah it was because the memory was clocked too high. but then i do i know what my memory max's out at, if its gona corrupt the boot files when it does?

thanks

saintly · 27 Mar 2006 at 13:09

boot your overclock into memtest?

You don't need to go anywhere near XP then.