Page fault in nonpaged area?

TrollMan

Member
Dec 2, 2000
55
0
0
I have been having this problem before, but thought it was due to my rapidly-dying motherboard and-or hard drive. However, with a spangly new Epox 8RDA+ and 80Gb Western Digital HDD (with fresh install of windows XP) I have started encountering the same problem again - what could be causing this?

Basically, when I switch the PC on, it takes 4 or 5 attempts to boot as I get stop errors saying "page fault in nonpaged area" citing Ntfs.sys as the culprit (with a different internal address each time). Also I sometimes get stops in 0x0000050 - what does this refer to? Once I get the PC into Windows I have occasional problems (especially with IE and explorer randomly crashing with no error) but if I reboot I get no stop errors unless I leave the PC switched off for more than about an hour...

Is this due to dodgy RAM or is it something I have failed to set up or what?

System:
Althon XP 1900+ (Palomino)
512MB DDR 2100 RAM
Epox 8RDA+ (set at 133MHz)
80Gb Western Digital HDD (primary master)
60Gb IBM DeathStar (primary slave)
Asus 12x DVD
Philips DVD/CD-R/W combo drive
Connect3D Radeon 9700 (non pro)

Any ideas?
 

TrollMan

Member
Dec 2, 2000
55
0
0
*bump*

Checked IDE connections and they are fine, also moved RAM to a different slot but still no joy!

Anyone have any ideas?
 

kursplat

Golden Member
May 2, 2000
1,547
0
0
1 stick of ram ? or more ? try 1 stick at a time if you have more . try your ram in another comp - try diferent ram in your comp - try memtest
good luck
 

TrollMan

Member
Dec 2, 2000
55
0
0
Every time I try to extract Memtest (before even rebooting into DOS to run it) I get a stop error saying PFN_LIST_CORRUPT

What is this?
 

Lipservice

Senior member
Oct 17, 2001
542
0
71
PFN_LIST_CORRUPT... This behavior occurs because a driver or other problem damaged the input/output (I/O) driver structures. PFN stands for 'Page Frame Database' I understand it is caused by corrupting I/O driver structures. If the kernel debugger is available, get a stack trace. This also may indicate that the memory management Page File Number list is corrupted. It can be caused by corrupt physical RAM.

 

TrollMan

Member
Dec 2, 2000
55
0
0
Thanks :)

A friend lent me two 256MB sticks of DDR2100 Infineon RAM last night so I took out my 512MB stick and tried them - booted up first time, no IE crashing, nada... I think I have my answer!
 

Motero

Senior member
Jan 31, 2001
889
0
0
I am having this problem with a pc I just got in for service. It's a compaq with win 2k...it will boot to safe mode, but not in normal mode. The ram is not the issue...i'm assuming its a driver issue, but I have tried removing various ones with no success. Any more help? I also tried to do a repair on the installation using the win 2k cd...any other options?
 

Motero

Senior member
Jan 31, 2001
889
0
0
I figured it out. I uninstalled all the drivers and booted to normal mode. Then installed sp3 and an older nvidia driver.