STOP 0X00000050 on bootup, both normal and safe mode

Mwiemers
15 pts.
Tags:
Code
Dell Precision 370
Page fault
RAID 1
RAID 2
Windows Backup
Windows XP boot failure
Windows XP SP2
Have a Dell Precision 370 with integral Raid 1 on 2 hard drives, Windows XP Pro SP2. After various error messages, it consistently showed PAGE_FAULT_IN_NONPAGED_AREA and STOP 0X00000050 on bootup, whether a normal boot or safe mode. Dell diags identified defective RAM and an "uncorrectable data error" on the primary H.D. Repair attempts so far: » RAM has been replaced - tests good. » Defective H.D. removed - running on only the secondary drive, which diags showed as good. » Swapped video adapters with a similar machine - STOP error stays with this machine, so it's not the video adapter or memory. » Ran CHKDSK /R from Windows Recovery Console, says it "found and fixed one or more errors..." » Tried a Repair Installation of Windows XP from system CD. Ran through successfully except for a "COM+ Setup Error" (I have all the details if it will help). » Machine has always booted fine from Windows XP and Dell diag. CDs, but every attempt at a boot from hard drive still shows the same STOP 0X00000050 error. » I have an external HD enclosure for access to the good hard drive, so I can provide minidump file(s) or other info. if it will help. My best guess is corrupted O/S on the good hard drive. Any ideas on how I can get around the STOP error and boot into Windows? I'm hoping to save installed software and configurations without doing a complete fresh installation of Windows XP Pro -- that's my last resort repair.

Software/Hardware used:
Dell Precision 370, RAID 1, Windows XP SP2
Asked: Last updated:
Related Questions

Answer Wiki

Thanks. We'll let you know when a new response is added.

It could have been caused by update KB977165.

I would try removing all hardware devices (including CD/DVD ROMs) to see if that makes any difference.

If you have more than one memory module, I would remove all but one, and would try switching modules if the error persists.

Also, I would run CHKDSK /r from the recovery console again to see if it keeps finding errors.

One other thing to try would be disabling any unnecessary feature from the BIOS.

-CarlosDL

———-

Discuss This Question: 2  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • Mwiemers
    Just as followup, and to close this thread: I tried all of these suggestions and more - never found a way around the STOP error. » Used the BlueScreenView utility to analyze minidump files, which showed that the bootup kernel NTOSKRNL.EXE was the process causing the error. This would explain why it would not boot into Safe Mode. I find notes that a virus can alter this process, but a full scan with the hard drive in a USB enclosure showed no indications of viral infection, so it appears that we were unfortunate enough to have a hard drive that happened to be corrupted in a bad location. » Finally gave up on fixing the existing installation & reinstalled onto a new, larger hard drive.
    15 pointsBadges:
    report
  • Brijesh
    Check out this microsoft kb article . This will helps you to solve your problem.
    14,450 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.

Following

Share this item with your network: