[Solved] Critical Error- Guru Meditation mode

[Critical error!!!]

Hi,
I'm using virtual box on a MacBook 12'' with McOS Sierra 10.12.4, to run a simulated win XP system on which I use my EPrime program for research.

Apparently something went wrong yesterday night while I was working on it. Since then it doesn't work. Its on a Guru Meditation Mode and the message says: "A critical error has occurred while running the virtual machina and the machine execution has been stopped."

Sorry, but I don't even know what I have to paste from the Vbox.log, so this is the last lines:

00:02:22.400231 !! {vgagr}
00:02:22.400231 !!
00:02:22.400231 VGA Graphics Controller (3CF): GR index 3CE:08
00:02:22.400231 GR00:00 GR01:00 GR02:00 GR03:00 GR04:00 GR05:50 GR06:05 GR07:0F GR08:FF
00:02:22.400231 !!
00:02:22.400231 !! {vgapl}
00:02:22.400231 !!
00:02:22.400231 read mode : 0 write mode: 0
00:02:22.400231 set/reset data: 00 S/R enable: 00
00:02:22.400231 color compare : 00 read map : 0
00:02:22.400231 rotate : 0 function : 0
00:02:22.400231 don't care : 0F bit mask : FF
00:02:22.400231 seq plane mask: 0F chain-4 : on
00:02:22.400231 !!
00:02:22.400231 !! {vgasr}
00:02:22.400231 !!
00:02:22.400231 VGA Sequencer (3C5): SR index 3C4:04
00:02:22.400231 SR00:03 SR01:00 SR02:0F SR03:00 SR04:0A SR05:00 SR06:00 SR07:01
00:02:22.400231 !!
00:02:22.400231 !! {vgatext}
00:02:22.400231 !!
00:02:22.400231 Not in text mode!
00:02:22.400231 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:03:16.986379 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenWorkAreaResized: Screen 0 work area is formally resized to: 39x23 x 1241x777
00:03:18.038305 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenWorkAreaResized: Screen 0 work area is formally resized to: 38x23 x 1242x777
00:07:05.580425 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenWorkAreaResized: Screen 0 work area is formally resized to: 39x23 x 1241x777
00:08:59.261906 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenWorkAreaResized: Screen 0 work area is formally resized to: 38x23 x 1242x777
00:09:16.886449 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenWorkAreaResized: Screen 0 work area is formally resized to: 39x23 x 1241x777

[socratis]

Sorry, but I don't even know what I have to paste from the Vbox.log, so this is the last lines:

All of it
Follow a "start the VM from cold-boot" / "observe error" / "shutdown the VM" cycle. With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log". Save only the first "VBox.log", ZIP it and attach it to your response (see the "Upload attachment" tab below the reply form).

[Critical error!!!]

Thanks for answering to me.

Now I attach it.

[socratis]

00:00:02.376308 Host RAM: 4096MB (4.0GB) total, 1243MB available
00:00:02.705836   RamSize           <integer> = 0x0000000040000000 (1 073 741 824, 1 024 MB)
00:00:02.706328   VRamSize         <integer> = 0x0000000001500000 (22 020 096, 21 MB)

Let's face it. You don't have a very powerful system. 4 GB of RAM is the minimum for your 10.12 host OS. A Win7-64 should require more than 1024 MB of RAM, but don't be surprised if that's the source of the Guru; lack of resources. On the other hand 21 MB for the VRAM seems too low. Increase it to at least 64 if not 128 MB RAM.

My advice? If you want to have a Win7-64 client, give it at least 1536 MB of RAM and 128 MB of VRAM. Start it right after you reboot your Mac (to clear all the memory), and without running any other application on your host.

[Critical error!!!]

Hi again,

I made the changes you recommended me but it still in the same mode. Here I send you again the log in case you see anything else.

Thank you very much again.

[andyp73]

00:00:02.859268 Host RAM: 4096MB (4.0GB) total, 1480MB available
00:00:03.570238 RamSize <integer> = 0x0000000060000000 (1 610 612 736, 1 536 MB)
00:00:03.57062 VRamSize <integer> = 0x0000000008000000 (134 217 728, 128 MB)

Even having rebooted your host and having nothing else running you are still short on RAM. I think you are going to need to go back to 1024MB allocated to the guest, stick with the 128MB allocated to VRAM and open nothing at all else on your host. If it is possible, you might want to consider upgrading the RAM on your MacBook to 8GB.

-Andy.

[Critical error!!!]

Yes!! Luckily now it works. I changed back the RAM to 1024Mb and kept the VRAM with 128MB. Additionally, the windows made several updates. Its slow but it works.

Thanks you to both of you.
-Valerie.

[socratis]

Glad you got it going. Marking as [Solved].