richardd43 wrote on Jan 11
th, 2008 at 12:25am:
SYSTEM 8:14:42
Error code 10000050, parameter1 c2000516, parameter2 00000000, parameter3 8060bd93, parameter4 00000000.
ANTIVIRUS 8:12:45
AAVM - scanning error: x_AavmCheckFileDirectEx: avfilesScanReal of C:\Documents and Settings\Wendy\Recent\%temp%dd_msxml_retMSI.lnk failed, 0000007B.
Nick
This is the only information we could find at the time of the error. Hope it can help us figure out the problem.
This is Wendy. Dont try too hard. If it doesnt get fixed, I get his new computer
LOL!!
Now I see why he is sweating
What you have is a typical STOP crash which started with the AV not being able to read a file but went downhill from there.
The problem is, its a generic crash and since it did not list a hardware driver the list of possibilities is large.
The #1 reason for a STOP x50 is the memory either being defective or not set up correctly in the BIOS. Verify the BIOS settings for the memory (sometime AUTO is not best) you should be able to run MEMTEST in DOS to confirm no errors. Memory voltage being too low can do it too.
The AV itself or 3rd party software services can cause this error but that is rare. Usually it is the memory or another hardware device.
Here is Microsofts rundown on x50 STOP blue screens
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.
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 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). 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.
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 menu that displays the operating system choices. At the resulting Windows XP 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 the hard disk is SCSI, check for problems between the SCSI controller and the disk.
Warning
If your system partition is formatted with the file allocation table (FAT) file system, the long file names used by Windows XP can be damaged if Scandisk or another MS-DOS-based hard disk tool is used to verify the integrity of your hard 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 XP version of Chkdsk on Windows XP 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.
Microsoft periodically releases a package of product improvements and problem resolutions for Windows XP called a Service Pack. Because many problems are resolved by installing the latest Service Pack, it is recommended that all users install them as they become available. To check which Service Pack, if any, is installed on your system, click Start, click Run, type winver, and then press ENTER. The About Windows XP dialog box displays the Windows version number and the version number of the Service Pack, if one has been installed.
Occasionally, remedies to specific problems are developed after the release of a Service Pack. These remedies are called hotfixes. Microsoft does not recommend that you install a post-Service Pack hotfix unless the specific problem it addresses has been encountered. Service Packs include all of the hotfixes released since the release of the previous Service Pack. The status of hotfix installations is not indicated in the About Windows XP dialog box.
Pages: 1
