Opened 5 years ago
Last modified 5 years ago
#18479 new defect
Can't restart saved state on Windows 10. Exception breakpoint 0x80000003
| Reported by: | jeanmiraptor | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 6.0.4 |
| Keywords: | Cc: | ||
| Guest type: | Windows | Host type: | Windows |
Description
Hi,
I'm running Virtualbox on a Windows 10 64b Pro 1803, and operating with a "IE 10 - Win 7" VM (downloaded on Virtualbox site a long time ago), NAT connection and Guest Add-ons installed. The VM runs perfectly well, but if I stop it via Saving State and try to re-open it I systematically have a crash error. The session is then marked as Aborted and If I start it again it works (I have to start Windows via the "BIOS" "Start windows normally" menu option, though). Is there any way I can solve this ?
I've seen in the tickets some which refer to that same breakpoint but they don't seem to apply to my case.
I attached :
- VBox.log
- VBoxHardening.log
- Screenshots of the various error messages I get
Thanks in advance.
Attachments (2)
Change History (3)
by , 5 years ago
| Attachment: | 20190307-VirtualBox logs.zip added |
|---|
comment:1 by , 5 years ago
Replying to jeanmiraptor:
Is there any way I can solve this ?
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 a [Duplicate] and someone from the developers has to deal with it and close it as such.
I've seen in the tickets
As they often say in Wikipedia: [Citation needed]
00:00:19.418137 Console: Machine state changed to 'Restoring'
If you take a look at the "Known Issues" in the Discuss the 6.0.0 release thread in the forums, there are 3 tickets regarding saved-state restore issues:
Logs as zip