Socket 754 Sempron 3100+ Overclocking *large image warning*

Associate
Joined
31 Aug 2006
Posts
423
Location
Stafford
hey im trying to overclock my socket 754 sempron 3100+, a possibly fruitless endevour but regardless i have stumbled upon a problem:

when increasing the FSB by 5MHz the ram speed obviously is going up but i cant get it back down to its original speed, heres a picture.

cmosconfighe1.gif
 
Last edited:
interesting, well thanks for that information.

it isnt running at that though, it would be if i saved the settings, but as you can see from the picture its default is 333MHz
 
Ive brung the HT multiplier down to 3 from 4, and changed the RAM devider to 2/1.33, this brings the RAM down to its original speed at the default FSB which is 333MHz... everything seems stable, the cpus operating quite a bit hotter now though
 
Last edited:
I tried setting the RAM divider to 2/2 but PC wouldn't soft reboot from BIOS, I'd be forced to reset it manually and the RAM divider would've defaulted back to its original setting. Now I've got the RAM divider operating below its default setting, and the HT multiplier as well, advice?
 
Just noticed I'm receiving a sort of electronic interfearance noise through my headset when a lot of SFX are coming from WoW, this almost definitely has something to do with the overclock, as im using a PCI sound card. :/
 
I ran SP2004 for 9 hours and picked up no errors, what do you reckon to a 3100+ sempron at 47c average under load?
 
I increased the FSB and changed the RAM divider so the RAM speed came to 400MHz, I think I lowered the HT multiplier to x3 aswell. When I booted up it went through the detecting IDE drives etc, then came to this screen which I thought was really bizzare.

dsc00031xw2.jpg
 
I'll just leave it at 250mhz fsb and 2/1.33 ram divider, everything else is at default. maybe i just need to increase voltage to either cpu or ram to make it work, dunno.
 
I need to keep posting, else the thread falls off the first page and no one sees it ><

But I will heed your advice!
 
So I increased the RAM divider to 2:2, left the FSB on default (200MHz), and increased the RAM voltage by +0.1v, which has equated to a successful boot into Windows. Without the voltage increase the PC would not soft reboot after saving the settings in BIOS.

What can I do now, reduce the RAM divider and increase the FSB untill the RAM speed is as close to 400MHz as possible? Or does it have to be dead on 400MHz?

In regards to PCI clock speed, I found only this - which I have disabled, to no discernable effect:
dsc00037ot8.gif


In response to steve
have you tried loosening your timings
I don't know how :( . Is it something to do with these:
dsc00038rz2.gif

???

nearly an hour later: playing Eve Online with x2 clients running, suddenly without warning the display signal from my graphics card to the monitor dissapears (happened before but only on initial bootup which required me to reseat the RAM). I knew it was just the signal that went because my music n everything was still going - this has not happened in windows before, and resetting the machine sorted it out..
 
Last edited:
I'd really appreciate some feedback from someone familiar with overclocking on a A64 SKT754 GA-K8NS mobo.

I'm concerned whether or not the RAM and FSB speed have to be a specific or even number. I've just booted up on 241FSB on a RAM divider of 2/1.66, giving 400MHz RAM speed. I'll be leaving SP2004 running over night and see how it goes. Screenshot of relevant information enclosed:


info4ocersxp0.gif



One last thing, I don't think SpeedFan is reporting the correct temps. The BIOS CPU temp is around 30c idle whereas SpeedFan reports around 25c idle, so chances are the CPU is atleast 5 degrees hotter than what SpeedFan is saying it is :/

ANOTHER THING (can't sleep), shall I assume 0.13um means 130nm? If so my chip really is quite outdated, makes me believe my upgrade will be even more justified.. mMMmMmM 65nm goodness.
 
Last edited:
Okay so here's how things look now:
cpuz141206yw4.gif
cpuz1412062af9.gif


Haven't stress tested the current settings in SP2004 yet, but I successfully ran it for 12 hours on the previous settings with no errors:
stable12hrsse2.gif
 
Back
Top Bottom