The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    Asus UX51VZ - Standby Problem

    Discussion in 'Asus' started by StandbySlouch, Aug 23, 2014.

  1. StandbySlouch

    StandbySlouch Newbie

    Reputations:
    0
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    5
    Dear experts,

    I have a problem with my standby mode (S3) on my Asus UX51VZ notebook. Sometimes the S3 fails in a very annoying way: First, the screen turns black as usual but instead of suspending (into S3), the fans begin to work at 100 % and it just wont suspend. Even after hours, the screen is black, fans at 100 % and cpu is really hot (-> endless loop?) and it does not respond to any key. The only escape is to kill it by pressing and holding the power button, which also means that the state (e.g. open documents) will be lost. This happens only sometimes (maybe 1/10) and it began just a few weeks ago (I own the notebook since 1 year). Unfortunately, I am not able to reproduce this glitch willfully - it always happens when it should absolutely not. I don't know in which state the PC must be so that the glitch occurs but it seems that it is more likely to occur when there are more open programs.

    I investigated in the internet a lot but since nothing helped me, I put my last hope in you guys: Anybody has an idea what could cause this problem or how I could get an useful error log?

    Asus UX51VZ (bios and all drivers up to date)
    Windows 8.1 (winupdate up to date)
    No new drivers or software installed in past few weeks.

    Thanks!
     
  2. petterk

    petterk Notebook Enthusiast

    Reputations:
    0
    Messages:
    49
    Likes Received:
    2
    Trophy Points:
    16
    Could be memory corruption. You could try downloading a program which checks your memory(RAM), or download a Linux distribution and running memtest86+
     
  3. StandbySlouch

    StandbySlouch Newbie

    Reputations:
    0
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    5
    Good guess. I ran several ram tests - no errors were found.
     
  4. Prostar Computer

    Prostar Computer Company Representative

    Reputations:
    1,257
    Messages:
    7,426
    Likes Received:
    1,016
    Trophy Points:
    331
    It may be part of the processors G1 power state. Can you recreate the problem using Hibernate, as well?
     
  5. StandbySlouch

    StandbySlouch Newbie

    Reputations:
    0
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    5
    Hi,

    Thanks for your replies!

    I already tried:
    x different gpu driver versions (oem)
    x disabling wifi
    x ram memtest

    Problem persists.

    I did not manage to reproduce the problem when going to hibernate (S1). But what I found out with the tool "BlueScreenView", is that every time the problem occurs, a driver_irql_not_less_or_equal bluescreen is thrown obviously, though the screen actually does not turn into a bluescreen. See detailed information attached.

    Any new suggestions for resolving this problem?

    Thanks again!

    Cheers
     

    Attached Files:

  6. StandbySlouch

    StandbySlouch Newbie

    Reputations:
    0
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    5
    Hi,
    Just if anybody comes here struggling with the same problem as me: Finally I found the cause of the bluescreens when turning into standby:
    Indeed, the firewall of the software "Avira Internet Security" caused the bluescreens. Avira told me that this product may not be fully compatible with Win8. I think, this is nonsense, because I have also had this problem when using Win7. After deinstallation of Internet Security and an upgrade to "Avira Antivirus Pro" (which uses the Windows Firewall from now on) 3 months ago, the problem did never every occur again since then.
    Thanks for your support guys.
    Cheers