Changes between Initial Version and Version 1 of Ticket #2763
- Timestamp:
- Dec 18, 2008 8:03:48 AM (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #2763
- Property Component VMM → VMM/HWACCM
-
Ticket #2763 – Description
initial v1 2 2 Following combination leads to a BSOD: 3 3 4 -Physical machine: HP 6715b, AMD Turion CPU (Dualcore), x1250 graphic chipset5 -Running Virtualbox on Vista 32 bit host6 -Linux as guest, eg Ubuntu 8.10 (same problem with Ubuntu 8.04 or OpenSolaris as mentioned here: http://forums.virtualbox.org/viewtopic.php?t=122314 * Physical machine: HP 6715b, AMD Turion CPU (Dualcore), x1250 graphic chipset 5 * Running Virtualbox on Vista 32 bit host 6 * Linux as guest, eg Ubuntu 8.10 (same problem with Ubuntu 8.04 or OpenSolaris as mentioned here: http://forums.virtualbox.org/viewtopic.php?t=12231 7 7 8 8 Starting the virtual machine leads to a BSOD (host) after selecting something in linux (guest) bootmanager. 9 9 10 Windows Eventmanager tells me something about a crash of the display driver (in german it says: {{{Anzeigetreiber atikmdag reagiert nicht mehr und wurde erfolgreich wieder hergestellt.}}}, in english it's something like {{{Display driver atikmdag stopped responding and was successfully recovered}}}).10 Windows Eventmanager tells me something about a crash of the display driver (in german it says: ''Anzeigetreiber atikmdag reagiert nicht mehr und wurde erfolgreich wieder hergestellt.'', in english it's something like ''Display driver atikmdag stopped responding and was successfully recovered''. 11 11 Display driver and bios of laptop is up-to-date. 12 12 13 13 A workaround is to enable AMD-V, guest will run normally then. BSOD will only appear with disabled AMD-V (which is the default setting after installation). 14 15
