This is a Numbered...UnOrdered List of points and solutions.
1. There should be more information than that.....it should give you an IRQ address and an exact error code. This could help us address your situation more.
2. Automatic updates and driver updates can rearrange your IRQ settings, as these can be done through windows hardware device manager.
3. Simplest, least technical trouble shooting way to deal with conflicting IRQs is, open up your machine, and anything that can be swapped around your machine....swap it, put your memory in a different slot, if you have to slots and two modules, swap them over, move your PCI cards.....like I said...this isn't a the most technical way round it, and it doesn't resolve the issue, but it can get rid of your conflict
4. Do what you should always do first with machine problems....strip your machine to bare bones. CPU (and cooler of cause), 1 memory module, gfx card, hdd. and boot it. if you have spares of these, that is handy cause if you get the same problem with these bare bones, swap these with spares one at a time, you may find that you have a bad peice of kit. If you find that the bare bones system now boots...add back your devices, again, one at a time, any extra memory, one at a time, obviously booting and testing as you go, then sound card (if not onboard), aditional USB ports, network card, firewire. USB ports/NICs and Internal Modems tend to be the highest cause of IRQ conflict failures.
You will probably find that you will put everything back in, and it will be a phenomenon, and it will all work, and you haven't really done anything...i think your machines is just bored and wants you to give it some attention...
my advice, is you probably haven;t been inside for a while....give it a good clean, get rid of those massive wedges of dust, but be careful that your dyson doesn't suck up some transistors off your board.
HTH
Peace out
NJC
