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!

[Paul K]

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

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

[Paul K]

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.

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

[jtwn]

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

Originally Posted by jtwn

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

No wireless hardware or network, just wired.

[greencreeper]

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

Originally Posted by greencreeper

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

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.

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

[Aragorn]

Originally Posted by Electrolyte

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.

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.

Originally Posted by Aragorn

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.

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).

[Paul K]

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

Originally Posted by Paul

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

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

[Paul K]

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?