XP embedded: processr.sys vs intelppm.sys

[ujr]

Hi,

I'd like to build a VM of Windows XP embedded.

In order to keep it simple I have a flat vmdk harddisk image, where I copy the XP embedded to. I can boot this system. Unfortunately shortly after booting, right before the XP embedded initialization starts, I get a blue screen:

DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS

The responsible driver differs, whether I include the "processor" component, "intel processor" component or "intel PIII processor" component: it's processr.sys, intelppm.sys or p3.sys, respectively.

Has anyone experience or a slight idea how I can prevent this BSOD?

BTW, I doubt that the XP embedded image is the culprit, because it works in VMWare server. However, I would prefer to use VirtualBox...

Thanks!

[sandervl]

This driver has some bugs. We added a workaround for it before, but apparently that doesn't work with XP embedded.

Could you create a ticket on our bugtracker? Unfortunately there's no quick solution. I'm not sure if XP will work if you simply delete this driver.

[ujr]

Thank you for your reply!

Could you create a ticket on our bugtracker?

Done.

Best regards

[sandervl]

Forgot that there's already one. (420) We'll discuss it there, ok?

There's a workaround documented here:
http://blogs.msdn.com/virtual_pc_guy/ar ... 84461.aspx

[j3ffyang]

Configuration: host OS = Ubuntu 9.04 VirtualBox = 3.0.0 Guest OS= Windows XP SP2

I received the same symptom

1. Windows crashes during boot
2. The dump says
DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS

which is related to intelppm.sys

Tried to remove intelppm.sys, but didn't work.

Fixed by http://blogs.msdn.com/virtual_pc_guy/ar ... 84461.aspx

[telerian]

How can I do the registry key workaround when I can not boot the VM ?