Custom Query (16363 matches)
Results (2062 - 2064 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #3696 | fixed | multiple vboxtray.exe on WTS crash system | ||
| Description |
On a W2K3 WTS (Terminal Services) System, when logging in from remote, system crashes ("Aborted") when VBoxTray.exe is already running in console. Problem is always reproducible. Temporaily (workaround): Remove vboxtray.exe from HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run and start it manually in the vbox window. After this, system doesn't crash anymore. Maybe there is no "already running" check in VBoxTray.exe? |
|||
| #3697 | fixed | Blue screen of death - Clock interrupt message | ||
| Description |
I get a BSOD from my Vista host which is a the 32bit version running on an AMD 64 bit Turan processor. This happens when I start my Windows 2003 Server 32 bit guest which is the eval version (evaluation is not expired) and this previously was able to be started. When it launches it begins to start and then the host computer does a BSOD with a statement about the Clock Interrupt and second processor. Just before I get the BSOD, my system eventlog will record the following in eventvwr.msc (Event ID 6 - Filtermanager): File System Filter 'AvgMfx86' (6.0, 12/10/2008 6:48:14 AM) has successfully loaded and registered with Filter Manager. Hope to submit more information on this soon. |
|||
| #3698 | fixed | System crash during upgrade from 2.1 to 2.2 => Stop all VMs before upgrade | ||
| Description |
Upgrade from virutualbox-2.1 to virtualbox-2.2 on Ubuntu 8.1 amd64 using apt. This will work if VirtualBox is not running. If VirtualBox is running during the upgrade the system will crash. Suggested solution 1:
Suggested solution 2:
|
|||

