Share via

Windows XP BAD_POOL_CALLER

Anonymous
2022-01-12T04:17:10+00:00

I know my computer is old but please help it is an acer aspire one windows xp it boots up fine but when it gets to the login screen is shows this code BAD_POOL_CALLER STOP:0x000000C2 (0x00000043, 0xDEEB0000, 0x00000000, 0x00000000).

I have tried last good configuration in advanced startup options but that didn’t work I also tried safe mode but same thing. I need help please.

Windows for home | Previous Windows versions | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2022-01-27T14:44:08+00:00

    Here are some ideas:

    1. Check your system drive for errors, using a bootable USB stick or CD.

    If the drive has errors, you will have to replace it, I recommend buying a SSD. Any decent cheap one will do fine for a Netbook.

    1. Check memory with a bootable MemTest86+ USB Stick or CD.

    Do at least 2 passes.

    If you have errors, you will have to replace the memory.

    1. If 1&2 don't work, backup your important data from your drive, as you will have to reinstall Windows. You will need an XP CD with a product key, or XP on USB via Easy2Boot.

    Delete all partitions in setup, create a partition and format it with NTFS (quick).

    After entering the product key and finishing setup, you will have to install drivers.

    Unless you are slipstreaming SATA drivers onto the XP CD/USB Stick, you will have to set the SATA operation mode in the BIOS to something like IDE/Native/Legacy/Compatible, as XP and older do not natively support AHCI without slipstreaming drivers.

    0 comments
  2. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more