dane m 0 Posted August 20, 2001 When ever i turn on my computer i get an error screen saying "Driver_IRQL_Not_Less_Or_Equal" Does anyone know how i can fix it, or why it's doing that? I'm using WIndows 2000. Share this post Link to post
Brian Frank 0 Posted August 20, 2001 I don't want to sound mean, but that honestly doesn't tell us much. Does the BSOD list any file, such as a .sys or .dll? And please list your system specs. Give as much info as you can, we're not mind readers. And when does the BSOD occur? Give more info, and I'm sure we can fix this up. Share this post Link to post
dane m 0 Posted August 20, 2001 sorry about that. i didn't want to give too much information and make you guys think that i think you're stupid or something... I'm running Windows 2000 in FAT32. 450Mhz 128mb RAM. It doesn't mention any .sys or .dll files it occurs when ever i restart my computer. i will see my desktop for a few seconds then i get the error screen saying "Driver_IRQL_Not_Less_Or_Equal" I also get another error screen whenever i turn off my computer. it says "Driver_state_power_failure." If this isn't enough information let me know. Thanks. Share this post Link to post
Brian Frank 0 Posted August 20, 2001 Which cpu do you have running at 450MHz? What is your power supply wattage? How long has this been going on? Can you put in some different RAM? What cards do you have in? Video: Sound: Modem: Ethernet: Other: Share this post Link to post
cablehog 0 Posted August 28, 2001 By chance, does your MB require a UDMA controller driver? I saw this error message just tonight, and it was a driver issue with the UDMA controller. That is where I would look first. Share this post Link to post
FatFish 0 Posted September 2, 2001 Quote: it occurs when ever i restart my computer. i will see my desktop for a few seconds then i get the error screen saying "Driver_IRQL_Not_Less_Or_Equal" I have seen the error message when i enable the memoy hole at some address in the bios setting. After i have disable it, the error message is gone. so... see if you have that setting enabled in BIOS, and disable it. Share this post Link to post
Flak 0 Posted December 19, 2001 I find i get that problem if I overlock my machine too far Share this post Link to post
Spuddeh 0 Posted December 27, 2001 i find i get that exact error if i use certain nvidia drivers (pre 11.xx) can you fill us in on your driver versions at all? Share this post Link to post