Page fault in nonpaged area BSOD

Status
Not open for further replies.
My sister's computer has been having a BSOD with this message:

Page_fault_in_nonpaged_area
stop 0x0x00000050

She also is getting this event in eventviewer

type: error
source: systemerror
Category: (102)
EventID 1003
BcCode: 100050 BCP1:FFFFFF78 BCP2: 0000000
BCP3: 80594A9D BCP4: 0000000 OSVER:5_1_2600 S_P: 3_0

Her specs are:

HP Pavilion a750e
CPU: AMD Athlon 64 3400+
Motherboard: ASUS: either K8S-LA or Salmon-GL6E
Ram Speed, size and #sticks: 2 sticks of DDR PC3200, 1 GB each
GPU: Nvidia Geforce 7600 GS
PSU: not sure as I don't have the computer in front of me right now; probably 350 Watts. We did upgrade her video card and made sure that her power supply that would accomodate the new card.
OS: Windows XP Professional SP3

The bsod seems to be a little random but it usually occurs when she clicks on certain folders on her desktop. We have tried rebooting in safe mode and with startup programs disabled, but it stil occurs.

Her ram is relatively new, it was already replaced once. She may have run some memory tests on it but I'm not sure. She doesn't remember making any hardware or software changes around the time the bsod started occuring. For some reason her system restore didn't have any restore points saved, so system restore is not an option. We have already searched for solutions for the page fault in nonpaged area error, but none of them have helped.

Here are some minidumps. Thanks for any help.
 

Attachments

  • Mini042810-01.dmp
    88 KB · Views: 2
  • Mini042710-01.dmp
    88 KB · Views: 1
  • Mini041810-01.dmp
    88 KB · Views: 1
  • Mini041510-01.dmp
    88 KB · Views: 1
  • Mini033010-02.dmp
    88 KB · Views: 1
All errors are the same 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
Requested data was not in memory. An invalid system memory address was referenced. Defective memory (including main memory, L2 RAM cache, video RAM) or incompatible software (including remote control and antivirus software) might cause this Stop message, as may other hardware problems (e.g., incorrect SCSI termination or a flawed PCI card).

Unfortuantely they only list Windows OS druvers as the probable cause and for the most part OS drivers are not much help for diagnosing the problem, only pointing out that there is a problem.

1. Have you scanned for infections?

2. Since it is an HP I am not sure you can do this but go into your BIOS, find the memory voltage setting and compare it to the voltage the memory was designed for by the RAM's manufacturer. Are there descrepencies?

3. Run Memtest on your RAM.

See the link below and follow the instructions. There is a newer version than what is listed but either one should work. If you need to see what the Memtest screen looks like go to reply #21. The third screen is the Memtest screen.

Step1 - Let it run for a LONG time. The rule is a minimum of 7 Passes; the more Passes after 7 so much the better. The only exception is if you start getting errors before 7 Passes then you can skip to Step 2.

There are 8 individual tests per Pass. Many people will start this test before going to bed and check it the next day.

If you have errors you have corrupted memory and it needs to be replaced.

Step 2 – Because of errors you need to run this test per stick of RAM. Take out one and run the test. Then take that one out and put the other in and run the test. If you start getting errors before 7 Passes you know that stick is corrupted and you don’t need to run the test any further on that stick.


Link: https://www.techspot.com/vb/topic62524.html


* Get back to us with the results.
 
Sorry for not getting back sooner, but she has taken her time and has just recently ran memtest. We tried running the computer with only one stick of ram at a time and the error occurred no matter which one was installed. She ran memtest for a long time and never got any errors.

As far as your other suggestions, we have scanned for infections and haven't found any. And her bios does not allow the memory voltage to be changed.

We have discovered that she can browse through all her files without the error occurring by using 3rd party file browsers such as FreeCommander; whereas using windows explorer to navigate to certain folders or navigating to those folders using a program's open dialog can crash the computer. Using an alternative file manager works as a temporary solution, but she would still like to find the problem and fix it, and she is worried that there may still be something going on that could damage her computer. We wonder if it could be a problem with her windows installation as opposed to a hardware problem.

Any other ideas about how to troubleshoot this would be appreciated.
 
Do you have more minidump files? If so attache the five most recent since your last posting.
 
Here are the most recent minidumps, all a month old because she hasn't been using the computer much.
 

Attachments

  • Mini061510-01.dmp
    88 KB · Views: 0
  • Mini061510-02.dmp
    88 KB · Views: 0
  • Mini061610-01.dmp
    88 KB · Views: 0
  • Mini061610-02.dmp
    88 KB · Views: 0
  • Mini061710-01.dmp
    88 KB · Views: 0
Status
Not open for further replies.
Back