IRQL_NOT_LESS_OR_EQUAL - ntoskrnl.exe BSOD
 

Lately I've been getting these really annoying BSOD's, from either of the following:

- Closing UT2004
- Map change in UT2004
- Seconds into a game in UT2004, lock up, then blue screen
- Changing speaker modes in the Creative panel (2.1 to 5.1)

The STOP messages are usually:

BAD_POOL_HEADER (usually on UT2004 map changes)

and

IRQL_NOT_LESS_OR_EQUAL (this one also states ntoskrnl.exe, and I have been getting it the most).

As it seems to be partly the Creative speaker panel causing this I thought it was a sound driver issue, but I've tried the latest stable version and the OpenAL beta driver but they both cause the same thing.

Any ideas what this could be, it's annoying the hell out of me! :(

I'm running Windows 2000 Pro SP4, all up-to-date.

Thanks!

Re: IRQL_NOT_LESS_OR_EQUAL - ntoskrnl.exe BSOD
 

I would remove and update drivers (graphics, sound, even mouse sometimes) and check your memory for problems.

Re: IRQL_NOT_LESS_OR_EQUAL - ntoskrnl.exe BSOD
 

I've done the graphics and sound, so I'll have to test my memory with memtest tonight :(

Re: IRQL_NOT_LESS_OR_EQUAL - ntoskrnl.exe BSOD
 

http://aumha.org/win5/kbestop.php#0x0a
Are you overclocking at all?
Can we have the entire error message as well? It will help pinpoint the problem.

Re: IRQL_NOT_LESS_OR_EQUAL - ntoskrnl.exe BSOD
 

No overclocking, and if I get the STOP message again I'll write everything down.

Re: IRQL_NOT_LESS_OR_EQUAL - ntoskrnl.exe BSOD
 

This is going to sound really random, but do you have a wireless nic?

Re: IRQL_NOT_LESS_OR_EQUAL - ntoskrnl.exe BSOD
 

No wireless hardware or network, just wired.

Re: IRQL_NOT_LESS_OR_EQUAL - ntoskrnl.exe BSOD
 

The IRQ one is usually driver/service related AFAIK, ditto the POOL one.

Re: IRQL_NOT_LESS_OR_EQUAL - ntoskrnl.exe BSOD
 

I actually started to get the IRQL one when I installed the BETA driver, so I've sent an email back to Creative (they were asking if the beta driver had fixed it) stating I've been getting a new STOP message since upgrading the drivers.

Will have to see what they say now.

Re: IRQL_NOT_LESS_OR_EQUAL - ntoskrnl.exe BSOD
 

Well it's not my memory, ran memtest on it for a good hour, finished the whole of the tests with no errors.

Re: IRQL_NOT_LESS_OR_EQUAL - ntoskrnl.exe BSOD
 

Hit the nail on the head I think - BSOD after installing beta drivers to fix another BSOD. Might be worth looking for an older driver, if there is one. Otherwise Creative need to fix their driver fast.

It may help them if you set Windows to create a minidump every time it crashes - should help isolate the problem.

Re: IRQL_NOT_LESS_OR_EQUAL - ntoskrnl.exe BSOD
 

Minidump is already set, and I can't actually use an older driver as it supports less then this one does (doesn't have support for EAX 4, while this one does).

Re: IRQL_NOT_LESS_OR_EQUAL - ntoskrnl.exe BSOD
 

You may have to sacrifice something for stability, as I've said before sometimes the newest drivers aren't the best drivers.

Re: IRQL_NOT_LESS_OR_EQUAL - ntoskrnl.exe BSOD
 

I don't understand how it can be these drivers in a way, it didn't do this until a few weeks before I did a format and put 2000 Pro back on :(

Re: IRQL_NOT_LESS_OR_EQUAL - ntoskrnl.exe BSOD
 

So you were blue-screening before installing the drivers? Or were you already running these drivers but downloaded and installed them again in case there was something wrong with the initial installation?
We may be groping around in the dark until we get the full error message :( Is there nothing in Event viewer?

Re: IRQL_NOT_LESS_OR_EQUAL - ntoskrnl.exe BSOD
 

I had these drivers installed for a few weeks, but I never played UT2004 then (was MOH and COD). Only since starting to play UT2004 this has happened, so it must be a connection between UT2004 and something else.

I found a "Save dump" in the event viewer which looks like around the time I had the BSOD, which states the following:

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x00000001, 0x00000002, 0x00000001, 0x80410363). Microsoft Windows 2000 [v15.2195]. A dump was saved in: C:\WINNT\Minidump\Mini070505-01.dmp.

Would that be it?

Re: IRQL_NOT_LESS_OR_EQUAL - ntoskrnl.exe BSOD
 

Re: IRQL_NOT_LESS_OR_EQUAL - ntoskrnl.exe BSOD
 

Looks like I'm going to have to wait for Creative to email me back :(

Re: IRQL_NOT_LESS_OR_EQUAL - ntoskrnl.exe BSOD
 

Just for reference, ntoskrnl.exe is the Windows NT kernel.

Re: IRQL_NOT_LESS_OR_EQUAL - ntoskrnl.exe BSOD
 

Which brings us back to drivers!
It's possible that UT is using some feature of the sound card that the others aren't eg DirectSound?

Anyway - the answer probably lies with Creative :(

Re: IRQL_NOT_LESS_OR_EQUAL - ntoskrnl.exe BSOD
 

Is there no other error message in the event viewer? If not try running UT again to see if it causes another error and write it down in full :)

Re: IRQL_NOT_LESS_OR_EQUAL - ntoskrnl.exe BSOD
 

I'm going to "stress" test it now, using full hardware sound mode, and keep opening/closing the game to see if it happens. I'll try full hardware and EAX, then software mode. If it doesn't do it in software but does in hardware then it's the drivers.

I'll also write down everything on the blue screen when I get it.

And Richard, I can tell easily by the name it's the NT kernel :rolleyes:
__________________

Looks as if i've identified a problem with UT2004 and the Audigy 2 ZS drivers when having EAX enabled.

My results:

Software 3D Audio - No problems
Hardware 3D Audio W/Out EAX - No problems
Hardware 3D Audio W/ EAX -

W/ Creative OpenAL driver enabled

***STOP: 0x0000000A (0x00000001,0x00000002,0x00000001,0x80410363)
IRQL_NOT_LESS_OR_EQUAL
***Address 80410363 base at 80400000, DateStamp 427b58bb - ntoskrnl.exe

W/Out Creative OpenAL driver enabled (UT2004 uses it's own built-in one)

***STOP: 0x0000000A (0x00000005,0x00000002,0x00000000,0x80413C05)
IRQL_NOT_LESS_OR_EQUAL
***Address 80413C05 base at 80400000, DateStamp 427b58bb - ntoskrnl.exe

Right I'm going to unistall this driver now and install the driver on my CD, which supports upto EAX 3 and see if the same thing happens. If not, I'm emailing these findings to Creative.

Re: IRQL_NOT_LESS_OR_EQUAL - ntoskrnl.exe BSOD
 

Well I did mention sound drivers in post 2 lol ;) Hope it works with the generic drivers, try removing the old ones and then reboot to clear out any entries to them before installing the new one. Delete the directory folder for the drivers in question if it installs to its own folder.

Re: IRQL_NOT_LESS_OR_EQUAL - ntoskrnl.exe BSOD
 

Problem solved, it's Creative's latest driver :rolleyes:

UT2004 with full EAX support and using Creative's OpenAL driver there isn't a problem at all.

When Creative get back to me I'll have to tell them they have stuffed their latest driver for UT2004 users ;)

Re: IRQL_NOT_LESS_OR_EQUAL - ntoskrnl.exe BSOD
 

Wouldn't be the first time a brand new set of drivers have fouled up for a particular game. At least it's stable now until they put a revised set of drivers out.