• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

Editorial Windows 10 1903 Has a Nasty Audio Stutter Bug Microsoft Hasn't Managed to Fix

You're assuming the existing drivers wouldn't work fine as-is(which they do BTW), again this is a Microsoft problem, not a driver problem. Microsoft needs to fix it.
Wait. What?
 
X-Fi Titanium Pci-E still broken with those garbage Win10 releases....
 
its hilarious how many people don't know creatives track record with there shit drivers
there drivers have been garbage since the sound blaster 16 in msdos

again you got driver problems blame the vendor vendors fault not Microsofts they are not the nanny for every lazy vendor that wants to code things like its still 2003

its been literally over 10 years since directsound was put down like the rabid dog it was ten years, and the vendors still have not bothered to get there shit together and use wasapi the right way



and yes the problems all of them are 100% driver and 100% the hardware vendors fault
there is low latency apis and paths that the vendors simply are not using
./thread

thx bta for another well written informational editorial =/
 
its hilarious how many people don't know creatives track record with there shit drivers
What's more hilarious is people who claim this. I've been using Creatives cards since the 90's and have never had the horrific experiences people claim to have had.. Never even seen it.
there drivers have been garbage since the sound blaster 16 in msdos
This is oh so wrong.
 
I guess we are blaming vendors too for MS destroying 3D Hardware sound on the PC...
 
I guess we are blaming vendors too for MS destroying 3D Hardware sound on the PC...
despite how bta's entirely wrong editorial has made it sound its been dead for 13 years (since vista)


and yes actually DirectSound was depreciated due vendors doing stuff there own way which lead to compatibility issues, bugs and was generally a mess to maintain (or do you know remember the bs that was eax Aureal3d, cmp ect ect )


btw wasapi in shared mode supports sub 10ms buffers if the vendors would bother to use them

and btw there is nothing stopping vendors from implementing direct3d paths using openal, in fact, there is a wrapper for it(google it) ,creative did this yes real hardware accelerated openal then decided to not support it

hardware-accelerated audio-only existed because at the time processing audio was intensive for cpus of the era from a flexibility and functionality standpoint hardware acceleration is inferior in every way

so again not Microsofts problem

are we done now ?

in the future,@btarunr do some dam research before posting sudo-rants like this again
 
Last edited:
despite how bta's entirely wrong editorial has made it sound its been dead for 13 years (since vista)
Wow, just wow.. You did actually READ the editorial, right?
or do you know remember the bs that was eax Aureal3d, cmp ect ect
None of that was a mess if you knew how to use it. Seems clear by your statement that you didn't.
so again not Microsofts problem
The problems did NOT exist before an update and exists now. Since we all know Creative drivers haven't been changed then one can only conclude, based on the evidence, that this is EXCLUSIVELY a Microsoft problem.
are we done now ?
You tell us...
in the future,@btarunr do some dam research before posting sudo-rants like this again
Take your own advice.
 
X-Fi Titanium Pci-E still broken with those garbage Win10 releases....
Is the XFTI_PCDRV_L11_2_40_0019 driver not workinkg for your card?
 
I might just wait for the 19H2 version looking at this shit. Hopefully it will be fixed by then.
 
My listening rig still rocks Windows XP Sp3 and a Creative X-Fi Xtreme Music! PCI dedicated hardware accelerated EAX card. Never had a problem with it...
 
Try enabling HPET and Disabledynamictick

bcdedit /set useplatformclock true
BCDEDIT /SET DISABLEDYNAMICTICK YES

Simply more accurate timing and disabling a power saving feature.
 
My listening rig still rocks Windows XP Sp3 and a Creative X-Fi Xtreme Music! PCI dedicated hardware accelerated EAX card. Never had a problem with it...

Windows XP eww hope that computer is not connected to the internet.
 
Windows XP eww hope that computer is not connected to the internet.
That topic belongs in the thread below;
 
no stutter whatsoever using a Fiio Q1 Mk II or X5 III with Fiio DAC driver ... didn't test with onboard tho ...
 
Hi
I had this problem with my new Ryzen build .My creative zxr sound crashed after 10 min in games...only way i got it to work was turning off Digital live and activate it again in the soundblaster control panel… and then it crashed again and again :(
I tried realtek onboard audio and there is was no problem. Installed win 10 build 1903 from usb and Amd chipset driver 1.07.29.0115, and besides the sound, the system just runs like a dream :D
Finally found a solution :) i bypass the digital live by using the option " Play stereo mix to digital output "
Now there is no problems , seems to be the Digital Live not working properly… why ? doesn't have a clue… maybe the win 10 1903 build causing trouble or it is the Zxr who need's a major update
But another thing i noticed is that the annoying stuttering is gone



Amd 3900x
asus rog swift x570 f Gaming
Corsair mp600 PCIe 4.0
G.Skill TridentZ 3600 C16
asus rog strix 2080 gaming
acer predator x34a
 
Creative Sound Blaster ZxR here, no such issues.
 
Last edited:
New Soundblaster X Katana, have issue, like sound pops

Hmm I never knew this product existed but then again I'm not a soundbar guy.
 
Asus XONAR AE became a total rubbish after the latest MS WIN 10 update. Can't fix the unbelievable delay and sound crackles. Tried every possible solution. Very frustrating..
 
I had them with xfi titanium hd, but build after .264+ fixed it. Atm at .297 version.


Lol now I saw new .327 can have a issue with - cortana bing search, can cause high cpu usage cycles.. funny stuff this MS.. xD
 
I had them with xfi titanium hd, but build after .264+ fixed it. Atm at .297 version.


Lol now I saw new .327 can have a issue with - cortana bing search, can cause high cpu usage cycles.. funny stuff this MS.. xD

Cortana was disabled the min I installed the 1903 build probably why I never noticed this.
 
Back
Top