Ok, so we know its not the soundcards. Its a problem with the OS/drivers. Now having 2 network adapters on the same IRQ has been known to cause some problems. Since 2000/XP uses ACPI which sets everything to IRQ 9 if memory serves, it can cause conflicts if the drivers are not written properly. Forcing an IRQ change normally fixes this problem. I say normally because nothing works all the time when it comes to computers. I haven't used Xp for a while since I use 2000 at home. So if I messed up with what I said there with XP used ACPI someone feel free to correct me. Just an idea.

Black Mage brings up a good point about ACPI. I don't know if it will help but at this point there isn't much left for you to try. You might want to disable ACPI. It has been known to cause quite a few problems in some configurations. I have it disabled because of a problem with my Tuner card, and I know a few others here have it disabled because of conflicts with devices.

I finally got to the point of no return.....

I reIstalled Xp....@##$@%%#^#$

That finally fixed the problem, and got me a new one...with my nerves...!!!!! ;-)

thanx guys...

I think reinstalling the operating system is not really fixing the problem but putting it off.

I agree Mic, If you never have the problem come up again then thats fine, but if the problem does show up again, you are right back where you started.

If there is no other way to fix the problem then why not reinstall windows. It would save me time, I just do not want to have to call MS again to get my product key, they have no sense of humor and are very unhappy people to deal with, especially with getting a product key. Its enough incentive to learn Linux.

Also: I tried the resetting the ACPI under device manager. Surprisingly . . . it did not work! I am about ready to drop this computer of mine from a precarious altitude. Thank you for all your help, but I think I have just about given up, unless someone else has any ideas.

I thought the problem was isolated to direct sound, but NONE of my drivers work, not even midi. I think I will try swapping the cards in different combinations to each of the PCI slots and finding if that will work, otherwise I have no idea of what to even think of trying.

Well, since it seems to be a DirectSound problem, ever considered installing the latest DirectX?

If it's possible, you could try flashing your Audigy firmware. I haven't seen anything of the like on Creative's website, but you may want to contact their technical support team about it.

I would reinstall DirectX again, but I already have the most up to date version installed. There are no reinstallers for DirectX on windows XP because it comes preinstalled with the operating system. As for the firmware idea, I think it might be a possibility. I am working with Creative Support now, and I think that they may have a solution (doubtful, already tried one, didn't work). Anyhow thanks for the help. I will let you guys know if I find anything out from Creative.

and finally reinstalled XP. It was hopeless. The guy at Creative just had me disable startup items and reinstall the drivers. If only he knew! I am getting quite disgusted with this whole soundcard issue and wish that Microsoft/XP would get off their butts and find a solution. It is ridiculous if you ask me. Anyhow, thanks for all of your help, I really appreciate it.

You reinstalled and still have the problem? Then it must be hardware related.

Did you try disabling ACPI in the BIOS? You said Device Manager but it needs to be done in the BIOS

I don't think it was hardware related. A fresh installation of XP fixed my problem, so it must have been a software issue. I think it happened after I tried to reinstall the same drivers using the creative SBLiveDrvPack.zip. I do not have a clue why that would have caused so much conflict, even after all that I tried. Everything works great now, though, thanks for all your help.

Good to Hear!

I misunderstood your reply prior to my last reply. I took it to mean that it still wasn't working after the reinstall. Glad to hear you got it fixed.

Yeah good to hear!

I got that same ¤¬¦¬¤¢£¤¢£@ problem on my laptop.

It's the fourth time now. But the three other times, it was when I updated my WindowsXP.

This time it just crashed and made that error.

The other times I went into the old windows Updates and after half a day of removing updates, I was able to get my sound back.

I really don't know why it's doing that. I run an intel soundcard integrated in my laptop motherboard.

If any of you found the reason of this mess, please advise!

Etienne

Well my search for a solution to the bad directsound driver when trying to play winamp led me to this forum. And I've noticed this problem has happened to people with different types of sound cards. Well I have onboard audio on an ASUS P4T533 - and it had not given me any problems... until today. I love my music and a bit 'o gamin - has anyone figured this out?



Any and all insightful help would be more than appreciated.

I also am having problems with a supposed Bad DirectSound driver, error code: 88780078. I also had my sound just suddenly stop one day, and is now very spasmodic in it's workings. I am running win98 and a Soundblaster AWE64. Has anyone come up with a solution to the problem yet?

Please Help!!!!

Yo all

Hope everyone's had/having a good easter


Doesn't this totally suggest it's a DX problem ? there's multiple ppl with Creative Soundcards, 1 Enqoniq and 1 Integrated Intel soundchip now

all the same Directsound error, so, it can't be a PCI slot issue, or a particular defective soundcard as they've all got/had it.

It's probably not ACPI, though i agree, it's an absolute bast in some cases.

the only real common denominator is.... DirectX!

I'll happily stand corrected for the sake of all these guys, I just think looking at certain firmware/driver releases is abit in-depth and the greater picture across all these different platforms suggests its something much simpler

ciao!

Hi all,


This forum seems to be quite old, but i think that my solution would still help the "88780078 community"

First of all, this is NOT a hardware problem. It happened to me this morning, without any apparent reason: I tried to listen to one of my favourite mp3 with winamp then i had the famous "bad directconnect..blabla...code 88780078".

This is a problem between directx and the sbdrivers that i solved by reinstalling directX9 then uninstalling my sbdriver from the device manager and scan for hardware change. But the first scan didn't worked, so i uninstalled the driver a second time and rescan twice....then -: Miracle :- creative SBLIVE! (WDM) driver appears and my sound came back.
I know that it is not a real technical explication but it should help some of you. Keep scanning for hardware change until the creative game port prob desapear.

Tato

My config :
athlon XP pro
creative soundblaster platinum

Ok, the prob appeared again this morning and my solution didn't worked..i 've got my sound back by changing the pci slot of my card.....So.....good luck