Audigy 4: DLL Module Loader (DLLML.exe) problem at shutd

Question

Hello,
I would like to get feedback and/or confirmation on the problem I am describing below from Creative and owners of Audigy 4 Pros that are running the latest Audigy 4 Pro updates in Windows XP SP2 and an nForce 4-based system. I am convinced the problem is a driver issue. I am not sure, though, if this is similar to the known conflict between Creative's Remote Control service and nVidia's RAID service.
For Creative, I am willing to try and test a newer build of a DLLML.exe file if any are available.
Thanks in advance for your help on this.
---------- 8< cut here ----------
Summary: There seems to be a problem with version .0.3.0 of the DLL Module Loader (DLLML.exe) file that is installed by one of the 3 available web updates for the Audigy 4 Pro. In particular, after these updates are installed, the Windows XP SP2 system generates the following error on every "Turn Off" and "Restart": Application popup: Audio Driver Emulator: DLLML.exe - Application Error : The instruction at "0x0ac42f" referenced memory at "0x00000008". The memory could not be "read". Click on OK to terminate the program
The problem can be easily reproduced continuously.
Workaround: Replacing the file DLLML.exe version .0.3.0 with version .0.8.0 found in the Audigy 4 Pro CD seems to solve the problem. This file is installed in C:\Program Files\Creative\Shared Files\Module Loader. The DLLML.exe file seems to be loaded at Windows startup by a service (?) called "AudioDrvEmulator" which runs the line "C:\Program Files\Creative\Shared Files\Module Loader\DLLML.exe" - AudioDrvEmulator "C:\Program Files\Creative\Shared Files\Module Loader\Audio Emulator\AudDrvEm.dll". It li'ves in the registry under HKLM\Software\Microsoft\Windows\CurrentVersion\Run
Notes:
- As of today, the updates available at Creative's web site are:
* Creative Smart Recorder Patch for Creative Sound Blaster PCMCIA Audigy 2 ZS Notebook and Creative Sound Blaster Audigy 4 Pro audio cards version 2.0.56 (2 Dec 04)
* Creative Audigy 4 Pro update version 3.00.55 (20 Dec 04)
* Creative MediaSource 3 web update version 3.0.6 for PCMCIA Sound Blaster Audigy 2 ZS Notebook and Sound Blaster Audigy 4 (29 Dec 04)
- The updates were applied from the oldest to the newest, one at a time, rebooting after each update was installed.
- The system is a freshly installed Windows XP SP2 (slipstream) w/all the latest WindowsUpdate updates. Data Execution Prevention (DEP) has been disabled in the "boot.ini" file to work around a known issue with the latest nVidia network driver available for the nForce 4 chipset.
- The system runs on an Asus A8N-SLI Deluxe w/003 BIOS, AMD Athlon 64 3500+, Mushkin 2GB PC3200 DDR 222 Black L2 Hi Perf LII V2, and Asus EAX800XT/PE/2DHTV/256. The system runs a Stripe RAID setup with a pair of WD Raptor HDs.
- The system is run at stock speeds (i.e. no overclocking) and all the drivers are the latest version available from each manufacturer (none are BETA).
Additional notes: The stock Audigy 4 Pro drivers have a known conflict with the "nvraidservice.exe"-based service when the Creative Entertainment Center's remote control service is run. Having these 2 services running at the same time would cause the "nvraidservice" to fail at Windows startup, and a few DCOM-related errors to be logged in the event logs. This issue with the nVidia RAID service stopped after applying the Audigy 4 Pro updates and disabling the remote control altogether in the Creative Entertainment Center control panel.

Answer 1

Yes, using the DLLML.exe from the CD should work as it does in my setup. Do a search using the Windows search tool, and it should find two identical instances of the file in the CD, one of them in a CAB file. You should be able to copy & paste either instance to your C: dri've's location as long as the DLLML.exe file is not already loaded/running in memory.
I had sent Creative's support an e-mail with exactly the same information, but unfortunately the first response I got from them was to do a cleansweep and install of the Creative software. I say "unfortunately" because Creative did not describe what are we trying to accomplish by "tainting" a fresh format/XP SP2 install with a massi've uninstall & reinstall of Creative software, even when I hoped narrowing the issue down to what seems to be a trivial EXE would have triggered some ideas as to what might be wrong with that particular version of the EXE file (i.e. it seems to be, after all, a DDL file loader, which does not seem to be driver engine code per se, but instead a DLL memory loader).
As I mentioned to them, this system simply has a fresh XP install, all OS updates, all peripheral drivers, and the Creative card and software was the last thing installed in the box. No tweaks other than DEP turned OFF, no overclocking, no extraneous services running in the background, not even any additional software. Installation of the software was done by the letter, with proper reboots.
I would appreciate if someone has an idea of what may be accomplished by a re-install of Creative software on a fresh OS install when the problem is squarely on the DLLML.exe file. You can be as specific as pinpointing DLL or registry entries that such a re-install is suppossed to fix (i.e. I am using the wrong files; a registry entry has the wrong value, etc.), and how this would have happened when following the installation steps as documented.
Thanks in advance.