Having pesky IRQ/uPnP conflicts during boot

BrokenVisage

Lifer
Jan 29, 2005
24,771
14
81
I've been having problems with my secondary computer lately after trying to install a RAID controller on it. I bought a Promise FastTrak card so I could run my SATA drive as ATA-300 and later get another drive to run some kind of RAID array with it.

I knew this wouldn't end well when my computer couldn't even recognize the card as new hardware and attempt to install drivers for it when I first booted up with it inside. To see if it wasn't just DOA I put it in my AMD computer at it came up fine. So I went ahead and installed the RAID drivers and management software on the secondary computer and kept trying to get it to work on that.

I just couldn't get it to work though, I moved all my PCI cards around and tried it in every slot but still got nothing. I decided to return the card to Amazon and try another brand, but now I have an issue that I think stems from trying to get this card to work on my board.

Basically, I use this computer as a quasi-fileserver to handle my torrents, newsgroup stuff, and P2P - and a quasi-HTPC set up with a firewire card to record content off my Comcast box, usually I just do this when I'm running low on DVR space. So before installing this RAID card I had these other two cards running fine with one PCI slot opened between them, the last empty slot.

Here's where the problems started, after giving up with this card and taking it out of my machine I've been getting IRQ/uPnP errors on boot with my other perhiperals. Basically, during boot after BIOS discovers my HDD, CDROM, and memory.. I get a 2-beep error that looks like the follow: "ERROR: IRQ/uPnP device conflict! Wireless-G Adapter Slot: 01 Bus: 02" I'll get you the exact wording if needed, but basically that's how it goes. Sometimes it was the Wi-Fi card throwing that error, other times it would be both my FireWire and Wi-Fi card. I've tried troubleshooting this problem over the weekend and got as far as this:

I can install my Wireless-G card in any slot and it works as long as it's the only card. My FireWire card doesn't work in any slot when it's the only card installed, however it doesn't throw a IRQ/uPnP error on boot like before, it just doesn't work and isn't even recognized by my computer (just like the initial problem I had with my RAID card). And when I have both cards installed no matter what card is in what slot, BIOS will always throw an IRQ/uPnP device conflict error against my Wireless-G card, and once it gets to Windows I get an explaination point icon next to it in the device manager signifying it has issues and does not work of course. HERE is a screenshot of each device and the IRQ port they currently occupy.

Over the past couple days I've tried a slew of things to get this resolved. I've went into BIOS and disabled ports I don't need like LPT, Serial, and COM ports to try and open up other IRQ instances, nothing seemed to work. The BIOS I have for this motherboard isn't very robust, but I've fiddled with every PCI/uPnP option it has get this fixed, none of them seem to work. One thing I should mention before I forget is that I was driven to formatting the drive completely and starting over from scratch, thinking it was a driver issue from the RAID card.

A couple random questions I'll throw out there now involve resetting my BIOS. What can I do to maybe force my devices to recapture IRQ's? Is there a special BIOS I can install that isn't too motherboard dependant where I can access more options? Windows doesn?t seem to let me choose different IRQ?s in the device manager, so is this something I have to do configure in BIOS and only BIOS? I'm willing to format again just to fix this issue; it's really no big deal for me to reinstall a couple programs on a fresh install of Windows.

So there's my story, at this point I'm sure this can be resolved by something simple that I'm just overlooking at the moment, but that's why I'm here. I'm posting this in several categories because I believe it's the kind of error that someone has came across before and fixed but rarely happens, so I want to reach out to those who visit only 1 or 2 forums on here.

Thanks in advance if you choose to help me, I'll be checking in regularly and answering any more questions I didn't answer in my post.
 

Peter

Elite Member
Oct 15, 1999
9,640
1
0
Unless you've been manually screwing with the PCI/PnP settings, there isn't much potential for PnP conflicts ever since ISA (!) PnP cards have disappeared.

Revert all BIOS settings to their "optimal" defaults, engage the "Reset ESCD Configuration" control when your BIOS's PCI/PnP page has one, and reboot. That should sort things - and if you still get that message, then that points more to a BIOS bug than anything actually to do with your particular configuration.
 

BrokenVisage

Lifer
Jan 29, 2005
24,771
14
81
Originally posted by: Peter
Unless you've been manually screwing with the PCI/PnP settings, there isn't much potential for PnP conflicts ever since ISA (!) PnP cards have disappeared.

Revert all BIOS settings to their "optimal" defaults, engage the "Reset ESCD Configuration" control when your BIOS's PCI/PnP page has one, and reboot. That should sort things - and if you still get that message, then that points more to a BIOS bug than anything actually to do with your particular configuration.

Thanks for the information, I've researched ESCD and think this might do the trick, however I've been up and down every inch of my BIOS and found nothing dealing with resetting the data, but I have seen what you mean in screenshots from the Award/Phoenix brand though. I have attempted resetting CMOS configuration data using the jumper for it on the motherboard, but it doesn't seem to do anything. I'll have to see if Award makes a compatible BIOS for my board and try to flash it with that when I get home.