UGN Security Forums
My ProfileMember DirectoryLogin
Search our ForumsView our FAQView our Site Rules
View our CalendarView our Active TopicsGo to our Main Page

UGN Security Store

Network Sites UGN Security, The GoNix Initiative, Elite Web Gamers, Back of the Web, EveryDay Helper, VNC Web Design & Development
Sponsored Links
Latest Postings
by Herbert_Sherbert
09/07/15 10:34 AM
Latest Reviews
Topic Options
Rate This Topic
#8382 - 12/03/02 06:10 AM w2ksrv & ACPI (IRQL ndis.sys crash)
jonconley Offline
UGN Super Poster

Registered: 10/08/02
Posts: 955
Loc: Merrill, IA, USA
Has anyone had a problem similar to this?

DRIVER_IRQL_NOT_LESS_OR_EQUAL. The error reports as happening in the file NDIS.SYS. The error also reports that the machine is BEGINNING DUMP OF PHYSICAL MEMORY.

PC Support Technician:

It seems most problems associated with NIC's - especially when running on 2000 / XP - are interrupt based. Win2000 / WinXP has special problems because Microsoft's default configuration is to assign all, or as many as it can, devices to a single interrupt, #9, and then 'load balance' from there.

'Load balancing' means to service the interrupts logically - that is, by software via the OS - rather than via hardware. One hardware interrupt and when activated the OS finds out which device is asking for service and via software answers that device.

The only, major problem with that is the bandwidth that the video subsystem and network interfaces use from the system total - they are both DMA capable, high bandwidth devices that therefore require a high level of servicing from the interrupt system. And since the interrupt system on 2000 / XP machines is software based the OS, at one time or another, cannot keep up with the demand (Windows was never designed to operate as a real-time OS) and the device fails - and takes down the entire system.

The solution, for a number of people's problems, it to make sure Windows is not IRQ sharing anything else important with the NIC. Now, some NIC chipsets are pickier about the IRQ level set than other, but on the whole I have personally found that IRQ 9, 10 or 11 are the only IRQ's that almost never give trouble to a NIC that are on them - once any IRQ sharing issues and driver update problems are resolved.

If your NIC is IRQ sharing and you are having problems I may suggest trying to change the interrupt of that NIC, or move the other device's IRQ off the NIC, first.

Now, that could be a chore in itself. Try removing the network stack and the NIC's entry in Device Manager, shut down, pull the NIC out completely, reboot, shut down, reinstall NIC, restart.

When computers start they report the BIOS IRQ settings at the first set of boot screens, before the Windows 'splash screen'. If you have problems reading it just hit the 'Pause Break' key when necessary to pause the boot sequence - hit 'Enter' to continue. Some computer BIOS's have their own splash screen to cover the POST screen output - 'Tab' sometimes works to turn that off temporalily - see you BIOS setup or motherboard manual.

If the BIOS is setting the NIC at a shared IRQ then Windows will probably keep it there, if only for convenience. In that case either move the NIC to a different slot, or if available, go into the PCI setting page of the BIOS and see if you can change which IRQ the BIOS is assigning to the slot that the NIC is in. Not all motherboards allow this.

Getting Windows to change a IRQ that it wants to use sometimes is just about as easy as bringing Elvis back to life. But, if the system is unstable because of the NIC and the NIC is IRQ sharing, moving that IRQ will most likely help immensely.
I am trying different things, I just posted this hoping one of you knows what is up or has solved a similar problem.

And yes, I have USB, Realtek NIC, Netgear NIC, TNT2, and Creative Audio all on IRC9

MS Knowledge Base

General Description of IRQ Sharing in Windows 2000
The information in this article applies to:
Microsoft Windows 2000 Server
Microsoft Windows 2000 Advanced Server
Microsoft Windows 2000 Professional

This article was previously published under Q252420
For a Microsoft Windows XP version of this article, see 314068.
NOTE: This article is for informational use only. It does not contain any troubleshooting information. If you are searching for troubleshooting information that is not mentioned in this article, search the Microsoft Knowledge Base again by using keywords that are listed in the following Microsoft Knowledge Base article:

242450 How to Query the Microsoft Knowledge Base Using Keywords

In Windows, peripheral component interconnect (PCI) devices can share interrupts (IRQs) by design. Per the Plug and Play capability that is defined by the PCI specification, adapters are configured by the computer's BIOS, and are then examined by the operating system and changed if necessary. It is normal behavior for PCI devices to have IRQs shared among them, especially for Advanced Configuration and Power Interface (APCI) computers with Windows ACPI support enabled.
In Windows, some or all of the devices on your ACPI motherboard may be listed when you view the resources in Device Manager as using the same IRQ (IRQ 9) (to view the list of resources click either Resources by type, or Resources by connection on the View menu). You cannot change the IRQ setting because the setting is unavailable. This occurs because Windows takes advantage of the ACPI features of the motherboard, including advanced PCI sharing. IRQ 9 is used by the PCI bus for IRQ steering. This feature lets you add more devices without generating IRQ conflicts.

Note that Windows 2000 does not have the ability to rebalance resources in the same way that Microsoft Windows 98 does. After PCI resources are set, they generally cannot be changed. If you change to an invalid IRQ setting or I/O range for the bus that a device is on, Windows 2000 cannot rebalance the resource it assigned to that bus to compensate. Windows 2000 does not have this ability because of the more complex hardware schemas it is designed to support. Windows 98 does not have to support IOAPICs, multiple root PCI buses, multiple-processor systems, and so on. Rebalancing becomes risky when you are dealing with these hardware schemas, and will not be implemented in Windows 2000 except for very specific scenarios. However, PCI devices are required to be able to share IRQs. The ability to share IRQs should not prevent any hardware from working in general.

The Plug and Play operating system settings in the computer's BIOS should not affect how Windows handles the hardware in general. However, Microsoft recommends that you set this setting to "No" or "Disabled" in the computer's BIOS. For information about viewing or modifying your computer's BIOS settings, consult your computer's documentation or manufacturer.

Manually assigning IRQs to PCI slots in the System BIOS as a troubleshooting method may work on some non-ACPI systems when using a standard PC HAL, but these settings are ignored by Plug and Play in Windows if ACPI support is enabled. If you need to manually assign IRQ addresses through the BIOS to a device on an ACPI motherboard, you will need to re-install Windows to force the installation to use a Standard PC HAL. For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

216251 How to Specify a Specific or Third-Party HAL During Windows 2000 Setup

Sponsored Links
#8383 - 12/03/02 06:29 AM Re: w2ksrv & ACPI (IRQL ndis.sys crash)
Infinite Offline

Registered: 03/09/02
Posts: 1041
Loc: Canada eh
Damn, Plug n PLay my ass eh?

I haven't had this problem but I'm interested to hear how you get around it.

#8384 - 12/03/02 07:39 AM Re: w2ksrv & ACPI (IRQL ndis.sys crash)
SilentRage Offline
DollarDNS Owner

Registered: 03/04/02
Posts: 1273
Loc: OH, USA
Well, I read the technicians comments - very informative stuff - I think I'll tuck that away for later reference - and stopped when I got to the MS article.

What exactly is your question? It seems that the technician's comments and the MS article tells ya all you need to know to fix your problem - if indeed that IS the problem.
Domain Registration, Hosting, Management

#8385 - 12/03/02 08:20 AM Re: w2ksrv & ACPI (IRQL ndis.sys crash)
jonconley Offline
UGN Super Poster

Registered: 10/08/02
Posts: 955
Loc: Merrill, IA, USA
My bios doesn't give me any configuration options related to this. So I cannot change the settings, and as far as I can see I am fuct in the ass.

#8386 - 12/03/02 10:01 AM Re: w2ksrv & ACPI (IRQL ndis.sys crash)
unreal Offline

Registered: 03/01/02
Posts: 860
This is why I hate my computer...this very problem. I might have to give some of this a try.

#8387 - 12/03/02 03:43 PM Re: w2ksrv & ACPI (IRQL ndis.sys crash)
SilentRage Offline
DollarDNS Owner

Registered: 03/04/02
Posts: 1273
Loc: OH, USA
IRQ's are also determined by the hardware device itself. Does any of the hardware sitting on IRQ 9 have a jumper or something to set the IRQ?
Domain Registration, Hosting, Management

#8388 - 12/03/02 04:27 PM Re: w2ksrv & ACPI (IRQL ndis.sys crash)
jonconley Offline
UGN Super Poster

Registered: 10/08/02
Posts: 955
Loc: Merrill, IA, USA
No, it states in the MSKB, that PCI devices, using the ACPI from BIOS set all PCI devices to IRQ9 and then from there, they cannot be changed at all in windows 2000. So I really have no choice, and the problem I think occurs because I have two NICs with heavy traffic and my video card on same PCI and w2k has trouble load balancing them and if it cannot do so, the entire system crashes. So there really doesn't seem to be a solution according to microsoft.

Maybe I am missing something?

#8389 - 12/04/02 11:38 PM Re: w2ksrv & ACPI (IRQL ndis.sys crash)
sinetific Offline

Registered: 03/02/02
Posts: 815
Loc: Ann Arbor
You really might want to take SR's advice and mine and check all your devices for jumpers more than likely soundcards, and network cards, have jumpers on them that force IRQ assignments. I would suggest completely removing the device from the machine putting a closing the IRQ assignment jumper pins and moving the card to a new pci slot.

This is kinda funny cause the other day someone was bashing linux cause of all the configuration files you go through to get a device working. Well at least with nix you have the ability to change it and arent stuck like you are with microsuck(as I type this from xp(lol what a hypocryte))

I always thought you were able to change IRQs from the device manager. I guess i was wrong cause I just checked and you couldn't...although the option was there, it was greyed out. Nothing like this has ever happened to me so I never really bothered looking.

#8390 - 12/06/02 06:57 AM Re: w2ksrv & ACPI (IRQL ndis.sys crash)
fleshwound Offline

Registered: 03/10/02
Posts: 536
Loc: CO
yeah... win2k is more stable than previous versions my ass.
"when you look around, you can't tell me honestly you're happy with what you see"

#8391 - 12/06/02 11:11 AM Re: w2ksrv & ACPI (IRQL ndis.sys crash)
jonconley Offline
UGN Super Poster

Registered: 10/08/02
Posts: 955
Loc: Merrill, IA, USA
Evidently in every other OS but windows 2000, you are able too. As stated about. Also has to do with ACPI. I will check the cards though. I am sure I would have seen it before, but hopefully its there. Thanks. and agreed fleshy

#8392 - 05/11/04 08:16 PM Re: w2ksrv & ACPI (IRQL ndis.sys crash)
wtimber Offline
Junior Member

Registered: 05/11/04
Posts: 1
Loc: NE
I think in this case the user is right
2k blues

check for presence of winhlpp32.exe in system32 folder

scan for viruses

check to see if svchost.exe is using 99 percent of CPU instead of system idle process.
wait a few minutes before checking for this to let everything start up.

bet it only blue screens in the email too...


Moderator:  Infinite 
Featured Member
Registered: 04/29/15
Posts: 2
Forum Stats
2158 Members
46 Forums
41462 Topics
76636 Posts

Max Online: 1567 @ 04/25/10 02:20 AM
Top Posters
UGN Security 34624
Gremelin 7193
§intå× 3255
SilentRage 1273
Ice 1146
pergesu 1136
Infinite 1041
jonconley 955
Girlie 908
unreal 860
Newest Members
Herbert_Sherbert, codemauve, Lillysdragon1984, Brewwit, Suri John
2157 Registered Users
Who's Online
0 registered (), 268 Guests and 172 Spiders online.
Key: Admin, Global Mod, Mod
Latest News

  Get Firefox!
Get FireFox!