are these bios number okay?

[toyota]

yes I meant to say numbers in the title.


I am running the E8500 at 3.8(9.5x400) 1:1. idle 33C and 48C max temp for 8 hours of Prime. actually those max temps were a little lower than I thought it would get to but my room is cool this time of year.

I have left most settings at auto except for vcore which you can see is at 1.275 and ram is at 1.82. do I need to lower or raise any of the other settings instead of leaving them on auto??

 

[toyota]

wow nobody?

 

[n7]

CPU PLL is higher than needed.

I could OC my quads to far higher FSBs than that with way less PLL voltage.

I'd lower that; i doubt you need more than 1.54v PLL, if even that much.

Everything else looks fine, though if you can, why not run the FSB higher + lower multi or even just the RAM higher.

Both of those won't affect real world numbers really, but if you like squeezing the most outta things, you go for the highest possible FSB + highest possible RAM speed.

 

[toyota]

CPU PLL is higher than needed.

I could OC my quads to far higher FSBs than that with way less PLL voltage.

I'd lower that; i doubt you need more than 1.54v PLL, if even that much.

Everything else looks fine, though if you can, why not run the FSB higher + lower multi or even just the RAM higher.

Both of those won't affect real world numbers really, but if you like squeezing the most outta things, you go for the highest possible FSB + highest possible RAM speed.

yeah I lowered the PLL to 1.5 since it certainly didnt need to be that high but everything else from that Easytune screenshot is the same. I was just worried that I had something overvolted or close to the edge of being stable.

I ran Prime95 for several hours today and even threw Furmark in the mix for about an hour just to see what would happen. no issues at all and the highest it got to was 53C with all of that running. most of the time it was right at 50-51C with Furmark in the mix and 46-47 running just Prime95.

I really dont want to go any higher since even now I dont need that much speed except for GTA 4. I was just trying to get a nice 1:1 stable 3.6 or 3.8 out of it because I plan to get a better gpu soon and wanted just a bit more out of it to keep things balanced. I will also probably get a new cpu/mobo/ram setup a few months after the new gpu too.

 

[n7]

Well, with temps that low, i'd be aiming a lot higher.

I'm sure 4.2+ GHz is something you could do easily.

But that's up to you

 

[toyota]

well the pc would not come out of sleep the other day. I clicked on the keyboard as usual but the pc came on and then immediately went right back off. then it started coming off and on and the fans were racing very loud. after about 5 or 6 times it finally stayed on but there was no video. I had to hold down the power button to get it to shut off.

I then rebooted and it turned right back off while it was starting up. it then booted itself and seemed to be starting up fine but it when the windows came up it said resuming windows and I had to click on that screen you get if you log out.

I just realized today that the issue was certainly related to my oc because my comp reset itself back to stock settings and let me know when I checked the bios. I had no issues in Prime95 or coming out of standby for weeks so I dont know what the issue is.

btw the PLL is at 1.5 and thats the only difference from the screenshot in the OP.

any advice???

 

[toyota]

well it looks like I am talking to myself here but today when I woke the pc up all the fans were racing really loud and I had to restart it.

 

[Markfw]

When I have that much problems on an OC, I just take the OC down a little. Not worth the aggrevation to me.

 

[Hyperlite]

I think your problem is EasyTune. It causes "Ghosts in the machine." My little bro recently got a Q8300, and while admittedly not much of an overclocker, easytune caused constant headaches. The system is 6+ hour prime and linpack stable, but randomly blue screens. We've reformatted, changed video cards, and the only constant is easytune. He can't overclock from the bios because of the gigabyte host clock control bug, which is extremely frustrating, but when he uses setFSB everything is just peachy. It's a shame too, because easytune is a great program.

 

[toyota]

I think your problem is EasyTune. It causes "Ghosts in the machine." My little bro recently got a Q8300, and while admittedly not much of an overclocker, easytune caused constant headaches. The system is 6+ hour prime and linpack stable, but randomly blue screens. We've reformatted, changed video cards, and the only constant is easytune. He can't overclock from the bios because of the gigabyte host clock control bug, which is extremely frustrating, but when he uses setFSB everything is just peachy. It's a shame too, because easytune is a great program.

I am not using easytune at all. in fact its not even installed on my pc at the moment. everything I changed was in the actual bios. the only reason its in the op was so I could conveniently show all the values I had set in the bios.

 

[toyota]

When I have that much problems on an OC, I just take the OC down a little. Not worth the aggravation to me.

but 3.8 running 1:1 at 1.275(set in bios) vcore isnt much of an overclock at all for an E8500. I mean the memory isnt overclock or anything else crazy like that. also its completely prime stable and runs intel burn test just fine. somebody mentioned that my mobo may have issues with resuming from sleep with my fsb above the stock 333 setting though.

EDIT: the ONLY thing that changed was the night before my first standby issue I had installed 2 windows updates. its probably just a coincidence but the next morning is when the issues started after weeks of being trouble free with the cpu oc.

 

[Markfw]

I gave up on my OC. My E8400 is at 3.6, as 3.9 was hard to maintain.

 

[toyota]

I gave up on my OC. My E8400 is at 3.6, as 3.9 was hard to maintain.

but if it was the oc that was the prob why is it 100% stable in every possible test? it just seems odd that such a fairly mild oc would start causing a problem with resuming from sleep after all this time.

 

[Hyperlite]

I am not using easytune at all. in fact its not even installed on my pc at the moment. everything I changed was in the actual bios. the only reason its in the op was so I could conveniently show all the values I had set in the bios.

ah. well. nevermind then.

 

[spinejam]

i had an e3110 (e8400) @ 4050mhz w/ 1.328 vcore and it ran rock solid.

make these changes independently so you'll know which one worked!

-- i think your vMCH may need a boost -- try 1.30
-- keep CPU PLL @ 1.5 -- no higher than 1.57
-- raise CPU Term to 1.25-1.30

 

[toyota]

i had an e3110 (e8400) @ 4050mhz w/ 1.328 vcore and it ran rock solid.

make these changes independently so you'll know which one worked!

-- i think your vMCH may need a boost -- try 1.30
-- keep CPU PLL @ 1.5 -- no higher than 1.57
-- raise CPU Term to 1.25-1.30

by vMCH do you mean MCH Core? I do have the PLL at 1.57 for now.

btw whatever issues I am having only happen after being in sleep mode for several hours. it does not happen if I resume from sleep after a short time.

 

[spinejam]

by vMCH do you mean MCH Core? I do have the PLL at 1.57 for now.

btw whatever issues I am having only happen after being in sleep mode for several hours. it does not happen if I resume from sleep after a short time.

yes, vMCH = MCH Core
what bios version are you running?
the ud3p mb's have had issues w/ unable to wake from sleep w/ some bios versions as well.

 

[toyota]

yes, vMCH = MCH Core
what bios version are you running?
the ud3p mb's have had issues w/ unable to wake from sleep w/ some bios versions as well.

I am on the F6 bios.

 

[zagood]

spinejam's got it right, there are problems with the EP45 (and a lot of 775 Gigabyte mobos) unable to wake from sleep. It usually shows at around 400+mhz fsb. I had the problem on my UD3P on an e5200 @ 333mhz FSB until I followed the instructions here:

http://www.vistax64.com/tutorials/63567-power-options-sleep-mode-problems.html

However with a Q6600 @ 417mhz FSB I can't get it to resume from S3.

Good thread to read through:
http://forums.anandtech.com/showthread.php?t=271227

 

[spinejam]

do you know what revision board you have? (1.0 / 1.1 / 1.6) -- if so, bios update time!

disclaimer -- at your own risk of course!

http://forums.tweaktown.com/f69/gigabyte-latest-bios-28441/

 

[zagood]

fyi: I'm using F8 on a revision 1.0. Tried F9 and F10f but my system was unstable. Available from Gigabyte if you want to try any of those:

http://www.gigabyte.us/Support/Motherboard/BIOS_Model.aspx?ProductID=2914

 

[toyota]

do you know what revision board you have? (1.0 / 1.1 / 1.6) -- if so, bios update time!

disclaimer -- at your own risk of course!

http://forums.tweaktown.com/f69/gigabyte-latest-bios-28441/

fyi: I'm using F8 on a revision 1.0. Tried F9 and F10f but my system was unstable. Available from Gigabyte if you want to try any of those:

http://www.gigabyte.us/Support/Motherboard/BIOS_Model.aspx?ProductID=2914

I have revision 1.0. so should I try going to F7 or F8 bios then? also should I go straight to F8 or would it be better to give F7 a go first?

 

[toyota]

spinejam's got it right, there are problems with the EP45 (and a lot of 775 Gigabyte mobos) unable to wake from sleep. It usually shows at around 400+mhz fsb. I had the problem on my UD3P on an e5200 @ 333mhz FSB until I followed the instructions here:

http://www.vistax64.com/tutorials/63567-power-options-sleep-mode-problems.html

However with a Q6600 @ 417mhz FSB I can't get it to resume from S3.

Good thread to read through:
http://forums.anandtech.com/showthread.php?t=271227

thanks I will look over that.

 

[Markfw]

but if it was the oc that was the prob why is it 100% stable in every possible test? it just seems odd that such a fairly mild oc would start causing a problem with resuming from sleep after all this time.

Well, I can;t answer yours. But in my case it would go at 3.8 or 3.9 for weeks, sometimes months. But a lockup or reboot, even in 3 months was not acceptable, as I would loose a days work. (work box). Mine was @100% load all time time, until I could no longer run F@H on win2k.

As for yours, it could be something similar. Try something like 3.6, and see how it does maybe.

 

[toyota]

well I removed the windows update that was installed the night before I had trouble coming out of standby and this morning I had no issues resuming. I am going to reinstall that windows update and see what happens tomorrow morning when I come out of standby.