Opened 9 years ago
Last modified 12 months ago
#15144 new defect
BSOD - Windows 10 host VBoxNetLwf.sys
| Reported by: | kpm | Owned by: | |
|---|---|---|---|
| Component: | network | Version: | VirtualBox 5.0.14 |
| Keywords: | bsod vboxnetlwf.sys | Cc: | |
| Guest type: | Windows | Host type: | Windows |
Description
I have had a handful of intermittent Windows 10 'blue screen of death' host crashes of type PAGE FAULT IN NONPAGED AREA which mention VBoxNetLwf.sys over the last few weeks. This has been observed with multiple minor releases of VirtualBox since version 5.0 and multiple releases of Windows 10 Professional.
I suspect this may not be a VirtualBox bug and more likely an issue with our security software (Symantec Endpoint Protection) or the host Windows OS (as I only noticed this issue since updating from Win 8.1 Pro).
Happy to provide any more info that might help, attached a screen grab of the crash.
Attachments (8)
Change History (22)
by , 9 years ago
| Attachment: | vbox-bsod.jpg added |
|---|
comment:1 by , 9 years ago
Sorry, forgot to mention the guest is a Windows 7 one I've been using without issues for years. With the latest guest additions on it.
comment:2 by , 9 years ago
Could you try the latest test build from here? If you still get BSOD, please run VBoxBugReport <vm_name> and send the result to aleksey dot ilyushin at oracle dot com. It would help immensely if you could send the minidump generated at BSOD as well.
follow-up: 5 comment:3 by , 9 years ago
We are still interested in the test results. Please test with VBox 5.0.16.
comment:4 by , 9 years ago
Hi, I just had a repeat of this intermittent issue but was using version 5.0.14 r105127. I have just downloaded and installed version 5.0.16 r105871 and will let you know if the issue is still present, thanks.
VBoxBugReport output and Windows 10 minidump files now attached for version 5.0.14 please if you can help that will be very much appreciated, this caused me to lose an hours work, quite frustrating!
Thanks,
KPM
comment:5 by , 9 years ago
I tested using 5.0.16 and I can confirm this issue is still present for me. I have attached minidump and VBoxBugReport.
Replying to frank:
We are still interested in the test results. Please test with VBox 5.0.16.
follow-up: 7 comment:6 by , 9 years ago
Just FYI - if it might help, I have zipped the full Windows 10 memory dump file and can upload it to a shared location. If any more info is required to resolve this defect please just ask, thanks.
comment:7 by , 9 years ago
Replying to kpm:
Just FYI - if it might help, I have zipped the full Windows 10 memory dump file and can upload it to a shared location. If any more info is required to resolve this defect please just ask, thanks.
Thanks a lot for providing the files! From what I can get out of the minidump it looks like a bug in packet logging, and the complete dump file would be an immense help. Could you upload it to a location of your choice and send me the link to aleksey dot ilyushin at oracle dot com?
by , 9 years ago
| Attachment: | bugreport_15-07-2016.tgz added |
|---|
Bug Report from VirtualBox 5.0.17 on 15th July
comment:8 by , 9 years ago
Had this critical issue hit me three times today. Tried changing the network mode of the VM from bridged to NAT and changed the vNIC driver too. Fingers crossed this goes away. I'm also uploading a full memory dump to my dropbox but its quite large (929MB zipped) and slow to transfer.
comment:9 by , 9 years ago
kpm, please let me know if you have an URL for the full memory dump. Feel free to contact me via email at frank _dot_ mehnert _at_ oracle _dot_ com. Don't forget to mention the exact VBox version where you took the dump from.
comment:10 by , 9 years ago
I have the same issue on WIndows 10 build 14372 - I startup a virtual machine and Windows 10 BSOD
by , 4 years ago
| Attachment: | 030621-22109-01.dmp.gz added |
|---|
Minidump from crash caused by VBoxNetLwf.sys
comment:12 by , 4 years ago
I've been getting random BSODs lately, after running driver verifier to narrow down the culprit I get a BSOD on boot and it appears VBoxNetLwf.sys is the problem. I've tried updating Virtual Box to the latest ( Version 6.1.18 r142142 (Qt5.6.2) ) but still get the same issue. I've attached minidump of latest BSOD (using driver verifier).
comment:13 by , 4 years ago
Hello,
VirtualBox 6.1.18 r142142 (Qt5.6.2)
I've recently upgraded Windows 10 to 20H2 19042.870, and suddenly VirtualBox cannot run *newly created* VMs. For example a new Ubuntu Focal (20.04) VM with NAT networking starts, some regular kernel boot output is seen, then the whole VirtualBox GUI is frozen.
Interestingly if I close the GUI via the task manager, then restart it I can click around, but it again freezes as soon as I click on the "running" VM.
Running a VM created previously seems to work fine, though I experienced some strange timeouts. (It also runs Ubuntu and a postgresql 10 DB, nothing else.)
Creating a completely new VM via the GUI using bridged networking seems to boot successfully, and the network seems to work too. (ping6 works.)
Today when restarting Windows after it close every window it produced a BSOD with "critical process died" error.
I checked the event log, there have been many VBoxNetLwf errors (at least since 2020-10, but it that's the start of the event logs).
comment:14 by , 12 months ago
https://i.ibb.co/SJSws9P/image.png i still face the exactly same issue with Windows 10 Version 22H2 and Virtualbox 7.0 latest version for now (
Windows 10 blue screen PAGE FAULT with VBoxNetLwf.sys