Intel Motherboards - Z390 Extreme 4 Win10pro sound stutter

Print Page | Close Window

Z390 Extreme 4 Win10pro sound stutter

Printed From: ASRock.com
Category: Technical Support
Forum Name: Intel Motherboards
Forum Description: Question about ASRock Intel Motherboards
URL: https://forum.asrock.com/forum_posts.asp?TID=17419
Printed Date: 31 Jul 2025 at 10:43am
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com

Topic: Z390 Extreme 4 Win10pro sound stutter

Posted By: booly
Subject: Z390 Extreme 4 Win10pro sound stutter
Date Posted: 06 Dec 2020 at 1:58am

Please can you help me fix a problem I am having with stuttering music playback via Groove and via YouTube etc in Win 10pro with a Z390 Extreme 4.

I tried default settings for optical playback of 48000Hz 16bit (by using reset following the manual instructions p102) and it stutters using the latest drivers from support downloads dated 2020/1/6 (v. 6.0.8750.1 ui 1.3.185.0)

All settings stutter except if I switch "RealTek Digital Output" to the lowest fidelity setting 32000Hz 16bit the stuttering stops and playback is smooth, but an optical link should be able to do better than this and I am concerned it is not working properly.

I built this system with an I7 9700 and 32Gb RAM and all SSD/M2, both M2 slots are populated. I am using the optical link to link with Logitech Z5500 5.1 speakers.

So far to resolve the stuttering I googled a lot for sound stuttering in Win10 and tried disabling speed step, set minimum power state to 100%, disabled fast boot, disabled and reenabled HPET in BIOS.

Also tweaked BCD settings, enabled and disabled without benefit.
useplatformclock
tscsyncpolicy
disabledynamictick

Can you help me improve performance in the higher settings please.

Replies:

Posted By: booly
Date Posted: 08 Dec 2020 at 2:49am

OK I can report with settings as above and removing BCD settings for the three parameters it was still stuttering.

But then it finally stopped stuttering after I switched it off and left it overnight and then booted up again to find the sound was working as expected.

I have no idea why.

Maybe there was an update processing in the background or something but eventually it just mysteriously fixed itself !

FYI