El controlador detectó un error interno del controlador en \Device\VBoxNetLwf.

Discussions related to using VirtualBox on Windows hosts.
negroscuro
Posts: 19
Joined: 4. Apr 2020, 13:46

El controlador detectó un error interno del controlador en \Device\VBoxNetLwf.

Post by negroscuro »

I am using VirtualBox-7.0.12-159484-Win in Windows10 and constantly receiving dpc_watchdog_violation blue screen.
I checked Windows events and got:

Clásico 14/12/2023 19:07:29 VBoxNetLwf 12 Ninguno

Nombre de registro:System
Origen: VBoxNetLwf
Fecha: 14/12/2023 19:07:29
Id. del evento:12
Categoría de la tarea:Ninguno
Nivel: Error
Palabras clave:Clásico
Usuario: No disponible
Equipo: BLACKPOWER-2
Descripción:
El controlador detectó un error interno del controlador en \Device\VBoxNetLwf.
XML de evento:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="VBoxNetLwf" />
<EventID Qualifiers="49156">12</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2023-12-14T18:07:29.8892033Z" />
<EventRecordID>15678</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="1996" />
<Channel>System</Channel>
<Computer>BLACKPOWER-2</Computer>
<Security />
</System>
<EventData>
<Data>\Device\VBoxNetLwf</Data>
<Binary>0000080001000000000000000C0004C0080000000000000000000000000000000000000000000000F46D046E90C70000</Binary>
</EventData>
</Event>

Is there any way to solve this? I cant use the computer for more than 30-40 minutes until it freezes and have to restart it, really inconvinient.
Thank you in advance.
scottgus1
Site Moderator
Posts: 20945
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: El controlador detectó un error interno del controlador en \Device\VBoxNetLwf.

Post by scottgus1 »

I also get VBoxNetLwf 12 errors all the time on my Virtualbox host, but no bluescreens and no problems on the host. We had a big discussion about it some time ago, but no one was able to demonstrate firmly that there was a problem behind the event viewer messages.

Please use the Microsoft Store's "windbg preview" app, to see what caused the actual bluescreen.
negroscuro
Posts: 19
Joined: 4. Apr 2020, 13:46

Re: El controlador detectó un error interno del controlador en \Device\VBoxNetLwf.

Post by negroscuro »

I removed VirtualBox and for now it seems there is no trouble. The problem is that i need to use VirtualBox.
Thank you, I will download it and check.
negroscuro
Posts: 19
Joined: 4. Apr 2020, 13:46

Re: El controlador detectó un error interno del controlador en \Device\VBoxNetLwf.

Post by negroscuro »

I reinstalled Virtualbox and removed this Windows feature (hypervisor windows platform) and for now it seem there is not trouble.
scottgus1
Site Moderator
Posts: 20945
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: El controlador detectó un error interno del controlador en \Device\VBoxNetLwf.

Post by scottgus1 »

That sounds good! If you have any other problems please let us know.
negroscuro
Posts: 19
Joined: 4. Apr 2020, 13:46

Re: El controlador detectó un error interno del controlador en \Device\VBoxNetLwf.

Post by negroscuro »

LoL, as soon as I posted I had another crash. I think its not related but usually happens when watching youtube videos.
:(
But this is happening without using Virtualbox. It is installed but I am not using it.
scottgus1
Site Moderator
Posts: 20945
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: El controlador detectó un error interno del controlador en \Device\VBoxNetLwf.

Post by scottgus1 »

negroscuro wrote: 17. Dec 2023, 15:10 But this is happening without using Virtualbox. It is installed but I am not using it.
So the crash only happens when Virtualbox is installed, but Virtualbox doesn't have to be in use?

Sounds like a driver incompatibility.

Please try this:
  1. Uninstall Virtualbox and reboot.
  2. Go to "C:\Windows\System32\drivers", look for any files called 'Vbox*.sys' (there could be up to 5) and delete them.
  3. Reboot again.
  4. Take a reliable & restorable backup image of the host.
  5. Check for any network card driver updates from Microsoft or the network card/motherboard manufacturer.
  6. Reboot again.
  7. If you have any 3rd-party security or anti-malware software, disable the living daylights out of it for a moment.
  8. Reinstall Virtualbox using right-click-Run-As-Administrator.
Please report back what happens.
negroscuro
Posts: 19
Joined: 4. Apr 2020, 13:46

Re: El controlador detectó un error interno del controlador en \Device\VBoxNetLwf.

Post by negroscuro »

I am still testing the error situation but I got in Windows event viewer this:
"El controlador detectó un error interno del controlador en \Device\VBoxNetLwf."
It says about controller error in \Device\VoxNetLwf,

I would say so, I am just using text editors and web browsers but not VirtualBox neither any virtual machine.

I just updated realtek LAN drivers for my motherboard, deleted just two vbox*.sys files I spotted where you pointed. Now I am reinstalling Vbox and lets see how it goes.

Thank you I will go through your steps, really appreciated.
negroscuro
Posts: 19
Joined: 4. Apr 2020, 13:46

Re: El controlador detectó un error interno del controlador en \Device\VBoxNetLwf.

Post by negroscuro »

After some hours using the PC i had almost the same situation. I say almost because this time I was not using the web browser neither watching youtube videos only listening at spotify while working.
The PC got frozen but music still playing, not a frozen sound like other times. After a minute or so it went unfrozen and then I could keep using the PC, so no blue screen, no need to reboot this time.
My worry is that I entered the Windows event viewer and I could not find any system event, not event at all at that date/time so I have no clue about what happened.
negroscuro
Posts: 19
Joined: 4. Apr 2020, 13:46

Re: El controlador detectó un error interno del controlador en \Device\VBoxNetLwf.

Post by negroscuro »

It happened again, but shorter and I located an event and it seems to be a permissions problem.

Nombre de registro:System
Origen: Microsoft-Windows-DistributedCOM
Fecha: 17/12/2023 22:06:02
Id. del evento:10016
Categoría de la tarea:Ninguno
Nivel: Advertencia
Palabras clave:Clásico
Usuario: BLACKPOWER-2\negro
Equipo: BLACKPOWER-2
Descripción:
La configuración de permisos específico de la aplicación no concede el permiso Activación Local para la aplicación de servidor COM con CLSID
{8BC3F05E-D86B-11D0-A075-00C04FB68820}
y APPID
{8BC3F05E-D86B-11D0-A075-00C04FB68820}
al usuario BLACKPOWER-2\negro con SID (S-1-5-21-1010681197-2761319968-156426552-1001) en la dirección LocalHost (con LRPC) que se ejecuta en el contenedor de aplicaciones con SID No disponible (S-1-15-2-2138201627-2370946588-2569457441-1783555471-4253601483-216551176-1766593237). Este permiso de seguridad se puede modificar mediante la herramienta administrativa Servicios de componentes.
XML de evento:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />
<EventID Qualifiers="0">10016</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2023-12-17T21:06:02.5738124Z" />
<EventRecordID>16369</EventRecordID>
<Correlation ActivityID="{de3eb25d-0ad1-48dc-a6bc-126d39d99144}" />
<Execution ProcessID="628" ThreadID="664" />
<Channel>System</Channel>
<Computer>BLACKPOWER-2</Computer>
<Security UserID="S-1-5-21-1010681197-2761319968-156426552-1001" />
</System>
<EventData>
<Data Name="param1">específico de la aplicación</Data>
<Data Name="param2">Local</Data>
<Data Name="param3">Activación</Data>
<Data Name="param4">{8BC3F05E-D86B-11D0-A075-00C04FB68820}</Data>
<Data Name="param5">{8BC3F05E-D86B-11D0-A075-00C04FB68820}</Data>
<Data Name="param6">BLACKPOWER-2</Data>
<Data Name="param7">negro</Data>
<Data Name="param8">S-1-5-21-1010681197-2761319968-156426552-1001</Data>
<Data Name="param9">LocalHost (con LRPC)</Data>
<Data Name="param10">No disponible</Data>
<Data Name="param11">S-1-15-2-2138201627-2370946588-2569457441-1783555471-4253601483-216551176-1766593237</Data>
</EventData>
</Event>
scottgus1
Site Moderator
Posts: 20945
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: El controlador detectó un error interno del controlador en \Device\VBoxNetLwf.

Post by scottgus1 »

And you're sure this freeze-up and bluescreening only happens when Virtualbox is installed? Have you let the computer run without Virtualbox installed for a long time lately? Just wondering if there is really a new problem with the disk or RAM, which could also cause freeze-up, and maybe Virtualbox is not involved.
negroscuro
Posts: 19
Joined: 4. Apr 2020, 13:46

Re: El controlador detectó un error interno del controlador en \Device\VBoxNetLwf.

Post by negroscuro »

Yes I did and there was no VBoxNetLwf error, no sound frozen, no blue screen. I thought about ram. This PC was only 8GB RAM and this issue was a reason to upgrade it, and I did, up to 16GB but the issue still there. What partiallly solved is the update of motherboard driver as you pointed (and the deletion of the system32 files).

Mmmmh i didnt installed any more software apart from vbox and vmware(I removed this second).
I had a virus and I removed it. Same as this guy posted here (https://answers.microsoft.com/es-es/win ... 3f7fdee3d7) I solved in the same way like he did, manually removing registry entries, some folders and files (.exe and .au3) from my C:/ drive and a windows start up process. After that i anallyzed with antimalwrebytes and other 2 antivirus/antimalware and ccleaner.

But I also remember a Windows mandatory update was installed last week or so, this is my Windows recent update history:
Image

The "El controlador detectó un error interno del controlador en \Device\VBoxNetLwf." still happen but system still working, no blue screen, just froze for half a second.
negroscuro
Posts: 19
Joined: 4. Apr 2020, 13:46

Re: El controlador detectó un error interno del controlador en \Device\VBoxNetLwf.

Post by negroscuro »

It just happened right now... blue screen, reboot. Same VBoxNetLwf event. I dont know what to do, its impossible to work for some hours in a row. Desperating.
I am removing VirtualBox, no chance...
scottgus1
Site Moderator
Posts: 20945
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: El controlador detectó un error interno del controlador en \Device\VBoxNetLwf.

Post by scottgus1 »

Sorry we couldn't help. I'm out of ideas. Looks like some compatibility issue between something on the computer, maybe a driver, and Virtualbox. The VBoxNetLwf error may be a symptom, not the cause: it's happened on my PC for years without crashes.

FWIW the Virtualbox installer allows disabling a couple Virtualbox features, one of which is networking, either Bridged or Host-Only or both, and USB. All of these need drivers plugged into the host OS. You could try different permutations and combinations of the installer options to see what doesn't cause the crash.
negroscuro
Posts: 19
Joined: 4. Apr 2020, 13:46

Re: El controlador detectó un error interno del controlador en \Device\VBoxNetLwf.

Post by negroscuro »

I really appreciate your concern about this, thank you!
This evening i had 3 crashes.
Last one virtualbox was uninstalled and sys files in /windows/system32/drivers, deleted.
I got this from event viewer:


Nombre de registro:System
Origen: Service Control Manager
Fecha: 18/12/2023 22:22:36
Id. del evento:7023
Categoría de la tarea:Ninguno
Nivel: Error
Palabras clave:Clásico
Usuario: No disponible
Equipo: BLACKPOWER-2
Descripción:
El servicio GameInput Service se cerró con el siguiente error:
El archivo compuesto GameInput Service se creó con una versión de almacenamiento más reciente.
XML de evento:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
<EventID Qualifiers="49152">7023</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2023-12-18T21:22:36.7939889Z" />
<EventRecordID>16565</EventRecordID>
<Correlation />
<Execution ProcessID="736" ThreadID="1224" />
<Channel>System</Channel>
<Computer>BLACKPOWER-2</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">GameInput Service</Data>
<Data Name="param2">%%2147680517</Data>
<Binary>470061006D00650049006E00700075007400200053006500720076006900630065000000</Binary>
</EventData>
</Event>

So looks like several things are crashing but maybe is not Virtualbox fault in the end...
Post Reply