Custom Query (16363 matches)
Results (1039 - 1041 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #10029 | fixed | BSOD if VirtualBox network and Applian network both enabled on nic | ||
| Description |
A BSOD will occur on Windows 7 Host 64 bit system if Applian's Replay Media Catcher and VirtualBox 4.1.6 are both installed and both network drivers are enabled. Disabling either or uninstalling either will fix the problem. DRIVER_CORRUPTED_EXPOOL (c5) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is caused by drivers that have corrupted the system pool. Run the driver verifier against any new (or suspect) drivers, and if that doesn't turn up the culprit, then use gflags to enable special pool. Arguments: Arg1: 000000000000745e, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, value 0 = read operation, 1 = write operation Arg4: fffff800031fbdd3, address which referenced memory
afflicting drivers: |
|||
| #6299 | fixed | Vbox causes BSOD on host system when run second time | ||
| Description |
I'm running Win 7 Pro x64. Running VBox 3.1.4. The problem I'm having is that VBox causes a BSOD when I run it a second time. I installed VBox and it was running fine when I was logged in as the administrator. In order to also run it as a normal user and use the same VMs, I moved the .VirtualBox directory and all VMs to another drive. Now I can run it either as the user or admin only once. If I exit VB and restart it my system crashes. Before, I moved the .VirtualBox folder I could not run VBox as the normal user. I would get a BSOD as soon as I ran VBox. So that both the admin and user could access the same VMs, I moved everything to E:\.VirtualBox using the following steps:
Now I can run VBox from either the admin or normal user but only once. If I launch it again my system crashes. Any ideas how to fix this? Is there something I missed in my process of moving the .VirtualBox folder? Is there a different way to setup VBox to be able to run as either the admin and normal user? I have attached the minidump file. I have not attached a VBox.log because the BSOD occurs before I launch any VMs. |
|||
| #15583 | obsolete | Audio driver set to null for all guests on Solaris host | ||
| Description |
Solaris 11.3 host: Upgraded from VirtualBox 5.0.22 to 5.0.24 and no sound in Windows or Linux guests. Found audio driver set to null for all guests. Even setting the audio driver to Solaris a pressing OK it reverts to null. Reverted to 5.0.22, set the audio driver to Solaris for each guest and sound now works. |
|||

