Serious error your computer has been recovered from

Topic

New Reply

Can anyone interprete those pics, please?

I have old machine end XP OS.

I notices severe slowness of the computer, one by one features are dropping out, I san’t watch videos on twitter and most of videos, Youtube often warns me on non-updated browser but I am mostly working on Word so I suffer in silence,

Just a half an hour ago when I turned on desk top I saw this message

Your system has been recovered form serious error.

I clicked on to see what error it is and I attach 2 pics.

My desktop can drop dead any minute, right?

Is it so serious?

 

Reply | Quote

Replies

STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
Usual causes: Defective hardware (particularly memory – but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS

The crash happened during a write to memory.

The above causes are listed in order of liklihood, based on Carrona’s study of many thousands of BSOD troubleshooting topicsfrom the mid-2000s on. Below is the official MS reference page for debugging (which only really became possible from Vista/W7, it’s still a random hit and miss ‘if you’re lucky’ situation with XP BSODs).

WinDbg Help File Entry:

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.

Reply | Quote