Page 1 of 1

[Fixed] "memory could not be read" when saving VM state after upgrade to VirtualBox 6.0.10

PostPosted: 26. Jul 2019, 13:03
by igorsol
Recently I upgraded from VirtualBox 5.2.30 to VirtualBox 6.0.10 (on Windows 10 host)
I have Ubuntu 16.04 and Ubuntu 18.04 virtual machines.
After upgrade when I chose to save VM's state (instead of shutting down the guest system) the save progress goes to 100% and then message window with this text appears:
---------------------------
VirtualBoxVM.exe - Application Error
---------------------------
The instruction at 0x00007FFA5B81CB3E referenced memory at 0x0000000000002DD0. The memory could not be read.

Click on OK to terminate the program
Click on CANCEL to debug the program
---------------------------
OK Cancel
---------------------------

After that VM's state in VirtualBox Manger is "aborted".
Before upgrade I was able to save VM's state without any issues.
Is this known problem? Are there any fixes?

Re: "memory could not be read" when saving VM state after upgrade to VirtualBox 6.0.10

PostPosted: 27. Jul 2019, 08:41
by socratis
We need to see a complete VBox.log, from a complete VM run, where the problem occurs:
  • Start the VM from cold-boot (not from a paused or saved state) / Observe problem / Shutdown the VM (force close it if you have to).
  • 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.
Image

Re: "memory could not be read" when saving VM state after upgrade to VirtualBox 6.0.10

PostPosted: 29. Jul 2019, 12:04
by igorsol
Thank you for the response. The attached file is the requested log.

Re: "memory could not be read" when saving VM state after upgrade to VirtualBox 6.0.10

PostPosted: 19. Sep 2019, 14:27
by igorsol
The issue has disappeared after upgrade to VirtualBox 6.0.12

Re: "memory could not be read" when saving VM state after upgrade to VirtualBox 6.0.10

PostPosted: 19. Sep 2019, 15:54
by socratis
igorsol,
Thank you for the feedback, glad everything is back to normal! Marking as [Fixed].