Recommended Posts

I experience problem with sound card drivers (Realtek ALC850 and SBLive 24bit!) under Windows 7 build 6801 x68.

Installation completes successfully, but drivers do not load with error code 39.

I tried to install different versions of drivers for Vista as well as installed drivers from Windows update with no result.

Other devices work stable with native drivers.

Does anyone know how to make system recognize my audio cards?

(Athlon X2 3800+, Gigabyte K8N-SLI, 2Gb DDR, Samsung 400Gb, Seagate Barracuda 11 - 500Gb, 2x Barracuda 10 - 80Gb)

Link to comment
https://www.neowin.net/forum/topic/697594-problem-with-sound-card-drivers/
Share on other sites

No problems with the realtek drivers here.. sounds like it's a conflict or can't handle 2 different sound devices at once. Try taking out the sblive from the computer, get rid of its drivers and see if the onboard will then work. Then reverse it all, disable onboard sound in bios, put the sb card back in and see if it will work. Question, why do you need 2 different sound cards running at once?

No problems with the realtek drivers here.. sounds like it's a conflict or can't handle 2 different sound devices at once. Try taking out the sblive from the computer, get rid of its drivers and see if the onboard will then work. Then reverse it all, disable onboard sound in bios, put the sb card back in and see if it will work. Question, why do you need 2 different sound cards running at once?

I used both cards since I obtained my PC in the march 2006. I installed different OSs (Windows XP and Vista both 32 and 64 bit, as well as different Linux compilations) and driver versions but never experienced conflict between these cards.

My SBLive is connected to stereo amplifier, and I also use Realtek with headphones. It's very convenient for me.

I had to reboot into safe mode and uninstall the drivers. Then redetect and install the realtek ones.

Thanks for advice, I will try to follow it

Reinstalled Wndows 7, downloaded and installed drivers from Windows Update successfully. Seems that Vista drivers were incompatible with Win7. My advice is to install all drivers from Windows Update first.

Which drivers were detected by windows update, the Realtek card or SB Live? My X-Fi card was never detected by windows update.

My X-fi is working on Windows 7 X64, used the Vista x64 drivers, version 5.12.17.1144

SB live wouldn't work out of the box in vista (x32), needed livedrv-unipack to make it work, this might also work on Windows 7 (haven't tried it, as the sb live is stored somewhere other then inside a computer).

I took out my Soundblaster X-Fi Extreme Audio card and enabled the on board Realtek sound chip. It worked fine. I just tried again to install the Vista 64bit driver for the X-Fi card but still no good. I downloaded the Soundblaster X-Fi Extreme Audio Web Update five installer and while trying to install the driver get an error message "Driver version not found"

I have a Sound blaster Live! card and it works but it the sound is a bit distorted any one else have this problem?

Yes. Since my x-fi card didn't work I tried an old Soundblaster Live card. I'm not sure what driver I downloaded. It installed but oh my god! Mine wasn't a bit distorted. It was almost all distortion. I even uninstalled Windows 7 64bit and installed the 32bit version. The Soundblaster cards still don't work. I'm also having an issue playing a dvd with Media Center. I put in one of my "West Wing" dvds and the picture kept freezing.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • The problem isn't with Epic, it's with the platform holders like Steam and Nintendo, they should be a lot more strict in their review process.
    • Hello, Installed here without issue. Regards, Aryeh Goretsky
    • Microsoft updates Visual Studio Code with easier language model discovery and in-app search by Paul Hill Microsoft has released Visual Studio Code 1.125, its latest weekly release. This week, the company has focused on discovering and installing extra language models via the Marketplace; searching the web and securely browsing over remote connections without leaving VS Code; choosing how long VS Code waits before installing extension updates; and delivering managed Copilot settings through existing device management tooling. In older versions of VS Code, extensions could contribute their own model providers, but to find these extensions, you needed the right tags to search for in the Extension view. Now, the Language Models editor gives you an Install Model Providers button that opens the Extensions view, which is filtered to extensions that contribute model providers, making it easier to find and install them. Once you install a provider, its model will appear in the model picker. If you use the integrated browser much, you can now look up information without leaving VS Code by typing a query into the integrated browser’s address bar. It will use your configured search engine, the same way a standalone browser does. You can use workbench.browser.searchEngine to pick a search engine. When the browser is opened in a remote workspace, it's now possible to proxy HTTP(S) traffic via the remote connection. This allows you to connect to any ports or services that can only be accessed from the remote machine. If you read our coverage from two weeks ago about VS Code 1.123, you might have seen that extension updates have a two-hour delay as a safety measure. In this update, Microsoft is giving you the ability to configure the time of the delay. You can find it under extensions.autoUpdateDelay. Finally, with this update, admins can deliver managed GitHub Copilot settings through native device management (MDM) channels on Windows and macOS, in addition to account-based enterprise settings files. Settings delivered via MDM appear as policy-enforced in VS Code and can’t be overridden locally. Future updates will extend the supported policy keys across Copilot surfaces. You can download the update from the Visual Studio Code website now.
    • "it opens up new doors for people who prefer using Edge, but cannot be bothered to configure a Microsoft account" You already have a Microsoft account if you are using Windows 11, because you can't set it up without one.
  • Recent Achievements

    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
    • One Month Later
      eurospharma62 earned a badge
      One Month Later
    • Week One Done
      With What earned a badge
      Week One Done
    • Week One Done
      Harris Gilbert earned a badge
      Week One Done
    • One Month Later
      Vincian earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      543
    2. 2
      +Edouard
      171
    3. 3
      PsYcHoKiLLa
      83
    4. 4
      ATLien_0
      64
    5. 5
      neufuse
      64
  • Tell a friend

    Love Neowin? Tell a friend!