VirtualBox

Opened 8 years ago

Closed 7 years ago

#15703 closed defect (fixed)

VM terminates, host error "The memory could not be read"

Reported by: wadewh Owned by:
Component: other Version: VirtualBox 5.1.2
Keywords: Cc:
Guest type: Windows Host type: Windows

Description

Host Win10 64 bit Guest Win10 32 bit

Start guest In the guest, start notepad. Type several characters by using alt-numeric key pad combinations. e.g. ALT 072 ALT 071 After a few characters the guest terminates and the host reports the error in the attached image.

The error is not specific to notepad. My initial discovery was in a different editor.

Verified to be present in v5.1.3 also. Tested in 5.0.20 and did not appear to be a problem in that version.

Attachments (3)

ErrorMsg.png (12.2 KB ) - added by wadewh 8 years ago.
Host error message
VBox.log (106.7 KB ) - added by wadewh 8 years ago.
VBoxHardening.zip (27.0 KB ) - added by wadewh 8 years ago.

Download all attachments as: .zip

Change History (7)

by wadewh, 8 years ago

Attachment: ErrorMsg.png added

Host error message

by wadewh, 8 years ago

Attachment: VBox.log added

by wadewh, 8 years ago

Attachment: VBoxHardening.zip added

comment:1 by Frank Mehnert, 8 years ago

wadewh, can you provide a Windows application dump, see here?

comment:2 by VVP, 8 years ago

Checked with VirtualBox 5.1.4 official release on the hosts:

  1. Windows10 build 10240 with the guests Windows7x64, Windows8.1 - Works.
  2. Windows7x64 with the guests Windows7x64, Windows8.1 - Works.

I typed different special symbols in the notepad - ALT + 40-49, 80-90, 91-99, 180-189:

()*+,-./01, PQRSTUVWXY, Z[\]_`abc, ┤╡╢╖╕╣║╗╝╜

comment:3 by wadewh, 8 years ago

Tested in 5.1.8 Host Win10 64 Guest Win10 64 Guest additions installed Pressing Alt and "1" on the number pad terminates the VM instantly

Tested in 5.0.28 -> OK, the error did not happen

I put in the "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps" entry but there was no log created. Not really a surprise considering the VM is being terminated instantly by the host rather than it crashing and being able to write a log.

comment:4 by Frank Mehnert, 7 years ago

Resolution: fixed
Status: newclosed

Fixed in VBox 5.1.10.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use