Custom Query (16363 matches)
Results (769 - 771 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #5382 | obsolete | Virtual Box Host Net Adapter cause a 9F error blue screen | ||
| Description |
Hello, I'm on a W7 64 bit machine and I usually disable Vbox host-only ethernet adapter because I don't need it. I forgot to do so after installing the latest version, and this morning I found my pc with a blue screen. Checking the logs I found out the blue screen happened while entering standby mode. It was a 9F error, Driver Power State Failure. It looks like a driver wasn't able to switch itself off for standby mode. Debugging memory.dmp and the related minidump file tells me this: Probably caused by : VBoxNetAdp.sys It never happened before, and my pc entered standby at least 10 times after installing 3.0.10, so it may be a very rare or one-off problem, but I thought it was worth mentioning anyway, since you do such great work on supporting and developing this software. Thanks, Daniele |
|||
| #13219 | fixed | VirtualBox-4.3.14-95030-Win not start | ||
| Description |
windows 7 x64 sp1 after install VirtualBox-4.3.14-95030-Win.exe as update on previous version(VirtualBox-4.3.12-93733-Win.exe) When i try run virtualbox i see error message (some time different) see attached screenshots Pls FIX ASAP Thanks |
|||
| #16255 | obsolete | host memory leak on CentOS 7 with VirtualBox 5.1.10 | ||
| Description |
I appear to be experiencing a host memory leak running VirtualBox 5.1.10 on CentOS 7 hostVM (uname -r) 3.10.0-327.36.3.el7.x86_64 Guest VM is Windows 10, build 1607 Suspect lines from the logs are: 48:01:00.432446 VMMDev: Guest Log: VBoxMP::DxgkDdiQueryCurrentFenceNew: WARNING! :=>DxgkDdiQueryCurrentFenceNew 48:01:00.481870 VMMDev: Guest Log: VBoxMP::DxgkDdiQueryCurrentFenceNew: WARNING! :uncompleted fences, u32FenceSubmitted(2257299), u32FenceCompleted(2257297) u32FenceProcessed(2257297) Originally, the VM was set for 12GB (Host has 16GB) and the VirtualBox user process ran up to 16GB, system started using swap heavily and ground to a halt. Reset VM to 10GB and user process has grown to 14GB and continues to grow slowly, requiring that the guest be shutdown and VirtualBox exited to free the memory. |
|||

