Custom Query (16363 matches)
Results (562 - 564 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #11196 | obsolete | Playing AAC HE2 content cause bugcheck in VAud_WDM.sys | ||
| Description |
Trying to play AAC HE2 content bluescreens winxp with BugCheck 1000008E, {80000003, f5da23b8, f36b7354, 0} Source appears to be in VAud_WDM.sys. Minidump of error provided as well as audio file crashing it and vbox log Behaviour observed in 4.1.22, 4.2.0 and 4.2.4 (dump from this version) Host: Win2008R2 and Win7, 64 bit Guest: Win XP, sp3, 32 bit Method to reproduce: 1) Install a fresh winxp 2) Install codecs to playback aac - I use LAC filters, which can be obtained here https://code.google.com/p/lavfilters/. Use default installation options. I tried versions 0.52 to 0.53.2 3) Playback the aac file in windows media player, selecting yes to play content with different extension 4) Crash and burn Minidump gives me VAud_WDM+0x33b9: f5da23b9 8b0d9c6edaf5 mov ecx,dword ptr [VAud_WDM+0x7e9c (f5da6e9c)] ds:0023:f5da6e9c=00000003 Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: DRIVER_FAULT BUGCHECK_STR: 0x8E This behavior can be alleviated by reducing the audio hardware acceleration to level 2 (see supplied screen shot). If this reduction is used, then playback occurs without crash. |
|||
| #12065 | obsolete | Suddenly no VM's will start - all give a RPC_S_SERVER_UNAVAILABLE error at 0% | ||
| Description |
I was in the process of creating a new machine, and it wouldn't start (more in a bit) - I then tried to start up a few old, reliable machines, and got the same behavior. The only change was that on startup a new version was mentioned; I installed it and saw this behavior. After some web research I went back to version 4.2.12, and still see the same problem - but this may have to do with having installed the 4.2.16 version and then, perhaps, and incomplete removal. I suppose technically this applies to both versions, as the problem shows up in both. When I try to start any machine, I see a small popup, "Starting virtual machine..." and "0%" - that never changes. My host OS is Windows 7 Ultimate; I have to kill the process for that machine manually. When I do, I get a popup from Virtualbox; the detailed error message is: Result Code:
Web searching shows this, or something like it, was a problem years ago, but apparently fixed. I found current ticket #10747 that looks similar. The VM I was trying to start as the main test case is a Windows 98 machine, fairly vanilla. I certainly haven't changed any of its attributes (e.g., hardware acceleration options) since it last ran. I have 17 VM's, all of some level of importance; it would not be a minor effort to recreate them, even if that helped. I tried to create a new Windows 2000 machine from scratch and had the same problem, that is the exact same hang and detailed error message. I'm willing to invest some time to help fix it, if any testing I can do on this end might help. |
|||
| #3008 | obsolete | VDI lost due to failed Discard Snapshot attempt due to out of disk space condition | ||
| Description |
Host platform: Dell Inspiron 1300/CPU:1.8G/RAM:2G OS: Win XP Pro SP2 My VirtualBox test platform: Guest OS: Win XP Pro SP2 I was down to approx 1.9G free disk space so was cleaning up... Noticed that test platform (with 1 snapshot) was consuming approx 9G (base VDI=6G, snapshot=3G). I selected Discard Snapshot - there was a LOT of disk activity and progress was slow... I noted progress at 77% approx 15 min after initiating discard operation. When I returned, there was a VirtualBox error dialog (unfortunately I did not make note of the error as I assumed it would be in the log - but it was not!). My recollection is that the error reported was an out of disk situation (ERR NO SPACE? or similar) I am now unable to start the VM as the following error is reported: VERR_FILE_NOT_FOUND - see attached log files for details. Sure was an easy way to free up 3G! ;) |
|||

