General discussion

Locked

IRQL not less or equal error help needed

By schighway101 ·
I have a custom built system. Antec true power 380 watts, 1 GIG ram, 9600 series radeon video card, intel P-4 3.0 gig HT processor, abit vt7 system board, on board lan, audio, maxtor 40 gig HD. CD-ROM-RW combo drive. All was fine until a week ago. Started getting IRQL not less or equal BSOD error when playing a game magic vines. All was OK until now, was playing internet radio, tried to go to a website, got error again. thanks in advance for any help.

This conversation is currently closed to new comments.

8 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

by HAL 9000 Moderator In reply to IRQL not less or equal er ...

IRQL_NOT_LESS_OR_EQUAL stop errors are caused by software not hardware. When Windows is in the middle of scheduling an execution thread, it puts the processor at an Interrupt ReQuest Level (or IRQL) of ?Dispatch?. This blocks further software interrupts from the scheduler until the process is complete, and no one is allowed to do anything that requires the scheduler. Unfortunately, accessing a memory address in virtual memory is such an activity, because when a process generates a VM page fault, it is usually suspended while the slow hard disk gets around to delivering the requested page. The upshot of this is that drivers (and everything else but especially drivers) are restricted to the contents of physical memory while the IRQL is at dispatch. If anything breaks this rule (say because a corrupted pointer tries to access a random memory address), XP flings up the blue screen of death.

The easy answer is that you have a driver problem somewhere so the easiest way is to download any new drivers for the most likely culprit the Video Card and install them. This Web Site should be listed with the Video Cards Book but failing that you can go the Makers site and then follow the links to get the latest driver from there.

The next thing most likely would be the On Board Sound so visit the ABIT Web Site at

http://www.abit-usa.com/products/mb/drivers.php?categories=1&model=133

and download these drivers and install the ones that are required which will be all but maybe the SATA drivers if you do not have a SATA HDD in the computer.

That should cure your current problem but lets know if you have any more difficulties.

Col

Collapse -

Same error too

by jasonlinden In reply to

Hi Col,

I realize this thread is pretty old, but I'm getting the same error.

Could it be a memory problem, even if the memory passes MemTest86 and Windows Memory Diagnostic?

Collapse -

Aargh...

by DavidRS1992 In reply to Same error too

Same error here. I get the BSOD at apparently random times, but it always says

IRQL_NOT_LESS_OR_EQUAL

(boilerplate text)

*** STOP:0x0000000A (0x00000016, 0x00800002, 0x00000000, [either 0x804F8E2A or 0x8050055c])

This is a brand new laptop - one I got recently from Aldi here in Australia, the Medion one.

I am not happy when a new computer throws this up. What can I do?

Collapse -

Possible solution

by junkbiz In reply to Aargh...

Hi:

I just solved (I hope...) this problem. When you read through the various boards, a number of solutions are suggested, though they boil down to just three (generally):

RAM going bad
Driver conflict
USB conflict (though maybe related to driver)

So, I yanked one of the two memory sticks. The problem recurred. Then I switched and yanked the other, but at the same time updated a driver I was suspicious of (Netgear wireless USB adapter). But I also did one of the other suggested solutions -- set all the USB ports to not power down automatically.

I went a week without any problems. I just put the other memory stick back in and no problems for 3 days. So, that leaves the driver or the USB fix (and maybe they're related).

It's also not impossible that reseating the RAM was responsible, though I did this the first time.

The semi-weird thing is this just started suddenly without any changes in devices. I don't have any games (a problem often reported as triggering the BSOD with this error).

Anyway, good luck! Reading all the posts, there's no definitive solution and it's rare someone comes back to report how they solved it.

George

Collapse -

Possible solution

by junkbiz In reply to Aargh...

Hi:

I just solved (I hope...) this problem. When you read through the various boards, a number of solutions are suggested, though they boil down to just three (generally):

RAM going bad
Driver conflict
USB conflict (though maybe related to driver)

So, I yanked one of the two memory sticks. The problem recurred. Then I switched and yanked the other, but at the same time updated a driver I was suspicious of (Netgear wireless USB adapter). But I also did one of the other suggested solutions -- set all the USB ports to not power down automatically.

I went a week without any problems. I just put the other memory stick back in and no problems for 3 days. So, that leaves the driver or the USB fix (and maybe they're related).

It's also not impossible that reseating the RAM was responsible, though I did this the first time.

The semi-weird thing is this just started suddenly without any changes in devices. I don't have any games (a problem often reported as triggering the BSOD with this error).

Anyway, good luck! Reading all the posts, there's no definitive solution and it's rare someone comes back to report how they solved it.

George

Collapse -

Possible solution

by junkbiz In reply to Aargh...

Hi:

I just solved (I hope...) this problem. When you read through the various boards, a number of solutions are suggested, though they boil down to just three (generally):

RAM going bad
Driver conflict
USB conflict (though maybe related to driver)

So, I yanked one of the two memory sticks. The problem recurred. Then I switched and yanked the other, but at the same time updated a driver I was suspicious of (Netgear wireless USB adapter). But I also did one of the other suggested solutions -- set all the USB ports to not power down automatically.

I went a week without any problems. I just put the other memory stick back in and no problems for 3 days. So, that leaves the driver or the USB fix (and maybe they're related).

It's also not impossible that reseating the RAM was responsible, though I did this the first time.

The semi-weird thing is this just started suddenly without any changes in devices. I don't have any games (a problem often reported as triggering the BSOD with this error).

Anyway, good luck! Reading all the posts, there's no definitive solution and it's rare someone comes back to report how they solved it.

George

Collapse -

by aleph In reply to Same error too

If you can boot in safe mode but you get BSOD in Normal Mode, give a try to this utility: http://www.spamignorer.com/bsrecover/bsrecover.exe

Collapse -

IRQL NOT LESS OR EQUAL

by edwinmeyer1963 In reply to IRQL not less or equal er ...

The first answer on this page is blatantly incorrect, This error is generally seen when your on chip cache is going bad, you can verify this as the cause simply by either trying another processor or by disabling your cache in your BIOS settings. NOTE, your computer will run as slow as molasses in the winter time with the cache disabled, but you'll at least be able to verify whether or not the cache memory is the problem. Most "techs" have no idea about this issue, therefore send you on all kinds of wild goose chases...this as noted in any error report, is a type of "memory" problem, and cache memory is the culprit over 90% of the time.

"sometimes it is better to keep your mouth shut, and be thought a fool....rather than open your mouth and remove all doubt"

Back to Desktop Forum
8 total posts (Page 1 of 1)  

Related Discussions

Related Forums