SoundBlaster ZxR, Windows 10 Issues.

Discussion in 'Soundcards, Speakers HiFI & File formats' started by TheDeeGee, Nov 24, 2016.

  1. Mineria

    Mineria Ancient Guru

    Messages:
    5,540
    Likes Received:
    701
    GPU:
    Asus RTX 3080 Ti
    New driver is pretty solid.
     
  2. Athlonite

    Athlonite Maha Guru

    Messages:
    1,358
    Likes Received:
    52
    GPU:
    Pulse RX5700 8GB
    I can't recommend Daniel K drivers enough he's the best at what he does and that's making the damn things work the way they're supposed to
     
  3. TheDeeGee

    TheDeeGee Ancient Guru

    Messages:
    9,676
    Likes Received:
    3,455
    GPU:
    NVIDIA RTX 4070 Ti
    The Creative Drivers work fine, as long as i keep HDMI Audio from the GPU Disabled in Device Manager.
     
  4. Mineria

    Mineria Ancient Guru

    Messages:
    5,540
    Likes Received:
    701
    GPU:
    Asus RTX 3080 Ti
    Daniel K drivers for ZxR??

    Issue is that Windows 10 sets the default audio device to DP/HDMI on every new display driver installation if the audio drivers are selected to be a part of the update or if the update is done after using DDU, since DDU also flushes the display cars audio driver.
    Disabling HDMI/DP audio fixes that, sometimes it requires 2 boots after the update.
     

  5. TheDeeGee

    TheDeeGee Ancient Guru

    Messages:
    9,676
    Likes Received:
    3,455
    GPU:
    NVIDIA RTX 4070 Ti
    Kinda guessed it was a Win 10 thing, since it never happend when i used Win 7 ^^

    Still happy with 10 though :)
     
  6. TheDeeGee

    TheDeeGee Ancient Guru

    Messages:
    9,676
    Likes Received:
    3,455
    GPU:
    NVIDIA RTX 4070 Ti
    Not sure if it's yesterdays Windows 10 Update, but something is wrong.

    I keep having to switch profiles in the SB Z Control Panel in order to get proper sound. When i booted up the PC this morning, everything sounded as if it was on the First Person Shooter profile, except it wasn't.

    This now keeps happening everytime i reboot or cold start.
     
  7. TheDeeGee

    TheDeeGee Ancient Guru

    Messages:
    9,676
    Likes Received:
    3,455
    GPU:
    NVIDIA RTX 4070 Ti
    Yep, tested it out.

    The new Windows Update screwed something up.
     
  8. TheDeeGee

    TheDeeGee Ancient Guru

    Messages:
    9,676
    Likes Received:
    3,455
    GPU:
    NVIDIA RTX 4070 Ti
    So i rolled back to the Anniversary Update and applied the same July 11th Update, and now the sound works fine.

    It seems to be a combination of Creators Update + July 11th which is causing issues with the SoundBlaster ZxR... atleast for me.
     
  9. TheDeeGee

    TheDeeGee Ancient Guru

    Messages:
    9,676
    Likes Received:
    3,455
    GPU:
    NVIDIA RTX 4070 Ti
    Well, fixed it by reinstalling via the Media Creation Tool on USB Stick, which instantly installs 1703.

    Applied all updates and now there are no issues.

    Guess something got screwed up somehow when updating from Anniversary to Creators.
     
  10. TheDeeGee

    TheDeeGee Ancient Guru

    Messages:
    9,676
    Likes Received:
    3,455
    GPU:
    NVIDIA RTX 4070 Ti
    It started acting up again after todays Update.

    After reboot and starting something which requires sound i hear one of the relays click, and the sound is really shallow. I have to select a different profile, and then back to my own again to fix it.

    Unlikely to be the soundcard failing, cuz as i said in the previous post it's a fresh Install of 1703. Not sure what's going on but the the Creators Update is clearly unstable when it comes to new updates.
     
    Last edited: Aug 9, 2017

  11. TheDeeGee

    TheDeeGee Ancient Guru

    Messages:
    9,676
    Likes Received:
    3,455
    GPU:
    NVIDIA RTX 4070 Ti
    Seem to have fixed it by switching stuff around PCI-E Slot wise.

    Old Config:

    GPU - PCI-E x16 Slot 2 (x8 Wired)
    Sound - PCI-E x1 Slot 1 (x1 Wired)

    New Config:

    GPU - PCI-E x16 Slot 1 (x16 Wired)
    Sound - PCI-E x16 Slot 3 (x4 Wired)

    Still think it has to with Windows 10 1703 though, as it worked for months and months in 1503 and 1603 with the old config and even for a while in 1703 untill some updates started rolling out.
     

Share This Page