Persistent BSOD DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1 NETwsw00.sys

[qpop]

Hi all,

The computer in question is an HP Folio 13-2000 (UK Edition)

I have had this computer for over a year now, and in the last month it has BSODed with the above error in the title every day or two, usually whilst idle (although qbittorrent is often running in the background).

I have searched for answers and it looks as though it is a WiFi driver crash. The original .sys file that was failing was not this one, but (something)nt64.sys - it was the Windows Update driver for the same (Intel Centrino 1030 Wifi).

Steps taken to resolve:

1) a clean install of Windows 7 Service Pack 1 x64(media provided by Digital River) and update to the newest essential Windows updates.
2) Uninstallation of the Windows Update driver for the wireless card, and installation of the newest Intel Wifi drivers.

Following these two actions the crash keeps happening.

I wonder if it's related to the latest version of qbittorrent?

I find it unusual that a BSOD relating to driver issues could happen, out of the blue, on a new installation of Windows.

These are the two latest BSOD dumps (one at 4.30am and one at 7.30am - 4.30am the PC had been idling all night, 7.30am I was using the PC whilst it BSODed).

Any help appreciated

System dump attached - here is the most recent minidump:

==================================================
Dump File         : 121813-7004-01.dmp
Crash Time        : 18/12/2013 04:32:36
Bug Check String  : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code    : 0x000000d1
Parameter 1       : fffff880`04b92000
Parameter 2       : 00000000`00000002
Parameter 3       : 00000000`00000000
Parameter 4       : fffff880`04c6c440
Caused By Driver  : NETwsw00.sys
Caused By Address : NETwsw00.sys+8440
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Crash Address     : ntoskrnl.exe+75bc0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\121813-7004-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 284,672
Dump File Time    : 18/12/2013 04:33:24
==================================================

 

[Capt.Jack Sparrow]

Hello there!

Seems like the crashes are caused by http://www.carrona.org/drivers/driver.php?id=NETwsw00.sys I would recommend to go the the manufature's website and download a clean version and update it. Make sure you remove the old drivers first before you install a new one.

How To: http://captaindbg.com/how-to-update-drivers-on-windows-7/

Capt.Jack Sparrow - BSOD Output

Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Wed Dec 18 12:53:02.117 2013 (UTC + 5:30)
System Uptime: 0 days 2:49:44.553
BugCheck D1, {fffff88005872000, 2, 0, fffff88005a33440}
*** WARNING: Unable to verify timestamp for NETwsw00.sys
*** ERROR: Module load completed but symbols could not be loaded for NETwsw00.sys
Probably caused by : NETwsw00.sys ( NETwsw00+8440 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  qbittorrent.ex
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Wed Dec 18 10:02:36.081 2013 (UTC + 5:30)
System Uptime: 0 days 11:05:55.517
BugCheck D1, {fffff88004b92000, 2, 0, fffff88004c6c440}
*** WARNING: Unable to verify timestamp for NETwsw00.sys
*** ERROR: Module load completed but symbols could not be loaded for NETwsw00.sys
Probably caused by : NETwsw00.sys ( NETwsw00+8440 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  qbittorrent.ex
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

 

[qpop]

I'm not sure I understand you - I have re-installed the driver (by opening Device Manager, uninstalling old drivers, rebooting, installing the newest version from Intel's website).

The BSOD still continues.

EDIT: Having re-read your post, it seems to suggest that qbittorrent is indeed part of the problem - perhaps it's the interaction between it and the wifi drivers?

EDIT 2: Having read up here others have complained of the same BSOD errors with the drivers and with qbittorrent, although the thread is quite old. One of the proposed solutions is to use the latest drivers, which I am doing. Could this really be caused by the software?

Hello there!

Seems like the crashes are caused by http://www.carrona.org/drivers/driver.php?id=NETwsw00.sys I would recommend to go the the manufature's website and download a clean version and update it. Make sure you remove the old drivers first before you install a new one.

How To: How to Update Drivers on Windows 7 | Captain Debugger

Capt.Jack Sparrow - BSOD Output

Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Wed Dec 18 12:53:02.117 2013 (UTC + 5:30)
System Uptime: 0 days 2:49:44.553
BugCheck D1, {fffff88005872000, 2, 0, fffff88005a33440}
*** WARNING: Unable to verify timestamp for NETwsw00.sys
*** ERROR: Module load completed but symbols could not be loaded for NETwsw00.sys
Probably caused by : NETwsw00.sys ( NETwsw00+8440 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  qbittorrent.ex
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Wed Dec 18 10:02:36.081 2013 (UTC + 5:30)
System Uptime: 0 days 11:05:55.517
BugCheck D1, {fffff88004b92000, 2, 0, fffff88004c6c440}
*** WARNING: Unable to verify timestamp for NETwsw00.sys
*** ERROR: Module load completed but symbols could not be loaded for NETwsw00.sys
Probably caused by : NETwsw00.sys ( NETwsw00+8440 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  qbittorrent.ex
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

 

[qpop]

I have published a speccy snapshot too: LINK

 

[Capt.Jack Sparrow]

Hello there!

It can very well be the software but we can't be sure of it. Sometime just uninstall the driver won't work since it will automatically reinstall it. You need to disable Automatic driver updating then reinstall the new version. We can enable the verifer to see if indeed it's the network related drivers. http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

 

[qpop]

Hello there!

It can very well be the software but we can't be sure of it. Sometime just uninstall the driver won't work since it will automatically reinstall it. You need to disable Automatic driver updating then reinstall the new version. We can enable the verifer to see if indeed it's the network related drivers. http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

Hi,

Thanks for your help so far.

I uninstalled the driver, ensuring that Windows didn't automatically re-install it, and then re-installed the latest driver from the Intel site.

Having just booted the PC and started qbittorrent, the PC blue-screened again, with the following dump:

==================================================
Dump File         : 121813-12480-01.dmp
Crash Time        : 18/12/2013 19:41:44
Bug Check String  : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code    : 0x000000d1
Parameter 1       : fffff880`00b8b000
Parameter 2       : 00000000`00000002
Parameter 3       : 00000000`00000000
Parameter 4       : fffff880`05aa2440
Caused By Driver  : NETwsw00.sys
Caused By Address : NETwsw00.sys+8440
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Crash Address     : ntoskrnl.exe+75bc0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\121813-12480-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 284,680
Dump File Time    : 18/12/2013 19:42:13
==================================================

Any more thoughts?

 

[qpop]

I'm so far trying a fix/workaround from the Intel website.

It involves enabling FIPS on the wireless connection.

I will report back if this resolves the issue (which will potentially help others.)

 

[Capt.Jack Sparrow]

I'm so far trying a fix/workaround from the Intel website.

It involves enabling FIPS on the wireless connection.

I will report back if this resolves the issue (which will potentially help others.)

That's great new