WinXP: intelppm.sys and processr.sys on certain processors

I needed to run "sc config p3 start= disabled " and "sc config intelppm start= disabled " in XP Safe Mode

Apparently happens with XP embedded too. (http://forums.virtualbox.org/viewtopic.php?t=1560)

New report:

Hi, I'm running VirtualBox 1.5.0 on Windows XP Pro and try to boot XP embedded for initializing (specifically that's XPe SP2, Feature Pack 2007, Update Rollup 1.0 - although I doubt that that makes a difference).

Just before the FBA (first boot assistant) starts, at least just before it shows its first window, I get a blue screen. The STOP error is DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS, the responsible driver file depends on the included processor component(s): "Processor" -> processr.sys "Intel Processor" -> intelppm.sys "Intel PIII" -> p3.sys

Best regards

Unfortunately, there is no easy way to carry out those registry changes in a newly built XP embedded guest: the OS has never been run and cannot be started at all.

However, as I just tested, as a first measure it helps to remove or rename processr.sys (or any other offending processor driver, probably).

Now, if I only knew, why there's another bluescreen (0x0000007B) when the system starts the first time after initialization. But that's another story, I suppose.

Another note: This applies for amdk6.sys and amdk7.sys as well.

We are observing this problem as well on some systems. Currently there is a workaround in our ASL code which should prevent Windows from loading this driver. However, this workaround (we just don't define an entry for a processor in the ACPI tables) seems to not work at every time.