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.

    My Asus F3sv crashed already

    Discussion in 'Asus' started by sutapanaki, Jan 9, 2008.

  1. sutapanaki

    sutapanaki Notebook Enthusiast

    Reputations:
    0
    Messages:
    10
    Likes Received:
    0
    Trophy Points:
    5
    I've got my first crash already, a week after I started using my new F3sv notebook. This morning it downloaded the latest Vista updates and while installing them it crashed. After rebooting I got a message from the boot manager that the registry was corrupted and I should insert my installation CD and do repair. I tried booting into Safe Mode and Last known good configuration but the result was the same. Well, I don't have an installation CD, only the repair disk that came with the laptop. I called Asus technical support and they recommended restoring the factory default installation of the operating system. So I did, which was not a big deal at this time since I didn't have many things installed nor a lot of my personal data. But the question is if this thing keeps crushing every once in a while what should I do? I can't keep restoring the operating system for ever, because every time I will have to start from ground 0. Not to mention how frustrating it will be if I have more things installed on the machine. So, what is the best approach to take? I want to be able to somehow restore my state before the crash. I can do backup in Vista but what if I can not access the windows as it happened today? Or may be do an image of the computer, but this is very unfamiliar activity for me since I've never done it so far. Any suggestions?

    Thanks
     
  2. JCMS

    JCMS Notebook Prophet

    Reputations:
    455
    Messages:
    4,674
    Likes Received:
    0
    Trophy Points:
    105
    It shouldn't happen to often.

    If you have SP1 RC installed, you can create a Windows Repair DVD
     
  3. kozzney

    kozzney Notebook Evangelist

    Reputations:
    41
    Messages:
    565
    Likes Received:
    0
    Trophy Points:
    30
    Sounds like what happened to me. I installed those same Vista updates and boom crash on my Dell M1330.
     
  4. sutapanaki

    sutapanaki Notebook Enthusiast

    Reputations:
    0
    Messages:
    10
    Likes Received:
    0
    Trophy Points:
    5

    And then what did you do?
     
  5. E.B.E.

    E.B.E. NBR Procrastinator

    Reputations:
    1,572
    Messages:
    8,632
    Likes Received:
    4
    Trophy Points:
    206
    To be ready for such occurences in the future, you should always keep your personal data on a partition separate from Vista. Then you can recover Vista without losing your personal data.

    To recover your applications as well, you can make an image of the Vista installation. Check my XP guide (linked in my sig) for how to do an image of an OS partition (it's the same for Vista).
     
  6. eteri

    eteri Notebook Enthusiast

    Reputations:
    0
    Messages:
    38
    Likes Received:
    0
    Trophy Points:
    15
    there r many reason y a computer may crash due, i know one is low ram with vista, u should probaly have at least 1 gb of ram

    -hope this helps
     
  7. precurs0r

    precurs0r Newbie

    Reputations:
    0
    Messages:
    9
    Likes Received:
    0
    Trophy Points:
    5
    Same thing happened to me with an Asus F7kr.

    I just picked up XP from school.. gonna be installing this weekend. I hate this Vista crap.
     
  8. E.B.E.

    E.B.E. NBR Procrastinator

    Reputations:
    1,572
    Messages:
    8,632
    Likes Received:
    4
    Trophy Points:
    206
    Low RAM will not cause crashes, it will cause slowdowns only.