PAGE_FAULT_IN_NONPAGED_AREA --> goin nuts, please assist

[TheVoice]

Hello people,

This is one of the most useful XP forums I've seen. I hope someone can help me analyze the minidumps I sent. I am completely out of ideas. :dead:

PC: AMD Athlon XP 2000+
ABIT KG7-Raid board
Disks attached to RAID channels (single disks, no raid mode)
2x256 MB RAM
ASUS V7100 Pro Video card (=GF4 mx200)
Windows XP SP1 (SP2 installation BSOD's on me when starting with unpacking files)

This is the situation: After a disk crash (Parents' PC) I repaired the original disk and installed a new disk as primary boot disk. I first repaired the original XP installation, but:

I kept and keep getting the PAGE_FAULT_IN_NONPAGED_AREA BSOD's which point at ntfs.sys, stop code 0x50. They happen every time I try to start any significant action (in my case, windows updates)

I already ran memtest, and found errors in test 5 (=stress test). I swapped memory modules but they both acted the same, so I concluded that bios timings were too tight. I relaxed the memory timings and errors are now gone.

I completely reinstalled the PC (XP SP1) and everything went ok. Installed many drivers, and things went still ok. Then I installed DirectX9 and after this, same crashes again. It points at the video card but still.. can be a coincidence.

The BSOD always looks the same so analysis should be easy. Would someone be so kind to check my attached minidump files? Thank you very much..
I've been working on this for days now, getting really tired about it.

 

[howard_hopkinso]

Hello and welcome to Techspot.

All your minidumps crash at hptpro.sys. This is your raid contoller driver.

Try uninstalling/reinstalling the drivers. Try searching for updated drivers.

Regards Howard :wave: :wave:

 

[TheVoice]

Hi,

I followed the manuals regarding minidump analysis - very useful! I found out the same thing.

Unfortunately the hpt driver problem seemed to have a different cause. Something was apparently broken on the motherboard. I actually replaced it.

Another problem was that the partition table on the primary disk (previously connected to the HPT RAID Controller) was damaged. This probably caused the hpt driver error.

New Mobo (K3T Ultra) gives much less problems, and repairing the partition table finalized the trick

Thanks for your help, I will keep checking this forum!

 

[howard_hopkinso]

Glad your problem is solved.

Thanks for letting us know.

Regards Howard

 

[cpc2004]

Hi,

This problem is similar to following problem
https://www.techspot.com/vb/showthread.php?p=181704#post181704

The stack trace of this problem
STACK_TEXT:
f896d798 f83ccb22 00000400 b96ee000 00000400 Ntfs!NtfsTransformUsaBlock+0x90
f896d984 f83cc4f1 f896d994 81531208 0110070a Ntfs!NtfsCommonWrite+0x182f
f896daf8 804eca36 818b3420 81531208 81f79b20 Ntfs!NtfsFsdWrite+0xf3
f896db08 f84683b8 815404f8 8189f758 f896db5c nt!IopfCallDriver+0x31
f896db18 804eca36 818b21e0 81531208 81f8db20 sr!SrWrite+0xa8
f896db28 f894a31d f894a2fe 8189f758 81531208 nt!IopfCallDriver+0x31