Networks

Ask something
Discussion Locked

BSOD STOP 0x50

0 helpful
9 replies

by william j sosville 2 views

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I am an administrator of 12 HP netserver LH3 application servers. One particular server has been recieving the BSOD STOP 0x50 PAGE_FAULT_IN_NONPAGED_AREA... the server had lop-sided processor times 90%/20% with processor queue lengths in excess of 7. HP has replaced a processor (dual PII 400)and the processor times are now equal yet very high 90% for each. The STOP 50 continues with failures arriving nearly the same time during weekday mornings. Never on weekends and never after 11am. Also after monitoring other identical servers some have processor queue lengths that avg 14 and never have any problems or failures, the servers are identical Dual PII 400, 256MB RAM. Could this be a RAM issue?

9 replies

by rcc

Hi
According to MS, " Stop 0x00000050 or PAGE_FAULT_IN_NONPAGED_AREA
This Stop message, also known as Stop 0x50, occurs when requested data is not found in memory. The system generates a fault, which normally indicates that the system looks for data in the paging file. In this circumstance, however, the missing data is identified as being located within an area of memory that cannot be read to disk. The system faults, but cannot find, the data and is unable to recover. Faulty hardware, a buggy system service, antivirus software, and a corrupted NTFS volume can all generate this type of error. "
Try identifying which process takes 90% of your prosessors. You can do this in Task Manager.
Also, try tunning the swap file and run a chkdsk on your volumes.

I hope this helps.If you need further assistance, let me know.

Regards,
Radu

by rcc

PART 1
Additional INFO from MS. It applies to NT4 as well.

Interpreting the Message
The four parameters listed in the message are defined in order of appearance as follows:

Virtual address which caused the fault
Type of access (0 = read operation, 1 = write operation)
If not zero, the instruction address which referenced the address in parameter 1
Opaque information about the stop, interpreted by the kernel
Resolving the Problem
Faulty hardware. Stop 0x50 usually occurs afterthe 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). 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.
"

by rcc

PART 2 - Additional info

"
Buggy system service. Often, the installation of a buggy system service is a culprit. 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 screen that displays the prompt "For troubleshooting and advanced startup options for Windows 2000, press F8." At the resulting Windows 2000 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.

Antivirus software. Antivirus software can also trigger this error. Disable the program and confirm that this resolves the error. If it does, contact the manufacturer of the program about a possible update.

Corrupted NTFS volume. A corrupted NTFS volume can also generate this error. 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 you cannot start the system due to the error, use the Recovery Console and run Chkdsk /r. For more information about the Recovery Console, see chapter "Repair, Recovery,and Restore" in this book. If the hard disk is SCSI, check for problems between the SCSI controller and the disk.
"

by rcc

PART 3 - Additional Info
"
Warning If your system partition is formatted with the FAT16 file system, the long file names used by Windows 2000 can be damaged if Scandisk or another MS-DOS-based hard disk tool is used to verify the integrity of yourhard disk from an MS-DOS prompt. (An MS-DOS prompt is typically derived from an MS-DOS startup disk or from starting MS-DOS on a multiboot system.) Always use the Windows 2000 version of Chkdsk on Windows 2000 disks.

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 this error."

by william j sosville

I used the same Technet article you quoted from. The idle process is the dominent process, no new hardware or installs within the last 6 months.

by rcc

Hi
You should have mentioned it in your innitial posting...
Have you tried applying the latest SPs and hotfixes? I had a similar problem once with some services I've reinstalled from the original CD, without reapplying SPs...
Regards,
Radu

by frobo

Hi,

yes this seems to be an RAM issue,
if you use the Diagnostic Tool from HP it could be that you have Messages in the CMOS-Log.

Frobo

by william j sosville

HP TopTools is of no assistance whatsoever It merely takes a snapshot of the current system state. The Diagnostic boot option (F12) is usless as well. All show no signs of trouble.

This discussion is closed to new replies.