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.

    Startup Error on new e1705

    Discussion in 'Dell' started by SF49ers, Dec 28, 2006.

  1. SF49ers

    SF49ers Notebook Enthusiast

    Reputations:
    1
    Messages:
    44
    Likes Received:
    0
    Trophy Points:
    15
    Hello,

    Every once in a while a get an error when starting up saying:

    Page fault in non paged area

    It comes up on a blue screen just after entering windows and I have to restart the computer. I am unsure of what caused this but here is what I am thinking:

    I used Gparted Live to move 4 GB of space on to my main partition. To do this I had to move that space onto the media direct partition and then onto my main partition.

    The only other thing I can think might be causing it is bootskin (a program to change the bootscreen).

    This does not happen everytime I startup and in total it has happened around 6-8 times.
     
  2. gridtalker

    gridtalker Notebook Virtuoso

    Reputations:
    18
    Messages:
    2,976
    Likes Received:
    0
    Trophy Points:
    0


    Start by removing bootskin and seeing what happens and if that is the problem.
     
  3. kegobeer

    kegobeer 1 hr late but moving fast

    Reputations:
    836
    Messages:
    3,682
    Likes Received:
    0
    Trophy Points:
    105
    Did your laptop do this before you monkeyed with things? If so, you might want to check your memory, as bad memory sometimes causes this error.
     
  4. SF49ers

    SF49ers Notebook Enthusiast

    Reputations:
    1
    Messages:
    44
    Likes Received:
    0
    Trophy Points:
    15
    I am really unsure if it did this before or after. I just ordered 2 GB of RAM so hopefully that solves the problem. I haven't had it happen in a while. But just in case I backed everything up.