Windows 8.1 BSOD: netwlv64.sys

Anonymous
2013-10-23T08:39:56+00:00

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?

Windows for home | Previous Windows versions | Windows update

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.

0 comments No comments

96 answers

Sort by: Most helpful
  1. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  2. Anonymous
    2014-01-26T20:11:58+00:00

    I have an Compaq/HP 8510p AND an nc8430 that both ran just fine on Windows 8 -- but like you after updating to 8.1 now the Wifi doesn't restart after sleeping/hibernating.  The device on each has to be reset to work again (not just turned off and on again). Fortunately I'm not seeing random crashes, but having to manually re-enable the wifi each time is annoying. 

    Where are you disabling 802.11n?  My wifi driver only has options for A, B and G.

    Intel Wireless WiFi Link 4965G

    Driver Version: 13.3.0.137  (c)2009

    netwlv64.sys

    Yes I know these are old computers -- I didn't necessarily expect Windows 8 to work well on them (or Win7). But it did. So a point-level update didn't concern me overly much. Obviously it should have!

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2014-01-19T00:13:10+00:00

    8.1 is GREAT and stable! Very simple, swap out the old card with a new or used Centrino Ultimate 6300 card and call it a day. Get one for Lenovo tho, I bought one by mistake for my Dell...I'll sell it to you for my cost shipped, $23.00. Has bluetooth also! I got the Dell version and VOILA! NO more crash!

    And it is an upgrade to dual band wifi! MUCH faster than the 4965AGN also. Why use OLD drivers on a NEW OS when you can take advantage of the 20 minute upgrade? For me, a no brainer.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2014-01-17T15:22:16+00:00

    I have the same problem, fresh install of 8.1 downloaded from MAP on a Lenovo X61. Gone from perfectly stable Windows 7 to this crash every day - what a pile of cr@p Windows 8 is. Oh and Word 2013 if often reluctant to open docs off a Sharepoint sync'd folder, just hangs opening and you have to kill the process. Never a problem previously with 7 & Office 2010.

    So Microsoft stop telling us "we're going to love" Windows 8 and Office 2013 because we don't, it is sh!t and verging on unusable.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2014-01-14T07:52:22+00:00

    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.


    Thank you, I edited the registry as instructed in this detail, and My 8.1 clean install has NOT rolled-over after many hours of operation.  If it doe I will edit this post, but if your getting this error, this worked on my Sony Viao  -

    Was this answer helpful?

    0 comments No comments