Gremlins won't let me overclock.

  • Thread starter Thread starter JHC
  • Start date Start date

JHC

JHC

JHC

Associate
Joined
29 Jan 2010
Posts
90
Location
in bed.
Helmet-Decal-US-Medic.jpg


The story starts in the bad old days. I was bumping my FSB up one at a time, aiming for 3.7/3.75. (On a Q6600 which was Prime95-ing for 8 hours at a time at 3.4ish without missing a beat btw, on a GA-965P-DS3)

Posted fine at 3.68, into Windows, all lovely. Decent temps even at load, etc. Thinking 3.7 should be within my grasp, I rebooted and set to 3.69. POSTed fine, but Windows froze on the startup screen. So I turned off, and back on again. It gave a nice long beep, probably 2 or 3 seconds and rebooted itself.

:mad:

Upon subsequent POST, it was back at stock speeds. Works absolutely fine, as you could tell if you were here - I'm using it. (phew, might I add.)

So I go to try an overclock again. Whatever settings I enter are over-ridden every time and it POSTs at stock 2.4. Yet when I got back in to the BIOS, all the overclocked settings are still there. :confused:

What terrible mistake have I made, how badly will I be mocked, and is there anything I can do about it? Tried re-flashing the BIOS to no avail.

If I can stop banging my head off the wall soon I might sustain consciousness. :)
 
Clearing the CMOS would be the obvious answer BUT my old (old:p) Gigabyte EP45-DS3R did this 2 or 3 times. Removing and re-seating the RAM was the only way to cure it. I even updated the BIOS as you have done which didn't work.
 
Don't know why I didn't think of a CMOS reset. I'll try both things and report back. Ta. :)
 
I did both at the same time, so I couldn't tell you. :( I'll remember for next time!

Back in Windows at 3.69 now. :D

Edit: Stability is a different matter, however, and yet to be determined. lol
 
Make that 3.6 still.

Changing the subject slightly, I think my cack RAM is holding me back, as it just isn't stable at anything over 400fsb, even if it will POST.

Cheers again, by the way. :)
 
JHC said:
Make that 3.6 still.

Changing the subject slightly, I think my cack RAM is holding me back, as it just isn't stable at anything over 400fsb, even if it will POST.

Cheers again, by the way. :)
Click to expand...

if you want to test that theory then lower you CPU multi to, say, 7 and then try a higher FSB. That will show you if it is the RAM/motherboard OR if if is the CPU. If you suddenly find you can run at 450x7 (3150mhz) then it will mean that it was you CPU that was the limit. On the other hand, if you still have the same FSB limit, then it will mean it's either your RAM or maybe the motherbord.
 
Tried that. It's unstable as hell over 404fsb. POSTS but no Windows, no POST, half a POST. Does not want to play.

I've got a pair of Corsair XMS2 512 800MHz and a single Elixir 1gb 800MHz. Got to be the single stick holding me up hasn't it?
 
Maybe. Try using just the corsair. The important bit is to make sure you have the correct timings and VDIMM set in the BIOS. If you leave it all to AUTO, especially the VDIMM then you will be running the RAM at 1.8v (DDR2 default) when your RAM could be meant to be run at 2.1v for example. It would also 'auto' slacker timings to allow this to work but it still means that you are both undervolting and attempting to overclock your RAM.
 
Lower the FSB to stable and up the RAM multiplier, is what I'd do, to make sure it's the RAM not the mobo. Using just the Corsair is also a decent plan :)
 
You must log in or register to reply here.
Back
Top Bottom