I could get my old AQXEA stable at just about 2.3 but cos of this crappy HyperX couldn't get it over 210FSB.
The moral of the story is buy Corsair
I could get my old AQXEA stable at just about 2.3 but cos of this crappy HyperX couldn't get it over 210FSB.
The moral of the story is buy Corsair
Knight 1: We are now no longer the Knights who say Ni.
Knight 2: NI.
Other Knights: Shh...
Knight 1: We are now the Knights who say..."Ekki-Ekki-Ekki-Ekki-PTANG. Zoom-Boing. Z'nourrwringmm.
Aren't the kt600 AGP/PCI busses locked anyway? I don't understand what the ballyhoo about overclocking the FSB is. Kt600 boards overclock FSB's decently, and it really isn't a big deal if things don't work out- you just bump your fsb back down. It seems a little paranoid not to fiddle with it at all.
Not had a KT600 so I couldn't say, I presumed from Turksters answers that they weren't locked as there wouldn't seem to be any other explanation.
Knight 1: We are now no longer the Knights who say Ni.
Knight 2: NI.
Other Knights: Shh...
Knight 1: We are now the Knights who say..."Ekki-Ekki-Ekki-Ekki-PTANG. Zoom-Boing. Z'nourrwringmm.
I belive they are locked, according to a legion hardware review.
Yeah I think they are locked in KT 600 boards. At the same time I do have problems with my soundcard if I push the FSB anything over 205Mhz. I presume it cant be an actual PCI problem but it is nearly certainly something with the mobo. The RAM can handle it and the CPU can handle it so I presume the mobo is having trouble.
Anyway I am not saying one shouldnt push the FSB beyond 200mhz its just it wouldnt be the first thing I would do. Get it up to 3200+ speeds with the FSB at 200 and if that is stable then try pushing the multiplier higher if that works then try pushing the FSB up. Thats the way I would do it.
Thanks for the replies, very insightful.
Currently having niggardly problems, dont know if its the mobo, hdd, soundcard or a combination of them.
Problem 1:
PC randomly locks up after heavy use(by that I mean after playing raven shield online for 45-60mins, plus browsing for a few hours).
I *think* it is soundcard related, but how could the soundcard lock the whole pc up and mean I have to turn power off at the PSU?
Problem 2:
After a cold start, it reads ram,cpu,drives fine, goes to next screen and I get a black screen with a slowly blinking underscore( _ ), does nothing.
Reboot, and it ALWAYS boots to windows fine.
Thinking its a hdd(although never have any other problems with them) or a mobo problem.
System:
2*512mb geil pc 433 golden dragon
athlon 2500(not overclocked)
soundblaster audigy 2 ZS
KT6 Delta-FIS2R
Sapphire radeon 9800(non pro) 128mb(not overclocked)
80gb maxtor
120gb samsung
460w enermax PSU
TT xaser III case.
Onboard sound disabled of course.
Any ideas?(have postponed getting a stable overclock until I work out these problems)
Update, left my PC running the GTR demo while I went to eat dinner.
Came back to a high pitched whine coming from the speakers, pc had locked up.
Turn off the PSU, and there is an audible THUMP from the speakers, as windows boots up, another THUMP(probably when initialising the sound card) and windows locks up again after soundcard loads.
I guess the simple way to figure it out is to take out the Audigy and try the onboard sound. I'm guessing it'll be fine if it's the soundcard thats borked and if thats the case then there is the option of RMA.
Knight 1: We are now no longer the Knights who say Ni.
Knight 2: NI.
Other Knights: Shh...
Knight 1: We are now the Knights who say..."Ekki-Ekki-Ekki-Ekki-PTANG. Zoom-Boing. Z'nourrwringmm.
Problem is it doesnt happen that regularly, sometimes it can be a week, sometimes 2 hours
Just ran prime95 for 2 hours, this was what mbm5 reported at the end.
[edit] **** just realised it didnt screenshot mbm's voltage reports...
was
1.67v vcore
3.31v +3.3
5.03v +5
12.04v +12
11.94v +12
5.3 +5
Yes it's usually good advice to take the PC as far as it will go and find out where it begins to get unstable then knock it back a tad for piece of mind and allow a little headroom for those hotter summer days - I always found 200FSB to be absolutely rock-solid on NF2's.Originally Posted by turkster
Sounds like it could be memory - set the timings to something less aggressive and if that doesn't fix it ... try taking one of the DIMMs out and running with half the memory to see if it's rock solid with one and not the other.Originally Posted by KDH
thanks ill try thatOriginally Posted by BlackSheep
There are currently 1 users browsing this thread. (0 members and 1 guests)