Page 1 of 2
EAX and UT2004 VS BSOD (ctaud2k.sys)
Posted: Sun 14 Aug , 2011 7:10 pm
by Nardaq_NL
I wanna give this issue another try after a year and wondering you have anny BSOD while using audio in "HW 3D +EAX" mode
(atm "system driver" enabled) and what drivers/patches you're using
I can play UT2004 in HW 3D EAX, but keeping random BSODing from 15m to 3 hours
Before I'm going to messing up my client I'd like to know your solution, or idea's
UT2004 3369 + EAX patch (don't recall witch one)
Soundblaster X-fi titanium
XP pro 64
Re: EAX and UT2004 VS BSOD (ctaud2k.sys)
Posted: Sun 14 Aug , 2011 10:38 pm
by Azarael
No known fix for this bug except dropping back to XP 32. Problem caused by lack of DirectSound acceleration in Vista or higher or something.
Re: EAX and UT2004 VS BSOD (ctaud2k.sys)
Posted: Mon 14 Nov , 2011 3:23 am
by Enzyme
had that issue for a while, turns out it was one of the driver releases, one that was soon replaced, it may be that it has left remnants, try using the safe mode\driver sweeper routine to clear it out followed up by a good scan through your registry to make sure.
i have to do the same atm after trying the pax drivers again after many years (last time was with my audigy2) and seeing he still cant build installers well, some registry settings or files refuse to be removed and although the latest drivers install i now get a whole load of bugs with the various creative software.
(running win7 64x with a x-fi titanium pro atm, original problem occurred on vista 64x with the same card)
and be sure to properly patch the ut directory with the latest OpenAL32 files.
Re: EAX and UT2004 VS BSOD (ctaud2k.sys)
Posted: Mon 14 Nov , 2011 12:11 pm
by giZmo
I got no problems with the latest (or older) PAX-Drivers
Win7 64bit
X-Fi Music
HW 3D EAX
3369 no further patch
No BSOD, CMSS-3D working fine and no sound bugs.
Latest drivers
Re: EAX and UT2004 VS BSOD (ctaud2k.sys)
Posted: Mon 14 Nov , 2011 7:58 pm
by Nardaq_NL
tnx,
I've figured the PAX drivers for XP 64 are a piece of shit (or my OS is

)
no uninstaller @ pax driver
and now im trying for 3 hours to get nu sound back, the default creative installer is saying now there is a newer version installed. yay fail driver sweeper and many other apps. the F**K
All HAIL the windows live update driver
finally.....ill try again whenEVER ill swap to windows 7
Re: EAX and UT2004 VS BSOD (ctaud2k.sys)
Posted: Mon 14 Nov , 2011 8:08 pm
by giZmo
Sorry
You removed the old driver before installation or did you overwrite them ?
Important :
Before installing, remove all traces of any previous x-fi drivers and all x-fi driver by removing the driver within "Device Manager".
Re: EAX and UT2004 VS BSOD (ctaud2k.sys)
Posted: Mon 14 Nov , 2011 8:15 pm
by Nardaq_NL
jup, and stupid enough i didn't make a restore point (and auto restore point disabled)
oh well, all working again

w/out EAX ofc.
Re: EAX and UT2004 VS BSOD (ctaud2k.sys)
Posted: Mon 14 Nov , 2011 8:18 pm
by giZmo
You know that if you enable system driver UT is using it´s own OpenAL driver ? You´ll have to rename the defOpenAL32.dll (UT2004/system) to defOpenAL32.old then
start UT2004 (no sound atm). Uncheck system driver and restart UT. Switch system driver back on and from now on UT should use the driver that came with
the soundcard.
Re: EAX and UT2004 VS BSOD (ctaud2k.sys)
Posted: Mon 14 Nov , 2011 8:51 pm
by Nardaq_NL
nop, not working, still no sound
even if i try to move the openAL.dll (and rename) manually from windows map
Re: EAX and UT2004 VS BSOD (ctaud2k.sys)
Posted: Mon 14 Nov , 2011 11:27 pm
by giZmo
openAL.dll or openAL32.dll ? Afaik you need the openAL32.dll in your windows/system32 directory !
I found an old post which discussed the problem with the system driver:
http://forums.epicgames.com/threads/363 ... ER-setting