Virtualbox bsod windows 10

Ticket #15144 (new defect)

Last modified 4 years ago

BSOD — Windows 10 host VBoxNetLwf.sys

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

Change History

Changed 5 years ago by kpm

Windows 10 blue screen PAGE FAULT with VBoxNetLwf.sys

comment:1 Changed 5 years ago by kpm

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 Changed 5 years ago by aleksey

Could you try the latest test build from here? If you still get BSOD, please run VBoxBugReport 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.

comment:3 follow-up: ↓ 5 Changed 5 years ago by frank

We are still interested in the test results. Please test with VBox 5.0.16.

comment:4 Changed 5 years ago by kpm

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!

comment:5 in reply to: ↑ 3 Changed 5 years ago by kpm

I tested using 5.0.16 and I can confirm this issue is still present for me. I have attached minidump and VBoxBugReport.

We are still interested in the test results. Please test with VBox 5.0.16.

comment:6 follow-up: ↓ 7 Changed 5 years ago by 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.

comment:7 in reply to: ↑ 6 Changed 5 years ago by aleksey

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?

Changed 4 years ago by kpm

Replaced due to personal reasons

Changed 4 years ago by kpm

Replaced due to personal reasons

Changed 4 years ago by kpm

Replaced due to personal reasons

Changed 4 years ago by kpm

Replaced due to personal reasons

Changed 4 years ago by kpm

Bug Report from VirtualBox 5.0.17 on 15th July

Changed 4 years ago by kpm

Windows 10 minidump from 15-07-2016

comment:8 Changed 4 years ago by kpm

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 Changed 4 years ago by frank

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 Changed 4 years ago by Witbro58

I have the same issue on WIndows 10 build 14372 — I startup a virtual machine and Windows 10 BSOD

Источник