UNSOLVED
G
guitarman04
17 Posts
0
2153
March 4th, 2005 02:00
PAGE_FAULT_IN_NONPAGED_AREA
Twice this week, when turning on my computer, I got a blue screen that read: PAGE_FAULT_IN_NONPAGED_AREA
then a bunch of stuff about if this is the first time seeing this, restart, etc....check your hardware....
then it said: stop: 0x00000050 (0xF796C750, 0x00000000, 0x7955051,0x00000000)
The first time, I shut the computer off, turned it back on, pressed F8, and selected to start the last *something* ( i can't remember the wording) without problems, and windows, loaded up, with no problems. I ran a virus scan (mcaffee), and found nothing, a spyware scan (microsoft beta) and also found nothing. The computer worked fine after that.
Two days later, I got the same blue screen, and tried to do the same thing, but it wouldn't work. I ended up starting windows in safe mode, and doing a system restore, to the day before, and here I am. It seems to be ok, for the moment.
Does anyone know what could be causing this?
P.S., my system is a Dell Dimension 2350, pentium4, windows xp, sp2.
Message Edited by guitarman04 on 03-04-2005 07:30 AM
guitarman04
17 Posts
206
0
Posted March 4th, 2005 12:00
Thank you, I will refer to that page when I get home after work.Interesting bit about the keyboard. I am using a logitec keyboard, which often asks if i would like to check for updates, and I always say no. One time when I restarted, it said "no keyboard connected"..I think I will try switching to the original keyboard first.Thanks again.guitarman04
17 Posts
206
0
Posted March 4th, 2005 23:00
I just noticed something that i didn't notice before.While starting windows, it only says "windowsxp", the "home edition" part is gone....Had this "50" BSOD (and others - 7F, 8E, D1 and more) on a DImension 8300, and it turned out to be the processor. Changing keyboard, new hard drive, memory, motherboard did not help. New processor - no problems anymore. Hope you are still under warranty....
Lemmi
chuket
1388 Posts
206
0
Posted March 4th, 2005 02:00
It could be RAM not seated completely or (unlikelty) bad RAM. Review the following for other possibilities:
http://kadaitcha.cx/0x50_error.html