VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (2386 - 2388 of 16363)

Ticket Resolution Summary Owner Reporter
#11195 obsolete BSOD vmmr0.sys DRIVER_IRQL_NOT_LESS_OR_EQUAL UrSuS
Description

I have BSODs coused by vmmr0.sys with random time periods.

Another BSOD started to appear after I've installed "hacked" version of my Wireless card drivers. Then I reverted the driver, and BSODs caused by vmmr0.sys started to appear.

#11196 obsolete Playing AAC HE2 content cause bugcheck in VAud_WDM.sys Brussel
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.

#11197 obsolete Upgrade changes Host-only network configuration Justin Finkelstein
Description

As a user of VirtualBox, I upgrade the software whenever a new release comes out. During this upgrade, the VirtualBox Host-Only Ethernet Adapter's IPv4 address is changed from the configuration I use (172.16.0.100) to a 192.168.x.y address.

I consider this to be unexpected behaviour as:

  • Upgrades should not alter basic configuration settings
  • The process to rectify this takes time and involves a reboot

This problem has affected all releases on Windows Host for the past 4 months.

Can this be investigated and fixed?

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy