I have a virtualbox with Windows XP.
Today suddenly it restarted. And then it started to restart repeatedly. When MS Windows reaches the logon screen it restarts again and again and again.
I entered in Safe mode. I went to see the system event log. And it was saying:
“The computer has rebooted from a bugcheck. The bugcheck was: 0x100000ce (0xf76bc8f8, 0x00000000, 0xf76bc8f8, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini012010-02.dmp.”
“Error code 100000ce, parameter1 f76bc8f8, parameter2 00000000, parameter3 f76bc8f8, parameter4 00000000.”
I switched off the automatic reboot after the BSOD. And I saw that the error was in file intelppm.sys
I searched the internet and I found out the following solutions which helped me:
This one solved my problem!!!
Problems with Intelppm.sys and processr.sys under Virtual PC / Virtual Server
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.
and this if one other way to do the same thing http://kb.parallels.com/en/5750
1. Attach Windows Installation CD to Virtual Machine (Parallels Desktop top menu -> Devices -> CD/DVD Rom).
2. Change boot sequence for Virtual Machine to boot from CD (Parallels Desktop top menu -> virtual Machine -> Configure -> Boot Order)
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:
You will see service current status SERVICE_DISABLED
9. Exit Recovery Console typing ‘exit’.
10. Restart Virtual Machine. Windows should be booted properly.
So if you face the same problem, I hope this may help you too.
And remember the saying of a wise man:
If Microsoft ever make anything that does not suck it will be a Vacuum cleaner