And it happened again: BSOD in netwlv64.sys after less than 1 hour of operation on Intel 13.4.0.139 driver.
This really sucks.
Good luck to you Coincoinlapin.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
My Windows 8.1 Pro running on HP 8510w mobile workstation keeps crashing with a Blue Screen of Death STOP error on random accasions.
Bugcheck code 0x000000d1, DRIVER_IRQL_NOT_LESS_OR_EQAL in netwlv64.sys
The driver is related to the built-in Intel WiFi Link 4965AGN WLAN module.
This is a fresh installation of Windows 8.1 Pro. Using default Microsoft driver for the wireless module:
Driver Provider: Microsoft
Driver Date: 15.08.2010
Driver Version: 13.3.0.137
There is no driver for Windows 8.1 provided by Intel for this module. The one from Microsoft obviously does not work properly and crashes Windows 8.1.
There is another issue with this driver not re-connecting after standby but this I was able to resolve by disabling 802.11n Mode in advanced device properties (device manager). But this is another topic.
There seems to be something seriously wrong with the driver Microsoft provides and Internet research provides many results about people having the same issue. Does anybody have an idea how to fix the issues?
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
And it happened again: BSOD in netwlv64.sys after less than 1 hour of operation on Intel 13.4.0.139 driver.
This really sucks.
Good luck to you Coincoinlapin.
I have done a bit of of research on the Intel web page and found that Intel seems to have dropped support for 4965AGN WiFi chipset somewhere between version 15.3.1 and 15.3.50 releases made on the same day. All following driver versions do not support this chipset.
So I have installed version 15.3.1 now and my device manager now shows:
Driver Provider: Intel
Driver Date: 07.10.2010
Driver Version: 13.4.0.139
Interestingly the data matches the one from the "Microsoft" driver quite well. I guess the Microsoft driver is just based on Intel 13.3 edition drivers released a couple of months earlier.
What I could test already is that also with the Intel 13.4.0.139 driver the card won't re-connect to wifi after standby resume. This time I just disabled MSI in the registry for this device rather than disabling 802.11n mode in device properties. It seems to fix the resume issue for me on the Intel 13.3.0.139 driver:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\PCI\VEN_8086&DEV_4229&SUBSYS_11018086&REV_61\4&34ad53c6&0&00E1\Device Parameters\Interrupt Management\MessageSignaledInterruptProperties]
"MSISupported"=dword:00000000
NOTE: You might have to adapt the device identifier (VEN_8086&DEV_4229&SUBSYS...) according to your hardware.
Though I have little hope that the driver will run stable for hours as it seems to behave exactly like the Microsoft driver (which is likely just re-branded Intel driver too).
I still wonder why the WiFi driver which was working fine with Windows Vista, 7 and even 8(.0) can crash the Windows 8.1 kernel so badly.
Update: I still had to disable 802.11n mode as standby resume issue was not fixed by just disabling MSI. I suspect this time it just took longer for Windows to notice that connection is actually lost after wakeup. This time the driver behaves quite randomly. Even with 802.11n mode disabled it sometimes does not return from standby and is unable to connect to any network after resume. The only way to revive it is to reboot or disable/enable the device.
Hi,
I have the exact same problem. No problem in Windows 8 / Random crashes in 8.1
Running an x64 version.
I'm currently trying an old Vista X64 driver from Dell, as some people seem to suggest it might work. If I don't post back...assume it worked.
Just a small update: My Windows 8.1 pro again crashed with BSOD on netwlv64.sys. It was running fine now for about 4 hours at least. Although I am not used any more to such unstable OS I have to say. So unless I find another magic switches or fixes I might sadly have to switch to another OS.
Understandable. I would provide more solutions without second thought if I had them, alas I do not given this is unfortunately as we've discussed related to a driver needing to be very badly published. It's great to hear you've hopefully found out a temporary workaround by disabling the MSI Wifi Interface. Keep me updated on whether or not this ends up solving your issue.
In the meantime, I will attempt to research and possibly find some solutions. No guarantees as again, this is unfortunately all on the fault of a driver and there is only so much to 'work around', if you will.
Regards,
Patrick