Pozrel som MSDN Library a nasiel toto. Kedze neviem presne kody, tak iba takto vseobecne. Je to vsak pre W2k, pre XP tam nic s chybami co si napisal nebolo.
Kód:
SYMPTOMS
When you use a Windows 2000-based computer, you may receive the following error message on a blue screen:
STOP 0x0000004E PFN_LIST_CORRUPT (Parameter1, Parameter2, Parameter3, Parameter4
1 - value 1
2 - ListHead value which was corrupt
3 - number of pages available
4 - 0
1 - value 2
2 - entry in list being removed
3 - highest physical page number
4 - reference count of entry being removed
CAUSE
This behavior occurs because a driver or other problem damaged the input/output (I/O) driver structures.
MORE INFORMATION
To troubleshoot this behavior:
Run hardware diagnostic tools that are provided by your computer manufacturer.
Disable all file system filter drivers, such as backup utilities, virus scanners, or firewall software.
View the following Microsoft Web site to verify that the hardware and the drivers for the hardware are compatible with Windows 2000:
http://www.microsoft.com/hcl/default.asp
For information about the hardware on your computer, contact the manufacturer.
If you receive this error message randomly, or when you try to start a program, remove extra memory or have the random access memory (RAM) in your computer tested. This behavior may occur if you have bad RAM.
Kód:
SYMPTOMS
If you are running Windows 2000, you may receive the following error message:
STOP 0x0000001A (parameter, parameter, parameter, parameter)
MEMORY_MANAGEMENT
For example:
Stop 1A (0x00000001, 0x00000043, 0x00024893, 0xffffffff)
The first parameter is 1, therefore the subtype is "The fork clone block reference count is corrupt. Only occurs on checked builds."
Everything else, must be examined individually.
CAUSE
This issue can indicate the existence of a general memory-management problem. The error message that is mentioned in the "Symptoms" section of this article is a Windows 2000 Executive character-mode STOP error message.
RESOLUTION
To resolve this issue, use the appropriate method:
If this is the first time you have started the computer after you install new hardware, remove the hardware and restart your computer.
View the following Microsoft Hardware Compatibility List Web site to verify that the hardware and its drivers are compatible with Windows 2000:
http://www.microsoft.com/hcl/default.asp
For more information about your hardware, contact the manufacturer of your hardware.
If you are installing Windows 2000 for the first time, verify that your computer meets the Windows 2000 system requirements, including the amount of RAM and disk space that are required to install the operating system.
If Windows 2000 is loaded and no new hardware has been installed, restart your computer with the recovery options set to create a dump file. If the error message that is mentioned in the "Symptoms" section of this article continues to appear, select the Last Known Good option when you restart your computer. If there is no Last Known Good configuration, try to use the Emergency Repair Disk (ERD).
For additional information about Emergency Repair Disks, click the article number below to view the article in the Microsoft Knowledge Base:
231777 How to Create an Emergency Repair Disk in Windows 2000
For additional information about the Last Known Good configuration and other Windows 2000 boot options, click the article number below to view the article in the Microsoft Knowledge Base:
202485 Description of Safe Boot Mode in Windows 2000