BAD_POOL_CALLER
-
I just got back from holiday, to find my Windows XP PC has somehow started getting this error (BAD_POOL_CALLER 0x000000C2). I can only assume it did a windows update or something before I turned it off and went away. The first parameter of the error is 0x43, which the KB says is something to do with a corrupt pool header. I get the error just after the windows loading bar, I think when it tries to load the login. Does anybody have any ideas as to what is causing it? Im pretty sure its not a hardware problem memory wise, as I ran memtest and it passed.
-
I just got back from holiday, to find my Windows XP PC has somehow started getting this error (BAD_POOL_CALLER 0x000000C2). I can only assume it did a windows update or something before I turned it off and went away. The first parameter of the error is 0x43, which the KB says is something to do with a corrupt pool header. I get the error just after the windows loading bar, I think when it tries to load the login. Does anybody have any ideas as to what is causing it? Im pretty sure its not a hardware problem memory wise, as I ran memtest and it passed.
From what I've seen Googling the message, it looks like you've either got a driver problem or a hardware problem. You can TRY to get a crash dump and run it through WndDbg. See this[^] for a bit of an explaination. You can also try to strip the machine down to nothing but a power supply, motherboard, RAM, and the Windows hard drive and see what happens. If it works, try adding one device back to the machine. Keep going until it fails again. Or, you're last resort is to reinstall Windows.
Dave Kreskowiak Microsoft MVP - Visual Basic