Page 1 of 1

BAD_POOL_CALLER error / BSOD on XP start

Posted: 24. Sep 2009, 09:27
by BVE
Background info:
I'm runing Ubuntu 9.04 as the host OS.
I was running VBox 2.2 with guest additions installed.
Upgraded to 3.06 after a complete removal of version 2.2.
Now my Windows XP guest boots, gets to after the splash screen, then flashes a BSOD and immediately reboots.
Keeps doing this forever.
After pausing the VM I found the BSOD was giving a BAD_POOL_CALLER error.

After searching for a solution, I found some older bug / ticket, but the solution is for an older version of VBox.

Extra info: Startint windows in Safe Mode does work. No idea what to install / remove or if it's even related to the XP guest OS (might be a problem with the install on the Ubuntu host OS).

I'm at a loss right now. Can anybody help me out?


thanks

Re: BAD_POOL_CALLER error / BSOD on XP start

Posted: 24. Sep 2009, 15:44
by Perryg
Is the IO-APIC enabled in the guest settings and is this a 32 or 64 bit os/guest?

Re: BAD_POOL_CALLER error / BSOD on XP start

Posted: 24. Sep 2009, 16:17
by BVE
yes it's enabled

and

everything is 32 bit

Re: BAD_POOL_CALLER error / BSOD on XP start

Posted: 24. Sep 2009, 16:54
by Perryg
That's bad. Version 3.x.x is smp aware and since the IO-APIC was enabled it has triggered XP to update its kernel.
I had the exact same thing happen to me. Here is how I fixed it.
  • (1) boot XP in safe mode
    (2) use system restore to take it back to before the update.
    (3) Instead of rebooting I told it to shut down.
    (4) took the checkmark out of IO-APIC and started the guest.
Hopefully this will work for you as well.

Re: BAD_POOL_CALLER error / BSOD on XP start

Posted: 25. Sep 2009, 08:23
by BVE
edit 1: Spoke too soon. Going back to the last known working config does get XP up and running, but I have to do this at EVERY boot right now. I'm trying again :)
edit 2: at first I got it working without disabling IO-APIC, but that only made it work once. Redid your entire instructions (as I should have in the first place :) ) and it seems it did the trick!

Note: I got a completely different BSOD error today after first start, so maybe we need a different thread title? Makes it easier for others to search in the future :)

thanks!