"The driver detected an internal driver error on \Device\VBoxNetLwf" happen many time.

[Eritque arcus]

I see error(Event ID = 12, source = VBoxNetLwf, general = The driver detected an internal driver error on \Device\VBoxNetLwf.) everyday in Event Viewer.
OS version = Windows11 21H2
Virtual Box version = 6.1.34 r150636 (Qt5.6.2)


error head:

<Provider Name="VBoxNetLwf" />

<EventID Qualifiers="49156">12</EventID>

<Version>0</Version>

<Level>2</Level>

<Task>0</Task>

<Opcode>0</Opcode>

<Keywords>0x80000000000000</Keywords>


Here are some errors with different data.

<EventData>

<Data>\Device\VBoxNetLwf</Data>

<Binary>0000180001000000000000000C0004C008000000000000000000000000000000000000000000000080B6555278CC80B6555278CBC85ACF44CC8100FFFD08E3FF</Binary>

</EventData>

<EventData>

<Data>\Device\VBoxNetLwf</Data>

<Binary>0000080001000000000000000C0004C008000000000000000000000000000000000000000000000000FF92A2455F0000</Binary>

</EventData>

<EventData>

<Data>\Device\VBoxNetLwf</Data>

<Binary>0000000001000000000000000C0004C0080000000000000000000000000000000000000000000000</Binary>

</EventData>

<EventData>

<Data>\Device\VBoxNetLwf</Data>

<Binary>0000140001000000000000000C0004C008000000000000000000000000000000000000000000000080B6555278CBC85ACF44CC8100FFFD08E3FF0000</Binary>

</EventData>

[scottgus1]

I get those errors too on my hosts. Nothing actually breaks or stops working, despite the error being logged.

Are you having any trouble running Virtualbox? If not, you can probably safely ignore the error, as I do.

[Eritque arcus]

I get those errors too on my hosts. Nothing actually breaks or stops working, despite the error being logged.

Are you having any trouble running Virtualbox? If not, you can probably safely ignore the error, as I do.

Yes, there isn't any trouble runing virtualbox. But recently, my windows will suddenly shutdown with bluescreen like code = power_state_fail or "The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f". So, I try to figure out is there any relationship between those.

[scottgus1]

The 'WinDbg" app on the Microsoft store will hunt up the reason for the bsod.

[AcidHorse]

https://answers.microsoft.com/en-us/win ... 349a2badf3

Says VBoxNetLwf is root cause of BSOD. And I've seen it also at the center of critical system errors too. Only resolved when VirtualBox was uninstalled.

[scottgus1]

It could be possible a network card driver doesn't interface properly with Virtualbox's network card. Anything is technically possible. Were this a major problem with Virtualbox's driver preventing stable host operation, there'd be far more discussion of it in the forums. That there isn't means either that there really no problems from this error, or some very few folks have that required yet undiagnosed condition where Windows + Virtualbox + something else no one knows about yet causes a BSOD that points to Virtualbox's network driver.

But I get these errors on my three Virtualbox hosts all the time with nary a BSOD's accompaniment, per my previous post on the subject. We had a super long topic on this where forum gurus also reported no BSODs despite the error being registered.

Acidhorse, you're re-opening this subject from someone else's topic from 6 months ago, posting a Microsoft forum report from 5 months ago. For what reason?

[fablege]

I see this error whenever I connect to a VPN, doesn't seem to hurt anything however, just the error is emitted.

[MikeRuth]

Thread is a bit old but this problem has cropped up on my customers PC.
Have found nothing to address it. Random crashes on W10 and the latest version of Vbox.
related or not at the same time the PC will no longer backup using EaseUS ToDo backup. Reinstalled that as well with no change.

At this point I'm just announciung the problem. The PC has been in service for a few years now and a reload is not going to be all that difficult. Not my first choice but under the circumstances thats the path I'm taking.

I will post up the results after the reload.

Mike R

[scottgus1]

MikeRuth, the VBoxNetLwf" error may be a red herring. It happens on many forum gurus' PCs without any host stability issues. Please start a new topic if you run into any problems.

All me-too-ers, please read my post above on this error, and start a new topic if you have solid evidence that the BSOD is coming from Virtualbox.