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.

    Escalating Problems Culminating in BSOD

    Discussion in 'Windows OS and Software' started by unrelatedwaffle, Apr 6, 2009.

  1. unrelatedwaffle

    unrelatedwaffle Notebook Enthusiast

    Reputations:
    0
    Messages:
    30
    Likes Received:
    0
    Trophy Points:
    15
    I have an Asus M50Vm, bought in December of 08, running Vista Home Premium. All was going well until about a week ago, when out of the blue, I started getting "Windows has encountered a problem" errors in every program I would run, randomly. It happened most often with Firefox, but soon OpenOffice and Winamp were crashing regularly, too.

    Then, a few days ago, I got a BSOD, and the computer auto-restarted before I had a chance to read the error message. It didn't happen again, so I thought it was just a freak occurrence.

    Yesterday I got three BSODs, one with a win32.sys error, one with a fltmgr.sys error, and another that I didn't have time to read. Today, my computer won't stay on for ten minutes before getting BSOD, and it runs incredibly slow and buggy for those ten minutes. I can't even get through a virus scan before it craps out on me. I did three System Restores to increasingly distant points in the past, to no avail.

    I have attached the two BSODs I had time to take pictures of. I've learned to keep my camera at the ready. The first happened immediately after signing on, and the second happened about 5 minutes after signing on and trying to run anti-virus.

    Any help would be GREATLY appreciated. I would not like to return the computer so soon after getting it!
     

    Attached Files:

    unrelatedwaffle, Apr 6, 2009
    #1
  2. Full-English

    Full-English Notebook Deity

    Reputations:
    1,227
    Messages:
    1,512
    Likes Received:
    8
    Trophy Points:
    56
    NTFS.SYS may have something to do with your HDD (but not definate), which it shows on the second picture.

    Any chance of uploading your minidump files (if they are still there) at:

    C:>Windows>Minidump>*****.DMP

    These might help in investigating the problem further.

    Edit: Just reading again and with you saying it runs very slow during the ten minutes before you get a BSOD would also suggest something wrong with the HDD.

    If you can, could you try and run HD tune and scan your HDD for bad sectors or errors, or run the disk checking tool within windows. Go to windows explorer, right click on the drive, properties, tools, then error checking.
     
    Full-English, Apr 6, 2009
    #2
  3. unrelatedwaffle

    unrelatedwaffle Notebook Enthusiast

    Reputations:
    0
    Messages:
    30
    Likes Received:
    0
    Trophy Points:
    15
    I just ran chkdsk, and got 0 errors. After doing some googling, ONE of the error screens I got has been linked to a RAM issue. I'm going to open her up and troubleshoot the RAM as soon as I can find my mini-screwdrivers. . .

    Has anyone else had this issue?
     
    unrelatedwaffle, Apr 6, 2009
    #3