IRQL not or less equal

[knucmo]

Hello there,

My friends computer is having a few problems at the minute. One of
which is a recurring BSOD containing the error message 'IRQL not or
less equal'. Coincidental (or perhaps caused by) is the fact that he
cannot connect to our router although the rest of us on our house
can. But the IRQL error is the one I would like to solve firstly. I
have ran a memory test as recommended by many IT experts and there was
no trouble with the memory. Any other things I can try?

 

[Malke]

Hello there,

My friends computer is having a few problems at the minute. One of
which is a recurring BSOD containing the error message 'IRQL not or
less equal'. Coincidental (or perhaps caused by) is the fact that he
cannot connect to our router although the rest of us on our house
can. But the IRQL error is the one I would like to solve firstly. I
have ran a memory test as recommended by many IT experts and there was
no trouble with the memory. Any other things I can try?

Usually the IRQ... Stop Error will give the name of the problematic file.
Post back with that important missing detail so we can help you. IRQ.. Stop
Errors usually indicate firstly a problem with drivers (hence the need for
the missing name of the file) and secondly a hardware problem.

And as always, have your friend answer The First Question Of
Troubleshooting: If the problem is new, what changed between the time
things worked and the time they didn't?

Malke

 

[Bob I]

The rest of the error message will tell you where to look. See link below

http://aumha.org/a/stop.php#0x0a

 

[knucmo]

The rest of the error message will tell you where to look. See link below

http://aumha.org/a/stop.php#0x0a

Hi guys, thanks for the advice, but it's just got worse now. I had a
look at the MSDN article - I tried to get the computer to boot into
safe mode to do a system restore. I did this using the MSCONFIG
method (Boot.ini) and it would not boot into safe mode. So the screen
came up whereby I could boot the 'Last Known Good Configuration' part,
which was temporarily heartening, but XP would not boot. A blue
screen flashes very quickly as XP is loading and then the computer
restarts. I suspect my meddling with the MSCONFIG has caused this,
and I need to get back to a point where the computer loads XP up at
least!! I have never had this much trouble with a computer before.

 

[Malke]

Hi guys, thanks for the advice, but it's just got worse now. I had a
look at the MSDN article - I tried to get the computer to boot into
safe mode to do a system restore. I did this using the MSCONFIG
method (Boot.ini) and it would not boot into safe mode. So the screen
came up whereby I could boot the 'Last Known Good Configuration' part,
which was temporarily heartening, but XP would not boot. A blue
screen flashes very quickly as XP is loading and then the computer
restarts. I suspect my meddling with the MSCONFIG has caused this,
and I need to get back to a point where the computer loads XP up at
least!! I have never had this much trouble with a computer before.

Sorry, but without knowing the original device file from your first Stop
Error, I can't possibly guess what was wrong in the first place. If XP
won't boot because you disabled the wrong thing, you can try a Repair
Install. If it were me, I'd first:

1. Pull the hard drive and back up any data if this needs to be done.
2. Disconnect any USB devices (except keyboard/mouse).
3. Since the problem seemed to be connected to Internet connectivity, pull
the network adapter (NIC) if it's a PCI card, disable it in the BIOS if
onboard.
4. Do some hardware testing - at least the RAM and hard drive.
5. If the hardware tests good, do a Repair Install without the original
network adapter. If all is well and you can get into Windows, I think I'd
uninstall the original NIC from Device Manager and just throw in a new PCI
NIC. This last is just a WAG but NICs are cheap so this extra step is no
big.

Malke

 

[knucmo]

Sorry, but without knowing the original device file from your first Stop
Error, I can't possibly guess what was wrong in the first place. If XP
won't boot because you disabled the wrong thing, you can try a Repair
Install. If it were me, I'd first:

1. Pull the hard drive and back up any data if this needs to be done.
2. Disconnect any USB devices (except keyboard/mouse).
3. Since the problem seemed to be connected to Internet connectivity, pull
the network adapter (NIC) if it's a PCI card, disable it in the BIOS if
onboard.
4. Do some hardware testing - at least the RAM and hard drive.
5. If the hardware tests good, do a Repair Install without the original
network adapter. If all is well and you can get into Windows, I think I'd
uninstall the original NIC from Device Manager and just throw in a new PCI
NIC. This last is just a WAG but NICs are cheap so this extra step is no
big.

Cheers Malke. I've already tested the RAM, and I'm going to repair XP
this morning. Here goes....

 

[knucmo]

Sorry, but without knowing the original device file from your first Stop
Error, I can't possibly guess what was wrong in the first place. If XP
won't boot because you disabled the wrong thing, you can try a Repair
Install. If it were me, I'd first:

1. Pull the hard drive and back up any data if this needs to be done.
2. Disconnect any USB devices (except keyboard/mouse).
3. Since the problem seemed to be connected to Internet connectivity, pull
the network adapter (NIC) if it's a PCI card, disable it in the BIOS if
onboard.
4. Do some hardware testing - at least the RAM and hard drive.
5. If the hardware tests good, do a Repair Install without the original
network adapter. If all is well and you can get into Windows, I think I'd
uninstall the original NIC from Device Manager and just throw in a new PCI
NIC. This last is just a WAG but NICs are cheap so this extra step is no
big.

I've tested the memory as mentioned already - no problems there. Do
you know of any hard drive integrity tests I can download?

One problem I have is that it will not boot from the XP CD even if I
switch the boot priority to the CD first. It will boot only from the
XP cd when I disable the hard drive in the boot priority - and of
course when I try to do a repair install it quite rightfully detects
no hard drive. Yet to boot from the repair CD I have to disable the
hard drive!! A complete Catch-22.

 

[Malke]

I've tested the memory as mentioned already - no problems there. Do
you know of any hard drive integrity tests I can download?

One problem I have is that it will not boot from the XP CD even if I
switch the boot priority to the CD first. It will boot only from the
XP cd when I disable the hard drive in the boot priority - and of
course when I try to do a repair install it quite rightfully detects
no hard drive. Yet to boot from the repair CD I have to disable the
hard drive!! A complete Catch-22.

If the machine won't boot from the CD if the hard drive is disabled,
something is wrong with your hardware. Hard drive diagnostics should be
gotten from the drive mftr.'s website. Maybe your power supply is going or
your motherboard is failing. I'm very sorry but there is simply no way for
me to troubleshoot this machine sight unseen.

I think you should take it to a reputable shop, not a
BigComputerStore/GeekSquad type of place, but that's your choice of course.
I hope you find the solution and I'm sorry I was unable to help.

Malke

 

[westom1]

I've tested the memory as mentioned already - no problems there. Do
you know of any hard drive integrity tests I can download?

One problem I have is that it will not boot from the XP CD even if I
switch the boot priority to the CD first. It will boot only from the
XP cd when I disable the hard drive in the boot priority - and of
course when I try to do a repair install it quite rightfully detects
no hard drive. Yet to boot from the repair CD I have to disable the
hard drive!!

So it tried to boot from the hard drive, cannot, gets stuck, and
therefore never tried to boot from the CD? Well then change the order
of boot selection.

Or it does not even try to boot because the BIOS gets locked on the
disk drive? Your post is not clear.

Meanwhile, critical information was even on the BSOD - numbers. No
numbers means you don't get replies from the better educated and
knowledgeable. What were all the numbers and specific messages on
that BSOD? If you don't have them, then appreciate why so much more
labor is required.

You problem is also why the few and far more responsible computer
manufacturers provide comprehensive hardware diagnostic for free on
the drive, on a CD, and from their web site. Sound like you have no
choice. Download diagnostics for each component from each
manufacturer. What is you disk drive manufacturer? That is where you
get them. What is your video processor manufacturer? Same is
required.

The underlying point - first get facts. Well, the problem could
have been seen by Windows long ago and stored in the system (event)
logs. Too late now./

I also hope you did not try to reload Windows. Not only would that
destroy useful facts in system logs. Defective hardware would only
result in defective Windows. Now you have two problems making the
solution exponentially more complex. Don't fix anything until the
problem is first identified. That means diagnostics and other facts.

Currently everything remains unknown. Your objective. Get every
component from unknown to either 'definitively good' or 'definitively
bad'. Your accomplishments are measured by the length of that list.
Another component that could cause all your symptoms is the power
supply system (not just a power supply). But again, replace nothing
until the problem is first identified. If due to a defective supply
system, well, that problem is known 'definitively good' or
'definitively bad' in but 30 seconds - without removing or
disconnecting anything.

But that is another post if you decide to address this problem in a
logical manner - without wild speculation such as reloading Windows.
We don't even know if you changed the boot order, if the BIOS gets
stuck before even trying to boot, or critically useful numbers and
statements from the BSOD screen.

 

[knucmo]

  So it tried to boot from the hard drive, cannot, gets stuck, and
therefore never tried to boot from the CD?  Well then change the order
of boot selection.

I did, only I did not mention this in the post. I switched the CD to
have first priority, then the floppy then the HD. It would not boot.
I then had the floppy first, then CD, then HD. Nothing. I tried all
manner of permutations which had the HD as the least prioritized and
it would not boot from CD until I disabled the HD altogether, which is
not going to solve many problems.

  Or it does not even try to boot because the BIOS gets locked on the
disk drive?  Your post is not clear.

  Meanwhile, critical information was even on the BSOD - numbers.  No
numbers means you don't get replies from the better educated and
knowledgeable.

Very well, but my friend who had the error could only remember the
error message, not the codes, and since I have not had time to see the
error I could make no judgment really. But yes, a fair point.

 What were all the numbers and specific messages on
that BSOD?  If you don't have them, then appreciate why so much more
labor is required.

I did. It was purely voluntary that you chose to respond my post, and
now you seem to demand some sort of tribute?! Let me state again, I am
very grateful for any help that comes my way, and I am not
purposefully being 'unclear' or ungrateful.

  You problem is also why the few and far more responsible computer
manufacturers provide comprehensive hardware diagnostic for free on
the drive, on a CD, and from their web site.  Sound like you have no
choice.  Download diagnostics for each component from each
manufacturer.  What is you disk drive manufacturer?  That is where you
get them.  What is your video processor manufacturer?  Same is
required.

  The underlying point - first get facts.  Well, the problem could
have been seen by Windows long ago and stored in the system (event)
logs.   Too late now.

  I also hope you did not try to reload Windows.

Reload, as in reinstall? No. I tried to use a Windows CD to get it to
boot into its normal mode or Safe mode, neither of which happened.

 Not only would that
destroy useful facts in system logs.  Defective hardware would only
result in defective Windows.  Now you have two problems making the
solution exponentially more complex.  Don't fix anything until the
problem is first identified.  That means diagnostics and other facts.

  Currently everything remains unknown.  Your objective.

Should you choose to accept it....

 Get every
component from unknown to either 'definitively good' or 'definitively
bad'.  Your accomplishments are measured by the length of that list.
Another component that could cause all your symptoms is the power
supply system (not just a power supply).  But again, replace nothing
until the problem is first identified.  If due to a defective supply
system, well, that problem is known 'definitively good' or
'definitively bad' in but 30 seconds - without removing or
disconnecting anything.

 But that is another post if you decide to address this problem in a
logical manner - without wild speculation such as reloading Windows.
We don't even know if you changed the boot order, if the BIOS gets
stuck before even trying to boot, or critically useful numbers and
statements from the BSOD screen.

The BSOD screen numbers are probably not going to be available til I
can boot into Windows.

Therefore: My first priority is to get Windows booting again. I am not
sure that the BIOS is getting stuck; it seems to be responding OK,
insofar as when I change the boot order it responds.

Thanks again

 

[westom1]

Therefore: My first priority is to get Windows booting again. I am not
sure that the BIOS is getting stuck; it seems to be responding OK,
insofar as when I change the boot order it responds.

Exactly. When BIOS first loads, it does things such as check for
various parts. IOW it must determine the video card. Later it must
verify memory. Later it will look for peripherals it can boot from
such as hard drive, floppy, USB port, CD-Rom, etc. Only long after
doing everything does it go back to trying to boot from those
peripherals.

Is BIOS even executing? Remove all memory and try to boot. If BIOS
is executing, then when it sees no memory, the BIOS will beep
speaker. Then BIOS is executing just fine.

Is BIOS getting stuck on the hard drive? Well, BIOS first looks for
various components. Does it try to find those other boot
peripherals? Does it move the floppy or trigger the CD-Rom light?

CD-Rom is another (shared) IDE peripheral. For example, if a disk
drive's computer is the primary drive, then a defective disk drive
computer also means the CD-Rom will not boot. Making the CD-Rom as
the primary drive means CD-Rom's internal computer (not hard drive's)
boots a CD-Rom. But then hard drive should not interfere with booting
of a floppy (if floppy is higher in the boot order).

If you can change the order of booting in BIOS, then BIOS is running
just fine. That means BIOS (motherboard computer) locks while waiting
for a response from the disk drive's computer. So now you know what
is wrong.

If hard drive is on the secondary IDE port, and CD-Rom on primary
IDE port, then CD-Rom's computer would let BIOS talk only to CD-Rom
AND hard drive's IDE port may not interfere.

I believe your BIOS is working just fine now that you provided
additional information - you can change boot order. I suspect your CD-
Rom and disk drive share a common IDE port - not good. I believe your
system should still boot from the floppy or USB memory stick just fine
if the boot order accesses those before the hard drive. If so, then
the disk drive manufacturer's diagnostic can be load from the memory
stick or floppy. Then disk drive can be studied by manufacturer's
comprehensive diagnostic.

But if I am correct, you need not even do that. If I am correct,
the disk drive's computer is completely defective, locking up the IDE
port, and also not permitting any secondary IDE drive (ie CD-ROM) to
be accessed.

It was purely voluntary that you chose to respond my post, and
now you seem to demand some sort of tribute?!

I seem to be doing nothing but going after hard technical facts.
Anything else you read in my post is your own wild speculation. I am
not a child. I only say what I mean. I did not state an emotion
exists - therefore nobody knows of or even considers any emotion. If
I demand some kind of tribute, you will hear it bluntly .... and
technically. And if you assume some kind of emotion in this
paragraph, well, I am intentionally writing this paragraph to imply an
emotion that is 100% wrong. Never speculate emotion in any adult's
post. (However some adults are still children.) Again, nothing
emotional is in this paragraph; not even a scolding. Just blunt
straight facts from one who means only what is bluntly said. The
only intention in every paragraph - contempt for a hardware failure
that insulted the universe by existing. This paragraph only says what
it says - without any emotion intended or implied - except for
contempt of failures. Even then, you never knew that emotion exists
until stated in this paragraph - because the only emotion that exists
is stated bluntly and obviously.

IRQL error does not correspond to a disk drive failure. Assuming
that all failures are traceable to a common point, one likely common
point (and there are others) is the power system. IOW a defective
power supply 'system' could have existed long ago and will often boot
a computer. Now the supply 'system' is getting worse causing the IRQL
error and now a BIOS boot problem. This paragraph is secondary.
First learn what a disk manufacturer diagnostic can discover or what
the BIOS is getting hung up on. Determining a defective power supply
'system' involves 30 seconds and never disconnecting anything. That
reserved for another post.