General discussion



By kyle2371 ·
I recently installed a new motherboard into my computer. It was working fine for a little bit, but now I'm having problems. At first, the computer would reboot just after it loaded Windows XP. It was basically stuck starting and restarting over and over again.

Because of that, I decided to format. Well, I formatted, but I can't get Windows reinstalled because I get the IRQL_NOT_LESS_OR_EQUAL error when setup is loading files. It gets past the formatting and loads about 70% of the files, and then the blue screen pops up. Then I have to restart and try all over again. I'm not sure what would be causing this one.

I have also gotten one other blue screen error in the same spot. It has to do with checking the hardware and software, but I didn't see any specific error name.

I just need to figure out how I can stop this error and get windows installed again so the machine is stable. I'm not sure if it's a hardware error because I checked all of my components individually and they seem to work fine. It just seems odd that this would happen as soon as I put in a new motherboard however. Plus, I can't see how this would have anything to do with software because it has been completely formatted, so there's no software even on the machine.

I don't know if it matters, but I'm using an Athlon 64 bit 3000+ and a Gigabyte motherboard.

Thanks for any help.

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

by HereInOz In reply to IRQL_NOT_LESS_OR_EQUAL

That error is typically associated with hardware, drivers and interrupts, although it can be a little hard to nail down.

Given that the problems started when you installed the new Motherboard, and you have since formatted and still the problems persist, clearly the first thing to suspect is that one of the on-board things - LAN, video, sound, or even the the chipsets or processor, is not working correctly and is giving you the error.

If you have an old version of XP - pre SP2, you may be running into the situation where the software does not have the necessary drivers to support the new hardware and the install is falling over. If this is the case, get hold of a more recent version of XP, even if you temporarily borrow someone else's copy, and run the install. If it works, that is the problem.

Good luck,

Collapse -

by Neil Cotton In reply to IRQL_NOT_LESS_OR_EQUAL

This is a Numbered...UnOrdered List of points and solutions.

1. There should be more information than 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 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...


Peace out

Collapse -

by dmiles In reply to IRQL_NOT_LESS_OR_EQUAL

The error is usually caused by bad RAM.

To narrow it down you basically have to pull any hardware out that might be causing it; NIC's, modem, soundcard, anything that can come out.

The reason you do not see it in 98 os that 98 and XP are VERY different OS's. The kernal that they are based on, use and interact
with the RAM differently.

Swap you RAM if you can.

Is you BIOS the latest?

Here is the link to the MS article on it.;en-us;314063

Collapse -

by lox In reply to IRQL_NOT_LESS_OR_EQUAL

Just had a friend with your exact problem....ended up being a bad stick of ram. #3 is correct

Related Discussions

Related Forums