View Single Post
  #4  
Old August 13th 17, 07:44 AM posted to alt.windows7.general
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default overclocking error

Seymore4Head wrote:
On Sat, 12 Aug 2017 17:52:13 -0400, "Mayayana"
wrote:

"Seymore4Head" wrote

| http://imgur.com/a/xwmgB
|

I find it often helps to search for the exact text.
A quick search didn't come up with a solution, but
did indicate that it's at least, probably, not malware.
The message seems to appear with some Gigabyte
boards when resuming from hibernation. I didn't find
anyone who'd solved it, but you can try searching
further for:

"while overclocking the system, it could be unstable"

I reset my bios to "optimum settings" and then turned back on AHCI

Thanks.


I can't find a root cause for that one.

1) It seems to be on newer systems. Is UEFI a factor ?
Is it a "feature" only on newer OS versions ?
2) Only seems to happen coming out of sleep/hibernation.

The hibernation process starts at shutdown. If something
went wrong when the hiberfile was being written, maybe
the system remembers that (somehow) ?

When the system starts, hibernation doesn't have a lot
of requirements in order to work.

The message could be coming from "hybrid sleep". You
actually put your system to sleep, and you see the
disk light go on as the computer also writes out
a hiberfile. If the power were to go off, after
that point, the system would know on recovery, it
had been in sleep state, but it was forced to load
the hiberfile. It would be reasonable at that point,
for it to print a snotty message on the screen.

You're going to have to use your brain to noodle
this one out. The breadcrumbs I can find so far, only
note the thing happening. But nobody has a suggestion
of what is actually triggering the message to appear.
Since there are not a lot of postings with that
message, it implies a degree of obscurity. And
what phase of recovery from hibernation, or
hybrid sleep, is that obscure ? Why don't more
people get that message ? Doesn't make sense.

You've got a mystery on your hands.

*******

An Asus BIOS will declare "overclocking fail", even
when the user was not overclocking. The traditional
BIOS, kept track of whether the system was shut
down normally. So when the OS shuts down, it actually
calls the BIOS to do the shutdown, and the BIOS
can clear a status bit of its own that says "OK, this
session was clean, and we went from sun-up to sun-down
without a problem". However, if you just flip the
power switch on the computer, the BIOS status bit
is now in the wrong state, because there was no
normal shutdown. Some Asus systems, when the power
comes back, will assume an overclocking failure, and
reset your BIOS to defaults.

So who cares what the BIOS does ? Well, it matters because
it may stop boot, and force you to do something to get
the machine to start.

But your photo is different, in the sense that it seems
to have the same orbit of symptoms, but the *OS* is
printing that message, not the BIOS. How the hell does
the *OS* know this, unless you were in Hybrid Sleep,
killed the power, the system recovered by reading the
Hiberfile (a feature only available via Hybrid Sleep),
and the system knew it was in hybrid sleep when it
was shut down. So it went down in S3, came up in S4,
and the massage "assumes" there was some sort of
instability causing this kind of session recovery.

The threads I could find, this message appears to be
recurrent, happening on each wakeup. And that doesn't
suggest a power problem.

So my guess at this point, is hybrid sleep may be involved.
Normally S3 sleep holds the session in RAM. Wakeup should
be almost instantaneous (except your hard drive still has
to be fully up to speed of course). When Hybrid sleep is
used, the machine is still in S3 state, except during
shutdown, as an "insurance policy", the session is
written to the hiberfile too. If the power is then
interrupted, the computer can still read the hiberfile
on next startup (as if it was coming out of S4). And it
really doesn't have to say a word. But the startup will
take additional time, if it's forced to read the hiberfile
to restore the session.

Paul
Ads