DRIVER_IRQL_NOT_LESS_OR_EQUAL ???

[ChrisADuffy]

Anyone else get this with Win XP? I have been using XP since it came out and never got this before. Did a search tried some reccomendations but it still pops up everytime I run a Error check on my disk.

 

[43st]

That's a common message for an error in XP/2k. Next time write down the application or dll that caused the fault. That'll help us much more. Just read through the error message, it'll tell you.

 

[thorin]

Ya that's XPs "dunno what's going on but have to say something" message.

Run chkdsk from a command prompt?
Run a defrag?
Run chkntfs from the command prompt? (Assuming the disk is NTFS formatted)

Thorin

 

[Adrian Tung]

That's usually attributed to a device driver, which mean either it's a bad driver or a bad piece of hardware.


🙂atwl

 

[ChrisADuffy]

Just reinstalled Nvidia drivers 41.09's and that did the trick. Don't understand why though. I won't dwell on it either.

 

[43st]

Originally posted by: Adrian Tung
That's usually attributed to a device driver, which mean either it's a bad driver or a bad piece of hardware.


🙂atwl

Not always... I've seen the error caused by antivirus software also. Though yes I would agree that mostly all are driver problems.

 

[Miramonti]

Originally posted by: Thera

Originally posted by: Adrian Tung That's usually attributed to a device driver, which mean either it's a bad driver or a bad piece of hardware. 🙂atwl

Not always... I've seen the error caused by antivirus software also. Though yes I would agree that mostly all are driver problems.

Yep I've gotten that with symevent.exe too. It also can happen when the cpu overheats.

 

[thorin]

Originally posted by: jjsole

Originally posted by: Thera

Originally posted by: Adrian Tung That's usually attributed to a device driver, which mean either it's a bad driver or a bad piece of hardware. 🙂atwl

Not always... I've seen the error caused by antivirus software also. Though yes I would agree that mostly all are driver problems.

Yep I've gotten that with symevent.exe too. It also can happen when the cpu overheats.

Or when the RAM is bad. Or when the mobo is bad.

Thorin

 

[deerslayer]

I tried windows XP when it came out, and I got that message a lot.

I finally got tired of messing with it and installed windows 2000. I probably could have figured it out eventually, but I wanted stability right away.

 

[Lars]

I had these problems a lot with one of my two computers that use Win XP Pro.

I got different BSOD at least 10 times a day. I read somewhere that changing 'ACPI Controler' in System Device Manager/Computer to 'Standard PC' helps. I tried that and since then I never had those problems anymore (few months now).

 

[Ketteringo]

One of the kids in my hall at school had the same problem on a Dell. There was some M$ article in thier knowledge base and it said that the most common cause of this is bad RAM or bad drivers for modems/NICs. You might want to try swapping out any of those components and see if that fixes your problem!

 

[yhdd]

i tried to upgrade the drivers for my SB Audigy and i got this error...i had to do system restore to get the old drivers back...seems to happen alot with soundcards in my experience

 

[Crusty]

I had it happen with my Seismic Edge 5.1 sound card. Just started randomly doing it. The errors i got were with ntoskrnl.exe sysaudio.exe tbdsp.dll or something like that. I just took the card and, i'm currently waiting for my new mobo to arrive, so I can put a new rig together. I hope that fixes the problem...if not i might have to rma.

 

[Mavrick]

Got the same problem too. I had to reinstall win2k to get rid of the problem, because nothing I tried worked (tried to change "ACPI" to "standard PC", changed the mobo, changed the RAM, changed the video drivers...)