MPHC playback issue.

[Morbus Chron]

After upgrading to Windows 10 on a newly built PC, I've run into a minor problem. On all playback, music and video, there would sometimes be a choppy second. I think "choppy" is the right word, it happens for a second, the audio makes a buzz sound, I have a hard time describing it. Think a damaged CD being played, it goes well until the sound in it buffers for a split second. I hope it makes sense. I believe everything plays fine on VLC, I use Media Player Classic mainly, with K-Lite's codec pack. Could it be always running on EVR Custom Presenter? I thought changing the audio renderer from system default to DirectSound from the speakers would work. It did for a while seemingly. The problem returned yesterday. I keep thinking it's my external hard drive, but it's happened on playback from the internal one.

[Detmek]

Could be a driver problem. Try to run LatencyMon and see if reports any driver problem or problem with multimedia playback.

[Morbus Chron]

It said it appears to be suitable and stuff. I'm running GTX 980TI with the latest drivers.

Edit: now it says...

[Detmek]

It seams that Atheros driver is creating a problem. It may still not be ready for Windows 10. Try to find another version for Windows 10 or search to see if version for Windows 8.1 will work. I don't have Atheros network card so I can not try.

[Morbus Chron]

I switched to Intel LAN and uninstalled the Network suite for Atheros. I still get the same red words, and I think it's dxgkrnl.

Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal.

Highest ISR routine execution time (µs): 187.273482
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Highest reported total ISR routine time (%): 0.086907
Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Total time spent in ISRs (%) 0.089843

ISR count (execution time <250 µs): 870376
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 0
ISR count (execution time 1000-1999 µs): 0
ISR count (execution time 2000-3999 µs): 0
ISR count (execution time >=4000 µs): 0

[Detmek]

Could be CPU throttling. Set in Power options High Performance mode and see if that helps. It could be GPU driver, too. Nvida and Intel still have a lot of probems with their drivers for Windows 10. AMD is in a bit better situation but not without bug, too.

[Morbus Chron]

17 minutes monitored, and everything's green, so to speak. Thanks a lot for the help. Actually on the second bar with the highest latency interrupt thing, I got the red words again, this time suggesting to disable WLAN (which I don't have an adapter attached to it currently). So maybe that's just network and doesn't effect playback with MPC?

[Detmek]

It may affect or it may not. Just play file in MPC and you'll see if there is a problem. BTW, if setting to High Performance helps then it is a driver optimization problem. Newer drivers should fix that in the future.

[Morbus Chron]

So far haven't had problems after setting to high performance. I guess you're right about the drivers, I'm sure I have the latest ones, does Direct X 12 have drivers I should install? It came in default on Windows 10.

[Detmek]

No, DX12 is a part of Windows 10. In order to use it you need graphic card and GPU driver with DX12 support. But media players do not use DX12. Most of the time it is DX9, and some use DX11.

You could run DirectX Web Installer (uncheck Bing if you don't need it) and update DirectX 9 because your player uses DX9 for playback. Maybe that can fix a problem.

Nvidia is working to fix all driver bugs in Windows 10. They had a few driver builds since Win 10 was launched but not all bugs are fixed. And some bugs might be in Win 10 itself, too.

[Morbus Chron]

It came back. However, it did when I switched from high performance to balanced, back to high performance. So maybe I need to restart the computer? I didn't get high stats during the latency check after switching back to high maintenance.