Try to clear CMOS first as described in the second part of this post. If 20 minutes don't do the trick leave the jumper on and battery out for a few hours/over night.
This fixed an identical problem for some users, for some it didn't.
Hey fellors,
Let me know what you think since I am pretty much stuck...
The problem started when my computer restarted with a crash - where my graphics starts to blackout with tons of artifacts.
Since then, my motherboard bios will now only default on CPU Host Clock Control as [Disable] even if I change it to acceptable FPS.
First I thought it may be due to CMOS Checksum Error but no matter how much small of value I change, it is always going back to default [Disable] now. I have disabled all the CPU Halt/CPU EIST etc. usual stuffs that may overrides this to Default but no luck.
Any thought?
Edit: I just recently flashed the BIOS to F9 Version. Still no go.
Board: GA-p35-DS3L
Here is a little background -
I was successfully overclocked Intel E6300 @ 1.86ghz to run at 3.2GHZ for almost a year all stable etc. but since yesterday, I am back to 1.86ghz
![]()
Try to clear CMOS first as described in the second part of this post. If 20 minutes don't do the trick leave the jumper on and battery out for a few hours/over night.
This fixed an identical problem for some users, for some it didn't.
So you do have C1E and EIST both disabled? Just checking
Yes, I advise you to try and clear the CMOS using the long method in post #2 linked above and see if that helps
~ X58 BCLK WORLD RECORD ~
~ <Mushkin Enhanced Alpha Team ~
* BIOS Templates (Give Us Your Settings Please) *
GIGABYTE Reviews - X58A-OC ~ P67A-UD7 ~ P67A-UD4 ~ 5870 SOC
<Mushkin Reviews - 998966 Radioactive ~ 998826 Ridgeback ~ 998679 Blackline ~ 996587 HP
Crucial Reviews - C300 SSD ~ Blue Tracer DDR3 ~ Ballistix DDR2
X58 BIOS LED Debug Codes
@Omega
I am having the exact same issue.
Are you running an HD4770 video card?
Tried LONG 1day+ hard-reset of CMOS while battery is out. NO GO.
Tried taking out memories...and reset and NO GO.
Now I just found out my memory wont' set to any thing higher than 800mhz. no matter which multiplier I use. (like x3.0/x3.22/3.50 etc.)
I can set it to 667 but nothing higher than 800mhz.
So either way, problem seems related to Northbridge or somewhere, where it is unable to regulate Bus speed and therefore board won't Force the overclock features.
MikeB: I have Nvidia EVGA 8800GT.
just out of curiousity...is this something RMA-able?
Sounds like a bad BIOS flash. If you already tried resetting to optimized defaults and the machine is stable I would try flashing to the latest BIOS again. Make sure you load default settings after the flash and then optimized settings, rebooting in between.
I agree, next step would be to flash the latest BIOS, please use Qflash here is a guide and the latest BIOS
http://forums.tweaktown.com/f69/bios...h-guide-27576/
http://forum.gigabyte.de/forumdownlo...19/P35DS3L.zip
You may also want to try flashing one of the older F8 BIOSes or starting your board with one stick of memory (Or a different stick if you have any) and see if that clears it up
Last edited by Lsdmeasap; 12-13-2009 at 04:27 PM.
~ X58 BCLK WORLD RECORD ~
~ <Mushkin Enhanced Alpha Team ~
* BIOS Templates (Give Us Your Settings Please) *
GIGABYTE Reviews - X58A-OC ~ P67A-UD7 ~ P67A-UD4 ~ 5870 SOC
<Mushkin Reviews - 998966 Radioactive ~ 998826 Ridgeback ~ 998679 Blackline ~ 996587 HP
Crucial Reviews - C300 SSD ~ Blue Tracer DDR3 ~ Ballistix DDR2
X58 BIOS LED Debug Codes
bios was reflashed w/ F9 version: NO GO after different trials/soft and hard resets.
bios was reflashed w/ F8 version, still NO GO. Same results.
I have also ran it with single ram etc. but no luck either.
I had this problem prior to flashing bios, so I don't think it is bios issue to begin with. I have also ran it with single ram etc. but no luck.
Since the days of celerons/p4s, I've been overclocking chips and I am fairly certain this may be hardware issue where something got burned and my computer therefore was shutdown.
Next step > going to try to RMA.
Sounds like it's come down to that, shame we couldn't get it working, good luck.
There are currently 1 users browsing this thread. (0 members and 1 guests)
Bookmarks