STOP: 00000050 Error

[emjaydee]

I've just installed SMS Server 2.0 & SQL Server 7.0 onto a fresh install of Windows 2000 Server. Patched Win2K to the limit, and SMS & SQL to SP4. This worked fine for a day, but today it's started crashing with the following error:

STOP: 0X00000050 (0XB547287F, 0X00000001, 0X813969A6, 0X00000000)
PAGE_FAULT_IN_NONPAGED_AREA

Anyone got any ideas?

Rgds

 

[gurner]

Check this MSDN posting

Explanation:
This Stop message 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 paged out 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.

User Action:
This Stop message usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, either 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. Run hardware diagnostics supplied by the system manufacturer. For details on these procedures, see the owner’s manual for your computer. Another cause of this Stop message is the installation of a buggy system service. Disable the service and determine if 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 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 can also trigger this Stop message. Disable the program and determine if this resolves the error. If it does, contact the manufacturer of the program about a possible update. A corrupted NTFS volume can also generate this Stop message. Run Chkdsk /f /r to detect and repair disk errors. 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 causing the error. Disabling memory caching of the BIOS might also resolve it. For more troubleshooting information about this Stop message, refer to the Microsoft Knowledge Base at

http://support.microsoft.com/support.

 

[emjaydee]

I've had a look at this, and all the hardware appears to be working fine. None of it has been changed since it was installed. Just to check it further I installed the software on to a different machine. On this other machine I was able to stop this error by disabling the Video Shadow, but then I started getting a STOP: 0x0000001E error

Any help would be appreciated

 

[BradSQLGuy]

This is what causes 1E stop messages.
1. Lack of disk space for installation.

2. Third-party video drivers (and the Windows Win32k.sys driver).

3. System BIOS incompatibilities.

To resolve this issue, use the appropriate method below:

1. Reinstall on another hard disk when disk space is low.

2. Remove the third-party video driver.

3. Upgrade the system BIOS.

Personally from the looks of it. My suggestion is first try reapplying the patches. If that doesn't work I'd try uninstalling both applications and loading SMS first. Apply the patch and see how it works. Then reinstall SQL and apply the patch. Somewhere along the line it's possible one of the patches were corrupted upon installation. I don't see any compatiblity issues but only you know what software and hardware drivers you have installed. Also from what I've seen an 0x50 stop is alot of the times bad RAM. You might want to try swapping chips or even reseating them might work. Good luck. -Brad
A+, MCSE NT4, MCDBA SQL7

-Best cartoon of all time :-D 'Spongebob Squarepants'