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.

    UX21 blue screen

    Discussion in 'Asus' started by UX21, Jul 5, 2012.

  1. UX21

    UX21 Newbie

    Reputations:
    0
    Messages:
    7
    Likes Received:
    0
    Trophy Points:
    5
    Got the Zenbook UX21E in March 2012. Already the first day's I got a blue screen where it said "dumping physical memory". Then there could be months without anything. Today I got the same thing many times again just being on youtube.

    It's windows 7 64 bit on it and I'm using Chrome and Spotify mostly and have Avast free anivirus installed, but there is no pattern in what I run when it crash.

    Will a bios update be a wise try? My system info tell me I have bios version 209. There are to date 2 newer versions. Here's the bios list;

    http://support.asus.com/download.aspx?SLanguage=en&m=UX21E&p=3&s=368&os=30&hashedid=GKaPKXPAHSUhQiWZ

    This is what appear most often;
    [​IMG]

    Sometimes once I get in after a crash it crash again, and then this is one of the following screens;
    [​IMG]
     
  2. ALLurGroceries

    ALLurGroceries  Vegan Vermin Super Moderator

    Reputations:
    15,730
    Messages:
    7,146
    Likes Received:
    2,343
    Trophy Points:
    331
  3. UX21

    UX21 Newbie

    Reputations:
    0
    Messages:
    7
    Likes Received:
    0
    Trophy Points:
    5
    Thank you so much for directions.

    I started using the notebook on March 20. First blue screen March 28th. BlueScreenView show total of 24 blue screens from March 28th until today.

    17 of them in the last 3 day's. 15 of them is caused by a "ntoskrnl.exe", 3 caused by a "aswSP.SYS", 2 caused by a "Ntfs.sys" & 2 caused by "rdyboost.sys", etc.

    -----

    Memtest86+ came back with no errors found!

    -----

    I googled "ntoskrnl.exe" and found a thread somewhere with a guy having the same problem, and his memory scan gave directions to Avast antivirus...
     
  4. ALLurGroceries

    ALLurGroceries  Vegan Vermin Super Moderator

    Reputations:
    15,730
    Messages:
    7,146
    Likes Received:
    2,343
    Trophy Points:
    331
    ntoskrnl is as it sounds, the windows OS kernel. That is possibly a driver issue.

    aswsp is avast, maybe try a complete uninstall/reinstall of avast with the latest version.

    The ntfs error could point to a failing hard disk, check it out with a free SMART utility like this: PassMark DiskCheckup - SMART hard drive monitoring utility
     
  5. UX21

    UX21 Newbie

    Reputations:
    0
    Messages:
    7
    Likes Received:
    0
    Trophy Points:
    5
    Thanks again. :biggrin:

    I removed Avast and installed Microsoft Security Essentials. Updated the bios to latest and updated the audio drivers.

    So far no blue screen...I hope it continues and that it was just Avast that didn't like my computer.
     
  6. UX21

    UX21 Newbie

    Reputations:
    0
    Messages:
    7
    Likes Received:
    0
    Trophy Points:
    5
    Little update on this. Avast had nothing to do with it. Have deleted program by program, and it turned out to be Uniblue "Speed up my Pc/Registry booster" thing I had. Didn't really run it very often...but the thing with these little programs was that they apperantly were running in the background (even if it didn't snow with any icon or anything). Not had a single blue screen since I removed them some weeks ago.
     
  7. ALLurGroceries

    ALLurGroceries  Vegan Vermin Super Moderator

    Reputations:
    15,730
    Messages:
    7,146
    Likes Received:
    2,343
    Trophy Points:
    331
    Oh man, registry cleaner/optimizers are like the plague. :p

    Glad you fixed it!
     
  8. UX21

    UX21 Newbie

    Reputations:
    0
    Messages:
    7
    Likes Received:
    0
    Trophy Points:
    5
    Me 2! Thanks again! :D
     
  9. Prostar Computer

    Prostar Computer Company Representative

    Reputations:
    1,257
    Messages:
    7,426
    Likes Received:
    1,016
    Trophy Points:
    331
    It is clearly to me one or more sector of your memory is defective. The reason you can still use it, because the program does not hit the defective sector (or sectors). I recommend you to replace the RAM memory or send to Asus for repair.
     
  10. UX21

    UX21 Newbie

    Reputations:
    0
    Messages:
    7
    Likes Received:
    0
    Trophy Points:
    5
    It seems to have been a software fault and I am very sure it is the program I wrote about above that caused this.

    I ran Memtest86+ and it tested my memory and the program didn't find anything wrong with it. That shouldn't have happened if I had some defective sectors in my RAM should it?