Windows 10 Guest Fails to Boot with "A Critical Error Occurred"

Discussions about using Windows guests in VirtualBox.

Windows 10 Guest Fails to Boot with "A Critical Error Occurred"

Postby WFields » 11. Jun 2021, 02:42

I've used this VM for about 3 years, I think, and have an actual digital license for it, so I hate to lose it.
I'm running VirtualBox Graphical User Interface Version 6.1.16_Ubuntu r140961, © 2004-2021 Oracle Corporation (Qt5.12.8) on Linux Mint 20.1 Cinnamon (Cinn. 4.8.6) with Kernel 5.4.0-74-generic. I've tried recreating a new VM with the old .vdi file which didn't work.
I also tried changing the VM memory from 4096 to 2048 but I get the same error. The log is attached. Thanks for your help!

Wendell
WFields
 
Posts: 6
Joined: 11. Jun 2021, 02:36

Re: Windows 10 Guest Fails to Boot with "A Critical Error Occurred"

Postby scottgus1 » 11. Jun 2021, 03:57

Try that log again please:
Start the VM from full normal shutdown, not save-state. Run until you see the problem happen, then shut down the VM from within the VM's OS if possible. If not possible, close the Virtualbox window for the VM with the Power Off option set.

Right-click the VM in the main Virtualbox window's VM list, choose Show Log. Save the far left tab's log, zip it, and post the zip file, using the forum's Upload Attachment tab.

WFields wrote:Version 6.1.16_Ubuntu

Please note that this is the Ubuntu fork of Virtualbox, and we don't support the forks here. However the problem could be inside the VM's OS. We'll see what can be done. But please be prepared to upgrade to official Virtualbox.
scottgus1
Site Moderator
 
Posts: 12448
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Windows 10 Guest Fails to Boot with "A Critical Error Occurred"

Postby WFields » 11. Jun 2021, 04:16

I'm sorry - I should have stated that the error appears during boot of the VM. I can't boot it to shut it down cleanly. I (accidentally) have opened it in headless mode. Is there anything that I can do there, like "Show Log" to help you? Actually, I'm going to attach that log with this post in case it expedites things.

Thank you,

WFields
WFields
 
Posts: 6
Joined: 11. Jun 2021, 02:36

Re: Windows 10 Guest Fails to Boot with "A Critical Error Occurred"

Postby WFields » 11. Jun 2021, 05:25

More info. Attached are a couple of files to show where my VirtualBox is at this point.

One is a PNG of the VBox gui. It shows that it is in guru mediation state. I didn't realize what would happen when I selected, "Ignore." Joke's on me!

The other shows my efforts to start the vm via VBoxManage and the error given when I tried "VBoxHeadless -s "Windows 10" - namely that it is an invalid object state.
Attachments
WFields_VBox_Windows_10.png
WFields_VBox_Windows_10.png is what the VBox gui looks like at this point
WFields_VBox_Windows_10.png (86.2 KiB) Viewed 1378 times
WFields
 
Posts: 6
Joined: 11. Jun 2021, 02:36

Re: Windows 10 Guest Fails to Boot with "A Critical Error Occurred"

Postby scottgus1 » 11. Jun 2021, 16:48

If the VM operation gets to "Critcal Error occured, and Guru Meditation, the vbox.log will show the problem. Save all the logs under "Show Log" (skip the "start-the-VM" part) and zip & upload them. Maybe one might show the problem.
scottgus1
Site Moderator
 
Posts: 12448
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Windows 10 Guest Fails to Boot with "A Critical Error Occurred"

Postby WFields » 12. Jun 2021, 04:02

Thanks. Here they are. Can you point me to a place that would show me what to look for in the future? You're golden, man!
Attachments
WFields_VM_Logs.zip
Logs for VBox 6.1.16_Ubuntu_A_Critical_Error_Has_Occurred"_at_Boot
(205.18 KiB) Downloaded 3 times
WFields
 
Posts: 6
Joined: 11. Jun 2021, 02:36

Re: Windows 10 Guest Fails to Boot with "A Critical Error Occurred"

Postby scottgus1 » 12. Jun 2021, 14:54

Thanks for the logs! I think we have something to go on.

The VM guru meditates a quarter second after the VM's OS starts booting. Probably not a real problem in the VM OS itself.

RAM is really tight:
00:00:01.607090 Host RAM: 7960MB (7.7GB) total, 4766MB (4.6GB) available
00:00:01.688287 RamSize <integer> = 0x0000000100000000 (4 294 967 296, 4 096 MB, 4.0 GB)
00:00:01.689028 VRamSize <integer> = 0x0000000008000000 (134 217 728, 128 MB)

This host is light on RAM for the amount the VM has. Try 3 or 2GB regular RAM, leave video RAM where it is, unless you enable 3D acceleration, at which point increase video RAM to the max 256MB.

Somehow your VM is attaching a second mouse:
00:00:02.016066 VUSB: Attached 'HidMouse' to port 1 on RootHub#0 (FullSpeed)
00:00:02.016276 VUSB: Attached 'HidMouse' to port 2 on RootHub#0 (FullSpeed)

This is unusual, but could be explained by your having a USB filter for a second physical mouse.

The biggest problem:
00:00:02.019057 NX - No-Execute/Execute-Disable = 0 (0)

Your host PC has the No-Execute (NX or XD bit) protection turned off. This system is supposed to mark RAM that cannot be used to store executable programs, for extra security. Windows 10 needs this enabled to run. Web-search your host PC to see how to turn this feature on (probably in your host's BIOS).
scottgus1
Site Moderator
 
Posts: 12448
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Windows 10 Guest Fails to Boot with "A Critical Error Occurred"

Postby WFields » 14. Jun 2021, 03:51

The NX being turned off was most of the problem. Now it's showing the normal W10 black background with the 4 blue window panes, then stops with the M$ error message: :( Your device ran into a problem and needs to restart. The Stop code is "INACCESSIBLE BOOT DEVICE."

I've removed the 2 USB filters. I can re-create them.

And, I've taken the RAM down to 2048 GB

The new zipped logs are attached.

Wendell

Edit: I just tried starting a NEW VM and selected "Use an existing virtual hard disk file," selecting the same VM file, and it opens correctly. I'm attaching the log for that one too. The VM is open - I haven't closed the session yet. It's name is "Windows_10_From_File-2021-06-13....log
It shows a different UUID and doesn't activate properly.
Attachments
Windows_10_From_File-2021-06-13-21-49-47.log
Same file, but it works when I create a new VM. Here's the log.
(67.42 KiB) Downloaded 1 time
WFields_VBox_Win10_Logs.zip
(101.29 KiB) Not downloaded yet
WFields
 
Posts: 6
Joined: 11. Jun 2021, 02:36

Re: Windows 10 Guest Fails to Boot with "A Critical Error Occurred"

Postby WFields » 14. Jun 2021, 07:05

Fixed. I found that I had changed the Storage from AHCI to PIIX4. No wonder it wasn't accessible!

Thanks so much for your help, Scottgus1!

Wendell
WFields
 
Posts: 6
Joined: 11. Jun 2021, 02:36

Re: Windows 10 Guest Fails to Boot with "A Critical Error Occurred"

Postby scottgus1 » 14. Jun 2021, 14:44

Great! Glad you're up and running!
scottgus1
Site Moderator
 
Posts: 12448
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux


Return to Windows Guests

Who is online

Users browsing this forum: m2i, Martin and 15 guests