Page 1 of 1

Blue screen lock up referencing "NDIS.sys"

Posted: Wed Aug 02, 2006 12:28 pm
by jamies
After using my Thinkpad T60 for a few weeks I went ahead and reinstalled Windows XP fresh and installed the appropriate Lenovo drivers. I did this to have a cleaner and faster OS running. I keep up to date with System Update, System Installer and Windows Update.

Since reinstalling my computer has been locking up with the blue screen. The message always references NDIS.sys. I believe that's network related. It happens in Windows, usually while switching or loading applications; it's pretty intermittent.

Has anyone else seen this? Windows says it's a device driver causing this problem.

Any help is appreciated.

Regards,
js

Posted: Wed Aug 02, 2006 4:17 pm
by Badger
Do you know what device it is that Windows is reporting is the problem? I'll offer this -- try uninstalling your NIC drivers from the device manager and reinstalling them from the manufacturer's website.

Posted: Wed Aug 02, 2006 4:51 pm
by jamies
Badger wrote:Do you know what device it is that Windows is reporting is the problem? I'll offer this -- try uninstalling your NIC drivers from the device manager and reinstalling them from the manufacturer's website.
So far I don't know what device. I assumed other the NIC or the Wireless card. The problem is does anyone know what NIC and Wireless card the T60 has? The intel site has drivers for almost a thousand different NICs.

Thanks for your help.

Posted: Wed Aug 02, 2006 5:29 pm
by Kyocera
Network Driver Interface Specification, like badger said uninstall the network drivers and reinstall, try the the system updater or software installer.

Posted: Wed Aug 02, 2006 5:41 pm
by Liam_
I thought Intel used the "one-driver-fits-all" concept?
At least I used the same driver here for desktops with different Intel NIC's and it works fine.

I thought the T60 uses intel NIC's so you could try and just go with one. If it doesn't work, it will report it. Or maybe you already have the wrong drivers and is it because of the wrong drivers you are getting those errors.

It definitly is a NIC driver, so take a look at that....