DRIVER_IRQL_NOT_LESS_OR_EQUAL in tcpip.sys

ElDonAntonio

Senior member
Aug 4, 2001
967
0
0
since a few days I got 3 three times the following blue screen when issuing a new request from my browser (ie clicking a link):

Stop: [some garbage]
DRIVER_IRQL_NOT_LESS_OR_EQUAL

Adress BB97F4F1 base at BB972000 in tcpip.sys


I'm using Win2k, and my computer used to crash *very* rarely, 3 crashes in a few days on the same error is worrying me. I can't recall any new installation I did recently. I've been using my same internet connection with the same hardware, so I doubt it's a bad driver or something like that. I checked in my device manager and there are no conflicts.

Anyone has an idea? Thanks!!
 

bsobel

Moderator Emeritus<br>Elite Member
Dec 9, 2001
13,346
0
0
Definately sounds like a driver issue, are you running any personal firewall software or anything else that might be plugging into your stack?
Bill
 

bsobel

Moderator Emeritus<br>Elite Member
Dec 9, 2001
13,346
0
0
Why are you running both ZA and AtGuard (curious).
Bill
 

ElDonAntonio

Senior member
Aug 4, 2001
967
0
0
I use an old version of Atguard. Atguard's firewall is disabled, but I use its web filters (removes ads and popups) and cookie management system.
 

thornc

Golden Member
Nov 29, 2000
1,011
0
0
Have you installed any new hardware/software recently??

I had the same error the other day, just after installing a new device....
 

ElDonAntonio

Senior member
Aug 4, 2001
967
0
0
No new hardware, it's a laptop...

As for software, I make modifications quite often, but I don't recall anything special in particular. Any way to get any more details on the error?

I found that exact problem on Microsoft's Knowledge Base. Their solution was to download Win2k SP2. Of course I did that a looonnng time ago and have been using windows update since then. I suspect one of the latest updates might be at fault.
 

Miramonti

Lifer
Aug 26, 2000
28,653
100
106
I used to get that constantly, where it started all of a sudden, and checked everything, and it turned out it was caused by the cpu running too hot. I put on a better heatsink and that fixed it.
 

ElDonAntonio

Senior member
Aug 4, 2001
967
0
0
But I notice it's happening immediately when I click on a link in IE (once every few days). Furthermore the error indicates tcpip.sys, so I don't think it's hardware-related, more like a problem with IRQ assignement in Windows.
 

bsobel

Moderator Emeritus<br>Elite Member
Dec 9, 2001
13,346
0
0
> Furthermore the error indicates tcpip.sys, so I don't think it's hardware-related, more like a problem with IRQ assignement in Windows.

What are you basing that on? You get an error in the tcp stack (not the network card drivers), you have a couple programs hooking that stack, and you think this is an IRQ problem?

Bill
 

ElDonAntonio

Senior member
Aug 4, 2001
967
0
0
I may be totally wrong but I thought the DRIVER_IRQL_NOT_LESS_OR_EQUAL part of the error was pretty straightforward...what does that error mean anyway??
 

bsobel

Moderator Emeritus<br>Elite Member
Dec 9, 2001
13,346
0
0
The IRQL_NOT_LESS_OR_EQUAL or Stop 0x0000000A errors are able to be generated by both software and hardware issues. The message indicates that a kernel mode process or driver attempted to access a memory address that it did not have access to.

Did you happen to install any critical updates or anything else lately that wasn't a 'full' install? Maybe something there triggered the new behaviour.

Bill
 

ElDonAntonio

Senior member
Aug 4, 2001
967
0
0
Yep, I regularly update my windows with windows update and install whatever's listed in the "critical updates"...stupid me trusting microsoft.
I'm still surprised no one is experiencing the same problem.
 

Miramonti

Lifer
Aug 26, 2000
28,653
100
106
You're right this may not be hardware/heat related at all but I wouldn't completely discount that idea as well. If your cpu is running to hot or it is overclocked to far, you won't get an overheating message, you will get something like this, which is not the cause, but a symptom of the problem. You're situation may be entirely different than mine, but I struggled with this issue (and this same message) for months before I resolved it by better cooling. Good luck.