We have VM windows Server 2012 R2 and it running on Windows 8.1 host machine.
We did Windows updates for the Server 2012 and rebooted the VM but it came with the error message:
Your PC needs to restart.
Please, Hold down the power button.
Error code:0x000000c4
Parameter:
0x0000000000000091
0x000000000000000F
0xfffff802B6DD0A00
0x00000
And it give us two options, OK to turn of the machine of Ignore to debugging. If click OK it will turn off the machine and if I restart it again it comes to the same error message after few second of Windows log appearance. If I click Ignore, it stay on the same error message.
Version of used VirtualBox is: 4.3.12 r93733
Please, and help to make this VM server to start up again.
VM can not startup again Error code: 0x000000c4
-
KnightofPeace
- Posts: 2
- Joined: 27. Jul 2020, 12:42
-
scottgus1
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows, Linux
Re: VM can not startup again Error code: 0x000000c4
The guru meditated over a 'triple fault', which basically means the guest tried something so unusual that Virtualbox couldn't figure out how to respond and just gave up.
The guest OS boots from the guest hard disk at 5 seconds, runs until 18 seconds, resets, reboots, then triple-faults at 30 seconds. Not much to go on in the log.
The updates in the guest OS went bad. Reboot in safe mode to get the updates rolled back, or restore the guest from a backup. Troubleshoot the cause of the guest OS BSOD inside the guest OS itself. I think this one is not caused by Virtualbox.
(Note, I see you're still on 4.3.12, no doubt to avoid hardening issues. Troubleshooting hardening problems has progressed quite a bit since early days. Though a Virtualbox update won't solve your guest problem now, it will make your host more secure.)
The guest OS boots from the guest hard disk at 5 seconds, runs until 18 seconds, resets, reboots, then triple-faults at 30 seconds. Not much to go on in the log.
If the guest's Virtualbox window stays open, and the guest OS shows errors that it typically shows on a real computer, then the problem is inside the guest OS itself, especially if no settings were modified in Virtualbox.KnightofPeace wrote:We did Windows updates for the Server 2012 and rebooted the VM but it came with the error message:
The updates in the guest OS went bad. Reboot in safe mode to get the updates rolled back, or restore the guest from a backup. Troubleshoot the cause of the guest OS BSOD inside the guest OS itself. I think this one is not caused by Virtualbox.
(Note, I see you're still on 4.3.12, no doubt to avoid hardening issues. Troubleshooting hardening problems has progressed quite a bit since early days. Though a Virtualbox update won't solve your guest problem now, it will make your host more secure.)
-
KnightofPeace
- Posts: 2
- Joined: 27. Jul 2020, 12:42
Re: VM can not startup again Error code: 0x000000c4
Than you very much scottgus1 for your assistance.
Unfortunately the guest OS (Windows server 2012) doesn't load. Once I start the machine, I can see the VirtualBox logo then it come up with the attached error message.
So it doesn't give me option to roll back the the windows update or to go into safe mode.
Any other suggestion please.
Unfortunately the guest OS (Windows server 2012) doesn't load. Once I start the machine, I can see the VirtualBox logo then it come up with the attached error message.
So it doesn't give me option to roll back the the windows update or to go into safe mode.
Any other suggestion please.
-
scottgus1
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows, Linux
Re: VM can not startup again Error code: 0x000000c4
The "Your PC needs to restart" message is coming from Windows 2012, not Virtualbox. Then the Virtualbox "hardware" crashes in the Guru Meditation.
You have to get into Windows 2012 just like you would if it was installed and crashing on a real PC.
I don't believe there is any special tool or Virtualbox command that can fix this.
Pretend this is a real computer, use Microsoft's help channels to find out how to start a 2012 R2 OS that is black-screening.
You have to get into Windows 2012 just like you would if it was installed and crashing on a real PC.
I don't believe there is any special tool or Virtualbox command that can fix this.
Pretend this is a real computer, use Microsoft's help channels to find out how to start a 2012 R2 OS that is black-screening.