Windows XP setup error message: IRQL_NOT_LESS_OR_EQUAL WTF????

[krazykilroy]

I've been trying to load Win XP pro for a couple of days now with a bunch of problems continually popping up.

First It didn't want to boot up from CD so that I could overwrite win98, so I had to load 98 first, then load XP froim the 98 OS. Had to take out half of the RAM to run 98, (back down to 512) and everytime it recognized the modem, it bluescreened. so I took it out and loaded XP.

It looked beautiful. so after loading video and sound drivers, I tried to load my memory and my modem back in. Then It all began!! Blue screens, continual reboots and the whole nine!!!!!

So now I formatted the Harddrive in another comp with XP hoping to see something, but nothing. After getting the 6-disk download of winXP boot-up, I still have this message: IRQL_NOT_LESS_OR_EQUAL.

How do I fix that???????

 

[MisterMe]

Clear your bios or reset default values and if the problem persists then try these links to see if anything jumps out at you...

 

[krazykilroy]

You think that my Promise IDE controller could be th culprit?

What I'll try to do is remove every PCI device piece by piece until I i might get a bite....

Keep you posted................

 

[serenedream]

I've found with XP, whenever i have my promise controller being used as the boot drive it causes problems.

Try and use the standard motherboard onboard controller for the harddrive you wish to install Xp on.

I just use a small 20gig drive for the XP install on the onboard controller and use my 2x60gig drives on promise raid controller for my Applications.

Seems to do the trick.

 

[krazykilroy]

well I put my two hard drives on the onboard controllers and my CD drives on the IDE controller (which is probably why it wont boot from CD) and I still have those kind of problems.

Took out the NIC card and still have those problems

 

[KB]

Are you getting random blue screens or always the same one? I have found that bad memory often causes random blue screens including the IRQ_LES_THAN_OR_EQUAL one.

"Had to take out half of the RAM to run 98, (back down to 512)" also makes me think RAM issues. Try to remove all but one stick and see how it goes. Try different sticks too. Good Luck.

 

[ketchupdog]

uninstall your video drivers, use default XP drivers, that will fix your bluescreen problem.

take a look at your IRQs. disable devices that you dont use and free up your IRQs




K

 

[Elvis2]

My problem turned out to be what KB described. I had two 256 meg sticks of Crucial pc2100 on my Asus A7V266-E and kept getting that same error. It wasn't 'till I reformated and installed a dual boot (98se) that I discovered the problem. While loading SE, I got a BSOD saying error @ vxd*** Vcache blahblahblah. I removed one stick and everythings been running fine since. My 512 should be here today.

 

[josphII]

sounds like memory problems