Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 879
  • Last Modified:

DRIVER_IRQL_NOT_LESS_OR_EQUAL BSOD

We have two users getting constant BSOD with the error DRIVER_IRQL_NOT_LESS_OR_EQUAL on the netbt.sys driver - how can I resolve this?

Debugging information below:

Loading Dump File [C:\Documents and Settings\pstiff\Desktop\Mini122310-022211\Mini022211-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.101209-1647
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Tue Feb 22 20:43:35.281 2011 (GMT-6)
System Uptime: 0 days 1:35:31.972
Loading Kernel Symbols
...............................................................................................................................................
Loading User Symbols
Loading unloaded module list
................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {a8997101, 2, 8, a8997101}

Unable to load image dne2000.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dne2000.sys
*** ERROR: Module load completed but symbols could not be loaded for dne2000.sys
Probably caused by : netbt.sys ( netbt!TdiBindHandler+ff )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: a8997101, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000008, value 0 = read operation, 1 = write operation
Arg4: a8997101, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS:  a8997101

CURRENT_IRQL:  2

FAULTING_IP:
netbt!TdiBindHandler+ff
a8997101 6a01            push    1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

LAST_CONTROL_TRANSFER:  from ba429d80 to a8997101

FAILED_INSTRUCTION_ADDRESS:
netbt!TdiBindHandler+ff
a8997101 6a01            push    1

STACK_TEXT:  
a72bb608 ba429d80 00000002 8a426550 8a579bd8 netbt!TdiBindHandler+0xff
a72bb634 ba42a2f5 ba42b408 8a579bd8 00000000 TDI!TdiNotifyPnpClientList+0xd0
a72bb658 ba42a70e 00000000 02ae73e8 00000000 TDI!TdiExecuteRequest+0x19b
a72bb694 ba42a7e5 8a426510 0000000e a72bb6ec TDI!TdiHandleSerializedRequest+0x1c4
a72bb6a4 a8a59d8f 8a426510 00000000 8aa05928 TDI!TdiDeregisterDeviceObject+0xf
a72bb6ec a8a549aa 8a0b62f0 00000001 8a8ec770 tcpip!IPDelInterface+0x1b2
a72bb708 b9de7803 a72bb7d4 8aa05928 a72bb728 tcpip!ARPUnbindAdapter+0x72
a72bb7dc b9de8b8b 8a8ec770 a72bb800 8a473ad0 NDIS!ndisUnbindProtocol+0x157
a72bb830 b9de9dc6 8a725ae8 8a473ad0 c0000001 NDIS!ndisCloseMiniportBindings+0x1f7
a72bb95c b9de9f27 b93bcc68 89d9d7c0 806e7830 NDIS!ndisPnPRemoveDevice+0x142
a72bb970 b93b0167 8a473ad0 89d42008 8a78cd40 NDIS!NdisIMDeInitializeDeviceInstance+0x44
a72bb988 b9de7803 a72bba54 01d9d7c0 a72bb9a8 psched!ClUnbindFromLowerMp+0xc9
a72bba5c b9de8b8b 89d42008 a72bba80 8a808ad0 NDIS!ndisUnbindProtocol+0x157
a72bbab0 b9de9dc6 8aa82bc8 8a808ad0 c0000001 NDIS!ndisCloseMiniportBindings+0x1f7
a72bbbdc b9de9f27 a72bbccc 89dab020 89dabad4 NDIS!ndisPnPRemoveDevice+0x142
a72bbbf0 b93e15da 8a808ad0 00000000 8aa6ae18 NDIS!NdisIMDeInitializeDeviceInstance+0x44
WARNING: Stack unwind information not available. Following frames may be wrong.
a72bbc34 b9ddefe6 a72bbccc a72bbc5c 89aa556c dne2000+0xa5da
a72bbcd0 b9de163d 806e7830 8a052130 8052b326 NDIS!ndisInitializeBinding+0x189
a72bbd58 b9de16d6 8a8b9fe0 80564820 89bbbba8 NDIS!ndisCheckAdapterBindings+0x13a
a72bbd6c b9dddbfe 8a8b9fd8 00052130 a72bbdac NDIS!ndisQueuedCheckAdapterBindings+0x83
a72bbd7c 805387cb 8a8b9fd8 00000000 89bbbba8 NDIS!ndisWorkItemHandler+0xe
a72bbdac 805cffa8 8a8b9fd8 00000000 00000000 nt!ExpWorkerThread+0xef
a72bbddc 8054615e 805386dc 80000000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP:
netbt!TdiBindHandler+ff
a8997101 6a01            push    1

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  netbt!TdiBindHandler+ff

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: netbt

IMAGE_NAME:  netbt.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  48025d1b

FAILURE_BUCKET_ID:  0xD1_CODE_AV_BAD_IP_netbt!TdiBindHandler+ff

BUCKET_ID:  0xD1_CODE_AV_BAD_IP_netbt!TdiBindHandler+ff

Followup: MachineOwner
---------

0
pstiffsae
Asked:
pstiffsae
1 Solution
 
Neil RussellTechnical Development LeadCommented:
First of all, have you applied ALL latest windows updates? Have you installed any new hardware lately? Have you updated any drivers lately?

I would start by making sure ALL windows updates are aplied and then checking you have the latest drivers installed for your network cards.
0
 
ccnsCommented:
According to Microsoft Support Online article Q243478, Microsoft released a bug fix for netbt.sys on October 11. You can obtain the updated version only from Microsoft Support
you may want to go down that road, unless you feel easier reinstalling the systems.
0
 
pstiffsaeAuthor Commented:
Care to link the article? All I'm getting is http://support.microsoft.com/kb/243478 
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
nobusCommented:
it can be malware, in which case i suggest to run these  :
      Spybot :        http://www.download.com/3000-8022-10122137.html
http://www.malwarebytes.org/mbam.php                         MBAM

info on netbt.sys :  http://www.file.net/process/netbt.sys.html
0
 
pstiffsaeAuthor Commented:
When updating his NetXtreme 57XX Gigabit Ethernet adapter, it immediately gives the BSOD. Is the NIC card bad?
0
 
nobusCommented:
that is possible - you can test with another card, or test this one on another pc (if separate)
0
 
nobusCommented:
or - if you want to know it's ok or not, run from the knoppix live cd, and check your internet connection - it should work : ftp://ftp.kernel.org/pub/dist/knoppix/KNOPPIX_V6.4.4CD-2011-01-30-EN.iso 
0
 
pstiffsaeAuthor Commented:
Since updating his BIOS and Network card drivers, I've not heard of anymore errors, however that was only as of yesturday
0
 
nobusCommented:
ok - keep us posted..
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now