- Joined
- Mar 8, 2004
- Location
- Canada, eh?
Excuse my CS l33t talk. I am an idiot.
At any rate, I've basically set myself up with a nice puter, after some earning of money and whatnot.
Specs can be found in this nice sig image I haven't bothered to put in my profile here yet:
So as you can see, I've got an unlocked 2500+ Barton, which I've currently O/Ced through multis to 3200+ speed.
NOW, the problem I am having is thus: I cannot get the FSB up from 166. Regardless of voltages or memory timings or whathaveyou, I cannot get the FSB up. It's like its locked, which is friggen weird.
I have contacted Giga-Byte Tech Support, and have learned that it's not the board's fault, supposedly.
Let me run you through what happens whenever I try this. First, I'll ramp the vcore up some, to 1.7 or 1.8, turn off the CPU Temperature Ramping "feature" (which, btw, is not the cause of this, but I don't want the damn thing to shut itself off if it thinks my temps are too high), set multi to like 11, and FSB to 200. Exit CMOS. Wait, 1, 2, 3, two little clicking sounds coming from PC speaker (I guess... I don't think motherboards make noise...) and then screen comes on (note also that this is like 5 seconds later than it would usually be...). I now apparently have an Athlon XP at 1100MHz. Weird. Basically, it ramps the CPU down to 100x11 whenever the FSB is above 166. It hits 166 fine, btw.
Alright. So, basically what I want to know is what the hell is wrong with this damn thing? I have absolutely no indication whatsoever that I am doing anything wrong (right? right? ) and so I am thus completely stumped.
Oh, and as far as temps go, O/Ced right now on multis, as I am, I'm getting about 39C idle, 41-43C loaded.
Any help would be hugely, greatly appreciated.
At any rate, I've basically set myself up with a nice puter, after some earning of money and whatnot.
Specs can be found in this nice sig image I haven't bothered to put in my profile here yet:
So as you can see, I've got an unlocked 2500+ Barton, which I've currently O/Ced through multis to 3200+ speed.
NOW, the problem I am having is thus: I cannot get the FSB up from 166. Regardless of voltages or memory timings or whathaveyou, I cannot get the FSB up. It's like its locked, which is friggen weird.
I have contacted Giga-Byte Tech Support, and have learned that it's not the board's fault, supposedly.
Let me run you through what happens whenever I try this. First, I'll ramp the vcore up some, to 1.7 or 1.8, turn off the CPU Temperature Ramping "feature" (which, btw, is not the cause of this, but I don't want the damn thing to shut itself off if it thinks my temps are too high), set multi to like 11, and FSB to 200. Exit CMOS. Wait, 1, 2, 3, two little clicking sounds coming from PC speaker (I guess... I don't think motherboards make noise...) and then screen comes on (note also that this is like 5 seconds later than it would usually be...). I now apparently have an Athlon XP at 1100MHz. Weird. Basically, it ramps the CPU down to 100x11 whenever the FSB is above 166. It hits 166 fine, btw.
Alright. So, basically what I want to know is what the hell is wrong with this damn thing? I have absolutely no indication whatsoever that I am doing anything wrong (right? right? ) and so I am thus completely stumped.
Oh, and as far as temps go, O/Ced right now on multis, as I am, I'm getting about 39C idle, 41-43C loaded.
Any help would be hugely, greatly appreciated.