What do you make of 'IRQL_NOT_LESS_OR_EQUAL'?

Jaeger

I've searched about the web and everyone has a different opinion on it. Some say it's a hardware problem, cpu overheating, RAM incompatibilities, bad sectors on hard drive, not powerful enough PSU, others say it's a drivers issue for whatever hardware you've got.

Of all the people whose cases i looked at, the vast majority had AMD chips...


I'd like ye're opinion.


Trying to play Worms Armageddon (released circa 1998) on my pc

winXP pro SP2
amd 3500+
1gb ddr 400mhz ram
leadtek nVidia 256mb pci-e gfx card
the mb is an asus something-or-other.

The compatibility mode in XP makes NO difference whatsoever. I'll grab some more of my specs and post em up tomorrow, just dismantling everything again and bringing it all back to my room. (had no dialup modem in my pc, have various parts of both pcs all around me )

The BSOD of death hits me usually right at the end of a game or shortly after. Sometimes it happens in the in-game menus.

The funny thing is that these days, with all the patches, the game records every game played, and stores it in the game dir, and those work fine. No crashing whatsoever.

Vikings

IRQL_NOT_LESS_OR_EQUAL is not the important part of the BSOD, the important part is the file it mentions down near the bottom, I suffered from that particular BSOD about a year ago for a month or two, ended up being my sound card drivers. So from my experience it is driver related.

Sherifu

Defo drivers.
The hex numbers on bsod should narrow it down more.

Random

These problems plagued me for months, turned out to be faulty RAM although it kept blaming the graphics drivers.

Get a RAM checker and make sure it's not faulty.

astrofool

usually a ram, or ide(hard disk) problem.

jessy

yes i've found that its a driver issue aswell, open up you event viewer when you boot up and dbl click on the last critical error, and if its a known issue then you will be brought to the ms web and it will tell you what it is there.

Jaeger

astrofool wrote:

usually a ram, or ide(hard disk) problem.

The hard drive is a 250 sata drive. How can it be an ide problem?

jessy wrote:

yes i've found that its a driver issue aswell, open up you event viewer when you boot up and dbl click on the last critical error, and if its a known issue then you will be brought to the ms web and it will tell you what it is there.

Don't think I've ever used the event viewer, is that in system tools?


I've tried using just 1 stick of ram and tried each one, but still the same. Waiting to see if the DnR of all drivers has made any difference when I get back tonight

irishgeo

had that for a while last year and it was down to faulty ram

jessy

Jaeger wrote:

Don't think I've ever used the event viewer, is that in system tools?

Control Panel - preformance and Maintenance - Administrative Tools - Event Viewer - System

Sully

Iv got this issue to, but iv only noticed it since iv upgraded to WinXP. It cant be a driver issue, it only happens every now and again (a rare occurence) and I aint put any hardware in that in years!

Tech Info:
** Stop 0x000000 D1 COXFF9F391300000002 0x00000000, 0xF8241B4D
NDIS.SYS - Address F8241B4D base at F8225000. Dates to 4107ec3


Thats not exact, but near enough to it :P Also the ****ty PC's power button doesnt work, the restart button is now the power button so there aint a restart option on the case either :P lol.

- Sully