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 BSOD Caused by Direct console

    Discussion in 'Asus' started by computer112, Dec 28, 2007.

  1. computer112

    computer112 Notebook Enthusiast

    Reputations:
    0
    Messages:
    35
    Likes Received:
    0
    Trophy Points:
    15
    I recently purchase an Asus G1s, and it worked fine for the first six days, but afterward when ever I am at the startup window the BSOD always comes up, and its keeps happening after every restart. After I went into safe mode and disable most of the exe file using msconfig the BSOD didn't happen. Through the process of elimination its seems like the ASUS Direct Console the exe file that controls the OLED screen on the G1s was the cause of the BSOD. But I don't know why it should be, I have already look in the web for similar stories but no other owners of a G1 seem to have this problem. Can anyone explain to me why this may happen, could it be the the OLED or some part of my G1 be faulty. Well I am actually planning on returning it today, which is the last day for return/exchanges. Please reply, and by the way the error code was 0x0000007F. Thanks
     
  2. computer112

    computer112 Notebook Enthusiast

    Reputations:
    0
    Messages:
    35
    Likes Received:
    0
    Trophy Points:
    15
    Sorry for posting this, It was actually either Mcafee AV or logitech webcam drive that may have caused this BSOD.
     
  3. ClearSkies

    ClearSkies Well no, I'm still here..

    Reputations:
    1,059
    Messages:
    2,633
    Likes Received:
    0
    Trophy Points:
    55
    I would lean toward the webcam as the culprit. DL the latest from Logitech's website, and install the driver only (skip the software portion, it can be buggy).