v4 upgrade (?) gives BSOD with an intelppm.sys error

synner

Bit poster
Like many others I have problems with the upgrade to v4.

I'm using a Bootcamp partition for my Virtual machine. Win XP Pro SP2 updated and updated and updated. Not sure where it's at, but it doesn't have any further updates to do. OS X 10.5.5 is the Guest OS. 2Gb Ram, and plenty of disk space. Auto login is enabled in Windows.

I get through the update right up to the prompt to do a manual update, the virtual machine then starts the boot process and gets to loading the user settings, then I get a BSOD with a intelppm.sys error which is a CE error. (see attached)

Now I assume this is all getting looked at, and I am prepared for a certain amount of product testing - particularly when you update at the bleeding edge, but this is terrible! This should not have been released in the state it's in at the moment.

That said I do appreciate the amount of work it must be to get windows working like this, and hopefully we'll get a solution soon.
 

Attachments

  • Picture 2.jpg
    Picture 2.jpg
    22 KB · Views: 10
I think this is the first report of such kind of a problem during upgrade.

The solution:
1. Attach Windows Installation CD to Virtual Machine.
2. Change boot sequence for Virtual Machine to boot from CD
3. Start Virtual Machine.
4. Immediately after VM is started, press Control+Option+Command+R key combination and agree to proceed to manual mode.
5. After you get your console unlocked, capture input and press any key so that VM boots from CD.
6. Once you see a first prompt from Windows, type "R" to enter recovery console.
7. In Recovery Console wait for a prompt to choose your installation, type '1' followed by Return and enter administrator password
8. Run the following command:
Code:
disable intelppm
You will see service current status SERVICE_DISABLED
9. Exit Recovery Console typing 'exit'.
10. Virtual Machine will be restarted, and Windows will boot properly.
 
Last edited:
further info

Thanks for the reply.

Through a mixture of brute force and sheer perseverance, I've managed to get most of the way there. Mainly by crashing out of the update process using ctrl-opt-cmd-r and booting the vm manually and helping it along each time and then crashing it closed and restarting it.

Anyway, I can now get the virtual machine to boot every time, but with a couple of problems.

Every boot the vm finds a PCI device and a VGA device that need installation.

I cannot install the Parallel tools. Every time I try it fails when installing the Shared folder option and then rolls back.

I've attached the parallels-tools-setup.log

Ticket number 12293
 

Attachments

I cannot install the Parallel tools. Every time I try it fails when installing the Shared folder option and then rolls back.

I've attached the parallels-tools-setup.log

Ticket number 12293

Thank you for the logs and report. I have created a support ticket with solution that should help. Please notify me if you will not receive mail with solution in fifteen minutes.
 
Thanks for the rapid response to these problems.

To all those with issues still, submit all the info about your setup you can through the correct channels (Help menu - report a problem) attach all you can, and these guys are on the case and will help.

Thanks again
 
Back
Top