Virtualbox 7.0.10 Snapshot run creates error " Referenced memory" "The memory could not be written" => fixed in SVN/next 7.0.x maintenance

[Pankaj Grover]

I just updated virtualbox 7.0.8 to 7.0.10. Everything is fine but when i start my latest updated saved snapshot error comes below:

" The instruction at 0x00007FFAOBEAA78A referenced memory at 0x0000017C742A02B6. The memory could not be written Click on OK to terminate the program" . In discard state no issue but snapshot not running. I revert back to 7.0.8 and and then no issue at all. may be this is bug in latest version 7.0.10. here screenshot attached.. Kindly provide fix and or any advise. Thanks...

[Pankaj Grover]

Screenshot

[fth0]

VirtualBox 7.0.10 tried to restore the saved state from a previous VM run with the same VirtualBox version, and failed when loading the saved TPM state. While trying to gracefully abort the VM run, a crash happened in the USB code in xhciR3RhDetach().

[Pankaj Grover]

Replying to fth0:

VirtualBox 7.0.10 tried to restore the saved state from a previous VM run with the same VirtualBox version, and failed when loading the saved TPM state. While trying to gracefully abort the VM run, a crash happened in the USB code in xhciR3RhDetach().

Hi, today how i fix this, i discard snapshot and shutdown. And after i switch off TPM to None. and after i restart and take snapshot and now this version 7.0.10 is able to start my snapshot. So problem is if TPM enabled and you taking snapshot. But this problem was not in 7.0.8 version. I hope in coming version they will fix it and we did not need to off the TPM while taking snapshot.

[fth0]

VirtualBox forum threads of other affected users:

​VirtualBox 7.0.10 not load from snapshot saved state

​Windows 11 guest in Windows 10

​Windows 10 guest won't start from saved state

[aeichner]

Thanks for the report, this is a 7.0.10 regression and will be fixed in the next 7.0.x maintenance release.

[fth0]

@aeichner: Can you share a few words about the nature of the bug, especially if you fixed the TPM related part of the issue or the USB related part?

[aeichner]

The root cause is in the TPM device emulation and a regression from 7.0.10. This would cause any saved state loading to fail with the config mismatch error and powering off the VM would cause a crash afterwards. I only fixed the TPM part so far because I couldn't reproduce the crash part so far.

[Pankaj Grover]

@aeichner yes there is nothing with USB related part. Only issue with TPM. As you said you already fixed this..that's good. How can i test this also.. you already fixed this in beta version or not ? So that i can test also... Thanks

Replying to fth0:

@aeichner: Can you share a few words about the nature of the bug, especially if you fixed the TPM related part of the issue or the USB related part?

[aeichner]

The fix didn't hit a public testbuild yet and won't happen this week anymore. You could monitor here and look for 7.0 testbuild with revision >= 158827. As I'm on vacation for the next two weeks don't expect any answers from my end here but maybe someone else in the team will upload a testbuild next week. :)

[fth0]

@aeichner: Thanks for the feedback and for fixing several bugs, and have a nice vacation! :)

[Pankaj Grover]

@aeichner okay thanks for consider issue and fixing. Enjoy your holidays.

[fth0]

This issue should be fixed in the VirtualBox test builds 7.0.11r159210 and newer.

[galitsyn]

Hi guys,

We just released a new version of VirtualBox today. This issue should be fixed there. Closing it. Please leave a comment if it is still actual for you. As usual, builds are available on Downloads page. Thank you for reporting.