July 20, 2009 @ 9:56
VirtualBox 3.0 BSOD
After updating VirtualBox from 2.2.4 (OSE) to full VirtualBox 3.0.2 I saw constant BSOD on guest Windows XP machine.
After googling for misbehaving intelppm.sys that was causing the BSOD I found this VirtualBox ticket #420 with this issue.
It seams that on Centrino hardware during the update of VirtualBox the Guest os now sees different CPU, and after the new CPU is installed intelppm.sys driver causes BSOD.
The solution is simple, open regedit go to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Intelppm
after changing the ‘Start’ value to ’4′ and rebooting everything works ok.
Thanks to Virtual PC Guy for his great blog entry regarding this issue.
5 Comments »
RSS feed for comments on this post · TrackBack URI
Posted by Pav
January 26, 2010 @ 15:31
Thx 4 this… it was exactly what was wrong and the perfect solution.
Posted by valent
January 28, 2010 @ 19:57
Glad to hear it helped.
Posted by Troyhy
September 13, 2010 @ 22:06
Thanks, this error was making VirtualBox windows clients almost unusable.
Posted by Marcos Di Fazio
November 24, 2010 @ 18:47
Amazing, this is i am looking for.
Im not updated my virtual box, instead i changed same values to the procesor settings for the guest and after that the BSOD apears
Posted by PodeCoet
December 5, 2011 @ 4:26
Thanks alot for this! I’ve been searching for hours, your solution worked perfectly