Dolphin, the GameCube and Wii emulator - Forums

Full Version: Should I upgrade to Windows 7?
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2 3 4 5
Well I can certainly explain it. Do you want the complex explanation or the simple explanation?

I need to know more details about your system though. I already know what cpu your using, q6600. What I don't know is what motherboard, memory, air cooler, thermal paste/grease, power supply, case. What software are you using for stress testing and temp monitoring?
(06-20-2010, 10:27 AM)NaturalViolence Wrote: [ -> ]Well I can certainly explain it. Do you want the complex explanation or the simple explanation?

I need to know more details about your system though. I already know what cpu your using, q6600. What I don't know is what motherboard, memory, air cooler, thermal paste/grease, power supply, case. What software are you using for stress testing and temp monitoring?

(Starting backwards) To be honest, I am using CPU-Z. For stress testing, I am unsure what you mean, but if I changed my RAM timings again I'd run, whats it called, Mem+ or whatever? if the overclocking works, I'd probably download one of those other programs. But so far it hasn't so I had no need to.

Motherboard: Gigabyte GA-EP35-DS3R
Memory: Corsair Dominator 4GB (2x) 240-Pin DDR2 SDRAM 1066
PSU: PC Power and Cooling S61EPS 610W Continuous @ 40°C

I believe it was thermal paste. It came with the Q6600. This is my case:
http://www.newegg.com/Product/Product.aspx?Item=N82E16811119068&cm_re=centurion_5-_-11-119-068-_-Product

I will appreciate any help you can give me. Someone said to manually set my RAM timings and I am good to go.
There are guides that are thorough because they need to be. If you aren't willing to read up on it then ocing is not for you because you can fry your memory or cpu. Also, I highly don't recommend software base ocing like what you are leaning towards. Good luck. He has a Intel p35 based mobo NaturalViolence.
(06-20-2010, 04:08 PM)obscured Wrote: [ -> ]There are guides that are thorough because they need to be. If you aren't willing to read up on it then ocing is not for you because you can fry your memory or cpu. Also, I highly don't recommend software base ocing like what you are leaning towards. Good luck. He has a Intel p35 based mobo NaturalViolence.

Where on Earth did you get that I was going towards Software-based OCing? Was it all the screen shots of my BIOS?
I miss understood the mem+ as a memory settings program instead of a error checker I guess. I would use linepack or prime to test stability instead.
Mem+ is Memtest86+. It's a program that you boot into. And it checks the RAM for stability. It is very important.
I know what memtest86 is I've oced for years.
Alright enough arguing. Now you didn't list your air cooler. Are you trying to overclock on stock cooling!?!? Because if so that is your problem right there.
(06-21-2010, 05:08 AM)NaturalViolence Wrote: [ -> ]Alright enough arguing. Now you didn't list your air cooler. Are you trying to overclock on stock cooling!?!? Because if so that is your problem right there.

No I am not trying to overclock on stock cooling I have a massive fan attached to it. But none of that matters. See, I change the FSB speed, I go into Windows, nothing changes. Nothing ever changes. There's no difference in speed.

If I was using a stock cooler, it would overclock, overheat, and turn off. But it never overclocks.
Wait wait wait. Ok clearly I didn't understand your problem. Are you saying that when you raise your fsb in the bios the bios says the proper number but in your os it still reads 2.4 GHz? I'm starting to wonder if your having the same problem I had/have. You see I have my q6600 running at 3.2 GHz 1422 MHz FSB but in cpu-z it still says the core clock is 3.2 GHz. But it's clearly not since every other program including dxdiag.exe and windows sys.exe say it's running at 3.2 GHz and the massive speedup I noticed in some programs clearly showed that it was indeed running at 3.2 GHz. So if your problem is just that cpu-z shows it still running at 2.4 GHz try running dxdiag (just go to run and type dxdiag).
Pages: 1 2 3 4 5