WinXP BSOD on startup (Everytime) Stop code 0X100000050

[Paul Goodyear]

spec
Intel P4 1.8GHz
512MB PC133 RAM
Elite P4vMM2 Motherboard

Recently removed a 256MB stick of RAM and replaced with a DDR stick that
this motherboard supports, Windows booted but behaved strangly, graphics
messy, and fonts not appearing. Changed RAM back to PC133 and system no
longer boots.

Stop code is always:
0x10000050 (0xcb140000, 0x00000000, 0x80511403, 0x00000000)

The mouse pointer appears 7 out of ten times and then the machien
restarts and trys again.

Changed RAM numerous times, grpahics card, all other cards removed.
Ghosted HD to another one and same problem.

Clean install works fine on current hardware.

Checked registry using ERD to detect any wierdness in the startup
registry but nothing.

What else can I try? Any suggestions to get this particular install up
and running again?

Thanks.

Paul.

 

[Ricky]

Maybe something here will help..
http://www.techspot.com/vb/topic21552.html

 

[Paul Goodyear]

Thanks, saw this article, but the problem is the system does not boot
full stop. So I have no way of altering the installed software.

I have used ERD and removed all startup software, virus etc. but still
no luck.

I think the OS its self has become corrupt in some fashion, I have
installed XP on this machine with another harddrive with no faults or
errors. But I would have thought a "Repair" would have overwrote any
corrupt files.

Paul.

 

[David Candy]

Driver Development Tools: Windows DDK

Bug Check 0x50: PAGE_FAULT_IN_NONPAGED_AREA
The PAGE_FAULT_IN_NONPAGED_AREA bug check has a value of 0x00000050. This indicates that invalid system memory has been referenced.

Parameters
The following parameters are displayed on the blue screen.

Parameter Description
1 Memory address referenced
2 0: Read operation
1: Write operation

3 Address that referenced memory (if known)
4 Reserved


If the driver responsible for the error can be identified, its name is printed on the blue screen and stored in memory at the location (PUNICODE_STRING) KiBugCheckDriver.

Cause
Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).

Another common cause is the installation of a faulty system service.

Antivirus software can also trigger this error, as can a corrupted NTFS volume.

Resolving the Problem
Resolving a faulty hardware problem: If hardware has been added to the system recently, remove it to see if the error recurs. If existing hardware has failed, remove or replace the faulty component. You should run hardware diagnostics supplied by the system manufacturer. For details on these procedures, see the owner's manual for your computer.

Resolving a faulty system service problem: Disable the service and confirm that this resolves the error. If so, contact the manufacturer of the system service about a possible update. If the error occurs during system startup, restart your computer, and press F8 at the character-mode menu that displays the operating system choices. At the resulting Windows Advanced Options menu, choose the Last Known Good Configuration option. This option is most effective when only one driver or service is added at a time.

Resolving an antivirus software problem: Disable the program and confirm that this resolves the error. If it does, contact the manufacturer of the program about a possible update.

Resolving a corrupted NTFS volume problem: Run Chkdsk /f /r to detect and repair disk errors. You must restart the system before the disk scan begins on a system partition. If the hard disk is SCSI, check for problems between the SCSI controller and the disk.

Finally, check the System Log in Event Viewer for additional error messages that might help pinpoint the device or driver that is causing the error. Disabling memory caching of the BIOS might also resolve it.

Comments
Typically, this address is in freed memory or is simply invalid.

This cannot be protected by a try - except handler - it can only be protected by a probe.

Send feedback on this topic. / Built on Thursday, February 13, 2003

It's quite possible that the driver at this address caused it 0x80511403. But it's useless to know if you can't boot.