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.

    screen problem: 6625

    Discussion in 'Other Manufacturers' started by Sprint, Jan 5, 2008.

  1. Sprint

    Sprint DTR Super Mod

    Reputations:
    20
    Messages:
    1,011
    Likes Received:
    0
    Trophy Points:
    55
    Now Iv noticed an really annoying bug or w/e wich makes the screen go black/turned off when I resume Windows from hibernation. Earlyer Iv solved it by simply putting it in sleep and starting up, but a moment ago, I completely had to reboot the lappy to get it back up.

    Iv had this problem with BIOSes 004, 008 and 011, so its probably not that.
    And the wierdest is that the screen is on when booting in BIOS and the "resuming windows" screen, but after that, it turns off (like it allways does at this point) but it doesnt turn on again (wich it normally does).

    Its really annoying :mad:
     
  2. ChristopherGrant

    ChristopherGrant Notebook Consultant

    Reputations:
    11
    Messages:
    223
    Likes Received:
    0
    Trophy Points:
    30
    Sounds really annoying! My 'K' key just started failing alltogether on my
    keyboard today... but that's off topic...

    It sounds like you might've switched screens or screen setups recently?
    I know in the past with my 6625wd (when using dual monitors) if I
    swtiched to single display it wouldn't always default back to the laptop
    monitor but think there was still an external monitor hooked up. The
    bios will still show up correctly on the screen but windows itself tries
    to use the other, unconnected monitor. I'd check your dual screen setup.

    Probably not the issue, but might be worth looking into until someone
    else comes up with something better.
     
  3. DodgeThis

    DodgeThis Notebook Guru

    Reputations:
    0
    Messages:
    72
    Likes Received:
    0
    Trophy Points:
    15
    I have had this many many many times... I am unsure whether it has something to do with the S3 power states or just the graphics drivers.

    I am looking into this at the moment, after updating my graphics drivers however it is not happening so much.
     
  4. Sprint

    Sprint DTR Super Mod

    Reputations:
    20
    Messages:
    1,011
    Likes Received:
    0
    Trophy Points:
    55
    what driver are you using? Iv had this problem with many drivers.

    Actually Im starting to think if Vista/some program is causing the OS to go nuts. Yesterday evening, was puttin it in hibernation, and Vista says "Locking your computer" :confused: And it didnt do anything either.
     
  5. kendle

    kendle Newbie

    Reputations:
    0
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    5
    If I hibernate and close the lid, I have exactly the same thing, blank screen and have to do a hard reboot to get it back; if I don't close the lid until hibernation is finished there is no problem. I've had this with all bios versions. I suspect Vista.
     
  6. John Ratsey

    John Ratsey Moderately inquisitive Super Moderator

    Reputations:
    7,197
    Messages:
    28,841
    Likes Received:
    2,166
    Trophy Points:
    581
    On my 6024W I had issues with Vista and the latest Intel graphics driver (fixed by going back to an earlier driver). You folk tend to have nVidia graphics, but maybe that is also tripping up. Do you still get problems with the latest Zepto approved driver?

    I've also been running vista SP1 RC for the past 3? weeks in case that fixes a few bugs (but evidently not this one) and that would be my first suggestion. However, some suspicion must also fall on the BIOS.

    John
     
  7. Sprint

    Sprint DTR Super Mod

    Reputations:
    20
    Messages:
    1,011
    Likes Received:
    0
    Trophy Points:
    55
    Well, I cant remember if this is true, but it might be a new bug wich came with SP1 RC. Im also using it