BSOD STOP in tcpip.sys 0x000000D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL with Intel Proset/Wireless drivers

I have a Dell Inspiron 1520

I upgraded from Vista Home to Windows 7 Ultimate.  Since that I had already 3 or 4 BSOD on tcpip.sys.

Before the upgrade Win7 detected 3 incompatibilities:

Skype 3.8
Intel ProSet/Wireless
Network Monitor 3

I would have solved the problems but when I click OK the installation continued.

After 7 hours to finish the upgrade (including downloading 1GB+), I was done :-/
IE8 wasl sometimes crashing randomly. I partially solved the problem moving to Firefox but when I forget I still have the problem now and then.

Anyway, I need to fix the Blue Screen of Death problems.

After the Win7 upgrade, I upgrade the Video Drivers NVidea 8400GS, Skype, Network Monitor 3 and the Intel PROSet/Wireless drivers.

I think the problem is in the Intel drivers becasue the BSOD is on tcpip.sys.

I downloaded the drivers here: http://www.intel.com/support/wireless/wlan/sb/CS-010623.htm throught the automatic detection.
It now find:
Product Detected  Intel® Wireless WiFi Link 4965AGN 
Current Intel® PROSet/Wireless WiFi Connection Utility Installed  13.1.1.0 

These are two logs that Win7 showed me after reboot after 2 different BSOD incidents:

Problem signature:
  Problem Event Name: BlueScreen
  OS Version: 6.1.7600.2.0.0.256.1
  Locale ID: 1033

Additional information about the problem:
  BCCode: d1
  BCP1: 00000006
  BCP2: 00000002
  BCP3: 00000000
  BCP4: 8D6938CB
  OS Version: 6_1_7600
  Service Pack: 0_0
  Product: 256_1

Files that help describe the problem:
  C:\Windows\Minidump\032110-35973-01.dmp
  C:\Users\Cris\AppData\Local\Temp\WER-78827-0.sysdata.xml

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

----------------------------------------------------------------------------------------------------

Problem signature:
  Problem Event Name: BlueScreen
  OS Version: 6.1.7600.2.0.0.256.1
  Locale ID: 1033

Additional information about the problem:
  BCCode: d1
  BCP1: 00000010
  BCP2: 00000002
  BCP3: 00000001
  BCP4: 8D68023A
  OS Version: 6_1_7600
  Service Pack: 0_0
  Product: 256_1

Files that help describe the problem:
  C:\Windows\Minidump\032310-21356-01.dmp
  C:\Users\Cris\AppData\Local\Temp\WER-45037-0.sysdata.xml

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

----------------------

I have already checked the RAM integrity and my computer passed the test.

What can I do to fix this problem?

Best,

     Chris

Product Detected Intel® Wireless WiFi Link 4965AGN
Current Intel® PROSet/Wireless WiFi Connection Utility Installed 13.1.1.0

 

Question Info


Last updated March 13, 2018 Views 11,330 Applies to:
Answer
Answer

I had a look at the minidump from your Windows 7 Forums thread and the driver that may be actually causing the crash is the nm3.sys. The nm3.sys appears to be accessing memory after the netw5v32.sys and ahead of the tcpip.sys. See this driver bolded in the Stack_Text field:

STACK_TEXT: 
WARNING: Stack unwind information not available. Following frames may be wrong.
82f2df80 8d68023a badb0d00 00000001 00000000 nt+0x4685b
82f2e11c 8d67f2bf 871f88a0 00000000 00000001 tcpip!TcpBeginTcbSend+0x9f6
82f2e280 8d6a90eb 871f88a0 00000002 00000000 tcpip!TcpTcbSend+0x426
82f2e2d0 8d68963f 00000000 00000000 8826307e tcpip!TcpFlushDelay+0x1f1
82f2e2e4 8d677ab8 00000000 00000001 00000000 tcpip!TcpExitReceiveDpc+0x61
82f2e31c 8d677812 871a8630 871ac000 00005000 tcpip!TcpPreValidatedReceive+0x29b
82f2e338 8d67d1d3 871a8630 871ac000 82f2e374 tcpip!TcpReceive+0x2d
82f2e348 8d6af48e 82f2e35c c000023e 00000000 tcpip!TcpNlClientReceiveDatagrams+0x12
82f2e374 8d6af251 8d70ef88 82f2e3c8 c000023e tcpip!IppDeliverListToProtocol+0x49
82f2e394 8d6aef26 8d70ed98 00000006 82f2e3c8 tcpip!IppProcessDeliverList+0x2a
82f2e3ec 8d6acb64 8d70ed98 00000006 00000000 tcpip!IppReceiveHeaderBatch+0x1f2
82f2e480 8d6abaf5 8af1de20 00000000 00000001 tcpip!IpFlcReceivePackets+0xbe5
82f2e4fc 8d6abc66 8ad08a38 8b6049d0 00000000 tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x746
82f2e530 82e9808a 8b6049d0 a85530bf 871a7520 tcpip!FlReceiveNetBufferListChainCalloutRoutine+0x11e
82f2e598 8d6abcee 8d6abb48 82f2e5c0 00000000 nt+0x9008a
82f2e5d4 8d49818d 8ad08a02 8b604900 00000000 tcpip!FlReceiveNetBufferListChain+0x7c
82f2e60c 8d486670 8af30008 8b6049d0 00000000 ndis!ndisMIndicateNetBufferListsToOpen+0x188
82f2e634 8d4865e7 00000000 8b6049d0 8ad0d878 ndis!ndisIndicateSortedNetBufferLists+0x4a
82f2e7b0 8d431ca5 8760b0e0 00000000 00000000 ndis!ndisMDispatchReceiveNetBufferLists+0x129
82f2e7cc 8d461a87 8760b0e0 8b6049d0 00000000 ndis!ndisMTopReceiveNetBufferLists+0x2d
82f2e7e8 8d461a21 8af1ce00 8b6049d0 00000000 ndis!ndisFilterIndicateReceiveNetBufferLists+0x46
82f2e804 8fd67837 8af1ce00 8b6049d0 00000000 ndis!NdisFIndicateReceiveNetBufferLists+0x2f
82f2e82c 8fd6b497 8af1ce00 86184018 85af4780 nwifi!Dot11IndicateRecvPackets+0x51
82f2e84c 8d461a87 8af1f720 8b6049d0 00000000 nwifi!Pt6Receive+0x1d3
82f2e868 8d461a21 87890288 86184018 00000000 ndis!ndisFilterIndicateReceiveNetBufferLists+0x46
82f2e884 91ce25a1 87890288 86184018 00000000 ndis!NdisFIndicateReceiveNetBufferLists+0x2f
82f2e8f4 8d486a2e 85af4780 86184018 00000000 nm3+0x45a1
82f2e91c 8d431c1e 8760b0e0 86184018 00000000 ndis!ndisMIndicateReceiveNetBufferListsInternal+0x62
82f2e944 9363a472 8760b0e0 86184018 00000000 ndis!NdisMIndicateReceiveNetBufferLists+0x52
82f2e974 937bf7ec 00000001 86184018 85c4e278 netw5v32+0xb472
82f2e9b4 937cae56 878cb710 86184018 8d43e5c0 netw5v32+0x1907ec
82f2e9d8 9363f1e0 00000001 8adab9d0 8bd09f00 netw5v32+0x19be56
82f2ea08 93640075 8adab9d0 8bd09ff8 8adab9d0 netw5v32+0x101e0
82f2ea20 9363cec9 8adab9d0 8bd09fd8 00000000 netw5v32+0x11075
82f2ea3c 937bed14 878cb750 000000e8 00000000 netw5v32+0xdec9
82f2ea60 9366a38f 878cb710 8bd45e98 82f2ea94 netw5v32+0x18fd14
82f2ea70 9369a8e0 878cd058 8bd45e98 8d43e5c0 netw5v32+0x3b38f
82f2ea94 9363f1e0 889d7000 860fa468 8bd45e98 netw5v32+0x6b8e0
82f2eac4 93640075 860fa468 8bd45ff8 860fa468 netw5v32+0x101e0
82f2eadc 9363cec9 860fa468 8bd45fd8 82f2eb38 netw5v32+0x11075
82f2eaf8 9366ab39 878cd098 00000076 00000000 netw5v32+0xdec9
82f2eb1c 93661240 878cd058 82f2eb38 87e84950 netw5v32+0x3bb39
82f2eb54 9366151e 87e84950 878de448 882630c0 netw5v32+0x32240
82f2ebb8 9365b91f 00000080 878de448 000000ff netw5v32+0x3251e
82f2ebf4 936591dc 878dc001 878de448 82f2ec10 netw5v32+0x2c91f
82f2ec04 938b9785 878de448 82f2ec50 8d486301 netw5v32+0x2a1dc
82f2ec10 8d486301 87890490 00000000 00000000 netw5v32+0x28a785
82f2ec50 8d4319f4 878e017c 008e0068 00000000 ndis!ndisMiniportDpc+0xda
82f2ec78 82e704b5 878e017c 878e0068 00000000 ndis!ndisInterruptDpc+0xaf
82f2ecd4 82e70318 82f31d20 82f3b280 00000000 nt+0x684b5
82f2ed20 82e70138 00000000 0000000e 00000000 nt+0x68318
82f2ed24 00000000 0000000e 00000000 00000000 nt+0x68138


STACK_COMMAND:  kb

FOLLOWUP_IP:
tcpip!TcpBeginTcbSend+9f6
8d68023a f00fc111        lock xadd dword ptr [ecx],edx

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  tcpip!TcpBeginTcbSend+9f6

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  tcpip.sys

 

 

The nm3.sys is a driver for Microsoft Network Monitor. I would suggest, if problems persist, to uninstall Microsoft Network Monitor and see if the BSODs resolve. 

 

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.