Bienvenido! - Willkommen! - Welcome!

Bitácora Técnica de Tux&Cía., Santa Cruz de la Sierra, BO
Bitácora Central: Tux&Cía.
Bitácora de Información Avanzada: Tux&Cía.-Información
May the source be with you!

Tuesday, September 15, 2009


ndis.sys related
There are a variety of possible causes for the DRIVER IRQL NOT LESS OR EQUAL problem. This is in no way an exhaustive list. However it does cover the most common problems. And ways to try to diagnose exactly what the problem could be.
Outdated Drivers
First, If you have a Broadband modem, especially an Alcatel, you should upgrade your drivers.(For other drivers go here)
Linksys network card Drivers If you have a Linksys NC100, LNE100TX model 5, Skymaster SK1207E, Planex FNW-9803-T, or any network card based on the AN983B chipset by ADMtek, also sold under Asound or Fast, motherboards' built-in Ethernet controllers, such as: MSI (Microstar) MS-6378, DFI NS70-EL & AZ30-EL, USI PM-845, Fujitsu D1451.. Update the drivers
Netgear FA311 and Netgear FA312 are also known to have issues. Try this driver update to resolve.
This is a NIC (Network Interface Card aka Network Card) related problem. most problems associated with NIC's - especially when running on 2000 / XP - are interrupt based.
Win 2000/XP has special problems because Microsoft's shortsighted default configuration assigns as many devices as it can to a single interrupt. Your computer then 'load balances' the lot. Don't ask why, its Microsoft.
Load balance depends on the Operating System to find out which device is asking for service and answers that device. This is all fine and dandy as long as you only play minesweeper and solitaire, but if you use things that actually use a lot of resources, this can cause real headaches.
The solution, for a number of people's problems, is to make sure Windows is not IRQ (Interrupt Request) sharing anything else important with the NIC. Some cards are a bit choosy about what IRQ level they use, but I have had no problems EVER, when using IRQ 9, 10 or 11 as long as drivers are current, and there is no sharing conflict.
First verify that your NIC is IRQ (Interrupt Request) sharing. You can do so by going into the device manager (control Panel, system, Hardware tab, and there should be a button called device manager about halfway down).
Once you have Device Manager open, select VIEW from the toolbar menu and then click Resources by Type.
From the example above, you can see there are several devices sharing the same IRQ. This is the most likely cause of your problem if you have already updated all of your drivers.
Changing IRQ Settings
Warning: Changing system resources such as IRQ channels can result in your computer not functioning correctly, always make a note of the settings before you change anything so you can restore them back if required.
If you do have a conflict and need to change an IRQ setting:
1. Right click on the device in the list (see above) and then select properties.
2. Click the Resources tab.
3. Remove the tick from the Use automatic settings option.
4. Select a non-conflicting configuration from the pull down box.
5. Click OK
It is very likely that you will not be able to manually change your IRQ settings (Use automatic settings will be grayed out), because of the ACPI functions in Windows 2000/XP.
The only way around that is to reinstall Windows without ACPI.
If you choose to do so, This Link should help you .
Just remember to make sure of a few basic things,
This Link actually can walk you through most of the procedure
Good luck, and remember to thank Bill Gates for not allowing this to be easily changed as it was in the older versions of windows.
Ram Issues
Some ram chips can play havoc on some motherboards. Check this link out Memtest86 may resolve your problem.

No comments: