IRQ_NOT_LESS_OR_EQUAL
- Thread starter Sharp67
- Start date
- Joined
- Oct 29, 2007
- Messages
- 2,341
Go to C:\Windows\Minidump and zip up the *.dmp files in there. Assuming you haven't played with the pagefile or crash recovery settings, there should be one for every BSOD. If you've got a whole bunch, just zip up the latest 5. Email them to [email protected] and I'll take a look.
Otherwise, IRQ_NOT_LESS_OR_EQUAL is a very general error most often related to a driver conflict, but without the dump files or more specific error parameters I can't give you more.
Otherwise, IRQ_NOT_LESS_OR_EQUAL is a very general error most often related to a driver conflict, but without the dump files or more specific error parameters I can't give you more.
- Joined
- Feb 18, 2008
- Messages
- 1,771
I just solved that problem on my machine. I found it was a problem with the RAM slots on my mobo. I'm sure you can guess the only solution there.
- Joined
- Feb 18, 2008
- Messages
- 77
Isn't the error actually "IRQL_NOT_LESS_OR_EQUAL"?
Anyways, this is from the Microsoft support page:
Bold not original, added for emphasis.
It seems like you need to get some new drivers Sharp!
Anyways, this is from the Microsoft support page:
Bold not original, added for emphasis.
It seems like you need to get some new drivers Sharp!
- Joined
- Feb 18, 2008
- Messages
- 1,771
I wasn't trying to make an assumption, so my apologies if it came off that way. I was just stating that for me, that error didn't indicate a driver problem, but a hardware problem. I had 3 of my 4 RAM slots that weren't functioning properly, and would end up writing bad memory to the RAM. My only solution was to replace my motherboard.
I'm not saying that this is Sharp's problem. However, I do believe that the more information you have, the better off you are.
I'm not saying that this is Sharp's problem. However, I do believe that the more information you have, the better off you are.
- Joined
- Oct 29, 2007
- Messages
- 2,341
I'm still waiting on dump files from him, if he's had multiple crashes a pattern should be pretty obvious. I've fixed this error with everything from uninstalling a single program to having to replace the RAM and everything inbetween. It's the most common blue screen other than everyone's beloved page pool header.
I've seen three causes of this in my time, personally, though I know there's many more--as Lafin said, it's one of the most common errors.
1. Bad/incompatible/corrupted/out-of-date drivers.
To fix this, be sure to update drivers for EVERY component in your computer that you can, especially the video card, any other PCI card (network adapter, sound card, etc.), hard drive, and motherboard chipset. Don't just use Windows Update or the "update drivers" option. You have to go to the manufacturer's site for each component and find the newest version of each driver.
2. Device IRQ/memory conflict.
To check for this, go to Start>Programs>Accessories>System Tools>System Information. Expand "Hardware Resources." Click "Conflicts/Sharing." Look for any listing of your video card on the right side, and check the device it's sharing with (which will be listed immediately above or below it). If the device is anything other than "PCI Bus" or some variation of "PCI-Express Root Port," pay attention to that. This doesn't always indicate a problem, some devices work just fine sharing an IRQ with another. However, if you're having this problem, physically moving the conflicting device to another PCI slot will often fix it. If you can't physically move it (not enough slots, part requires a specific kind of slot, etc.) then you'll have to manually edit the IRQ Windows uses for that part, which can be tricky or impossible depending on your computer's individual voodoo. I'll give you details on that if you run into it.
3. Heat.
Make sure the environment inside your case is cool, and try checking the motherboard, northbridge (and/or southbridge) temperatures if you can. You should be able to check from bios, or download any of various motherboard monitor programs (depending on motherboard manufacturer). Heat can cause all kinds of crazy errors, and I've seen this one from it fairly commonly. Sometimes just unclogging (or removing) a fan filter or blowing dust out of your computer will fix this.
Still, be sure to get your dump files and throw them at Lafinass. He'll probably be able to pinpoint the issue a lot quicker than you could through trial and error or trying all these steps, though you may wish to give my suggestions a shot while you wait for Lafinass's response. He'll also be able to tell you if it's a purely software-side issue, which is a lot harder to diagnose through trial and error.
1. Bad/incompatible/corrupted/out-of-date drivers.
To fix this, be sure to update drivers for EVERY component in your computer that you can, especially the video card, any other PCI card (network adapter, sound card, etc.), hard drive, and motherboard chipset. Don't just use Windows Update or the "update drivers" option. You have to go to the manufacturer's site for each component and find the newest version of each driver.
2. Device IRQ/memory conflict.
To check for this, go to Start>Programs>Accessories>System Tools>System Information. Expand "Hardware Resources." Click "Conflicts/Sharing." Look for any listing of your video card on the right side, and check the device it's sharing with (which will be listed immediately above or below it). If the device is anything other than "PCI Bus" or some variation of "PCI-Express Root Port," pay attention to that. This doesn't always indicate a problem, some devices work just fine sharing an IRQ with another. However, if you're having this problem, physically moving the conflicting device to another PCI slot will often fix it. If you can't physically move it (not enough slots, part requires a specific kind of slot, etc.) then you'll have to manually edit the IRQ Windows uses for that part, which can be tricky or impossible depending on your computer's individual voodoo. I'll give you details on that if you run into it.
3. Heat.
Make sure the environment inside your case is cool, and try checking the motherboard, northbridge (and/or southbridge) temperatures if you can. You should be able to check from bios, or download any of various motherboard monitor programs (depending on motherboard manufacturer). Heat can cause all kinds of crazy errors, and I've seen this one from it fairly commonly. Sometimes just unclogging (or removing) a fan filter or blowing dust out of your computer will fix this.
Still, be sure to get your dump files and throw them at Lafinass. He'll probably be able to pinpoint the issue a lot quicker than you could through trial and error or trying all these steps, though you may wish to give my suggestions a shot while you wait for Lafinass's response. He'll also be able to tell you if it's a purely software-side issue, which is a lot harder to diagnose through trial and error.
- Joined
- Feb 18, 2008
- Messages
- 77
Oh, ya, I'd like to add that I have gotten this blue screen from even out of date mouse drivers...
- Joined
- Oct 29, 2007
- Messages
- 2,341
Aye, the website generates the link and quite cleverly breaks up the actual address in the link- it's good to stop the bot trolls. It's: lafinass at gmail dot com
Also, if you right-click on the email link and select properties you will see in the address field...
javascript:window.location="mai"+"lto:"+"lafinass"+"@"+"gmail.com";self.close();
Also, if you right-click on the email link and select properties you will see in the address field...
javascript:window.location="mai"+"lto:"+"lafinass"+"@"+"gmail.com";self.close();
- Joined
- Oct 29, 2007
- Messages
- 2,341
Alright, you sent me 5 dump files, so I'll break it down by instance first.
Dump 1 & 5
Both of these are DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) caused by cmaudio.sys, an audio driver for C-Media.
Dump 2
This dump file was corrupt and could not be processed. It happens sometimes.
Dump 3
This is another DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) caused by portcls.sys, which is a generic sound driver from Microsoft.
Dump 4
This is a PAGE_FAULT_IN_NONPAGED_AREA (50) caused by ati2cqag.dll while you were playing Oblivion. I am inclined to believe that this is an anomaly that has no bearing on the other bluescreens. If it occurs again, update your ATI drivers and look for any patches for Oblivion.
Alright, so you have 3 IRQL errors caused by two different audio drivers. I'd wager solid money your problem is directly related to your audio setup. Do you have onboard audio or do you have a sound card? If you DO have a sound card, are you certain that the onboard audio is disabled in BIOS? If you have onboard audio or you have a sound card with the onboard properly disabled, update the drivers. If it still occurs, yank out the audio card and see if it still occurs when you're playing without it. If you have onboard, I highly suggest getting a sound card- onboard audio is usually done half-assed and is prone to low quality and failure. It also, in many boards, is in fact a software audio solution and eats up far more processor cycles than it should.
Dump 1 & 5
Both of these are DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) caused by cmaudio.sys, an audio driver for C-Media.
Dump 2
This dump file was corrupt and could not be processed. It happens sometimes.
Dump 3
This is another DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) caused by portcls.sys, which is a generic sound driver from Microsoft.
Dump 4
This is a PAGE_FAULT_IN_NONPAGED_AREA (50) caused by ati2cqag.dll while you were playing Oblivion. I am inclined to believe that this is an anomaly that has no bearing on the other bluescreens. If it occurs again, update your ATI drivers and look for any patches for Oblivion.
Alright, so you have 3 IRQL errors caused by two different audio drivers. I'd wager solid money your problem is directly related to your audio setup. Do you have onboard audio or do you have a sound card? If you DO have a sound card, are you certain that the onboard audio is disabled in BIOS? If you have onboard audio or you have a sound card with the onboard properly disabled, update the drivers. If it still occurs, yank out the audio card and see if it still occurs when you're playing without it. If you have onboard, I highly suggest getting a sound card- onboard audio is usually done half-assed and is prone to low quality and failure. It also, in many boards, is in fact a software audio solution and eats up far more processor cycles than it should.
- Joined
- Mar 27, 2008
- Messages
- 160
Links to some guides I wrote up a while back...
Random Reboot / BSOD Guide
Dump Debug Guide
I know you figured it out, but just for reference..
Random Reboot / BSOD Guide
Dump Debug Guide
I know you figured it out, but just for reference..
well i have a sound card but idk how to check for driver updates because it is so old...it is a mad dog and that is basically all i can tell you ...i have two sound things running...sound media mixer and sound max...whether or not this has anything to do with it idk...sometimes the BSOD pops up while i am booting my comp...other times it doesnt come on at all...
- Joined
- Mar 27, 2008
- Messages
- 160
Old sound card (or chipset) drivers tend to cause nasty problems...
If you don't know which MadDog card you have, just look at the ports...
http://www.mdmm.com/sound_card_drivers.php
If you don't know which MadDog card you have, just look at the ports...
http://www.mdmm.com/sound_card_drivers.php
idk if this has anything to do with anything either but sometimes it will just randomly just shut down and not even show the BSOD...it was randomly restarting itself before without the BSOD now it all of a sudden shows the BSOD...hope this helps something...ty all who have posted btw you dont know how many times i have posted in a forum and they didnt tell me anything
- Joined
- Oct 29, 2007
- Messages
- 2,341
Well, from your dxdiag I see no sign of a Mad Dog audio device at all. You have C-Media Wave Device (cmaudio.sys), which is your default audio device. And SoundMAX Digital Audio (smwmd.sys), which is most likely your built in audio. It isn't set as your default, but I highly recommend going into BIOS at the start and disabling the onboard audio if you have a sound card. Consult your motherboard's manual on this.
Also, do me a favor and right click on 'My Computer' and select 'Properties'. On the 'Hardware' tab, select 'Device Manager' and tell me what, if any, devices hare a yellow exclamation point next to them.
Also, do me a favor and right click on 'My Computer' and select 'Properties'. On the 'Hardware' tab, select 'Device Manager' and tell me what, if any, devices hare a yellow exclamation point next to them.
