Opened 7 years ago
Last modified 7 years ago
#16229 new defect
Blue screen of the death when you change to Bridged Adapter
Reported by: | AlekseiG | Owned by: | |
---|---|---|---|
Component: | network | Version: | VirtualBox 5.1.10 |
Keywords: | Cc: | ||
Guest type: | Windows | Host type: | Windows |
Description
All worked fine before update of my network driver. (I updated by KillerSuite_1.1.65.1752_Win7_Win81_Win10).
But after update, when I share internet using Bridge, blue screen of the death for host machine is appeared. If i don't have connection to the internet on host machine (Wi-Fi/Ethernet), all are working fine, but after connection all crash too.
version of Vbox is 5.1.10 r112026 (Qt5.6.2) Both(host and guest) have windows 10
Could you please tell, is it problem of Vbox or my driver? What is the best way to resolve it? Rollback driver\create ticket for them or is it Vbox problem?
Attachments (3)
Change History (9)
by , 7 years ago
by , 7 years ago
Attachment: | VBoxHardening.log added |
---|
by , 7 years ago
Attachment: | VBox.log.1 added |
---|
comment:1 by , 7 years ago
- I would uninstall and re-install VirtualBox, just to re-enable the binding to the wireless driver. Uninstall VirtualBox, right-click on the installer and "Run as Administrator". Don't elect to run it at the end of the installation, but start it normally as you would every day.
- Roll back the drivers. Buggy drivers are not unheard of.
- Talk to the KillerNetworking support. They are in the unique position to be able to debug their drivers and it's really easy to install VirtualBox and try to reproduce the problem on their side, vs Oracle getting a hold of that specific network card that you have.
comment:2 by , 7 years ago
I can verify that this happens on Windows 10 Pro, VirtualBox 5.1.10 r112026, plus Killer Ethernet E2200 driver version 1.0.857_x64 downloaded today from Killer's networking site (Updated on 15 November 2016). Note that I installed the drivers, not the suite.
Every time I put a Windows 7 guest into bridged mode, my Windows 10 host crashes. I've done no additional diagnostics on this, but it works in NAT mode.
comment:4 by , 7 years ago
Yes, I saw your answer. But isn't it nice to have more than one data point to ensure that you can safely say "it's not our problem?" :-)
follow-up: 6 comment:5 by , 7 years ago
Solution: Go to control panel, networking, select your network adapter (Local Area Connection), select properties, and uncheck the Killer Bandwidth control.
comment:6 by , 7 years ago
Replying to EricLoyd:
Solution: Go to control panel, networking, select your network adapter (Local Area Connection), select properties, and uncheck the Killer Bandwidth control.
I can confirm, disabling "Killer Bandwidth Control" fixed it for me too. (Windows 10, VirtualBox 5.1.14).
logs are attached