NDIS.sys

[Kal]

Dear Helper

First of all here is my system information:
Laptop, Fujitsu C Series Life Book
Windows XP Pro, CPU 700MHz PentiumIII, RAM 256MB, 20GB HDD
Internet: ADSL ( Provided by TPG, Australia ), Modem D-Link
DSL200, USB Port, Connection is 256Kbps

I'm writing to you to ask what is NDIS.sys, what does this
file do? Has microsoft updated this file?

Well, lately, i've been playing an online game called
"GunBound", which similar to Worm game but people can join
up and play online via the internet.

For the first few weeks, that i played this game, it was
fine, but since this game has updated it file system and
preventing hacking system. My computer cannot play the game
anymore, everytime that I start to play with other people,
my computer freezes and display a blue scrren error message
telling me something like this
"DRIVER_IRQL_NOT_LEST_OR_EQUAL" and techincal information is:
STOP: 0x000000D1 (0x00000008,0x00000002,0x00000000,0xF98C2DC1)
NDIS.sys-Address F98C2DC9 base at F98B0000 date stamp3d6de4c3

I suspected problem might be because of the Modem because
at the first time that i installed the modem, there was an
error message telling me that, the hardware has not passed
Windows Logo or sth like that, but i continued the
installation anyway.

Can you please help me about this?

I'm looking forward for recieving your asnwer in the near
future.

Best regards

Kal

 

[RobD]

The NDIS library (Network Driver Interface Specification) is contained in
ndis.sys. It is a collection of routines that applications can invoke to
perform network-related operations. Ndis.sys is an integral part of the
kernel and it must match other kernel components to work properly. Perhaps
the update you installed requires a particular version of NDIS you do not
have, or the update replaced some of the system components used by ndis.sys.

You didn't say which service pack you have installed (if any). The latest
released service pack is 1a. Service pack 2 should be out soon. You could
look at the version number of your ndis.sys (...\system32\drivers) and make
sure it matches ntoskrnl.exe and hal.dll (both in ...\system32). These two
components are used by ndis.sys. I would also highly recommend you check
with Windows Update for possible missing updates. If everything looks good
but it still crashes, you might try running a repair install. Doing that
should give you a matching set of system components; however, in some
instances it could make things worse. Backup any important data before you
attempt a repair.

The BSOD you had means ndis.sys tried to access memory that was swapped out
to disk. The first parameter is the address it tried to read (0x00000008).
This is not a valid address. I'm speculating that it pulled it out of a
corrupted or misaligned data structure given to it. I would expect a
failure like this if the wrong version of ndis.sys were used.

FYI -- the warning you saw while installing the modem driver simply means
the driver has not passed Logo Certification. It is a certification process
that verifies a driver can handle adverse conditions (low on memory and
other system resources), the driver only uses the resources it acquired, and
the driver releases all resources it acquired, when it is done. Using a
non-certified driver does not mean the system will crash. However, using a
certified driver does mean it is less likely to crash the system.

- Robert -

 

[Angela Lee]

I also have a problem with the ndis.sys driver.
it caused a "invalid_work_queue_item" blue screen error
and stated that it's ndis.sys.
It crashes everythign time I turn on the laptop in normal
mode. I played gunbound too, but i haven't played it for
a few weeks and this error is not only shutting down teh
game, it's my laptop that got shut down.

I am not a computer expert and I have no idea how to fix
it. Please can you help me?
How to do repair install? How to update the driver?
I saw that the ndis.sys has version number 5.1.2600.1106.
the ntoskrnl.exe has version number 5.1.2600.1151 and
hal.dll has version number 5.1.2600.1106.
Please help me...millions of thanks in advance

 

[RobD]

The 5.1.2600.1106 version is from SP1, and 5.1.2600.1151 says it is from SP2
but I believe it really means SP1a. I don't think this combination should
be a problem. The problem may be with another component. Have you tried
uninstalling the game? If yes, you can try an update or repair to see if
that fixes it.

If you're going to try to repair your laptop, the first thing you need to do
is backup any files you do not want to lose. I have seen instances where a
repair operation made the system unbootable. This has happened with SP2 RC1
installed, and trying to repair from the original CD (no service packs). If
the system won't even boot, you can still retrieve the data by booting an OS
like Koppix Linux, which boots enough of a standalone system so you mount
the drive. You can even enable the samba server and access the drive from a
network. If you're not familiar with Linux, you could use a spare drive for
a temporary Windows installation, or possible attach your drive to another
system. The first problem to solve is how to save your data.

The next thing to do is see if updating Windows solves the problem.
1. Go to the Windows Update site (you should have a shortcut for it in
the Start menu, or go to www.windowsupdate.microsoft.com) and let it check
for missing updates. Install all listed "critical" updates (if any).
2. Reboot and see if the problem went away.

If you still have a problem with ndis.sys, try a repair install.
1. Boot from the Windows CD and follow its instructions as if you are doing
a new install.
2. It will eventually tell you that it found a Windows installation already
on the disk, and ask you if you want to repair it. Enter "R" to repair the
OS. Note -- don't confuse a "repair install" with the "recovery console".
They both tell you to enter "R"; skip over the recovery console.
3. If everything works as planned, you should see it complete the repair
and reboot.
4. See if the ndis problem still exists. If not, go to Windows Update and
install missing updates. Otherwise, I would suggest a fresh install. The
recovery console could be used to replace a bad file if you could find it.
It takes too long to do that, that's why I suggest a fresh install.
Besides, everything important is backed-up, right?

I hope uninstalling the game or repairing the OS solves the problem. Let me
know how it went. Good luck.

- Robert -

 

[cvedel]

I'm having a similar problem to the one described already, but there ar
some differences. I'm running Windows XP (SP2) and a D-Link DSL-200 ADS
Modem.

Every once and while my computer crashes to the blue screen an
provides the same kind of message already listed. But, when I run DC+
the system always crashes within 10-15 minutes.

I've done what was suggested and have found that my NDIS file an
hal.dll files are version 5.1.2600.2180. My ntoskkrnl file i
5.1.2600.2622.

I'm not sure what to do know or even if I'm on the right track...

Cheers

 

[MISTER PC]

Hi,

The original post in this thread seems to be caused by a certain type of network card with Service Pack 2 on XP. From what I can tell it is a conflict with Windows Firewall and the network card.

Try removing your network cable, if the problem no longer occurs, then your network card is probably the cause.

I had trouble finding a resolution on the internet so here it is for anyone else having this issue.

Replace the network card with a differnet type and BSOD 0xd1 will be gone.

Regards
Brenden

MISTER PC

 

[Lithargoel]

SOLUTION - here is the FIX

The fix is simple.

Reboot, but disconnect the internet connection from back of PC.

System will reboot no problem.

Then open your network connection properties. (right click Local Area Connection - select Properties)

From the list select Internet Protocol(TCP/IP), and click on Properties button.

Click on Advanced button(lower right)

Click on WINS tab.

In the NetBIOS settings(bottom) select Enable NeBIOS over TCP/IP.

Then plug in your network capable again, and all should be fine!

Your welcome!

NOTE: if you do not disconnect your network capable, the system will shut down within 5 minutes of trying to communicate. It is a Windows problem, not a virus.

 

[Lithargoel]

ok, my first solution above did not work.

But Good news, I found the solution(i think...still waiting test results).

If you are using a static IP address for your connection settings on Local Area Connection, it will fail (as above).

Change your router to use DNS instead, providing IP addresses automatically,
and also change your network card(Local Area Connection) settings to Obtain IP address automatically (check box).

So far I am still connected after one hour!