bklynbound01
asked on
help rescue my Dell Dimension E521
Hello all.
I keep getting this page fault in non area BSOD page when my pc starts up.
I ran memtest to check each dimm separately on the pc and there were no errors.
I ran the drive tests from western digital and found no drive errors.
I can't enter safe mode or go back to last know config. Is windows just too messed up to boot? or am I missing a hardware issue?
page fault in non paged area
0x00000050 (0xc1ec0000, 0x00000000, 0x8053a8d3, 0x00000000)
these numbers seem to change with every boot
I keep getting this page fault in non area BSOD page when my pc starts up.
I ran memtest to check each dimm separately on the pc and there were no errors.
I ran the drive tests from western digital and found no drive errors.
I can't enter safe mode or go back to last know config. Is windows just too messed up to boot? or am I missing a hardware issue?
page fault in non paged area
0x00000050 (0xc1ec0000, 0x00000000, 0x8053a8d3, 0x00000000)
these numbers seem to change with every boot
noxcho
Have you installed anything recently? Any driver or software?
It would suggest something wrong with the Windows installation itself. Load the XP installation CD and then enter the recovery console. Once in the recovery console enter "chkdsk C: /f" without the quotes. This will scan the drive for problems with the XP installation and repair them if it can.
ASKER
i just tried getting into recovery mode with the xp cd and when i hit r I got the BSOD screen again
Download ERD Commander (http://www.fullandfree.info/software/erd-commander-2005/) and burn it to CD. Boot it up and see if that can access the partition. If it can it also has several diagnostics and repair tools that can fix problems with XP. If that also BSOD then you either have a hardware problem, or more than likely your XP installation is FUBAR. Try reinstalling XP. If it fails to reinstall then it's a hardware fault.
To troubleshoot Stop error 0x00000050
1.Remove any newly installed hardware (RAM, adapters, hard disks, modems,
and so on).
2.Run any system diagnostics supplied by your computer manufacturer,
especially the memory check.
3.Verify that any new hardware or software is properly installed. If this is
a new installation, contact
your hardware or software manufacturer for any Windows 2000 updates or
drivers you might need.
4.If the computer is formatted with NTFS, restart your computer, and then
run Chkdsk /f /r on the
system partition. If you cannot start the system due to the error, use the
Command Console and run
Chkdsk /r.
5.Disable or uninstall any antivirus programs.
6.Disable BIOS memory options such as caching or shadowing.
Also:
http://support.microsoft.com/kb/171003
These both seem to support the faulty ram as an indication of what is wrong. Replace the ram and see if you still get the problem. The fact that you are getting this while accessing the recovery CD shows it's likely not the hard drive.
1.Remove any newly installed hardware (RAM, adapters, hard disks, modems,
and so on).
2.Run any system diagnostics supplied by your computer manufacturer,
especially the memory check.
3.Verify that any new hardware or software is properly installed. If this is
a new installation, contact
your hardware or software manufacturer for any Windows 2000 updates or
drivers you might need.
4.If the computer is formatted with NTFS, restart your computer, and then
run Chkdsk /f /r on the
system partition. If you cannot start the system due to the error, use the
Command Console and run
Chkdsk /r.
5.Disable or uninstall any antivirus programs.
6.Disable BIOS memory options such as caching or shadowing.
Also:
http://support.microsoft.com/kb/171003
These both seem to support the faulty ram as an indication of what is wrong. Replace the ram and see if you still get the problem. The fact that you are getting this while accessing the recovery CD shows it's likely not the hard drive.
You mentioned that you tested your RAM by checking each DIMM separately. Do you mean by that that you removed all DIMMS except one, ran memtest, and then tried it with another DIMM? In the same slot each time? If so, then you've tested all your DIMMS, but you've only tested one slot.
Have you tried starting Windows with only one DIMM installed? And then with another one?
Have you tried starting Windows with only one DIMM installed? And then with another one?
ASKER
erd commander won't boot, i still get the bsod.
i am running memtest and checking all dimms in the second dimm socket now.
i am running memtest and checking all dimms in the second dimm socket now.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.