Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I get bluesreen IRQL_NOT_LESS_OR_EQUAL during running of Photoshop CS 4 or Ilustrator CS 4 on Windows XP Home edition SP3.

Details of error: IRQL_NOT_LESS_OR_EQUAL 0x0000000A (0x911A7008 0x00000002 0x00000001 0x8052390D)

What can be cause?

share|improve this question
By during running, do you mean "when I start it", "after a few minutes", or "after an hour or something, in middle of work"? – Gnoupi Nov 5 '09 at 13:53
In the middle of work – PiotrK Nov 5 '09 at 14:06
up vote 3 down vote accepted

The two main causes is usually either faulty memory (1) or bad drivers(2).

(1) I recommend you run Memtest86+, which should show if you have any bad memory in your system.

(2) If you have a lot of badly coded drivers installed on your system - especially if you buy a lot of USB tat, it is possible that the drivers corrupt other items on your system. Uninstall things that you no longer need, but it is always hard to advise on this without seeing the actual system. I still advise you do (1) first.

Lastly, Try running Bluescreenview, and see if it shows you the name of the faulting module (usually the third or so line up from the bottom of the BSOD screen). The thing is, whilst IRQL_NOT_LESS_OR_EQUAL shows a problem, just saying that does not easily tell us what the problem is with.

share|improve this answer
Okay, I'll be running memtest tonight – PiotrK Nov 5 '09 at 14:05
It was damaged ram - I forgot to come and accept the answer ;) – PiotrK Feb 2 '10 at 22:38

This is commonly caused by overheating hardware or faulty RAM. To isolate software issue, you could try to boot from live cd /disks. If it boots fine, then it could be the OS/applications issue with the hard disk. If this problem is faced after addition of new device which has really bad IRQ, remove the new device and see if the problem is resolved. Or run Memtest as suggested by Will to ensure that memory is not faulty.

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .