Custom Query (16363 matches)
Results (2221 - 2223 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #15801 | fixed | Support for STMXCSR instruction: VERR_IEM_INSTR_NOT_IMPLEMENTED | ||
| Description |
VirtualBox crashes at a predictable point during the installation of Microsoft Visual C++ Resitributable (x64) version 12.0.21005 via the Visual Studio Community Installer. The machine crashes every time the package tries to install. I have tested with the latest development version and found it was unable to open a session for the virtual machine let alone boot it. The host is an Intel Macbook Pro circa 2009 and the guest is Windows 7 x64 SP1. The issue appears to be that the stmxcsr instruction defined in the Intel 80/86 istruction set is not yet implemented in VirtualBox. I am also aware that this instruction is being used more often in windows 10 software so this issue may become worse over time. I would be very appreciative if you could implement the instruction as it is causing me a small nightmare since I rely on VirtualBox for my work. |
|||
| #15800 | worksforme | VirtualBox 5.1.2 Oracle VM VirtualBox Extension Pack crash my system | ||
| Description |
I just install VirtulaBox 5.1.2 updating my previous system. I install, as well, VirtualBox 5.1.2 Oracle VM VirtualBox Extension Pack. Now my system can´t start. It is a Windows XP 32b image with 40 GB of vdi file fixed. Attached my .log and .png files |
|||
| #15799 | obsolete | "The memory could not be written" a few seconds after Openbox starts | ||
| 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. |
|||

