Fatal error on starting windows

[JZK]

Hi All,

When starting my windows 7 in the VB environment I receive a fatal error (see attachment error message).

This is something I receive from time to time.

After clicking at OK, VB closes.
When I start VB again I see a screen which gives me the option to start windows normally or start the repair modus (recommended).

Using the repair modus results in a message that windows was unable to repair and it will be restored.

After all those steps, windows will run again.

As said, this situation will occure sometimes. It doesn't matter if whether I shutdown the guest, save the state or pauze the virtual machine.

Hopefully, anyone can help me with this issue.

[mpack]

00:00:02.721433 Host RAM: 3981MB total, 556MB available
...
00:00:03.133403 RamSize <integer> = 0x0000000040000000 (1 073 741 824, 1 024 MB)
00:00:03.133938 VRamSize <integer> = 0x0000000002800000 (41 943 040, 40 MB)

Memory overcomitted.

A VM needs real memory to run in. Close down some host apps before launching the VM. Or, add more RAM the host.

[JZK]

ok, thanks.

Unfortunately, it is not possible to add more RAM to the host, so I think i have to close some programs.
I will increase the video RAM which is allocated to the guest.

[mpack]

Unfortunately, it is not possible to add more RAM to the host

Oh? That surprises me. I saw you were using a 64bit host OS, the main purpose of which is to allow the use of >4GB RAM, but you only have 4GB installed, so I assumed you must be able to add more.

I will increase the video RAM which is allocated to the guest.

I wasn't suggesting that. I simply listed virtual graphics RAM as another significant user of host RAM: the VRAM feature alone was grabbing 7% of available host RAM. However, 40MB is actually a good number if your host can afford it.

[JZK]

I think you are right about the possiblity to expand the RAM, but I am using an Asus ultrabook, so this is not an easy job. It also looks that the current RAM is partially integrated.

But still, I am surprised that this would cause a problem with the VB environment. I used VB before (Ubuntu or Mint guest) and had no issues at all.

[mpack]

Sorry, "I didn't realize this would cause a problem?" - what is "this"?

If you are referring to the problem of using memory you don't have to run a VM, then that has always been an error. VMs run at elevated privilege levels, they can't use app level paged memory (indeed, the VM will very likely be creating its own paging mechanism). If you didn't see an error before then you weren't overcommitting memory before.

[JZK]

whit this I meant the error which I receive now.

So, I understand that the only thing to solve the error is to increase the RAM of the host, or to decrease the applications which are open when I use the VM.

Thanks for your explanation en replies.

[Tomino]

I have the same problem and I found the Google Chrome is locking memory. When I start the CHrome browser before
Virtualbox Windows Machine then I receive this error. But If I start virtual machine and then Chrome browser all is working.
Try to find the conflicting application or service.

[mpack]

Thanks, but in that circumstance while the VirtualBox error message may be the same, the log file is different. The OP doesn't have the Chrome crash reporter problem you refer to. He simply needs to close a few apps.