IRQL_NOT_LESS_OR_EQUAL

  • Thread starter Thread starter avianchaos
  • Start date Start date
A

avianchaos

So I've done some research about this problem and people say that it
can be caused by anything from a bad heatsink to bad video drivers to a
bad motherboard. I'm pretty sure I've narrowed down what is causing
it, though - the network. The only time my comp crashes and gives me
the BSOD with this error is when I'm connected to the router. I'm
plugged directly into the modem right now, and it works fine. I
installed a new NIC card, instead of using the onboard LAN, and it
still happens. I'm running an Athlon 3500+ on a Chaintech motherboard,
Radeon AIW x600 with 1GB Corsair RAM. I've run Memtest, the RAM is
fine. I've tried rolling back my video drivers and a lot of other
things, but the only thing that stops this from happening is taking the
router out of the equation. Any suggestions on how to fix the network
drivers so that this won't happen? Can I buy a different router? What
if I run the modem through a switch before it gets to the router (it's
a WLAN, other people use it in the house), and then run my comp off the
switch? Could that work?
 
That heppened to me. It's network. Install sp2, it's fixed. Also,
configure the router's security/encryptian to something lower. Sp2 works
well, though.
 
Treeman said:
Check here for the MS explanation;
'IRQL_NOT_LESS_OR_EQUAL ' (http://tinyurl.com/yvpfa)
Treeman

I had this problem develop suddenly as well and then it seem to get
better but then came back stronger and faster! Im the end after endless
searching I came to the opinion that it was because I had installed or
modified a driver or hardware that was disagreeing with windows. I
checked the IRQ list in device manager and although I had several items
that shared the same IRQ none of them seemed to be marked with a yellow
! mark. I ran the driver verifier and after rebooting it showed me the
problem. In ignorance I deleted the file thinking that windows will
reinstall it when I rebooted. Boy was i wrong I got another BSOD and
then when I attempted to sort THAT out I got a BSOD on reboot that would
even let me boot in safe mode let alone normal!!

I tried many things, like using the restore(or is it repair) console in
xp but that didn't work either. In the end I had to do a clean reinstall
of windows and decided to reformat my drive at the same time. I then
installed all my HDD and other devices one by one and made sure I had
the latest drivers for each one. That was a LONG Friday I can tell you!

Fingers crossed - I havnt had a problem since Friday!

If you want my advice think carefully which device or driver you
installed before the problem first started and then go back and either
to a rollback (in the case of the driver) or a clean uninstall, reboot
and install (in the case of the hardware). Make sure you do a system
restore before this just in case and also make sure EVERYTHING is uptodate.

Hope this helps and works out better for you.

Zankhna
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Back
Top