• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Gigabyte P35-DS3R not OC'ing???

I built my current system back in Sept 07 with the P35-DS3R. I have a Q6600 with 4 gb ram. Originally I was running XP 32 bit. I have had it OC to 3.2 ghz with no problems. Back in December I installed Win 7 and have it set up as a dual boot system, XP 32 bit and Win 7 64 bit. Now, when I run CPU-ID it shows only 2.4 ghz. I thought maybe it was because of Win 7. So I boot up in the xp 32 bit and it shows the same, 2.4 ghz. But if I boot into bios, it shows 3.2 ghz. I have it 356 x 9 to get to the 3.2. But in CPU-ID it shows 266 x 9. If I try to run the Easy TUne that Gigabyte provides, it won't let me adjust anything now, says the Dynamic Energy Saver is on. But my mobo doesn't support that. Does anyone know of a sure way of seeing if it is OC to 3.2?

Thanks...
 
Sounds like Speed Step may have been enabled in the BIOS, look for a setting called EIST. This will change the clock speed of the CPU according to how much it is being used. If EIST is on just try turning it off and see what that does.
 
I went and checked my bios and EIST was enabled, I disabled it, saved, rebooted...still shows 2.4 as speed. bus speed won't come off of 266.67 in CPU ID or EasyTune...even though bios is 356. Any other thoughts?

Thanks...
 
Last edited:
Okay, check these settings in the BIOS, see if turning off the settings below helps.

Limit CPUID Max. to 3.....................: [Disabled]
No-Execute Memory Protect............: [Enabled]
CPU Enhanced Halt (C1E)................: [Disabled]
C2/C2E State Support....................: [Disabled]
x C4/C4E State Support..................: [Disabled]
CPU Thermal Monitor 2(TM2) ...........: [Enabled]
CPU EIST Function.........................: [Disabled]
 
Well I got up this morning and now I am getting nothing, a black screen. I am thinking about reseting the CMOS but wanted to know something first. I have a Raid 5, 3 x 500 gb drives, setup and running in the system. Will clearing the CMOS destroy the raid setup, I have a ton of pictures on the Raid system. It is setup through the board ICHR9 chipset. I am hoping the raid setup won't be effected.
 
No clearing the CMOS will not break the array. Worst case scenario you may just have to re-enable RAID operation on the drives in the BIOS. The RAID subsystem runs on a different BIOS separate from the main BIOS so clearing it will not affect the RAID setup. Usually you will see three options for hard drive operation, IDE, RAID, and AHCI mode. Make sure its setup as RAID after clearing the CMOS. Most Gigabyte boards have a clear CMOS jumper area next to the CMOS batter, either take the battery out for 15-30 seconds or put a jumper on the board at the Clr-CMOS pins and hold in the power button for 30 seconds to 1 minute without a battery in the board.
 
I have tried taking the battery out and unplugging the power for about 15 minutes and also tried jumping the cmos clearing pins. Nothing, just a black screen. Not sure where to go now...
 
Interesting, try pulling every expansion card except the video card and 1 RAM module and see if it POSTs. Try the RAM by itself in each DIMM and see what happens. Also try POSTing the system without RAM and see if it beeps. Do you have another power supply and video card to test with the system?
 
I just tried another video card, the one from the system I am using now. Nothing. I don't have anyother expansion cards, except the video. I pulled all of the memory out (4 x 1GB) and put multiple combinations in. Nothing. I then checked the voltage coming from the power supply to the MB and all of the voltages are correct. I am stuck..
 
Well I went and picked up a EP45-U3DP board and new memory, 8 GB (4 x 2GB). When I got home, I thought, let's try the memory on my old board. I put it in the system posted on my monitor (not my usual monitor). So I connected everything back up and tried it again. Still worked. Then I connected my usual monitor and black screen. So I un-connected the DVI cable and power cord. Connected them back and had a light green screen with lines, terrible looking. So I moved the DVI cable connector at the monitor and it popped back to the correct look. I am thinking the monitor has a problem. So it seemed to appear that my memory was bad as well as my monitor trying to go out. Hopefully my monitor still has warranty left on it, it's a 26".

But now I can OC with no problem. When it started working again, my bios was at F6, the original, so the clear CMOS activities worked. I then q-flashed to the latest. All is good, for now... 🙂
 
Back
Top