Ticket #18744 (new defect)

Opened 20 months ago

Last modified 20 months ago

Virtualbox causes an abend Windows when it opens a Linux VM

Reported by: Speedycool Owned by:
Component: other Version: VirtualBox 6.0.8
Keywords: VBoxNetLwf Cc:
Guest type: Linux Host type: Windows


I Use Virtualbox since several years. My host is a Windows seven with 8 Go RAM. I tried several linux with success until some days. I had Linux Mint Plasma, Windows 10 as VM. Windows 10 works ithout problem. But when i tried to access Linux Mint, it abends Windows Seven. I get out Linux Mint from Virtualbox, and tried to re-install it. No success. Each try Abends Windows. I tried the Virtualbox 6.0.6 .... : same effects.

The message in Windows events is : Nom du journal :System Source : VBoxNetLwf Date : 05/07/2019 16:08:37 ID de l’événement :12 Catégorie de la tâche :Aucun Niveau : Erreur Mots clés : Classique Utilisateur : N/A Ordinateur : Daniel-PC Description : Le pilote a détecté une erreur de pilote interne sur \Device\VBoxNetLwf. XML de l’événement : <Event xmlns="">


<Provider Name="VBoxNetLwf" /> <EventID Qualifiers="49156">12</EventID> <Level>2</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2019-07-05T14:08:37.444012300Z" /> <EventRecordID>794248</EventRecordID> <Channel>System</Channel> <Computer>Daniel-PC</Computer> <Security />

</System> <EventData>

<Data>\Device\VBoxNetLwf</Data> <Binary>0000080001000000000000000C0004C0080000000000000000000000000000000000000000000000BCAEC55CB4500000</Binary>



I Hope to understand this problem, and resolve it ! Thanks.

Change History

comment:1 Changed 20 months ago by socratis

  1. It's usually better and faster, if issues get first addressed in the  VirtualBox forums, a lot more eyes there. More than 95% of the issues are resolved in the forums, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of. For example, yours is most probably not a bug and someone from the developers has to deal with it and close it as "Invalid".

Plus a discussion and analysis on the bug tracker is going to help me, you, and potentially a future drive-by user or two. Not so in the forums, many more tend to benefit...

  1. It's also equally important to use a simple search before filing a ticket. Searching for  VBoxNetLwf for example, returns the following thread in the forums:  ID Event 12 for VBoxNetLwf. Read the thread, it might help you understand that this is not what caused your system to crash.

I have that error in my EventViewer (plenty of instances) and I've never had a single crash...

Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use