IRQL_NOT_LESS_OR_EQUAL

Is the rig overclocked? Does it pass memtest? Is it undervolting the CPU or memory? Is it overheating?

There are loads of different things that could cause such a BSOD.
 
I've been getting this BSOD for the last 2 years, and have only just solved the problem....1 faulty RAM module (out of two). I had to run memtest for an hour to get the error to show though.

This is most likely to be either a RAM problem or a driver issue; I'd put my bet on the RAM. Can we have some more info about your rig?
 
no its not
its a driver error
Click to expand...

directly it is yes. but the likelyhood is the driver is fine, and is simply addressing nasty memory.

EDIT: G|mp, just to add to that, you'll know whether it's a specific driver/device or something more general (ie. memory) that's causing the problem by which files are indicated to have supposedly caused the BSOD.

For example, when I was mistakenly undervolting my vid card, I kept getting BSODs pointing to nvdisp.dll --> graphics card driver. Every single one pointed to this file, (some of which were IRQL_NOT_LESS_OR_EQUAL BSODs). However, when my RAM packed in recently, I was getting BSODs pointing to all sorts of things...usbport.sys, nv[something[.dll, etc. This suggested that there was something more widespread than specific device incompatibilities causing the BSODs. Nevertheless, these things have a habit of breaking trends sometimes...
 
Last edited:
on one or two systems, a full format has made this problem disappear (probably due to drivers in the cases i had)

run the memtests (on each ram stick -only use one at a time) from the ultimate boot cd, can often be bad ram as said above
 
You must log in or register to reply here.
Back
Top Bottom