Page_fault_in_nopaged_area

Discussion in 'Windows Desktop Systems' started by BOB050082, Jun 19, 2002.

  1. BOB050082

    BOB050082 Guest

    I was forced to re-install windows XP because on every startup, just before windows loaded, i got a BSOD displaying a message says "PAGE_FAULT_IN_NOPAGED_AREA". I tried every boot option but still got the same BSOD. Any idea on what caused this or how it can be prevented in the future?
     
  2. allan

    allan Guest

    You might want to run a check on your ram.
     
  3. Perris Calderon

    Perris Calderon Moderator Staff Member Political User

    Messages:
    12,332
    Location:
    new york
    my idea is you might have lowered your page file, which of cource should never be done in xp, or you might have created a static page file, which again should never be done
     
  4. BOB050082

    BOB050082 Guest

    my RAM is fine, and i didnt change any pagefile settings. This problem happened once before and i didnt think anything of it. Thanks for the input
     
  5. Binary

    Binary Guest

    According to Windows XP Inside Out:

    Stop 0x00000050 or PAGE_FAULT_IN_NONPAGED_AREA
    A hardware driver or system service requested data that was not in memory, causing an exception error. The cause may be defective physical memory or incompatible software, especially remote control and antivirus programs. If the error occurs immediately after installing a device driver or application, try to use Safe Mode to remove the driver or uninstall the program.
     
  6. allan

    allan Guest

    Dealer - You should never have a static paging file? I certainly disagree with that (yeah I know, someone else thinks otherwise). And as for "lowering" the paging file, there are clearly times that's also appropriate. For example, if you have a gig of ram, XP will set a 1.5 gig paging file - which we all know is much too large.
     
  7. firehawk

    firehawk OSNN Addict

    Messages:
    72
    Do we really need to start another debate on pagefiles?
     
  8. xsk8zerox

    xsk8zerox Moderator

    Messages:
    746
    Location:
    Philly
    New hardware can also cause that
     
  9. allan

    allan Guest

    firehawk - good point.:)
     
  10. Perris Calderon

    Perris Calderon Moderator Staff Member Political User

    Messages:
    12,332
    Location:
    new york
    ok, no debate, but I do get to respond...allan, that's right, you should never set a static page file...well proven...ESPECIALLY if you have a gig of ram...you see allan, xp wants to have the ability to dump all the ram...it assumes that if you have a gig of ram, you are going to need a gig of ram...of course you need a dynamic page file, 1.5 is never too big a file for whatever amount of ram you have... if you have a gig of ram, xp will make sure it has whatever it wants,(usually 1.5), one way or the other, and that's a performance hit right there...and if the file is not dynamic, when you do appraoch the limits, you will get another performance hit...absolutely no reason to turn the file static whatsoever, and every reason to keep it dynamic...don't forget...the file remains static even with a dynamic setting...UNLESS the file becomes too small for your needs... fragmentation is a non issue.
     
  11. allan

    allan Guest

    Nonsense.

    XP wants the ability to dump the ram because the programmers decided that in the event of an anomalous program termination there should be a record of what was in ram at the time so someone could analyze the "crash dump" (which, by the way, is next to impossible for even those programmers to do). So given the fact that the contents of ram are of little help at best (if anyone could make heads or tales of the dump in the first place) and since it makes more sense to disable write debugging information anyway, your argument is invalid. You're spending far too much time listening to people who know more about technical backstories and not enough about practical usage.
     
  12. Perris Calderon

    Perris Calderon Moderator Staff Member Political User

    Messages:
    12,332
    Location:
    new york
    uh huh...I'm not making any argument whatsoever of why XP wants to dump, but we all know it wants to dump, and it will make sure it can.

    a static file makes no sense, as you are just forcing XP to page somewhere else if it needs to...a file smaller then 1.5 makes no sence , as XP will just make room for it somewhere else whenever it needs to...you are trying to hold your breath...you can't hold your breath, you're going to breathe, period...it doesn't matter if someone somewhere doesn't think you aught need oxygen, you still need it just the same

    anyway, I thought we weren't going to debate this
     
  13. BOB050082

    BOB050082 Guest

    Ok, enough with the debating. I think there might actually be a problem with my RAM. How do i go about checking this...
    Thanks
     
  14. joshuajme

    joshuajme Guest

    what kind of ram do you have?
    which slot is it in?
    what temperature is it running at?

    It sounds like your ram is to hot to me, either that or its buggered. Get a ram heatsink kit, they dont cost much.
     
  15. BOB050082

    BOB050082 Guest

    Ive got 1GB of RDRAM (dont even begin to flame) 4x256. Ive been noticing some other RAM related problems lately as well, such as programs refusing to run/open and error messages with RAM related messages. I have no idea how to check the status or temp. Any help is appreciated
     
  16. allan

    allan Guest

    If you do a search on Google for Ram Diagnostic Utilities you'll find a few cownloads to choose from. I'd do it for you but I'm on the run at the moment...sorry.
     
  17. joshuajme

    joshuajme Guest

    Run your system for 10 minutes, restart it and go into your BIOS, then go into sumthing like PC Health STATUS. Tell me ur system temp and cpu temp. (1gb of rd ram? nice, shame it aint working) wish i could afford that!
     
  18. BOB050082

    BOB050082 Guest

    I think i have come to a conclusion, that it is not my hardware that is causing problems, but infact nView. Debugging utilities, have shown problems with the nView.dll. I can solve the problem by replacing the dll, but once i restart, the problem comes back again. I think it is best to entirely remove nView, but i dont know how.
     
  19. Bytes Back

    Bytes Back Ex Police Chief

    Messages:
    1,383
    Location:
    Kernow
    *Bytes searches through "Most wanted Criminal magazine" for Allan, No joy, Looks through the latest wanted posters. AH ! interesting *
     
  20. BOB050082

    BOB050082 Guest

    Success! I completely removed nView and without a hitch. Everything seems to be working fine now.