|
Page 1 of 1 |
Xemaniac
Posts: 11
Location: Wherever u want me 2 b!
|
Posted: Thu, 18th May 2006 10:16 Post subject: driver irq not less or equal |
|
 |
How can i find where the problem lies when I get this blue screen? It is SO frustraiting that sometimes windows just closes and I get this message in a blue screen.
Does anyone have the same problem, or does anyone know how I can find what causes it or how to fix it!
Thanx in advance.
/Xem
"Only two things are infinite; the universe and human stupidity.....and I'm not sure about the former." - Einstein
|
|
Back to top |
|
 |
|
Posted: Thu, 18th May 2006 12:17 Post subject: |
|
 |
put some more info CPU, sound, video card etc...
|
|
Back to top |
|
 |
Xemaniac
Posts: 11
Location: Wherever u want me 2 b!
|
Posted: Thu, 18th May 2006 14:56 Post subject: |
|
 |
P4 2.8, Radeon 9800pro, sound integrated in Asus P4 800Deluxe motherboeard.
2 x 3com Lan cards, one gigabite(integrated) and one normal!
"Only two things are infinite; the universe and human stupidity.....and I'm not sure about the former." - Einstein
|
|
Back to top |
|
 |
|
Posted: Thu, 18th May 2006 16:14 Post subject: |
|
 |
i found description of the problem:
Quote: |
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.
|
try to update all drivers (motherboard,video.... etc.)
see if it will help
btw maybe memory problem
|
|
Back to top |
|
 |
|
Posted: Thu, 18th May 2006 16:28 Post subject: |
|
 |
Got this problem since months, no solution.
i updated bios, driver, even reinstalled windows and checked the hardware.
if you guys find any solutions let me know.
|
|
Back to top |
|
 |
|
|
Back to top |
|
 |
|
Posted: Sat, 20th May 2006 12:04 Post subject: |
|
 |
driver irq less or equal used to be a really common problem caused by shared IRQ's which I think may have died down because of ACPI
if you right click My Computer > Properties > Hardware > Device Manager > View Resources by Connection then look at the IRQ list and see if anything is sharing an IRQ if so that'll be the likely culprit
to stop sharing IRQ's you will most likely have to find out what slots on your motherboard are sharing an IRQ, eg, slot 2 could share an IRQ with the IDE chipset, and try to use different slots accordingly. Slots 4 & 5 are usually the best to go for
then of course to free up some IRQ's you can disable any unused com (serial) ports in BIOS, as well as the parallel port
updating drivers may often help as it can solve imcompatabilities, however it's best to have your cards in an unshared slot and to disable unused ports anyway
|
|
Back to top |
|
 |
Page 1 of 1 |
All times are GMT + 1 Hour |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
Powered by phpBB 2.0.8 © 2001, 2002 phpBB Group
|
|
 |
|