Help me OC my q6600!

Okay, fair enough! Pop quiz:

  1. What does the big long beep mean? (HINT: you will find the answer to that question in your motherboard manual under beepcodes).
  2. If you manage to get your BIOS to accept the newly entered FSB, how will you test your components to make sure that the new setting is a stable setting? (NOTE: if you don't test your changes then your computer could be unstable. Therefore, when you least expect it your computer could crash and this might happen right before you're about to win your game.)

Remember: if overclocking were easy then everyone would buy the lesser expensive stuff and overclock it. There are no gaurantees when overclocking: 30 people can have the same stuff as you but your results may be diametrically different than theirs or your stuff might die long before theirs does. Therefore, you need to understand how to address the many obstacles you'll face when attempting to overclock your computer.
 
Everybody is wrong. Period. It's not that easy, and there's a good reason for it too. You have to understand that what ever change you do, there will be a side effect, and simply raising the FSB sky high and leaving the vCore at Auto could soon leave you with a hot piece of expensive garbage. Therefore, as mentioned above, read a few howto's (believe me, there's a lot of them out there). Only a few months ago, I was a complete noob in the OC department, but a lot of reading around has given me so much more knowledge about what I'm doing, so I'm starting to get fairly confident in the BIOS settings, and that's when the fun starts.

Now, as for the Linked/Unlinked-problem. Linking the DRAM:FSB-ratio makes the memory frequency increase automatically when the FSB increases. I prefer to run the memory unlinked, as I can clock the two frequencies independently.
 
ok a friend of mine told me to bump the voltage up by .2 when i move the fsb to 1333 because the beep is from the system not being stable and i need to try moving voltage up
 
If you depend on your computer for anything important then I would respectfully and strongly advise you against overclocking. Should you choose to ignore my advice then you must be prepared not only for a system crash in the midst of an important project, but also for the loss of work incurred from that crash.

A perfectly good computer with stock configurations can fail or crash at any time for a myriad of reasons, so there is little reason to believe that those chances aren't increased when overclocking -- especially when overclocking foolishly.

Board of Dreams.

(whispering)

"If you read the stickies, it'll overclock."​

Again, just my ten cents.
 
Back
Top