Windows 10 virtual machine network access causes BSOD on Lenovo Laptop with Win 8.1 Pro when accessing internet via wireless

Hello everybody,


i've installed a win 10 insider preview as Hyper-V virtual machine on my Lenovo T540p laptop with Intel network and wifi. If this machine is connected to external network through wifi card, then host OS crashed with blue screen after booting the VM. Crash occurs some minutes after VM is booted completed, in my opinion when network traffic is initialized.

Blue screen reason is irql_not_less_or_equal.

Connecting via same HV-virtual switch bound to wired network interface, everything is working fine. Same without network connection.

I can run other VM's (server 2012r2) without any problem via wireless interface. Interface is Intel Dualband Wireless-AC 7260 with original Lenovo driver.

What do you think, should i submit a bug report to

- lenovo

- Intel

- Microsoft

What would you prefer?

Greetings,

Markus

June 19th, 2015 9:17pm

  We do need the actual log files (called a DMP files) as they contain the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.  

Please follow our instructions for finding and uploading the files we need to help you fix your computer. They can be found here If you have any questions about the procedure please ask
Free Windows Admin Tool Kit Click here and download it now
June 19th, 2015 9:29pm

Hello,

please find the last 4 dumps in onedrive:

https://onedrive.live.com/redir?resid=6003A47B1A65554B%21138

June 19th, 2015 9:47pm

Three different error codes.  Run verifier to find the underlying issue

These crashes were related to memory corruption (probably caused by a driver). 

Please run these two tests to verify your memory and find which driver is causing the problem.  Please run verifier first.  You do not need to run memtest yet unless verifier does not find the cause, or you want to.


If you are over-clocking anything reset to default before running these tests. In other words STOP!!!  If you do not know what this means you probably are not

1-Driver verifier (for complete directions see our wiki here)
2-Memtest. (You can read more about running memtest here)


Free Windows Admin Tool Kit Click here and download it now
June 20th, 2015 12:14am

Hi,

here is my diag:

- overclocking? never ever. Bios defaults are used

- memtest: successful without errors

- check device manager for visible errors: none found

- driver verifier like describe in your link: crash on start with irql_not_less_or_equal - reset driver verifier in safe mode

- driver verifier again, but do not check netwbw02.sys (Intel wifi driver): system boots up and crashed with DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL (epfwwfp.sys) ESET personal firewall.

... uninstall eset and uninstall intel wifi driver now and will test again...

June 20th, 2015 4:42pm

Second update:

Downgrade Wifi driver to 17.13.12.1 (from 17.16) and running verifier again without eset AV: startup ok, verification ok, running Win 10 VN with network via wifi also ok

Installing latest eset, rebooting and activate verifier causes BSOD with epfwwbw02.sys and IRQL_ BSOD again after reboot again. But, this is important, Win 10 VM works :)

Seems i should fill a bug report to eset. But i am very tired in testing, my laptop is protected with bitlocker and typing recovery key again and again is really stupid

PS: Wifi 17.16 was deliverd through Lenovo System Update, 17.13 through MS Windows Update.

Free Windows Admin Tool Kit Click here and download it now
June 20th, 2015 6:12pm

laptop is protected with bitlocker and typing recovery key again and again is really stupid

Supposedly you can have a "USB key" do that for you.  That is something that I have long had buried in my To-do list.

http://windows.microsoft.com/en-us/windows7/learn-more-about-bitlocker-drive-encryption

June 21st, 2015 9:48am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics