BCP1: 0000502065685420
Code A is usually related to either the BIOS or Power and not anything to do with the operating system or hardware.
http://aumha.org/a/stop.php#0xa5
0x000000A0: INTERNAL_POWER_ERROR
0x000000A1: PCI_BUS_DRIVER_INTERNAL
0x000000A2: MEMORY_IMAGE_CURRUPT
0x000000A3: ACPI_DRIVER_INTERNAL
0x000000A4: CNSS_FILE_SYSTEM_FILTER
0x000000A5: ACPI_BIOS_ERROR
(Click to consult the online MSDN article.)
The cause of this message is always errors in the ACPI BIOS. Usually, nothing can be done at an operating system level to fix the problem. See the articles linked here for more details.
- 0x000000A5 {KB 256841} Win 2000, Win XP (when installing Win 2000 or later)
- “Stop error 0xA5” error message when you dock a Win 2000-based portable computer to a docking station while the computer is running {KB 840172} Win 2000 (hotfix available)
0x000000A6:
0x000000A7: BAD_EXHANDLE
0x000000A8:
0x000000A9:
0x000000AA:
0x000000AB: SESSION_HAS_VALID_POOL_ON_EXIT
(Click to consult the online MSDN article.)
This indicates that a session unload occurred while a session driver still held memory. Specifically, a session driver is not freeing its pool allocations prior to a session unload. This indicates a bug in win32k.sys, atmfd.dll, rdpdd.dll, or a video driver.
- A Terminal Services Server Generates a “Stop 0xAB” Message on a Blue Screen {KB 317855} Win 2000 SP1 & SP2 (SOLUTION: Upgrade to SP3 or later)
- You may receive a “Stop 0x000000ab” error message logging off a Terminal Services session on a Windows Server 2003 SP1-based Terminal Server {KB 901150} Server 2003 SP1 (Caused by mismanagement of a font object. Hotfix available. WORKAROUND: Remove SP1. SOLUTION: Hot fix available from Microsoft.)
- You receive a “Stop 0x000000ab” error message logging off from a Terminal Services session on a Windows Server 2003 SP1-based Terminal Server {KB 907242} Server 2003 (Bug in Win32k.sys, Stmfd.dll, Rdpdd.dll, or a video driver; hot fix available from Microsoft)
LibreOffice
Firefox
No comments:
Post a Comment