Sign in with
Sign up | Sign in
Your question

DRIVER_IRQL_NOT_LESS_OR_EQUAL ?

Last response: in Motherboards
Share
March 5, 2003 4:08:54 AM

Jesus I have seen this before and have fixed it, but of course I cannot remember. I get this when I am trying to install windows xp. Can someone remind me how to remedy this !


Thanks in advance, Guaranteed its something stupid !

<P ID="edit"><FONT SIZE=-1><EM>Edited by MonteMan on 03/05/03 02:23 AM.</EM></FONT></P>

More about : driver irql equal

March 5, 2003 9:09:04 AM

any chance it's got something to do with RAID controller drivers?

<i>It's always the one thing you never suspected.</i>
Related resources
March 5, 2003 5:59:51 PM

In my experience,(i am not an expert by any means-especially when it comes to software) this error message seems to be a very generic one that could be any number of things.Can you give your full spec (incl. psu etc.) and whether you are overclocking?

no matter how hard you try, you can't polish a turd. :]
March 7, 2003 4:24:00 PM

I ran into this problem as well, tried many things without any success. I installed Win 98, RedHat Linux on same system without any problems. Finally I slowed my FSB to 100 mhz (was 133) and Windows XP installed. Set it back to 133 after install completed.
March 8, 2003 9:57:52 AM

When I had this problem it was relating to a dodgy ram chip. So it could be an actual chip fault or the ram clock is turned too high for stable use.
March 8, 2003 1:49:23 PM

As mentioned this Irql_not_less_or_equal is a generic error - actually a default error exit (and I am an expert or at least totally certifiable, haha, hoho, heehee).

Probably the best thing is to notice the second paragraph or group of information on the blue screen! (if it goes away and reboots too fast, change the error recovery options in control panel, system, advanced, startup and recovery options NOT to automaticly reboot).

In the first line of the second group of info will be an address and a module name! Somethin like...
at AE80EB00h in NV_AGP.sys (or)
at xxxxxxxxh in somethin.ocx...
There's always a "Module.Ext" name in every blue screen and that will point ya toward the related problem. Now it may be a hunt to find exactly "How' that module is related - but its a start - and that modname will relate to the problem - like NV_AGP.SYS is part of the Nvidia AGP driver
Take the module name and Google it for related info!
*** Overclocking produces some really wierd stuff and anything related the hardware abstraction layer will be unreliable - but at least points ya to the subsystem thats getting whacked - slow stuff down to stock for for debug, then go from there ***
Debug is an art in itself - Good Luck - but always get the modname of the dump!
March 8, 2003 9:12:30 PM

Whoa Comp Sci.Thanks for sharing the knowledge. I too have seen a few blue screens with the afformentioned NV_AGP.SYS. It drives me crazy but now I know how to slow it down and get the info. Thanks for that.

A7n8x dlx G Bios Agressive settings
xp1700 Paly W 2x 256 Crucial 2700@ cl 2.5
Ge Force2/WD 60gig w 8mb Cache @ 7200
March 8, 2003 10:31:41 PM

I used to get that, fixed it by buying a Nforce2 and pulled out the KT266A gigabyte board I previously used.

In fact, leaving VIA motherboards has fixed about every problem I used to blame incompetence on.

America- The Home of the Brave

Athlon 1700+, Epox 8RDA (NForce2), Maxtor Diamondmax Plus 9 80GB 8MB cache, 2x256mb Crucial PC2100 in Dual DDR, Geforce 3, Audigy, Z560s, MX500
!