Opened 8 years ago
Closed 8 years ago
#15805 closed defect (fixed)
VirtualBox crash - Memory could not be read
| Reported by: | xonfug | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 5.1.4 |
| Keywords: | Cc: | ||
| Guest type: | other | Host type: | other |
Description
Just upgraded from 5.1.2 to 5.1.4. Started a guest, did some work and installed Windows updates. Shut down the guest. A few seconds after the guest window had gone, the error message appeared. Clicked OK, VirtualBox Manager continued ok, so I guess the crash was related to the closing VirtualBox guest. Screenshot and log files attached. So 5.1.4 doesn't fix the crashes (all memory could no be read) that I got in 5.1.2 but never got in 5.0.x Windows 7 Enterprise host and Windows 7 Pro guest
Attachments (1)
Change History (4)
by , 8 years ago
| Attachment: | VBox.log.zip added |
|---|
comment:1 by , 8 years ago
comment:2 by , 8 years ago
Been using 5.1.6 for 2 weeks now and not had a single crash so looks like its fixed.
Note:
See TracTickets
for help on using tickets.
Please could you install + test the latest 5.1.x test build for Windows from here? It has fixes for 2 potential crashes. Thank you!