Hyper-V Program Manager
Under certain circumstances with a Windows XP / 2003 operating system - intelppm.sys and processr.sys can cause a virtual machine running under Virtual PC / Virtual Server to crash (by default this will cause the Windows guest operating system to reboot automatically - but if you have changed this setting you will see a blue screen). The reason for this crash is because these drivers are attempting to perform an unsupported operation inside of the virtual machine (like upgrading the physical processors microcode, changing power state on the physical processor).
Today this problem only occurs on Centrino and AMD K8 processors. Most people see this problem when they move a virtual machine that was created on another type of processor to a computer running one of these types of processors (and then they usually see the problem when they attempt to shutdown their virtual machine for the first time). Now you may be wondering why you have not heard about this problem more often - and the reason for that is that if these drivers fail once - they are smart enough to not attempt to perform the operation that failed again.
If you are seeing this problem repeatedly you can manually disable these drivers (with no negative side effect) by going to the following location in the registry:
And changing the 'Start' value to '4'.
In the mean time we have made some subtle changes to the way our hardware exposes the processor in Virtual Server R2 so that in future products these drivers should never get loaded inside of virtual machines.
Thanks for this very useful tip. It's still a problem in October 2010. With your help I have successfully imported a virtual machine from my AMD based desktop to my Intel based Thinkpad. I had begun to think I was going to have to rebuild it completely. This has saved me hours of time. Thank you again.
I migrated a virtual XP machine from one Intel machine to another lower end Intel machine. I tried intelppm.sys start value to four but no luck so i placed both processor and intelppm.sys start values to four and it worked. Thanks for the post and your help this was a life saver.
WooHoo, that worked!
Thanks Virtual PC Guy! You da man!
Thanks man! It was really helped me!
The problem appeared when I updated VirtualBox to v 3.2.1. I spent whole day for that, and only your decision really helped.
Thank you Ben, you are VM god!
Prior to finding your blog I spend 3 days fruitlessly trying to boot Win7 and WinXP VirtualBox's that I copied
from a Dell Studio XPS Desktop development PC (Intel Core i7 Vista x64 PC with 12GB RAM) to a a Core i5-430UM Win7 x64 PC (HP TouchSmart tm2 with 8GB RAM).
Changed the Intellppm registry entries in the VMs and viola, they booted!
Ben, thanks for the post. I had exactly this problem with VirtualBox 3.2.12, Fedora Core 12 host on my Thinkpad X301 (Interl Centrino 2), WinXp Pro SP3 guest. Your workarounf did the trick. The driver in my case was Intelppm. Strange that the problem still persists five years after your post...
Anyway, you saved me the day. Thanks a lot!!!
thank you very much,that's so good!!
All these years later and this post still helped me out with an issue I was having tonight.
Thank you very much!
Thanks, you saved me a lot of time (preventing from installing new Windows OS)
I disabled through registry as you and said but i get the same error blue screen.
I even tried to remove vdi image and changed evry settings control and nothing helps :(
I even reinstalled xp and installed original microsoft xp and nothing helped.
so how do you fix this i have crossed all google pages but nothing can help me.
So do not understand what's going on here.
This is first time when this happens.
Incredible, 6 years later It works! I'm executing a Windows 7 64bits host and a XP as guest OS.
Thank you very much, I have been trying to figure this out all day, thank you.
Hi, I tried to move a Virtualbox VM from an AMD processor to an INTEL and I had this problem 0x000000CE
Maybe should I fix another key? maybe an AMD key??
Thx, solved my virtual box troubles ?
Sir, you're my god! Couldn't believe this page was the first option i found when googling for intelppm.sys.
Thanks a lot!