IRQL_NOT_LESS_OR_EQUAL - ntoskrnl.exe BSOD

Originally Posted by Paul

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?

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?

[Paul K]

http://support.microsoft.com/default...;en-us;Q314063

Originally Posted by Paul

http://support.microsoft.com/default...;en-us;Q314063

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

[Richard M]

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

[Aragorn]

Which brings us back to drivers!

If you receive the Stop 0x0A error after Windows XP is already installed, use the following troubleshooting methods to verify other components. Examine third-party software or drivers

If you have installed any third-party software or drivers, try removing them or disabling them so that they do not load, and then restart the computer to see whether that software or driver is causing the error. If that software or driver is causing the error, report the problem to the vendor of the software or driver.

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

[Paul K]

Originally Posted by Electrolyte

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?

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

Originally Posted by Paul

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

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
__________________

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.

[Paul K]

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.

Problem solved, it's Creative's latest driver

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

[Paul K]

Originally Posted by Electrolyte

Problem solved, it's Creative's latest driver

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

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.