Win2k BSOD in NDIS.SYS - (Win2k sucks)

[Dubious]

First off, I'd like to say that Win2k Pro is a complete POS operating system. With that said, here is my problem.

I get 20+ BSOD's in Win2k Pro daily. My data is massively corrupted because of it, and I cant perform basic computing functions anymore.

Problem:
STOP: 0x000000D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL ..... ..... Addresss BFF0Bc70 base at BFF02000, Date Stamp 39196393- NDIS.SYS Beggining Dump of Physical Memory

I get this frickin ALL THE DAMN TIME. Times when I can reproduce it:
- sending mail in Eudora 5.0+
- exiting out of Incredimail by right-clicking the icon in the system tray
- Selecting a server in Napigator
- and other completely random times when my PC has to access some network resource (hence, the error in NDIS.SYS).

Attempted solutions:
- formatted/reinstalled at LEAST 6 times in 2 months
- updated all drivers
- reinstalled NIC more times than I care to recall
- got real drunk
- punched monitor
- yelled at a cat

Solve my problem and you get a cookie.

System Specs:
Win2k sp2
Athlon 800
Asus K7V mobo
512m PC-133
Guillemot GF2 GTS 32m
Linksys LNE100TX v4
SB Live! Value
DVD-ROM
CD-R
ZIP
1.44

 

[Dually]

ndis is a novell deal, any novell software installed?

also eudora is bad.

 

[GrumpyMan]

Getting rid of ACPI might help. An IRQ conflict of somekind? Are they all on the same IRQ like Win 2000 likes to do?

 

[Dually]

<< Getting rid of ACPI might help. An IRQ conflict of somekind? Are they all on the same IRQ like Win 2000 likes to do? >>



its not acpi, its network software related.

 

[miltimj]

It's not a Novell issue.. this has happened to me before also.. only in Eudora 5.0 (sending mail, also). I don't use any of the other apps, so I don't know about them. I'm thinking it may also be a resource conflict - the error even says so (and I do get the exact same message that you do).

I probably should have tried switching PCI slots and disabling one of the IDE controllers that I don't use to free up an IRQ, but I'm not sure. I think it's simply that it needs it's own IRQ. Try reserving it in the BIOS, if possible.

As for me, I tried a fresh install, but it didn't work well (dual booting). It was freezing on the main Win2K splash screen, and wouldn't get past that (just after installing).

I ended up formatting the C: drive (win2k partition), but that was a bad idea because now my Win98 partition (D: drive) doesn't work.. I'm trying to rebuild that, but it says there's no valid OS..

I'll probably wipe that out and reinstall again, since that's easy enough. I do have a SCSI drive I'm doing all of this on though, so that may add to the mess. I heard you can't really install Win2K on a SCSI drive unless it's from Win9x?? (though I did that and it freezed, as I said) Anyone know why this is?

Good luck with the problem.. my recommendation is freeing up an IRQ and moving cards around until the NIC gets an exclusive IRQ assigned to it.

 

[DevGrp]

I had the same problems that you had, but not as often. To fix the problem I uninstalled Live Wire and the drivers for my SBLive and now its fine. Just reinstall the sound card with the drivers from the W2K cd, and see if that works.

Hope that helps

 

[murdock2525]

zzzzzzzzzzzzzzzzzzzzzzz

 

[Zoltarc]

I think its ACPI too. Disable it in the BIOS.

Remove all hardware apart from your video card and then format and reinstall WIn2k. Try and crash it. If you can't add one piece of hardware at a time and then try to crash it. Its a very long and boring proccess but it could help.


BTW: Eudora Good....Outlook bad...

 

[Zoltarc]

POSSIBLE FIX! CLICK ME!!

Click the link! Possible fix!

 

[AngelOfDeath]

I might have a solution. Try switching the nic-card to another pci-port. Make sure that it has it's own pci-slot without sharing any IRQ with another slot.

I seem to recall that exact problem with my own system a long time ago. A found out that makeing sure that the nic had it's own slot without IRQ-sharing solved the problem.

AoD

 

[Davegod75]

First of all, any one with 20+ BSOD's in w2k has serisouly screwed up something. Try reading a book on w2k.

 

[MulLa]

I also get the same BSOD constantly when I use netmeeting with my webcam. I believe it's also due to ACPI and w2k's habit of sharing IRQs. Definately reinstall the OS with ACPI disabled. My IRQL blah blah blah BSOD certainly did go away after I have done that. Although, I simply changed the drivers didn't reinstall as I was lazy ^^

 

[Dubious]

<< Getting rid of ACPI might help. An IRQ conflict of somekind? Are they all on the same IRQ like Win 2000 likes to do? >>


Yeah - I read up on that. First I thought it weird that Win2k had a ton of my IRQs set to 9. Then, after reading, I realized that this is the new-fangled way of handling IRQ steering. I definitely dont like it.

So, I'm thinking of turning off ACPI, manually setting the IRQs in the BIOS and reinstalling. That, and getting rid of this Linksys NIC and getting a 3com.



<< First of all, any one with 20+ BSOD's in w2k has serisouly screwed up something. Try reading a book on w2k. >>


Thanks there, Skippy. Its easy to get 20+ BSODs - just reproduce the problem. See, that's the beauty of a reproducable problem - you can reproduce it. Try looking up &quot;reproducable&quot; in a book.

I'm convinced that it is either an IRQ conflict or a network driver/resource problem. First, I'm gonna replace NIC. If that fails, I'm going to reinstall without ACPI.

Thanks to everyone for their help, minus that &quot;book&quot; guy.

-Dubious

 

[GrumpyMan]

I could be wrong but I will stand with my original answer and say ACPI is the most likely suspect, I have seen it a thousand times.

 

[Rellik]

First of all, Eudora is not bad(all you MS Outlook guys make me sick with your security issues...). but now for something more constructive:

First: You can certainly install W2K on a SCSI drive. My system is pure SCSI(although I will det ide for sheer storage) and it installed fine. Maybe a problem with the controller?

To the guy who started the thread: What kind of RAM do you have? the VIA Chipsets of the K7M and K7V are pretty picky about RAM. Also,
I have found that installing the standard pc version(without ACPI) and referring to APM is way better then ACPI. It still shares IRQ´s and shuts down, but it doesn´t have the trouble ACPI can cause. Also recommend trying different slots and exchanging the Live card. I have
a live card myself and it works great but I have an BX chipset. And the patches. Do not use Liveware. It is really bloated. You can access all really important fetures from the creative launcher and Audio
HQ which get installed with the standard driver.

I hope you get it running again because w2k really is way better then w98 and ME in my experience...