Failed to initialize DirectSound

MDM1982 · Oct 23, 2009, 02:51 PM

Hi,

Just installed the latest 3500 beta driver after a reboot and after Windows starts I get an error message that says - KX Mixer - Error initializing DirectSound (screenshot can be seen below) it only does this once so was wondering if it was normal or not?.

http://i35.tinypic.com/iolypx.jpg

Also have an error when running DxDiag which can also be seen here, is this also normal to see?:

http://i37.tinypic.com/15nkny9.jpg

I have installed the latest DirectX August 2009 redistributable on and still get this message. I have this problem with both the x86 and x64 drivers on two seperate systems with Windows XP Pro with SP3 slipstream (Athlon64 and 2GB RAM) and Windows XP Pro x64 Edition (Core 2 Quad and 4GB RAM) using an Audigy 2 and an Audigy 2 ZS.

I also have a problem where the on-screen volume bar and mute button graphics aren't visible (On Screen Display setting enabled is checked) for some reason now after a re-install, this was working before the re-install and I also don't remember getting the DirectSound initialization error before either.

Thanks for any replies.

Russ · Oct 23, 2009, 11:27 PM

It is not normal to see those errors.

I can only guess that something is wrong with DirectX on your system(s).

Maybe try to force a full reinstall of DirectX 9.0c.

i.e.
You could try the following:

Quote:

“Normally the DirectX installer will refuse to install if it detects that you already have the latest version of DirectX installed. This makes it a pain in the ass to fix a broken DirectX installation. Luckily, there is a small workaround to trick the DirectX installer into a full re-installation.

Run the Registry Editor: Start -> Run -> regedit

Navigate to this key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DirectX

Change the value of version from ‘4.09.00.0904′ to ‘4.08.00.0904′.

Now run the DirectX installer.”

...or you could try one of the applications shown here:
How to Uninstall DirectX and Reinstall to Repair DirectX Raymond.CC Blog

MDM1982 · Oct 26, 2009, 04:55 PM

Thanks for replying Russ.

I re-installed the OS and even tried re-installing with an XP SP2 slipstream instead but still got the same error messages. I found that using the 3539 or 3541 drivers the errors have gone both on startup and in DxDiag.

I've also noticed that with all the KX drivers I will get a slight pause when entering folders in Explorer this does not happen with the Creative drivers any ideas what might cause this?.

Russ · Oct 26, 2009, 05:57 PM

Hmm, that is strange... I am using WinXP SP2 and have no such errors.

As for the pause, are you sure it is not your anti-virus software causing it? I remember having that problem some time ago when I was using AVG (it is one of the reasons that I stopped using AVG)... it would take forever to open a folder that had a lot of files in it.

MDM1982 · Oct 26, 2009, 06:24 PM

I don't suppose it could be because I'm using headphones would it, really not sure what else could cause this?

I didn't have any anti-virus or firewall software on at the time, I usually use AntiVir (have stayed away from AVG since 8.5+ got so bloated) and Comodo for the firewall.

Russ · Oct 26, 2009, 06:34 PM

I cannot think of any reasons why using headphones should make any difference...

MDM1982 · Oct 26, 2009, 07:10 PM

Is there a way to show a log or something after the drivers have installed to see if there are any problems?.

Russ · Oct 26, 2009, 07:22 PM

Not that I know of...
But there is the Event Viewer in Windows, and you can use a program like DebugView to view debug info from kX (and other programs) while it is running (i.e. DebugView will shows some status messages or errors from kX).

MDM1982 · Oct 26, 2009, 08:42 PM

Thanks Russ. Will give DebugView a go then and see.

Nothing really out of the ordinary in Event Viewer except in System >

disk > The system failed to flush data to the transaction log. Corruption may occur.

and a few WinMgmt warnings in Application, I think these are normal though due to the service pack being slipstreamed:

A provider, Rsop Planning Mode Provider, has been registered in the WMI namespace, root\RSOP, but did not specify the HostingModel property.

A provider, Rsop Planning Mode Provider, has been registered in the WMI namespace, root\RSOP, but did not specify the HostingModel property.

A provider, Rsop Planning Mode Provider, has been registered in the WMI namespace, root\RSOP, but did not specify the HostingModel property.

A provider, Rsop Planning Mode Provider, has been registered in the WMI namespace, root\RSOP, but did not specify the HostingModel property.

A provider, CmdTriggerConsumer, has been registered in the WMI namespace, Root\cimv2, to use the LocalSystem account.

A provider, CmdTriggerConsumer, has been registered in the WMI namespace, Root\cimv2, to use the LocalSystem account.

A provider, HiPerfCooker_v1, has been registered in the WMI namespace, Root\WMI, to use the LocalSystem account.

SamatiX · Jan 10, 2010, 03:04 PM

Quote:

Originally Posted by MDM1982

Error initializing DirectSound

I have a same problem... How to solve it?

coolies · Jan 16, 2011, 04:36 AM

I also have this problem with only 3550 Windows XP. I thought it was because I was falling behind in the DirectX or Windows version. I am using 3549

SamatiX · Jan 16, 2011, 10:06 AM

Quote:

Originally Posted by coolies

I also have this problem with only 3550 Windows XP. I thought it was because I was falling behind in the DirectX or Windows version. I am using 3549

After hardware upgrade (Changed MB and now have 4GB RAM, WinXP x86) version 3549 giving same error as in 3550.
Using 3548 now, it's ok, without this problem.

Tyrsonswood · Jan 16, 2011, 12:49 PM

Most XP users are probably best using 3545 as the later versions were produced mostly for 64 bit/greater than 2 gig systems and Win7 support, that's where the majority of the changes were. An XP x86 system with 4 gig (about 3 gig usable because of 32 bit limitations, should use the 3548 as mentioned) Using later versions can be done, but some problems and instability has been noted here on the forum.

Oct 23, 2009, 02:51 PM	#1
MDM1982 DriverHeaven Newbie Join Date: Oct 2009 Posts: 5 Rep Power: 0	Error initializing DirectSound Hi, Just installed the latest 3500 beta driver after a reboot and after Windows starts I get an error message that says - KX Mixer - Error initializing DirectSound (screenshot can be seen below) it only does this once so was wondering if it was normal or not?. http://i35.tinypic.com/iolypx.jpg Also have an error when running DxDiag which can also be seen here, is this also normal to see?: http://i37.tinypic.com/15nkny9.jpg I have installed the latest DirectX August 2009 redistributable on and still get this message. I have this problem with both the x86 and x64 drivers on two seperate systems with Windows XP Pro with SP3 slipstream (Athlon64 and 2GB RAM) and Windows XP Pro x64 Edition (Core 2 Quad and 4GB RAM) using an Audigy 2 and an Audigy 2 ZS. I also have a problem where the on-screen volume bar and mute button graphics aren't visible (On Screen Display setting enabled is checked) for some reason now after a re-install, this was working before the re-install and I also don't remember getting the DirectSound initialization error before either. Thanks for any replies. Last edited by MDM1982; Oct 23, 2009 at 08:42 PM.

Oct 26, 2009, 04:55 PM	Thread Starter #3
MDM1982 DriverHeaven Newbie Join Date: Oct 2009 Posts: 5 Rep Power: 0	Re: Failed to initialize DirectSound Thanks for replying Russ. I re-installed the OS and even tried re-installing with an XP SP2 slipstream instead but still got the same error messages. I found that using the 3539 or 3541 drivers the errors have gone both on startup and in DxDiag. I've also noticed that with all the KX drivers I will get a slight pause when entering folders in Explorer this does not happen with the Creative drivers any ideas what might cause this?.

Oct 26, 2009, 05:57 PM	#4
Russ HardwareHeaven Extreme Member Join Date: Jan 2005 Posts: 5,507 Rep Power: 61	Re: Failed to initialize DirectSound Hmm, that is strange... I am using WinXP SP2 and have no such errors. As for the pause, are you sure it is not your anti-virus software causing it? I remember having that problem some time ago when I was using AVG (it is one of the reasons that I stopped using AVG)... it would take forever to open a folder that had a lot of files in it.

Oct 26, 2009, 06:24 PM	Thread Starter #5
MDM1982 DriverHeaven Newbie Join Date: Oct 2009 Posts: 5 Rep Power: 0	Re: Failed to initialize DirectSound I don't suppose it could be because I'm using headphones would it, really not sure what else could cause this? I didn't have any anti-virus or firewall software on at the time, I usually use AntiVir (have stayed away from AVG since 8.5+ got so bloated) and Comodo for the firewall.

Oct 26, 2009, 06:34 PM	#6
Russ HardwareHeaven Extreme Member Join Date: Jan 2005 Posts: 5,507 Rep Power: 61	Re: Failed to initialize DirectSound I cannot think of any reasons why using headphones should make any difference...

Oct 26, 2009, 07:10 PM	Thread Starter #7
MDM1982 DriverHeaven Newbie Join Date: Oct 2009 Posts: 5 Rep Power: 0	Re: Failed to initialize DirectSound Is there a way to show a log or something after the drivers have installed to see if there are any problems?.

Oct 26, 2009, 07:22 PM	#8
Russ HardwareHeaven Extreme Member Join Date: Jan 2005 Posts: 5,507 Rep Power: 61	Re: Failed to initialize DirectSound Not that I know of... But there is the Event Viewer in Windows, and you can use a program like DebugView to view debug info from kX (and other programs) while it is running (i.e. DebugView will shows some status messages or errors from kX).

Oct 26, 2009, 08:42 PM	Thread Starter #9
MDM1982 DriverHeaven Newbie Join Date: Oct 2009 Posts: 5 Rep Power: 0	Re: Failed to initialize DirectSound Thanks Russ. Will give DebugView a go then and see. Nothing really out of the ordinary in Event Viewer except in System > disk > The system failed to flush data to the transaction log. Corruption may occur. and a few WinMgmt warnings in Application, I think these are normal though due to the service pack being slipstreamed: A provider, Rsop Planning Mode Provider, has been registered in the WMI namespace, root\RSOP, but did not specify the HostingModel property. A provider, Rsop Planning Mode Provider, has been registered in the WMI namespace, root\RSOP, but did not specify the HostingModel property. A provider, Rsop Planning Mode Provider, has been registered in the WMI namespace, root\RSOP, but did not specify the HostingModel property. A provider, Rsop Planning Mode Provider, has been registered in the WMI namespace, root\RSOP, but did not specify the HostingModel property. A provider, CmdTriggerConsumer, has been registered in the WMI namespace, Root\cimv2, to use the LocalSystem account. A provider, CmdTriggerConsumer, has been registered in the WMI namespace, Root\cimv2, to use the LocalSystem account. A provider, HiPerfCooker_v1, has been registered in the WMI namespace, Root\WMI, to use the LocalSystem account.

Jan 16, 2011, 04:36 AM	#11
coolies HardwareHeaven Newbie Join Date: Jan 2011 Posts: 5 Rep Power: 0	Re: Failed to initialize DirectSound I also have this problem with only 3550 Windows XP. I thought it was because I was falling behind in the DirectX or Windows version. I am using 3549