IRQL_Not_Less_Or_Equal on Vista

[Meian]

Today, I have been receiving this error causing it to reboot. It occured when I was running Byond then did it again during AVG/Spybot and browsing the internet in general. I did Windows update on Vista (64 bit).

I was informed that Startup Repair would help fix this but the instructions said by windows and others does not work for me.

Did a system restore for days before and it still occurs.

Starting to think it is the memory as things are loading slower now.

[Cephius]

That usually means a driver conflict of some sort. Try using Driver Sweeper (google it) to wipe out your video card drivers, then reinstall it.

[Meian]

I downloaded it and it shows:
ATI - Display
Creative - Sound
Microsoft - Mouse
NVIDIA - Chipset
NVIDIA - Display
NVIDIA - PhysX
Realtek - Sound

I use an NVIDIA GeForce 8800 GTS. Would I just click all the NVIDIA boxes?

[Cephius]

Leave the chipset alone, but have it remove the PhysX and Display drivers.

[Kryssan]

I downloaded it and it shows:
ATI - Display
Creative - Sound
Microsoft - Mouse
NVIDIA - Chipset
NVIDIA - Display
NVIDIA - PhysX
Realtek - Sound

I use an NVIDIA GeForce 8800 GTS. Would I just click all the NVIDIA boxes?

Wait, you have nV card but ATI drivers installed? Or were those just the general options that DH has and you listed all of them?


While not as often, this can also be an example of a memory problem. Wouldn't hurt to do a scan just to see. I remember on a watercooling setup once I had a pinhole leak that was very slowly filling up the spaces between a heatspreader on a memory chip and it caused the IRQ errors. Took forever to figure that one out.


However, at least the way I'm reading your original post, you said this started occurring after a Windows update; check to make sure Windows didn't do you a 'favor' and update a driver for you.

[Meian]

Wait, you have nV card but ATI drivers installed? Or were those just the general options that DH has and you listed all of them?


While not as often, this can also be an example of a memory problem. Wouldn't hurt to do a scan just to see. I remember on a watercooling setup once I had a pinhole leak that was very slowly filling up the spaces between a heatspreader on a memory chip and it caused the IRQ errors. Took forever to figure that one out.


However, at least the way I'm reading your original post, you said this started occurring after a Windows update; check to make sure Windows didn't do you a 'favor' and update a driver for you.

It was the general options I assume I am not sure.

This occured after Spybot was updated and I was running Byond.

[Meian]

Removed the drivers and tested by running AVG. Same issue.

[Cephius]

Can you please extract the dump file and post it here, or take a picture of the blue screen and upload it so we can get a better idea of what's going on?

[Meian]

Sorry to ask but could you tell me how to make a dump? When it crashes it mentions making one at the bottom I believe but not sure where to locate it

[Cephius]

It should automatically be put in your windows directory in the minidump folder

[Meian]

Think I loaded it here properly

[Eticket]

This exact error was happening to my wife's laptop running Vista last year. In the end one of the memory modules was bad. They replaced it and it's been fine since.

[Haiko]

omg i have the same issue as well and best buy says it was a virus and tried to charge me $200 for it but they remove it without my consent so i got the service for free but i still got the same error a day later when i got my PC back...

[Kryssan]

This exact error was happening to my wife's laptop running Vista last year. In the end one of the memory modules was bad. They replaced it and it's been fine since.

Yeah, this issue occurs when a program tries to use a memory resource that is being used elsewhere or improperly calls for the use of a memory resource. The most common cause is driver conflicts. The second most common cause is your memory going bad, and a program/driver calling on a corrupted memory sector. Since replacing drivers is easier and doesn't cost money, its usually the first stop. Of course, you should also be able to do a memcheck at bootup with any standard utility and see a memory problem - I guess the only time it costs money is when you're replacing the bad modules.

[Cephius]

Yeah, try running memtest86. Let it do 2-3 passes and see if it returns any errors. If it does, you'll need to replace the chips.

[Tymon]

Yeah, try running memtest86. Let it do 2-3 passes and see if it returns any errors. If it does, you'll need to replace the chips.

Do this, but first, run CCleaner and do a registry/file clean

CCleaner - Home

It's not exactly the straight diagnosis for a memory problem, but a lot of times what has been diagnosed as a memory error to me was fixed by doing a registry clean from CCL

Clean out the drive with it too, it's really an awesome program.

Straightforward too, I shouldn't have to explain how to use it.

[Khamsin]

Speaking of which, what exactly is the IRQL supposed to be less than or equal to? And why is the fact that it's not so bad?

[Cephius]

Speaking of which, what exactly is the IRQL supposed to be less than or equal to? And why is the fact that it's not so bad?

This Stop error message usually occurs during installation when there was an attempt in kernel mode to touch pageable memory at too high a process internal request level (IRQL). Typically, this error occurs when a driver uses an incorrect memory address. Other possible causes of this error include an incompatible device driver, a general hardware problem, or incompatible software.

Pretty simple, really.

[Khamsin]

So what happens when a driver uses an incorrect memory address at an IRQL that does happen to be less than or equal (to the highest IRQL allowed for the driver at that address?)

[Meian]

I ran the Vista memory diagnostic tool and it found hardware problems with my memory. I have two sticks of memory 1 GB each to test with tomorrow to see if that helps until I can replace the damaged sticks (both under warranty so I assume it would be better to replace both to be safe)