Opened 8 years ago
Closed 5 years ago
#15799 closed defect (obsolete)
"The memory could not be written" a few seconds after Openbox starts
| Reported by: | jeff.deseret.tech | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 5.1.2 |
| Keywords: | Cc: | ||
| Guest type: | other | Host type: | other |
Description
Windows 10 host, running an ArchLinux 4.7.0 guest. Upgraded to 5.1.3 test build, r110028, to resolve issue #15769 where vboxvideo crashes. I installed this version on the host and the Guest Additions on the Guest. After doing so and running startx, which runs openbox, Windows pops up an error reading "The instruction at 0x000000006473C330 referenced memory at 0x000000001AE24000. The memory could not be written. Click on OK to terminate the program". The memory locations differ each time. After clicking OK, the virtual machine terminates and the machine status gets set to "Aborted". This is reliably reproducible. I tested multiple times with 3d acceleration enabled and disabled in the settings; the crash occurred each time.
Attaching relevant logs. #14363 could be related.
Attachments (6)
Change History (10)
by , 8 years ago
| Attachment: | ArchLinux-2016-08-15-22-59-13.zip added |
|---|
by , 8 years ago
| Attachment: | vbox-dmesg-occurrences.log.gz added |
|---|
Output of "dmesg | grep -i vbox -C 3" on guest
by , 8 years ago
| Attachment: | VirtualBox_2016-08-15_22-59-11.png added |
|---|
Windows error message on crash
comment:1 by , 8 years ago
Correction: it seems that different versions of the Windows VBox exe and the Guest Additions are currently on the test builds page. I used r110028 for the Windows host and r110032 for the Guest Additions ISO, which I installed in the guest. These are currently the most recent builds on the Test builds page at https://www.virtualbox.org/wiki/Testbuilds.
I run VirtualBox as the Windows admin user because that's required to make raw disk passthrough work.
I also see that I am using the 5.1.2 extpack. I have downloaded the 5.1.3 extpack r110032 and am installing now. I will retest if this is thought to be a likely cause of the issue.
comment:2 by , 8 years ago
Just retested with new extpack. No improvement. Near-immediate crash right after Openbox starts.
comment:3 by , 8 years ago
Actually, not sure if that Xorg.0.log shows the crash. Weird stuff going on with the location of Xorg log files on Arch these days. It can at least serve as some information about the environment, at least.
comment:4 by , 5 years ago
| Resolution: | → obsolete |
|---|---|
| Status: | new → closed |
Crash with no 3d acceleration