Custom Query (16363 matches)
Results (109 - 111 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #16959 | fixed | fatal error since 5.26: instruction 0x3f526d32 uses memory that can not be read | ||
| Description |
Host: win 8.1 64 bit; guest: Debian 8 The VM in question used to work until yesterday, with VBox up to 5.24. Today I updated to 5.26 and at VM boot I get the error as per the attached image. On the same host, another Debian 8 VM works fine. |
|||
| #16961 | fixed | Crackling audio on Windows 10 guest Mac host | ||
| Description |
MacOS 10.12.6 Windows 10 professional, latest Audio settings started on the default CoreAudio and Intel HD Audio, and I experienced crackling audio. After seeing some similar reports that were solved by using the ICH AC97 driver, I switched to that and installed the drivers in the guest, but that didn't help. I tried the latest Test Build as of last night as well, which didn't solve the issue (was also confused since the test build seems to be 5.1.25 and release builds 5.1.26) Will attach logs |
|||
| #16968 | fixed | When starting two VMs at same time, one regularly aborts | ||
| Description |
Version 5.1.26 r117224 (Qt5.6.2) Running on Win 10 Pro 64 bit, 32 Gig memory in box typically 50-70% available when this occurs. Invoking two VMs at the same time results in one of them 'aborting' about 90% of the time. This is a much higher failure rate starting with this version of VB than in previous versions (very rare...MAYBE 1% of the time) problem independent of whether invoked from Manager or command line problem independent of OS running in the client VMs (typically Win 10, or XP) |
|||

