EP31-DS3L "CPU Host Clock Control" causes boot failure (also updated to latest bios) - Overclock.net

beanbagofdoom · 09-19-08

No matter what I try simply turing on the cpu host clock control makes it fail to boot and then a auto reset turning the clock control off, even if I dont acauly overclock.

Im using E5200 which is a new 45nm cpu 800fsb. And I've tested with and older E6600 and different memory. still the same issue.

I've also tryed flashing the bios to the latest version (f3->f4). Still no good.

I've tried getting support with gigabyte, but they just said up the voltage (which was stupid and I tried anyway) and then they said "I dont reccomened overclocking" Even though I bought a product with full overclocking bios options. I'll have more words with them later.

Also the motherboard runs very well and stable and this not just a 1 off as you can see on this newegg review I found.

Quote:

Pros: Runs fine. Has many BIOS options and overclocking options. Decent budget board.

Cons: Oveclocking DOES NOT WORK. This seems to be a common problem with Gigabyte P31/P35 boards. Once CPU Host Control is enable, the system will either not POST or reset to default settings. No matter what I tried I could not get this board to overclock.

Other Thoughts: If this board is needed for a system where overclocking will not be used, it should work fine. If overclocking is needed, look elsewhere. You may get lucky and get a board that can overclock, but it is not worth the risk.

I'm realy pissed off and not looking to RMA as it seems to be a problem with most "EP4/3/1

Any tips?

Wiremaster · 10-15-08

Yeah, I have a similar problem. I have a E2180 in a Gigabyte P31-S3G, and it SHOULD be able to OC to 3ghz easy, but if I set it above 2.70, blammo. Unstable all around. Changing the voltage does nothing. I think it's just the board. It sucks.

Edit: I got 3Ghz now... the ram didn't have enough voltage. now it's +.4v and running well. 1200mhz fsb/ram. might want to try the ram volts.

Wrenchrider · 12-31-08

Quote:

Originally Posted by Wiremaster

Yeah, I have a similar problem. I have a E2180 in a Gigabyte P31-S3G, and it SHOULD be able to OC to 3ghz easy, but if I set it above 2.70, blammo. Unstable all around. Changing the voltage does nothing. I think it's just the board. It sucks.

Edit: I got 3Ghz now... the ram didn't have enough voltage. now it's +.4v and running well. 1200mhz fsb/ram. might want to try the ram volts.

I also got the rev 2.0 and its behaving funny. I have generic ram rated 667mhz (1.8v), an e4400 and hdt-s1283. So as for the ram cant go beyond an fsb of 333 otherwise wont post since my SPD lowest is 2.0 I was warned if I dare overvolt it, it might be the last thing I do with it.
I have updated to Fda bios. OCs to 2.93ghz [EIST and CIE disabled]to windows. Increasing beyond this causes blues and blacks screens there after and thats only when the system has been running for 12min at default settings.
If you perform a cold boot straight to an overclocked profile the system boots like twice or thrice resetting to stock. Stock speed for an e4400 is same as for an e2180 right? Why will it reset everything even if you try a cold boot OC straight to 2.1ghz if its a stability issue? I thought stock volts for this speed was stable for 2.1ghz probably until about 2.4ghz.Or is it just me who hasnt the slightest idea how to overclock using a processor on this board coz I have read people reaching 3.2ghz with a q6600
Is my board behaving normarly?

lsdmeasap · 01-01-09

Try PCI Express Freq 102-105

Wrenchrider · 01-01-09

Quote:

Originally Posted by lsdmeasap

Try PCI Express Freq 102-105

I think that would effectively start overclocking my graphics card too. Am not to sure how it'll respond to that coz its so old Windows has its drivers

but will be getting a HD 4870 to replace it, but at the moment I just want to make sure my core can get to atleat 3ghz stable.

I have been ravaging through the net and got this so I will give this one a try

Quote:

Originally Posted by Idontcare

@http://forums.anandtech.com/messagev...readid=2243775

I have DS3L and this issue is common.

What happens is that the BIOS is set to error on the side of caution and pretty much assume that any computer reboot or system shutdown which isn't "clean" must be a bad overclock.

To "clear" the lingering memory of this false-positive you have to unplug the PSU from the outlet and set the mobo clear cmos jumper and leave it like that for about a minute.

Then set your clear cmos jumper back to default, then plug the PSU back into the wall. I have confirmed repeatedly that you must unplug the PSU from the wall to make the process work.

The next thing you must do when your system reboots is go into the BIOS and first select the load defaults option, save (F10) and reboot.

Then go back into the BIOS and setup your OC options. Save and reboot.

Now at this point in the timeline there is some kind of reboot/cold-boot counter in the BIOS and if it doesn't register a controlled shutdown followed by a clean cold-boot then it will assume that any subsequent reboots (initiated by you, windows, or a failed OC) are all counted as failed OC's.

So once you set your OC settings and the BIOS does it's mandatory reboot to get out of the BIOS screen the very next thing you need to do whenever the reboot is complete and you are in windows or linux is you must do a hard-shutdown (not a restart). Let the computer sit at least a minute after shutdown before booting again.

This sets whatever register Gigabyte uses for tracking "known good BIOS settings" as your OC settings and now you can initate reboots/restarts and not have the OC get mis-percieved as a bad OC.

Wrenchrider · 01-02-09

Tried the above and the only thing that happens twice instead of the regular once is this message at each OC boot:

Which ever option you choose really doesnt make any difference. I tried them all.
Problem still there

lsdmeasap · 01-03-09

Uninstall DES Software or return your system to the same speed it was when you installed the program, normally stock. If not, you may just need to uninstall it if you are not sure

j0z3 · 01-03-09

Quote:

Originally Posted by Wrenchrider

I think that would effectively start overclocking my graphics card too.

Wrong.

Try doing that, in my old 945 board it helped.

Wrenchrider · 01-05-09

Quote:

Originally Posted by lsdmeasap

Uninstall DES Software or return your system to the same speed it was when you installed the program, normally stock. If not, you may just need to uninstall it if you are not sure

At the moment I just want to know quickly if I can get to my target frequency coz the earlier I know, I then get a chance to send a friend with it by plane rather than rma it if it turns out bad

Quote:

Originally Posted by j0z3

Wrong.

Try doing that, in my old 945 board it helped.

Your actually right, someone gave me a wrong impression.

Anyway guys guess what?
I still dont understand what happened but for some funny reason I decided out of the blues to soft restart my pc 10 times consequtively in the shortest time possible. 1st,2nd,3rd reboot nothing happened however 4th reboot a process called Gsvr.exe crashed and I kept on. On the next reboot a process called RTHDCPL.exe crashed and finally on the next reboot the bios trashed itself.
So the board auto recovered to the bios it came with from the factory.
Funny enough my temps dropped by 2°C and I was able to boot at 2.8ghz this time with EIST and CIE enabled with stock volts all round and no resetting no matter how much I restart or yanked the power plug. At 3ghz on stock volts the system would post, show that its at 3ghz then restart post and again show its at 3ghz and continue until I modify the mobo settings.The only thing that seemed to reset my overclocks was when my external HDD was plugged in one of the usb ports. So finally I updated to FDa bios and everthing seems okay now, just dont understand why my EHDD is resetting the clocks when plugged. This board looks like it can give 3.2ghz on an E4400. Normally I dont like doing things I dont understand but this one is beyond me, I cant explain what happened.

Some interesting finds I got
http://www.xtremesystems.org/forums/...3&postcount=26

http://www.xtremesystems.org/forums/...19&postcount=8

http://www.xtremesystems.org/forums/...4&postcount=68

lsdmeasap · 01-05-09

Why didn't you just uninstall DES, that would fix your error imaged above, and the ones you just mentioned about Gsrv.exe that is part of the DES. It was all really a software issues in this instance nothing to do with the board/BIOS

Either way, glad to see you got it fixed up!

		Overclock.net - Overclocking.net > Intel > Intel Motherboards > Intel BIOS
EP31-DS3L "CPU Host Clock Control" causes boot failure (also updated to latest bios)

01-02-09	#6 (permalink)
Wrenchrider New to Overclock.net Join Date: Dec 2008 Posts: 14 Rep: 0 Unique Rep: 0 Trader Rating: 0	Tried the above and the only thing that happens twice instead of the regular once is this message at each OC boot: Which ever option you choose really doesnt make any difference. I tried them all. Problem still there

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)