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.

    SZ 160 --WAY too long to resume after hibernating

    Discussion in 'VAIO / Sony' started by swheatie78, Jul 4, 2006.

  1. swheatie78

    swheatie78 Newbie

    Reputations:
    0
    Messages:
    7
    Likes Received:
    0
    Trophy Points:
    5
    Hi all,
    Newbie here and NOT all that computer educated (but willing to learn). Have an SZ-160, and overall, have been very happy with it. However, it recently started taking FOREVER to resume after having been hibernated. It shows that black window with the "resuming" thing going on, and it takes way longer than it should to get back to working screen. Boot up is otherwise without problems. I don't know even where to start with this! Is anyone else having this problem??

    Thanks in advance for any help you can offer!
     
    swheatie78, Jul 4, 2006
    #1
  2. _radditz_

    _radditz_ Fallen to the Sith...

    Reputations:
    120
    Messages:
    1,584
    Likes Received:
    0
    Trophy Points:
    55
    Im guessing because your not computer savvy you havent re-installed windows on your computer. Sony does put a lot of junk on their systems which could be causing the system to slow as it loads up all of the unnecessary processes.

    Have you tied doing a semi-restore as others have in the forum?
     
    _radditz_, Jul 4, 2006
    #2
  3. Bomfunk

    Bomfunk Notebook Consultant

    Reputations:
    3
    Messages:
    210
    Likes Received:
    0
    Trophy Points:
    30
    I had the same problem. It happens when you have less than approximately 1GB of free space on your harddisc (Windows partition). Try moving some data to a different partition to free up some space and see if the problem persists.
     
    Bomfunk, Jul 5, 2006
    #3