ID Event 12 for VBoxNetLwf

Discussions related to using VirtualBox on Windows hosts.

Re: ID Event 12 for VBoxNetLwf

Postby scottgus1 » 11. Sep 2019, 14:09

Throwing in my oar, same results as Socratis: hundreds of the error, not a single BSOD.
error 12 VboxNetLwf.png
error 12 VboxNetLwf.png (37.13 KiB) Viewed 290 times
Human government is like that crazy uncle who hides a quarter in his fist behind his back, then asks you to guess which fist the quarter is in...
No matter which side you choose, Left or Right, both Sides are empty.
scottgus1
Volunteer
 
Posts: 4502
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Win7

Re: ID Event 12 for VBoxNetLwf

Postby Opsen » 27. Sep 2019, 00:23

I think I've discovered the issue folks. So if you've such a file(vboxusb.inf) in your system even though you've uninstalled the vbox or restored windows image, somehow you should get rid of it!

Annotation 2019-09-26 155514.png
vbox file after system restore
Annotation 2019-09-26 155514.png (95.02 KiB) Viewed 236 times


I was just touching this file today and believe me my pc restarted at least 2 or 3 times with kernel power critical errors. I've installed ubuntu and I don't have anymore this problem atm :evil:
Opsen
 
Posts: 1
Joined: 27. Sep 2019, 00:13

Re: ID Event 12 for VBoxNetLwf

Postby socratis » 28. Sep 2019, 11:15

Opsen wrote:I was just touching this file today and believe me my pc restarted at least 2 or 3 times with kernel power critical errors.

Nope, that can't be it. This is the "DriverStore" (cache) of already installed drivers. Touching/modifying a file there shouldn't produce a BSOD, doesn't make sense...

Also, if you're only seeing the ID Event 12 for VBoxNetLwf, again, that's a red herring.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
socratis
Site Moderator
 
Posts: 26017
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5

Re: ID Event 12 for VBoxNetLwf

Postby te777 » 1. Oct 2019, 11:14

Please delete this post.
Last edited by te777 on 1. Oct 2019, 12:07, edited 2 times in total.
te777
 
Posts: 28
Joined: 15. Jul 2014, 19:09

Re: ID Event 12 for VBoxNetLwf

Postby socratis » 1. Oct 2019, 12:02

te777,
You threw in a bunch of unrelated issues in your 1st paragraph. We like to observe the "One issue, one thread" rule...

And in your 2nd paragraph, the VBoxNetLwf error on your host has absolutely nothing to do with the VBoxSVGA controller for your guest.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
socratis
Site Moderator
 
Posts: 26017
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5

Re: ID Event 12 for VBoxNetLwf

Postby aymaliev » 1. Oct 2019, 14:19

Hello

Just wanted to say that this error "ID Event 12 for VBoxNetLwf" is very problematic.
On my fujitsu e736 (win7x64,vbox 6.0.4), it destroys all currently established network connections and I cannot reconnect for about 10 minutes after this happens.

Also, being a standard user, it took me a great deal of time (reading, visits from the ISP support) to find out what is causing this behaviour.

Huge "Thanks!" to the guys, who suggested disabling the virtualbox Host-Only network adapter. It solved the problem and, I guess, I am not using that for anything :)

Hope this error gets a solution soon.
aymaliev
 
Posts: 1
Joined: 1. Oct 2019, 14:02

Re: ID Event 12 for VBoxNetLwf

Postby socratis » 1. Oct 2019, 21:22

aymaliev wrote:it destroys all currently established network connections and I cannot reconnect for about 10 minutes after this happens.
This has absolutely nothing to do with the "Network filter driver is not set to go to sleep properly", which is what Event 12 is.

aymaliev wrote:who suggested disabling the virtualbox Host-Only network adapter. It solved the problem
Again, the HostOnly adapter is an additional adapter for the host. The VBoxNetLwf driver is part of the Bridged networking. Nothing to do with the HostOnly part.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
socratis
Site Moderator
 
Posts: 26017
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5

Re: ID Event 12 for VBoxNetLwf

Postby Haeckli » 2. Oct 2019, 10:13

I have this same error in my events since quite some time on each reboot. So in the recent days I finally did some "forensics" in the history of my event-log's and I found 2 events which contributed to this error:

  1. In January 2018 I installed the 'Nmap Security Scanner' (Version 7.60) which came along with a new network-device: the 'Npcap Loopback Adapter' (Version 0.93)
    Screenshot - 02.10.2019 , 08_56_16.png
    Network adapters in device manager
    Screenshot - 02.10.2019 , 08_56_16.png (10.06 KiB) Viewed 167 times
  2. In May 2018 I updated VirtualBox from 5.1.34 to 5.1.38
Immediately after that Vbox update I got the first 'VBoxNetLwf' error and ever since I had it on each reboot.

I never thought that these 2 events caused an incompatibility which I only found today. The point is, that the 'VirtualBox NDIS6 Bridged Networking Driver" is linked into just ALL current network adapters, so it was also linked to the 'Npcap Loopback Adapter'. I now disabled it in the adapter's properties and the 'VBoxNetLwf' error was immediately gone.

Screenshot - 02.10.2019 , 08_16_22.png
Properties Npcap Loopback Adapter
Screenshot - 02.10.2019 , 08_16_22.png (40.33 KiB) Viewed 167 times

'Playing' around a bit more I finally found 3 possible solutions of the problem:
  1. De-Select the 'VirtualBox NDIS6 Bridged Networking Driver' as described before
  2. Update the 'Npcap Loopback Adapter' to its latest version 0.9983 (which you find here)
  3. Uninstall the 'Npcap Loopback Adapter' if you don't really need it.
Any of these methods work perfectly fine - no such error ever occurred again, regardless of which solution I applied.

In my case it was the 'Npcap Loopback Adapter' but there may be other network devices around which cause the same problem. I would therefore suggest that the 'VirtualBox NDIS6 Bridged Networking Driver' is enabled only in the physical network-ports and in the 'VirtualBox Host-Only Network'.

Comments welcome...
Haeckli
 
Posts: 15
Joined: 18. Aug 2014, 08:24
Location: Zürich, Switzerland
Primary OS: MS Windows 7
VBox Version: PUEL
Guest OSses: W7-64, W10-64

Re: ID Event 12 for VBoxNetLwf

Postby nono303 » 2. Oct 2019, 16:12

Hi,

Thanks to @Haeckli feedback, i've just De-Select the 'VirtualBox NDIS6 Bridged Networking Driver' for my TAP-Windows Adapter V9 (openvpn, not required for my virtual machine) and the Event ID12 disappear after reboot :)
nono303
 
Posts: 1
Joined: 2. Oct 2019, 16:10

Re: ID Event 12 for VBoxNetLwf

Postby socratis » 3. Oct 2019, 00:02

Haeckli, nono303
It is to be expected that if a driver isn't loaded, that driver won't generate and Events in the Event Viewer... ;)
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
socratis
Site Moderator
 
Posts: 26017
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5

Re: ID Event 12 for VBoxNetLwf

Postby Haeckli » 3. Oct 2019, 09:12

socratis wrote:It is to be expected that if a driver isn't loaded, that driver won't generate and Events in the Event Viewer... ;)

But the 'VirtualBox NDIS6 Bridged Networking Driver' is still loaded because it is still enabled in all other network devices...
Haeckli
 
Posts: 15
Joined: 18. Aug 2014, 08:24
Location: Zürich, Switzerland
Primary OS: MS Windows 7
VBox Version: PUEL
Guest OSses: W7-64, W10-64

Re: ID Event 12 for VBoxNetLwf

Postby socratis » 3. Oct 2019, 09:35

Oh... I didn't realize that/read that correcty, sorry, mea culpa. :?
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
socratis
Site Moderator
 
Posts: 26017
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5

Previous

Return to VirtualBox on Windows Hosts

Who is online

Users browsing this forum: No registered users and 37 guests