Originally posted by: Kougar
Just how many people are interested in a Gigabyte overclocking how-to article? I'm not trying to be rude but it looks like I could spend days just trying to help people... if there is enough interest I can look into getting one written up, but it wouldn't happen overnight as it would be indepth and published on a website. Any thoughts? Would having to wait for the article kill the interest?
Originally posted by: Kougar
... I'm not trying to be rude but it looks like I could spend days just trying to help people... if there is enough interest I can look into getting one written up, but it wouldn't happen overnight ...
Originally posted by: mtnboydl
anyone on the RAM question? (see above)
Originally posted by: drakore
Phhh overclocking the gigabyte boards is easy.... don't forget u need to hit CTRL+F1 in the main bios screen to unlock the memory options...
Just set your divider to 2.00 (aka 1:1). keep the multiplier at the highest setting, ramp fsb by 5 mhz increments. Til u can't boot. It will then reset itself to the last known fsb. run windows... if unstable (which is should be) add voltage in smallest increments. Assuming you are using a C2D. add until u get til about 1.4v ish.. if still unstable then start decreasing the fsb slowly until it is. Then tighted ram timings, mainly the CAS timing. Add voltage if needed.
Yes i know this guide sucks and is semi backwards, but whatever if someone looking for a small overclock, this will get the job done.
Originally posted by: drakore
Phhh overclocking the gigabyte boards is easy.... don't forget u need to hit CTRL+F1 in the main bios screen to unlock the memory options...
Just set your divider to 2.00 (aka 1:1). keep the multiplier at the highest setting, ramp fsb by 5 mhz increments. Til u can't boot.
Yes i know this guide sucks and is semi backwards, but whatever if someone looking for a small overclock, this will get the job done.
Originally posted by: adrunkgerbil
Hi guys, I just put my new rig together tonight. GA-P35-DS3R + E6320. I want to overclock a wee bit, but my main goal is probably to get it to 1:1 so it's stable. Can anyone point me in the right direction or shoot me PM?
Any reason why it's only recognizing 3.5 gigs of ram?
Originally posted by: TheBeagle
I recently installed one of the new Zalman 8700 coolers on a GA-G33M-DS2R board. I had to nip a few fins off the NB heatsink on the side closest to the CPU socket (no big deal, and very easy to do), and that 8700 cooler then fit like a charm.
Originally posted by: Rebel50
Thanks for the info Kougar - I did have some suspicions about the RAM - turns out that the Corsair Ram I have actually uses ProMos 667 Mhz chips that overclock to 800 Mhz, so they sell them as PC6400 chips. Mine work OK at 900 Mhz 5 5 5 18 at 2.1V.
I hear that DDR2 RAM prices are going up again soon, so I might invest in some better quality DDR2 800 sticks.
I will update the bios as well, just to see if that helps.
Cheers
Good Evening Everyone,
I believe that I have some "Good News" to share with you with regard to my continuing problems with bootup on the N680i board. I took some very good advice from our colleague Mr. Gary, and wiped out the CMOS settings, and then rebooted. Then I set the "Optimized Defaults" (which was apparently a mistake), and then shut down, rebooted, and set all the BIOS settings as per usual. No luck with that routine, since I still got the constant reboots, and the message:
"Building DMI pool .............................................Flash ROM Protected"
So I decided to take another look at what I had done, and wiped out the CMOS settings again, rebooted, and this time on bootup I utilized the "Fail-Safe Defaults," and then went directly into the BIOS flash utility (Q-Flash), via the F8 key. In the Q-Flash, I changed the setting for "retain DMI settings" to disable, and also loaded the default CMOS settings from within Q-Flash. I then exited Q-Flash (F10 key) and shut down. On reboot, I went into the Setup, and set all the BIOS values to their full performance settings (as before), EXCEPT that I changed the value for "Flash ROM Protection" from "Auto" to "Enable."
When I rebooted at 384 x 9 (E6850), with auto voltages, the machine booted right up, with no reboot. After Vista 64 loaded, I shut it down cold, and then started it up again. It started again, went through the POST, no hesitation, and went right into Vista again. This sure looks like the best solution I've seen so far, and this PC is running quite well at 3.45 GHz at auto voltages, and the memory set at 5-5-5-15-2T. If this holds, it will be a miracle.
I've been racking my brain on what might be causing the reboot problem, and I think it has something to do with some DMI values that were being retained in the CMOS, and because I had the "Flash ROM Protection" set to Auto instead of Enable, that allowed those settings to be written to the BIOS during bootup, thus messing up the boot process. Now that's only my humble diagnosis of this recurring plague, but it seems the most logical answer. Many thanks to Mr. Gary for his suggestion about clearing the CMOS, etc., since that got me thinking in the right direction about the other steps that I needed to take.
I hope the foregoing may assist some of the other Forum members (and others) who have had that same type of problem. Take care and have a nice evening. TheBeagle
I shutdown and restarted my rig last evening about a dozen times, and each time it booted up without any of those nagging reboots. I haven't changed any OC settings, etc since it was stabilized, so I'm not positive about it being a complete cure. However, I NEVER previously had that number of starts, stops, and restarts without encountering that DMI message and reboot situation. I'm almost afraid to tinker with it (but I eventually will, of course) since I'm just enjoying the flawless bootup sequence at the present time.
After I wrote the posting last evening on this whole problem, it seems that wiping out the retained DMI code (whatever it may have been), by the method I employed, was what the board needed for a fresh start. Incidentally, after I accomplished the rebirth of the flawless bootup sequence, I encountered an interesting collateral situation. About an hour after I "fixed" the problem, an alert message appeared on my screen indicating that my copy (100% legit) of Vista 64 Ultimate required activation within 3 days. Since I had already activated my OS months ago, I was quite surprised by that message. The alert message indicated that Windows Vista 64 had sensed that there was a major change in the hardware base for the previous activation, and that the OS needed to be re-activated.
Since the ONLY change in anything related to the hardware base of my PC was the CMOS procedure and BIOS settings outlined above, I suspect that that procedure did, in fact, wipe out the CMOS setting, including some stored DMI settings, that were residing within the bowels of the motherboard. It was a reasonably easy task to re-activate the OS, but it required a toll-free telephone conversation with someone, who by her accent, was located on the other side of the world from the USA. The M$ activation representative was very nice, and gave me the 48 digit code to get things back in shape. It would seem that the re-activation requirement may be proof of the wiping out process that I described. I'll keep you posted on whether or not this "fix" sticks. But for right now, it sure has been a blessing!
Best regards to everyone. TheBeagle