No, in the BIOS my FSB is raised, but when I boot up the computer that splash screen shows no change. It stays 333 in the BIOS, however. (dxdiag.exe shows nothing different.)
Someone has suggested automatically changing my RAM timings.
http://i.imgur.com/cM4AK.jpg
Is that "Standard" box where I change them? I've been told to change them to 5-5-5-15. What goes in the box below it?
Ram latency has nothing to do with it. I know it sounds stupid but I have to ask, your using "save and exit" when your exiting the bios right?
(06-22-2010, 08:51 AM)NaturalViolence Wrote: [ -> ]Ram latency has nothing to do with it. I know it sounds stupid but I have to ask, your using "save and exit" when your exiting the bios right?
Yes. And if RAM latency has nothing to do with it, what is keeping my computer from overclocking?
On the startup splash screen, should the change in FSB speed be shown properly? Because it isn't, and that would seem to imply that something is throttling the speed down outside of Windows.
win7 x64 the fastest you will get its the best.
take out your CMOS battery, hold the powerbutton for 10 secs, put it back in, that will reset your bios. after doing that try to raise the FSB
Good idea. The BIOS isn't making the change if it's not showing up during post, it has nothing to do with the os.
After some procrastination, I took out the battery. A lot of settings were changed, but everything looks fine in my BIOS. But now, when I change the FSB, after my PC resets it doesn't boot, and I have to wait for it to reset itself and turn that feature off.
What is wrong NOW?
that happens ONLY when change the FSB?
maybe could be intel speedstep?
Nope, speedstep doesn't work like that. It seems like for one reason or another your system is simple not capable of running the cpu past the stock speed. It sounds like before the bios was preventing the change in fsb to maintain stability, now that it's working the cpu is unstable and forcing it to reset the cmos. This is exactly what happens to me if I try to push my cpu to high (in my case I'm limited by my motherboard not temperature or power).
Edit: I looked back through the thread to try and see any potential problems and noticed this
Quote:If I was using a stock cooler, it would overclock, overheat, and turn off. But it never overclocks.
Actually it would do exactly what your describing now. You would turn on the system, nothing would happen and it would reset the cmos the next time you turned it on to prevent further damage. Now did you buy an aftermarket air cooler and put thermal grease on or did you just attach a bigger fan to your stock cooler? Because when I was reading through the thread it sounded like you just attached a fan to your stock cooler. Maybe you meant to say something different.
The fan is attached to the CPU with thermal grease.
NaturalViolence, for all the help you've given, you haven't found the issue. It is the memory multiplier - it is set too high to begin overclocking at.