Win2k Pro Crash

I'm having a trouble with this. It never happens until near March (according to my sister) even though she had the computer since last year and even longer than that.

Bascially, it started when she locks the C (C= computer, my term), it BSOD.

Lately, since she came home, it happens to BSOD often, at least once every 24 hours.

It also ends with this error:

0x000000D1 (the 3 codes is always random here, must be memory) DRIVER_IRQL_NOT_LESS_OR_EQUAL

Address BFEF76B5 (random too) base at BFEED000 (random too), Datastamp 3 CDAEE06 (random too) - NDIS.SYS

The only consistant error is the 0x000000D1 and NDIS.SYS.

Basically I only have the v-card, s-card, Service Pack 3 (for Win2kPro) installed.

Does anyone have a clue on what's happening? Or suggestions on what I should do?

I tried checking the Microsoft Database on this and I can't find any "sure" answer for this (aside from saying to "debug" the NDIS.SYS which I have no idea what to do or anything).

For right now, I just did another reformat and leaving it alone (fresh install with nothing) and see if it'll BSOD, then I'll add SP3 and see for another day or 2, then keep adding to see what is the problem.

Specs:
{Hope}
PIII 800mhz
ABIT BE6 (latest bios)
Creative Labs Live5.1! MP3+
Creative Labs Geforece 2
Linksys NIC

and of course: Windows 2000 Pro (no SP.. fresh install.. right now).

 

irq errors in nt based systems are usually driver or hardware related. NDIS is a file used by network cards and the like. Remove any programs that may be tampering with this file. Zonealarm changes the file, norton replaces it with it's own. Basically you want to get it to nothing but the driver. Check for an updated driver. If the problem persists then it's probably a hardware failure.
here is a link to a post that directly matches your error and the culprit was zonealarm
http://forums.zonelabs.com/zonelabs/board/message?board.id=win_za_msgs&message.id=210

a full inventory of the programs running at startup and more specific hardware specs would be helpful if these suggestions don't fix the issue.

 

That's the extremely strange part... I have "Hope" for over 2 years with ZA and NAV and I never have this problem until after this Winter of 2k2 (flawless).... which then I installed the Linksys TX100 version 4.1.

I believe that NIC is the curplit to this problem because ever since then... my sis told me it crashses every week or so.

Of course, to be on the safe side, I'm planning to install the other NIC I have Linksys TX100 version 5.1 and see how it fares for the day (with no other software other than: SP3, Scard drivers, Vcard drivers).

As startup, there is nothing since it's clean format + reinstall. And more specific hardware specs... there's really not much I can give you... but:

Abit BE6 (bios latest)
Win2k Pro (will install SP3 when I wake up)
Creative Labs Live! 5.1 MP3+ (latest drivers)
Creative Labs GeForce 2 GTS (latest drivers)
HP' CD-RW (no drivers needed)

will also install when I wake up:
Linksys 100TX version 5.1


Weird that they make different NIC versions, maybe the 5.1 version will fare better than the 4.1 (if that's teh curlpit).