Windows 8.1 BSOD: netwlv64.sys

the problem is with the in box 13.3 drivers packaged with 8.1 and 10 

those drivers labelled 13.3  has the same symptoms with win 7 as well . avoid using the 13.3 versions

i have retried the win 7 inbox driver (12.xx.xx)  by Microsoft should resolved the issue 

download here and install the INF 

http://www.mediafire.com/download/lxvks6f4j3b4qh6/Intel%28R%29+Wireless+WiFi+Link+4965AGN.rar

Thank you.

Additional problem is that these Windows 7 drivers are treated as unsigned by Windows 10 (no *.cat file from them - they are trusted as long as they are not "exported" out of Windows 10). That means you have to disable digital driver enforcement. And there is currently no parament way of doing so in Windows 10 (the usual "bcedit" and gpedit.msc methods no longer seem to work).

Thank you.

Additional problem is that these Windows 7 drivers are treated as unsigned by Windows 10 (no *.cat file from them - they are trusted as long as they are not "exported" out of Windows 10). That means you have to disable digital driver enforcement. And there is currently no parament way of doing so in Windows 10 (the usual "bcedit" and gpedit.msc methods no longer seem to work).

so did u try the drivers i provided? does it help? please report thank u 

are u sure the BCDedit dont seems to work?  did u input the commands correctly ? open a CMD  ( right click , runs as administrative and type 

Bcdedit.exe -set TESTSIGNING ONafter this step reboot and u will be able to install unsigned drivers

so did u try the drivers i provided? does it help? please report thank u 

are u sure the BCDedit dont seems to work?  did u input the commands correctly ? open a CMD  ( right click , runs as administrative and type 

Bcdedit.exe -set TESTSIGNING ONafter this step reboot and u will be able to install unsigned drivers 

I did not try the drivers for too long as I would have to keep disabling digital driver signature enforcement on every boot. Even if I install the driver with the signature enforcement set to disabled Windows will not allow the driver to be loaded after reboot.

bcdedit.exe -set TESTSIGNING ON does not help

bcdedit /set loadoptions DISABLE_INTEGRITY_CHECKS does not help

bcdedit /set loadoptions DDISABLE_INTEGRITY_CHECKS does not help

Bcdedit.exe /set nointegritychecks ON does not help

Those bcdedit commands might have worked in the past but they don't seem to work now (at least for me).

I'm currently using the 11.5.0.32 driver version. It seems to have some quirks for me (for example sometimes there is no reconnection to wireless network after resuming from sleep) but no BSODs.

U can try another way to disable Intergrity checks through gpedit.msc . I know the commands still works in Windows 10 latest build , so it must have been some settings which are messed up in yr comp. 

so did u try the drivers i provided? does it help? please report thank u 

are u sure the BCDedit dont seems to work?  did u input the commands correctly ? open a CMD  ( right click , runs as administrative and type 

Bcdedit.exe -set TESTSIGNING ONafter this step reboot and u will be able to install unsigned drivers 

I did not try the drivers for too long as I would have to keep disabling digital driver signature enforcement on every boot. Even if I install the driver with the signature enforcement set to disabled Windows will not allow the driver to be loaded after reboot.

bcdedit.exe -set TESTSIGNING ON does not help

bcdedit /set loadoptions DISABLE_INTEGRITY_CHECKS does not help

bcdedit /set loadoptions DDISABLE_INTEGRITY_CHECKS does not help

Bcdedit.exe /set nointegritychecks ON does not help

Those bcdedit commands might have worked in the past but they don't seem to work now (at least for me).

I'm currently using the 11.5.0.32 driver version. It seems to have some quirks for me (for example sometimes there is no reconnection to wireless network after resuming from sleep) but no BSODs.

U can try another way to disable Intergrity checks through gpedit.msc . I know the commands still works in Windows 10 latest build , so it must have been some settings which are messed up in yr comp. 

The Group Policy Object that you refer to only disables the Program Application Compatibility prompt while installing the driver. It does not prevent the drivers from being loaded once they are installed.

It is possible that the Insider builds allow for driver signature enforcement to be permanently disabled while the regular builds don't (or stopped allowing after some updated). I use Windows 10 version 1511 build 10586.