Guest randomly crashes with "The memory could not be read"

[Aren Cambre]

I am running a Windows 10 1903 host and a Ubuntu 19.04 guest. The Ubuntu guest crashes fairly often with the attached dialog (see attached PNG file), warning of "The memory could not be read."

Both host and guest are using the latest patches. The guest has the current VMWare Extensions installed. The guest has 3D acceleration enabled.

Almost all of this guest OS's usage is for using Chromium browser to browse everyday sites, like Gmail, Facebook, CNN, etc. I feel it's fairly vanilla other than installing a few commodity apps like Chromium, GIMP, and Visual Studio Code.

The crash can happen when I am using nothing other than Chromium. In fact, just today, the crash happened less than 15 minutes after starting the VM. I attached log files from that crash.

Sometimes right-click context menus in Chromium go black. That is, you right-click on something, and the context menu that pops up is just a black rectangle. You can still click on things in that menu, but . I loosely correlate this to "the VM is going to crash sooner than later", but I am not sure there is a correlation. This morning, I did not notice the black context menus, although I do not think I invoked one.

[Aren Cambre]

this is the hardening log

[Socratis]

1. It's usually better and faster, if issues get first addressed in the ​VirtualBox forums, a lot more eyes there. More than 95% of the issues are resolved in the forums, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of. For example, yours is most probably not a bug and someone from the developers has to deal with it and close it as "Invalid".

Plus a discussion and analysis on the bug tracker is going to help me, you, and potentially a future drive-by user or two. Not so in the forums, many more tend to benefit...

2. You have a hardening problem:

   1320.5c8c: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0xc0000005 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 843234 ms, the end);
   

   Please read really carefully the following FAQ: ​Diagnosing VirtualBox Hardening Issues for some generic guidelines/ideas. Those are guidelines, you have to use your judgement as to which program might be responsible, most probably with your GPU. Reinstall your GPU drivers.

If you still have a problem after reading through the whole thing, please head to the ​forums, and open a new thread. Please be sure to mention that you came from the bug tracker and include the ticket number.

3. See if disabling 3D acceleration in the VM Settings, and disabling "hardware acceleration" in Chrome help...