VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1141 - 1143 of 16363)

Ticket Resolution Summary Owner Reporter
#10070 fixed BSOD when Installing after Win7x64 and then on Boot Edmund Watson
Description

Upgrading from version 4.1.16 to 4.1.18 Installed Virtual Box (get past network interface warning)

BSOD is BAD POOL HEADER STOP 0x19 (0x20, 0xFFFFFA8004A9C00,0xFFFFA8004A9C070,0x4070000)

Then same error after log in after then.

System restore was required to fix this. 2nd Attempt of same error.

Can give any more info, when asking, ask for all that you can. As it is a long process as it requires a system restore.

#9726 obsolete BSOD when Online Armor installed pcguy
Description

Virtualbox 4.1.4 causes BSOD in Online Armor software firewall for Windows 5.1.0.1370 http://support.emsisoft.com/topic/6048-online-armor-5101370/page__view__findpost__p__35369

"It is an interaction we can't fix though. So please report it to the VirtualBox guys. The crash is caused by the VBoxNetFlt.sys driver that is always running even when VirtualBox is closed. To be more precise it crashes when freeing a chunk of memory. Most likely a case of bad error handling or parameter verification. "

#5674 fixed BSOD when USB & Uniprocessor HAL * VT-x/AMD-V Mark Cranness
Description

Enabling USB on an existing Windows VM that did not have USB enabled causes a BSOD on the second boot after Windows has installed USB drivers.

Affects 3.1.0 r55467. The same steps do not affect 3.0.10 or 3.0.12 (There are other similar reports on Windows XP guests, but presumably on VMs that always has USB; they will not boot anymore.)

Reproduce:

Windows 2000 Server VM with NO USB controllers OR drivers installed: 'set devmgr_show_nonpresent_devices=1& start devmgmt.msc' and Uninstall any USB controllers with Device Manager.

Enable USB in VirtualBox and boot VM. Windows recognizes USB and installs drivers. Shutdown and reboot gives BSOD as below:

*** Stop: 0x0000001E (0xC0000005,0x8046ACC8,0x00000000,0x00000000)
KMODE_EXCEPTION_NOT_HANDLED
*** Address 8046ACC8 base at 80400000, DateStamp 4a781d9e - ntoskrnl.exe

... BSOD occurs (80%+ of the time) when all of these conditions are true:

  • Uniprocessor version of ntoskrnl.exe in use.
    This means 'ACPI Uniprocessor PC' HAL or 'Advanced Configuration and Power (ACPI) PC' HAL.
    (When 'ACPI Multiprocessor PC' HAL is installed, ntoskrnl.exe == ntkrnlmp.exe, and boot is OK.)
  • USB host controllers recognised in Device Manager and drivers installed.
  • Guest Additions installed. 3.0.10 or 3.1.0 beta1,2,3,release does not matter: they all BSOD.
    (If Guest Additions are not installed then boot is OK.)

Because VT-x/AMD-V is involved, my CPU might be significant: Intel Core 2 Duo E8400 E0.

Logs and more description here: http://forums.virtualbox.org/viewtopic.php?f=15&t=24753

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