Quote:
Originally Posted by Puddingbroodje
IRQL_NOT_LESS_OR_EQUAL
|
Can mean either (a) you have a hardware conflict because plug-n-play incorrectly allocated IRQ's to your hardware (or your hardware configuration is such that no workable IRQ configuration exists for it), or (b) one of your hardware drivers has a bug that causes it to make invalid calls on the wrong IRQ.
Solution:
First check for an IRQ conflict. Don't always trust Windows that there's no conflict on a shared IRQ -- your video card and sound card probably
can't share an IRQ, no matter what Windows thinks. If you find a dubious configuration, you'll have to uninstall and physically remove components and reshuffle the order you install in and what goes in which slot until plug-n-play comes up with a workable configuration.
Second, assuming no actual IRQ conflicts, then you need to find the buggy driver. Try updating all your drivers (maybe the problem is already fixed by an updated driver). If that doesn't help, you'll have to uninstall and remove things one at a time until you figure out which device is causing the problem. Then live without that device until a fixed driver is released.
(@Snogorat: It's
possible that bad RAM (probably on the video card) or overheating could just happen to be corrupting data destined to become an IRQ signal in a way that mimics this error, but it's unlikely, and would probably also cause other noticeable (and constant) problems if it were happening.)