Official GIGABYTE Forum
Questions about GIGABYTE products => Motherboards with Intel processors => Topic started by: C-BuZz on July 04, 2012, 05:13:49 am
-
G'day
Bios multi set @ 40x. When it resumes from sleep EVERY time I get this... ??? Regardless of what is set in bios. G1.Assasin2. All power saving settings disabled. I'm leaning towards a lame bios issue because I cant think of anything else. If I turn off sleep altogether & never put the pc to sleep it works 100%, but I don't want the PC running 24/7. Only happens when resuming from sleep.
Running the latest F10 bios.
(http://s15.postimage.org/70auzdciz/bench.jpg)
The system is NOT crashing/restarting/bluescreening ect.. HALP!! LoL..
-
Mine [3960x] runs low clock low power low temps till I give it some work to do, then clocks and power go to max and temps climb.
Try running a stress tester like prime95 [free dl] or similar and see what happens.
-
Hi
Make sure that you haven't got conflicting settings in Windows and the BIOS for the sleep cycles.Also make sure that everything is 100% stable as any instability can cause problems with sleep.
-
Mine [3960x] runs low clock low power low temps till I give it some work to do, then clocks and power go to max and temps climb.
Try running a stress tester like prime95 [free dl] or similar and see what happens.
3.5Ghz priming 100% load after waking from sleep, already tried that thanks anyway.
Hi
Make sure that you haven't got conflicting settings in Windows and the BIOS for the sleep cycles.Also make sure that everything is 100% stable as any instability can cause problems with sleep.
Hi,
Low power state is set to %100 in Windows. It's 100% stable, no doubt about it. Heck, I can bench all day at 4.8Ghz. But waking from sleep, the multi is 35x.... Even if it wasn't, doesn't explain why the multi is 35x waking up from sleep. I can sit here & watch it go to sleep @ 4Ghz. I can then immediately wake it up & it's stuck on 35x multi LOL!!!
Err ???
-
Ok, that is quite bizzare! ???
Will check how mine behaves in this regard after I've chased the bsod on resume problem.
What OS are you running and hdd config?
-
Ok, that is quite bizzare! ???
Will check how mine behaves in this regard after I've chased the bsod on resume problem.
What OS are you running and hdd config?
Indeed it's really bizzare. Running 2 x 120GB SSD's in Raid0 (onboard raid) with Win7 64bit SP1. See if your overclock sticks after resuming from sleep.
Thx mate.
-
No probs, but first I have to get mine to successfully resume from sleep without bsod'ing >:(
Other's in this forum are having issues with this as well.
-
No probs, but first I have to get mine to successfully resume from sleep without bsod'ing >:(
Other's in this forum are having issues with this as well.
Weird, I've had zero bsod issues. Has not Bsod'd once resuming from sleep. Only the multi dropping to 35x.
-
It's a config and/or installed OS issue. 7x32 on ide sata port works fine. Working my way through the list to identify which setup fails.
I'll try the OC issue while I have 7x32 installed and let you know how that goes.
-
It's a config and/or installed OS issue. 7x32 on ide sata port works fine. Working my way through the list to identify which setup fails.
I'll try the OC issue while I have 7x32 installed and let you know how that goes.
what do you mean 7x32?
-
F11 Bios did not fix this issue...
BEFORE SLEEP:
(http://s15.postimage.org/czdpfjwaj/b4sleep.jpg)
AFTER RESUMING FROM SLEEP:
(http://s11.postimage.org/9mwflev5v/aftersleep.jpg)
Why?? ???
-
what do you mean 7x32?
Win7 32 bit
So, another bios release - F11 - and it's quoted as improved sata hdd compatability...hmmm....
Have to admit, I'm still getting my head around the bios in this m/b.
Are you setting the cpu multiplier in bios or via the gigabyte software tools [or ezitune]?
-
Ok, so I move the cpu multiplier in bios from the default x33 to x34. set turboboost to disable so I can see in cpuz that my max multiplier is now x34 under full load, but nooo, it still wants to go to x36 [turbo multiple] ???
Have set min power state in cpl to 100%, but nooo, it still idles at x12 ???
Not only that, I tried pressing the OC button in at one stage to see what that did and after that, pressing del to get into bios either did nothing and windows would boot, or the tab menu would come up ???
Pressing ctrl-alt-del at that point would always work, so the del key is definitely working.
Sometimes F12 boot options would work [sometimes] and I could get to bios from there.
Tried a ps2 kb and it was no different.
I turned the OC button off and am still having troubles pressing del to get to bios.
Not only that, I've noticed from day 1 that sometimes after doing a restart without even having entered bios and with everything on default [load optimized defaults] except 'show full logo', that it would turn on the green m/b led [m/b is sitting on a box atm] like it was about to boot, but then the led goes off then after a few secs comes back on, then [maybe then] you get the megatrends splash and system beep ???
Sometimes it will have a few goes before finally starting.
I have run memtest for 24 hours with no errors and prime95 for a few hours with no errors.
Maybe the F11 bios might solve some of these issues.
Does anyone get the feeling that it's left to end users to do the debugging these days... :)
Maybe I'm being a bit harsh, the complexity bar has been raised a bit lately.
But goddammit, I just wanna play a game and my m/b is STill sitting on a cardboard box!! :D .....yeah, gotta keep smiling!
-
what do you mean 7x32?
Win7 32 bit
So, another bios release - F11 - and it's quoted as improved sata hdd compatability...hmmm....
Have to admit, I'm still getting my head around the bios in this m/b.
Are you setting the cpu multiplier in bios or via the gigabyte software tools [or ezitune]?
I only ever overclock in bios. Only use ET6 to see if I could see why the multi was dropping.
Ok, so I move the cpu multiplier in bios from the default x33 to x34. set turboboost to disable so I can see in cpuz that my max multiplier is now x34 under full load, but nooo, it still wants to go to x36 [turbo multiple] ???
Have set min power state in cpl to 100%, but nooo, it still idles at x12 ???
Not only that, I tried pressing the OC button in at one stage to see what that did and after that, pressing del to get into bios either did nothing and windows would boot, or the tab menu would come up ???
Pressing ctrl-alt-del at that point would always work, so the del key is definitely working.
Sometimes F12 boot options would work [sometimes] and I could get to bios from there.
Tried a ps2 kb and it was no different.
I turned the OC button off and am still having troubles pressing del to get to bios.
Not only that, I've noticed from day 1 that sometimes after doing a restart without even having entered bios and with everything on default [load optimized defaults] except 'show full logo', that it would turn on the green m/b led [m/b is sitting on a box atm] like it was about to boot, but then the led goes off then after a few secs comes back on, then [maybe then] you get the megatrends splash and system beep ???
Sometimes it will have a few goes before finally starting.
I have run memtest for 24 hours with no errors and prime95 for a few hours with no errors.
Maybe the F11 bios might solve some of these issues.
Does anyone get the feeling that it's left to end users to do the debugging these days... :)
Maybe I'm being a bit harsh, the complexity bar has been raised a bit lately.
But goddammit, I just wanna play a game and my m/b is STill sitting on a cardboard box!! :D .....yeah, gotta keep smiling!
Ok, so if it's not booting flip the power supply to completely off then press the small "Clear Cmos" button at the back near the overclock button & hold it for 5seconds. Will boot every time if you do that. Mine sometimes goes into an infinite boot loop if my overclock is bad. Have to turn the system completely off & press the clr Cmos button to get it booting again. If your multi is still going to 36x then you probably pressed the overclock button at the back. I noticed it increases the turbo speed.
You need to disable all power saving features like C3/C6, EIST & real time clock ratio changes in OS ect.. That way it will always run at full speed without the power saving crap.
Here you go:
(http://s14.postimage.org/fzn93rd69/P7060003.jpg)
-
Thanks for the pic showing the relevant power states to disable :)
I will revisit clearing cmos and loading defaults, but i'm pretty sure that it still quite often gets stuck momentarily.
I know the clear cmos button is doing it's job as the first screen you get is the load defaults screen.
It could be that it trips over itself when querying the hdd's or bd-drive and bios F11 will fix that.
I note that someone else with a different m/b has posted a new thread and is having the exact same issue.
Have to go out for a bit, brb.
-
You wouldn't belive it! I disable Full Screen Logo Show [the only change] and the bios has a meltdown!!
Same story as before, endless retries to initialize and when that finally succeeds the press del for setup is now bringing up the tab menu. ???
Have started a new thread for this one.
-
Ok, have set bios as per your pic and now have full control of multiplier in control panel, which I left set at 100%
I initially left the bios multiplier on x33 and set turbo boost to disable, then booted to check that the cpu was running at x33 - all good.
Then changed the mult in bios to x35 and rebooted.
Cpuz now showed x35 and no amount of sleeps/resumes would move it off that.
Try yours at 1 or 2 clocks above stock and see what happens.
If you want me to try something else on mine, let me know :)
edit: Just remembered your running 7x64, will load that up and see what happens.
-
Ok, did a install of 7x64sp1 with all drivers and still cannot duplicate your clock problem.
One interesting thing though, whereas in 7x32sp1 I had control of the multiplier in control panel > min power state after disabling the power/sleep settings in bios, in 7x64 I no longer have that control. The clock is always flat out even with min power state on 0%
The question is, is this a 32 versus 64 difference, or is it because I installed 7x64 with those settings already disabled in bios?
I tried re-enabling them, rebooting, checking cpuz was now showing low clock - all good, then disabling them again and rebooting, but still had no control of clock via min power state.
Another thing noted, not all sleep/hybrid states are available in control panel until the vga drivers are installed.
I did try hybrid sleep enabled and disabled but that had no effect on cpu clock after resume.
I also tried sleeping with cpuz still running and not running without issue, my clock was always x35 as per bios.
Im still on F10 bios
-
Ok, did a install of 7x64sp1 with all drivers and still cannot duplicate your clock problem.
One interesting thing though, whereas in 7x32sp1 I had control of the multiplier in control panel > min power state after disabling the power/sleep settings in bios, in 7x64 I no longer have that control. The clock is always flat out even with min power state on 0%
The question is, is this a 32 versus 64 difference, or is it because I installed 7x64 with those settings already disabled in bios?
I tried re-enabling them, rebooting, checking cpuz was now showing low clock - all good, then disabling them again and rebooting, but still had no control of clock via min power state.
Another thing noted, not all sleep/hybrid states are available in control panel until the vga drivers are installed.
I did try hybrid sleep enabled and disabled but that had no effect on cpu clock after resume.
I also tried sleeping with cpuz still running and not running without issue, my clock was always x35 as per bios.
Im still on F10 bios
Thanks for all your testing there mate. I think after resuming from sleep it's defaulting to 35x multi. So yours could still be having the same clock issues. Can you try setting 40x multi in bios (or something higher than 35x), then boot into windows > sleep > resume?
Cheers
-
Yeah, was thinking the same thing, but I don't have a whole lot of cooling on mine and was a bit paranoid about pushing too hard, brb
-
Ah-ha, nailed it! Finally got it to do what yours is doing. I set x37 in bios, boots and shows x37 in cpuz, but after resume from sleep was now back to x36.
We were right, it's defaulting back to the max turbo frequency after resume, even though thats disabled in bios.
When I set mine to x37, it would go back to x36 after resume, which is the default 6 cores active turbo frequency for this processor.
The trick is to enable [auto may work also - untested as yet] turbo frequency in bios and set the active core settings to the minimum you want.
I left my 1 and 2 core as-is [39] and set all the others to 37, which is the default for 3 and 4 cores active so I could probably have left them as-is as well, but for 5 and 6 cores active the default was 36 and after setting them to 37, it will now boot and show x 37 and still be on x37 after resume from sleep.
Mind you, my systen totally spat the dummy on the first resume from sleep!! :o
It seem to give up trying to resume, went into bios loop a couple of times, then started with the logo but asking me if I wanted to boot from the dvd, 7x64 was still in the drive but boot order was such that this message should not have appeared.
I ignored the message and there was a momentary flash of something on the screen [bsod I think] and it booted the dvd anyway ["goddammit, what the hell are you doing!!" ]
So I ctrl-alt-del out of that, bios starts ok this time [no loops] but I'm still asked if I want to boot the dvd, I ignore, it flashes the sceen and boots the dvd again.
I ctrl-alt-del out of that again and remove the dvd from the drive while it's re-posting.
This time it pops up the boot screen for safe-normal boot etc. I tell it to boot normal [if it knows what that is anymore!!] and it gets on with the job and I arrive at the desktop with a message that windows has recovered from a problem..."you don't say!!" :)
I tried cpuz, still on x37 and was able to sleep/resume any number of times after that and it remained on x37 with no issues resuming from sleep....go figure!! :D
-
Oh, forgot to add, I also figured out why min power state in cpl was having no effect. It's because of disabling EIST in bios. Disabling it also prevents cpuid h/w monitor from picking up and displaying many of the temp sensors.
Enabling it does not have any effect on the multiplier problem.
-
Nice work Rob, that workaround works!
-
No probs :)
I'm not sure I would classify it as a workaround, it's proably quite normal behavior for any bios/cpu with these features.
My theory is, that when you disable turbo, all your doing is turning off the ability to make changes, the machine still sees the turbo settings and reacts to them.
I have to say that my bios has totally behaved itself for quite a while now with logo enabled, even after many changes - no loops!
Have struck another oddity though, with ahci versus ide sata settings. Not necessarily a problem, just a curiosity, but it could have deeper consequences.
Have started another thread for it.
-
No probs :)
I'm not sure I would classify it as a workaround, it's proably quite normal behavior for any bios/cpu with these features.
My theory is, that when you disable turbo, all your doing is turning off the ability to make changes, the machine still sees the turbo settings and reacts to them.
I have to say that my bios has totally behaved itself for quite a while now with logo enabled, even after many changes - no loops!
Have struck another oddity though, with ahci versus ide sata settings. Not necessarily a problem, just a curiosity, but it could have deeper consequences.
Have started another thread for it.
It's not normal, I've had literally dozens of systems with the Turbo feature & none of them defaulted to max turbo freq after resuming from sleep. Good to see that your bios is finally behaving. Have you updated to F11?
-
Ah-ha, ok, then it is not normal 4 sure. And certainly one could argue that, when you disable something, you expect it to have no further influence on the system at all, not just prevent further changes to the settings.
No, I'm still on F10 trying to islolate the bsod after resume issue.
-
Ah-ha, ok, then it is not normal 4 sure. And certainly one could argue that, when you disable something, you expect it to have no further influence on the system at all, not just prevent further changes to the settings.
No, I'm still on F10 trying to islolate the bsod after resume issue.
Exactly, if it's disabled it's disabled. Not disabled then active after resuming from sleep.
Update to F11 bios & see if it resolves your bsod issues.
-
Yeah I'm wanting to pin down exactly which configs have a problem first, make sure it's not something I'm doing, then see if F11 fixes it. But I'm a bit reluctant on F11 with it's retry issue.
-
As per logo/loop thread, F11 is working fine but did not resolve the resume > bsod on raid issue.
This one is critical to me and have logged it directly with gigabyte support.