Sign-in / Sign-up
Your question

Ram problem after CPU OC

Tags:
  • RAM
  • CPUs
  • Overclocking
Last response: in Overclocking
January 6, 2011 9:01:59 PM

I was getting a score of 930 in the overall mem test in passmark with a Phenom II 955 BE @ stock and G skill DDR3 7-7-7-21, I set the RAM timings manually in BIOS.

Now I increased the CPU multiplier to x4.5 from x4 to get 3.6Ghz and now I'm getting a score of about 230 in passmark. The system starts up slower and programs start slower too.

I tried to increase the voltages a little to see if there was a problem but that didn't help. I'm new to OCing so does anyone know what could be wrong?

More about : ram problem cpu

January 6, 2011 10:15:11 PM

multi should be at 18 - 200 * 18 = 3600
m
0
l
January 8, 2011 5:25:02 PM

r-sky said:
multi should be at 18 - 200 * 18 = 3600


18? I dont get it. I set the CPU multiplier to x4.5 from its default x4 and I get a speed of 3.6Ghz, but thats not the problem, read the OP
m
0
l
Related resources
January 11, 2011 4:45:56 AM

ngoing001 said:
18? I dont get it. I set the CPU multiplier to x4.5 from its default x4 and I get a speed of 3.6Ghz, but thats not the problem, read the OP



I think his point is that when you set the multiplier high and the FSB low, you get increased stability vs what you currently have. In my experience, it is always better to have the multiplier as high as you can, but then mine is limited while your's effectively isn't.

Setting your multiplier higher, at the suggested setting of 18x with an FSB speed of 200mhz should eliminate your ram from the equation.

Raising the FSB ultimately affects the RAM timings due to a ratio of sorts, which results in errors that can cause your system to act anomalously.
m
0
l
January 12, 2011 10:07:42 PM

Well, I found my problem. I thought x4 was auto, and in CPU-Z when I had it at x4 it was showing 800MHz under core speed so I thought that made sense since 800 x 4 (number of cores in my CPU) = 3200GHz. Well it turns out I ran some other programs and found out my whole CPU was only running at 800Mhz lol, thats why it was performing so badly.
m
0
l
January 13, 2011 3:04:14 AM

Yup, that can happen. I'm glad you figured it out.
m
0
l