Okay, bear with me on this one. In my PCI Device Listing, I've noticed a few shared IRQ adresses - Device Class IRQ
SMBUS Cntrlr 4
Multimedia Device 4
USB 2.0 EHCI Cntrlr 5
Mass Storage Device 5
USB 1.0/1.1 Cntrlr 7
Display Cntrlr 7
IDE Cntrlr 10
IEEE 1394 Open HCI Cntrlr 10
IDE Cntrlr 11
nVidia Ethernet Bridge 11

As you can see, there are more than one device assigned to 5 of my IRQ addresses. I'd like to know, can this cause a problem, and if so, what is the solution?
Thanks a lot.

Do you have a problem? If not don't worry about it. Windows know what it is doing with IRQ addresses.

i_XpUser

It's normal to have some shared IRQ's. They don't have an address you would need to be concerned about, but each device has it's own I/O address, and you would have a problem if the I/O addresses conflicted.
It's unfortunate they list Sharing and Conflicts under the same heading - sharing is usually benign, and conflicts often do not show up under that heading, but if they do they would probably be highlighted with some red words.

Devices built into the mboard often share the same IRQ with no problem.
All your onboard USB controllers, or rather, all your onboard USB 1.x controllers, and/or all of your onboard USB 2.0 controllers, may have the same IRQ with no problem. Sometimes a USB card will share the same interrupt with onboard USB and that causes no problems.
Devices built into the mboard can often share the same IRQ with your video card or onboard video with no problem, but a device that isn't built into the mboard may have a problem sharing an IRQ with a video card or onboard video.

XP handles IRQ sharing much better than Win 9x/ME does.

If you do have an IRQ sharing problem sometimes it doesn't show up in System Information - sometimes the IRQ, and both (or all) devices that are trying to use it will not show up there.

If you do have a problem, you are more likely to find info about it in System Information under the Components - Problem Devices heading, and if there is anything listed, it isn't necessarily a real problem unless it has some red lettering in it - e.g. if you intentionally disabled a device in Device Manager, it will show up under Problem Devices.

Hi, The guys are right. If you have no problems don't worry about it. Everybody has a bunch of shared IRQs. As long as sharing is allowed in the BIOS SETUP, if it's there, Windoze will take care of it.

Luck, Jim

I know of no way you can turn off IRQ sharing in the bios Setup, other than specifying only one IRQ per one or all slots, and even then you can't turn it off for IRQ's other than for the slots. Some devices are legacy and can only use one IRQ and can't share it. You can specify whether the OS is PNP aware in the Bios Setup in most cases, and turn it on or off, and how the OS deals with that can be quite different depending on whether that setting is on or off.

You can force settings for some specific devices in some cases in Win 9x and up, but I know of no other way to disable IRQ sharing in Win 9x and up, other than forcing it off by changing specific default settings in the operating system.

Hi again, It may not be in the BIOS SETUP, but is definitely somewhere in most systems. Don't remember where, but definitely have seen in many times over the past 30 years. Try SYSTEM INFORMATION. It has a function that will tell you if there are conflicts with IRQs. A shared IRQ is not necessarily a Conflict.

Luck, Jim

I usually get "Stop 0x000000D1 or DRIVER_IRQL_NOT_LESS_OR_EQUAL" upon wake up from standby. I assumed it could be due to IRQ conflicts when I noticed thoses entries in the PCI Device listing upon system boot. I am, however, having a problem with chkdsk, as well. I cannot schedule a chkdsk /f, nor defrag due to this, however chkdsk in a cmd prompt will let me know that there are problems with the file system. Perhaps if I fix this it'll go away. Also, upon Windows startup, a mystery SCSI/RAID is found, but all of my drivers are installed. Any suggestions about the file system without a reinstall, since I can't seen to run chkdsk /f?
Thanks.

You should have mentioned that error in your first post. It has probably got nothing to do with your IRQ's. You may need to clean the contacts on your ram, or make sure your ram is well seated, or there can be other causes for that error.
See response 3 in this:
http://www.computing.net/hardware/wwwboard/forum/44009.html

It also sounds like your Windows installation is damaged.
Once you have cured the rebooting problem and your system is stable, you could try doing an XP Repair Setup, which will not harm your existing Windows installation, but it can only fix things Windows detects as wrong, or replace corrupted or missing Windows files that are on your original XP CD. If running it doesn't cure enough of your problems and/or the problems are caused by things not on the original Windows CD, you will probably have to make a clean install of Windows from scratch.

You will need a Windows CD of the same version as the one of your Windows installation, and the Product Key, preferably the one that was used to install it, but it can be one for the same version as the one of your Windows installation.

how to do an XP Repair Setup, step by step:
http://www.windowsreinstall.com/winxppro/installxpcdrepair/indexfullpage.htm

Oops - my last post was posted in the wrong thread.
Although you could try that if you like.