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.

    System Standby Failed

    Discussion in 'Asus' started by Tarage, Jan 25, 2009.

  1. Tarage

    Tarage Notebook Enthusiast

    Reputations:
    0
    Messages:
    31
    Likes Received:
    0
    Trophy Points:
    15
    Hi folks,

    I recently got my G50V A1 back from repairs(Faulty motherboard), and have been trying to re-install everything. I formatted the drives, installed XP, and followed the instructions for all of the drivers.

    However, I am getting a problem I have never seen before. The computer won't enter standby mode. When I close the laptop, it stays on. When I try to manually enter standby mode, I get the following error:

    ---The device driver for the 'Default Monitor' device is preventing the machine from entering standby. Please close all applications and try again. If the problem persists, you may need to update this driver.---

    I have not a clue. Any thoughts?

    EDIT: It appears I'm missing the monitor driver... but this is completely baffling because I don't ever remember having to install one before. I don't even know where to find that driver.
     
    Tarage, Jan 25, 2009
    #1
  2. David

    David NBR Random Reviewer NBR Reviewer

    Reputations:
    7,515
    Messages:
    8,733
    Likes Received:
    7
    Trophy Points:
    206
    This is most likely a graphics driver issue. Try install another GPU driver from laptopvideo2go and see if that solves your issue.
     
    David, Jan 26, 2009
    #2
  3. Tarage

    Tarage Notebook Enthusiast

    Reputations:
    0
    Messages:
    31
    Likes Received:
    0
    Trophy Points:
    15
    Yeah, turns out I installed a newer driver than one one linked for some reason, and it was the problem. After I installed the older one it started working.
     
    Tarage, Jan 26, 2009
    #3