|
Korean Job Discussion Forums "The Internet's Meeting Place for ESL/EFL Teachers from Around the World!"
|
View previous topic :: View next topic |
Author |
Message |
Blind Willie
Joined: 05 May 2004
|
Posted: Tue Apr 05, 2005 11:47 am Post subject: PAGE_FAULT_IN_NONPAGED_AREA |
|
|
I've checked up on this error on my blue screen of death, and I know what it signifies, but I'm hoping to narrow it down to what bit of hardware is acting like a jerk before I go spending money on replacement parts.
An odd additional problem is that my browsers simply cannot keep their cookies. Does it relate? Anyone have similar experiences? |
|
Back to top |
|
 |
Demophobe

Joined: 17 May 2004
|
Posted: Tue Apr 05, 2005 12:40 pm Post subject: |
|
|
Ummm.....sounds more like a driver than hardware. Did you install any new drivers lately? What did you do on the machine prior to this happening? Is it regular or occasional? If it's regular, you made a change and it's not good. Try to recall what it was. If it's irregular, what do you do on the computer to make it happen? Try to recreate the fault and make notes.
If you want to test the hardware, again, you will need to know how to re-create the scenario, if it isn't regular. You can turn off the system and physically remove bits on by one until you find the part that you think is causing the problem, or you can go into "device manager" and disable them. Both ways involve patience and lots of reboots. I would go with physically removing them.
However, there are utilities in Windows for de-bugging and driver checking. This page outlibes these scenarios quite well...and with a brevity that I couldn't re-create, so check them out carefully. Don't let the jargon fool you; this is very do-able, but it will take some time.
Honestly, there are a number of possible reasons why this happened...from a bad data packet through a network to corrupt NTFS volumes, so run CHKDSK /F /R to check for corruption and check the event log for any clues as well. |
|
Back to top |
|
 |
Demophobe

Joined: 17 May 2004
|
Posted: Tue Apr 05, 2005 4:32 pm Post subject: |
|
|
As for the cookies, is your cache folder read-only? Right-click on it to see. Perhaps also some settings in your browser need to be changed to accept cookies. Check the options...also in the Windows security setting...perhaps there is something in there to override default cookie handling, which may solve the problem in an odd way. Override the already "accept" state of the cookie handler to accept cookies...?!
Windows....should call it "Walls"
Do you run a clean-up utility llike ccleaner or window washer? If so, it's wiping the cookies out.
Back to the first problem....is there a numeric value with the pagefault? Like an error code. If you manage to (or can't avoid) re-create the problem, jot down the complete message on the BSOD. |
|
Back to top |
|
 |
Blind Willie
Joined: 05 May 2004
|
Posted: Wed Apr 06, 2005 12:31 pm Post subject: |
|
|
Demophobe wrote: |
Back to the first problem....is there a numeric value with the pagefault? Like an error code. If you manage to (or can't avoid) re-create the problem, jot down the complete message on the BSOD. |
0x00000050
The cookies only seem to vanish when the BSOD hits. Which sometimes happens at least twice a day but it's random. I can go weeks without it happening. Sometimes it happens while it's loading up XP. |
|
Back to top |
|
 |
Demophobe

Joined: 17 May 2004
|
Posted: Wed Apr 06, 2005 12:53 pm Post subject: |
|
|
Ok...well, it's one of a few problems.
1. A bad driver. Did you install any new drivers or add any new hardware recently? If so, roll it back either via the system restore, or uninstall it. Then, try again...if the problem persists, then there is a conflict that needs to be worked out by other means. This is a whole different ball of wax...cross that road if we come to it.
2. A system process problem. This will be a bit more difficult in terms of what you must do to actually solve the problem. One must go through the active services and disable them until the problem ceases. That is nothing short of a drag and a lot of time.
Think about one thing; does it happen at a particular moment that you can re-create? For example, if Windows has a system process that is enabled but inactive, then, through something you ask the computer to do, that process becomes active. This may also trigger a driver call, which too may be the issue. Being able to re-create the problem specifically goes a long way to the diagnosis. Try to pinpoint if there is anything specifically triggering the BSOD. If you can re-create the scenario, work backwards through the problem, beginning at the BSOD, next to the last action, etc... .
3. A corrupt NTFS volume. The checkdisk function command parameters I gave earlier will find this and hopefully fix it.
4. A memory or video memory eror. Run memtest and see what it comes up with. If it's video RAM, that's again, a different ball of wax, and a much, much more difficult situation. Buy a new video card.
I'm sure you have "googled" the error, and if you have, you probably will find a wealth of sites that tell you nothing different from what I have. Oh well...nothing new under the sun or in the box.
Did you try removing bits one by one? Do this with the RAM sticks (how many do you have? You need to leave at least one in the slot to have functionality) Then try the PCI cards, then CD-ROM drives. Try to isolate if it's a hardware problem.
Do you have any idea what makes it happen? Did you look at the event log? There should be a hint in there. Your cookies being lost in a dump is no surprise.
Sisoft Sandra, although not fomally a diagnostic utility, can help push the system to find the problem. Download the free version and run some of the specific tests. This will push certain parts of the system and in doing so, may help to pinpoint the problem.
EDIT:
I just ran across a Windows Knowledge base memo that claims it is most probably a display driver conflict. Though this seems likely as one of the possible problems, it doesnt strike me as the definitive problem or solution. However, it can't hurt to try this. Before proceeding, download the latest video (graphics) card drivers from your maker, probably ATI or Nvidia. You will need these after you have completed the steps below (uninstall the old drivers and eradicate any lingering .old files), and then re-install the downloaded new drivers.
1. Start Windows in Safe mode. To do so:
a. Restart the computer, and then press F8 while the computer starts.
b. On the Windows Advanced Options Menu that appears, use the ARROW keys to select Safe Mode, and then press ENTER.
c. Use the ARROW keys to select the operating system to start, and then press ENTER to start Windows XP in Safe mode.
2. In the message that states that Windows is running in Safe mode, click Yes.
3. Click Start, click Run, type msinfo32 in the Open box, and then click OK.
4. Under System Summary, expand Components, and then click Display.
5. In the right pane, note the information that corresponds to the INF File item, for example, Nv4.inf, Oem0.inf, or Atim128.inf.
6. Quit the System Information utility.
7. Click Start, right-click My Computer, and then click Properties.
8. Click the Hardware tab, and then click Device Manager.
9. Expand Display adapters, right-click the display adapter, and then click Uninstall.
10. Click OK.
11. Click Start, click Run, type cmd, and then click OK.
12. In the Command Prompt window, type the following commands, and then press ENTER after each line:
ren %systemroot%\inf\INF file name from Step 5.inf *inf.old
ren %systemroot%\inf\INF file name from Step 5.pnf *pnf.old
13. Close all open windows, and then restart the computer in the typical
manner.
14. Log on to Windows by using an account that has administrative privileges, and then wait for Windows to detect new hardware.
15. When the Found New Hardware Wizard starts, click Cancel.
If you receive a stop error after you remove the updated display drivers, restart the computer and use the Last Known Good Configuration option. To do this, restart the computer, and then press the F8 key while the computer starts. On the Windows Advanced Options Menu that appears, use the ARROW keys to select Last Known Good Configuration, and then press ENTER.
If you receive a "System Has Recovered from a Serious Error" message when Windows starts, restart the computer again. This error message does not recur. |
|
Back to top |
|
 |
Blind Willie
Joined: 05 May 2004
|
Posted: Sat Apr 09, 2005 7:40 am Post subject: |
|
|
Demophobe wrote: |
Ok...well, it's one of a few problems.
1. A bad driver. Did you install any new drivers or add any new hardware recently |
Nope, but I tried rolling bad a couple of them like the video, sound card, and the scanner, and it seemed to have made it worse. Usually it'll crap out within five minutes.
Quote: |
2. A system process problem. ...
Think about one thing; does it happen at a particular moment that you can re-create? |
It appears to be random.
Quote: |
3. A corrupt NTFS volume. The checkdisk function command parameters I gave earlier will find this and hopefully fix it. |
No problem there.
Quote: |
4. A memory or video memory eror. Run memtest and see what it comes up with. |
I havent treid this yet. I'm seeing if the soultion below worked first.
Quote: |
If it's video RAM, that's again, a different ball of wax, and a much, much more difficult situation. Buy a new video card. |
Man, sinking more money into this thing?
Quote: |
EDIT:
I just ran across a Windows Knowledge base memo that claims it is most probably a display driver conflict...{snip} |
This solution seems to be working thus far, but as I said, the problem has always seemed random. Assuming it doesnt pop up again would you reccommend getting a new video card anyway? Right now it's a Nvidia Geforce FX5200. |
|
Back to top |
|
 |
Blind Willie
Joined: 05 May 2004
|
Posted: Sat Apr 09, 2005 7:58 am Post subject: |
|
|
Okay, it crapped out again with the same error. I'm gonna try the other solutions |
|
Back to top |
|
 |
Blind Willie
Joined: 05 May 2004
|
Posted: Sat Apr 09, 2005 8:41 am Post subject: |
|
|
Okay, I ran Memtest for about ten or so minutes. I let it go to about 102% coverage of "All unused RAM"
I got 11 errors, roughly one every minute, that looked like this:
"error found with word pair #51969431 or 51968076 (Either vould be source)"
And I got one error at about 38% coverage that said:
"error found with word pair #52005647 values 1425357557, 35728410205 not match"
Does this mean my RAM is shot? |
|
Back to top |
|
 |
Gollum
Joined: 04 Sep 2003 Location: Japan
|
Posted: Sat Apr 09, 2005 7:24 pm Post subject: |
|
|
 |
|
Back to top |
|
 |
Demophobe

Joined: 17 May 2004
|
Posted: Sat Apr 09, 2005 11:49 pm Post subject: |
|
|
Well, yes. Do you know what brand it is?
I have a GB of Kingmax RAM...certinly not Crucial or Mushkin quality, but it's runnng well over spec and passes memtest clean. It wasn't that much money....GEIL is also pretty good. |
|
Back to top |
|
 |
Blind Willie
Joined: 05 May 2004
|
Posted: Sun Apr 10, 2005 1:51 am Post subject: |
|
|
Well, I used to know who made it, but I've since forgotten and it's too much effort to crack open the case and look.
But we seem to have isolated the problem, so thanks for the assitance. |
|
Back to top |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|