Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion.

Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules.

 

Go Back   Doom9's Forum > Hardware & Software > Software players

Reply
 
Thread Tools Search this Thread Display Modes
Old 11th June 2019, 12:50   #381  |  Link
SamuriHL
Registered User
 
SamuriHL's Avatar
 
Join Date: May 2004
Posts: 4,121
Well it's not going to f***ing happen any time soon as my system crashed again overnight and won't boot anymore. The brand new 970 pro appears to have completely f***ing died and I'm so far beside myself given what I paid for it it's not even funny. All the work I spent last night rebuilding the goddamn thing is gone again. WTF Samsung!
__________________
HTPC: Windows 10, I9 9900k, RTX 2070 Founder's Edition, Pioneer Elite VSX-LX303, LG C8 65" OLED
SamuriHL is offline   Reply With Quote
Old 11th June 2019, 13:41   #382  |  Link
huhn
Registered User
 
Join Date: Oct 2012
Posts: 5,600
Quote:
Originally Posted by el Filou View Post
Oh my. Thanks for confirming though.
And this also happens if you change refresh rates in rapid succession, like less than 10 seconds?
I know that now the NVIDIA audio driver forcefully closes the HDMI audio stream after 10 seconds of no sound to save power but I've edited the registry to fix this, so it isn't the cause.
i don't have the issue anymore i don't run new windows version at the moment.

i personally would just ignore this "issue" an audio pop with an resync is sadly relative normal with all kinds of devices.

i'm using an bad expensive PCIe sound card not an good realtek onboard soundcard and this can easily the reason for me. can't wait for my ryzen with proper onboard soundcard...
huhn is offline   Reply With Quote
Old 11th June 2019, 15:57   #383  |  Link
gonca
Registered User
 
Join Date: Jul 2012
Location: Scarborough, Canada
Posts: 895
Quote:
Originally Posted by SamuriHL View Post
Well it's not going to f***ing happen any time soon as my system crashed again overnight and won't boot anymore. The brand new 970 pro appears to have completely f***ing died and I'm so far beside myself given what I paid for it it's not even funny. All the work I spent last night rebuilding the goddamn thing is gone again. WTF Samsung!
What MoBO do you have?
Never had a Samsung SSD (or NVME) just die
Did you try unplugging the power supply from the wall for a minute?
Power supply still good?
gonca is offline   Reply With Quote
Old 11th June 2019, 16:48   #384  |  Link
SamuriHL
Registered User
 
SamuriHL's Avatar
 
Join Date: May 2004
Posts: 4,121
Yea, it's not the SSD. It's a much more complicated problem, unfortunately, which may end up ultimately coming down to my RTX 2070. I spent too much time this morning debugging the issue already so I have to set it aside til tonight. The issue is more bizarre than anything I've ever seen on a PC, though, which troubles me as everything is brand new within the last 45-60 days. The SSD, however, is not the issue and has been ruled out.
__________________
HTPC: Windows 10, I9 9900k, RTX 2070 Founder's Edition, Pioneer Elite VSX-LX303, LG C8 65" OLED
SamuriHL is offline   Reply With Quote
Old 11th June 2019, 17:40   #385  |  Link
hotripper
Registered User
 
Join Date: Apr 2019
Posts: 37
Quote:
Originally Posted by el Filou View Post
Oh my. Thanks for confirming though.
And this also happens if you change refresh rates in rapid succession, like less than 10 seconds?
I know that now the NVIDIA audio driver forcefully closes the HDMI audio stream after 10 seconds of no sound to save power but I've edited the registry to fix this, so it isn't the cause.
pLE4ASE tell me wherein regedit and how u did this I am interested!
__________________
4790K - RTX2070 - 970EVO - EVGA Supernova 750W Gold - Sony KD55X720E
hotripper is offline   Reply With Quote
Old 11th June 2019, 18:24   #386  |  Link
el Filou
Registered User
 
el Filou's Avatar
 
Join Date: Oct 2016
Posts: 451
@hotripper

1. Device Manager: open the sound controller device properties => Details => copy the 'Driver key' property
2. Regedit: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\<********paste Driver key here********>\PowerSettings => change the PerformanceIdleTime key to 00 00 00 00

(there's also a ConservationIdleTime key if you want a different timeout for when a laptop is on battery)

source: https://docs.microsoft.com/en-us/win...power-settings

Disclaimer: this may make your AVR consume more power when no audio is played, depending on its design
__________________
HTPC: W10 1809, E7400, 1050 Ti, DVB-C, Denon 2310, Panasonic GT60 | Desktop: W10 1809, 4690K, HD 7870, Dell U2713HM | MediaPortal 1/MPC-HC, LAV Filters, ReClock, madVR
el Filou is offline   Reply With Quote
Old 11th June 2019, 18:48   #387  |  Link
gonca
Registered User
 
Join Date: Jul 2012
Location: Scarborough, Canada
Posts: 895
Quote:
Originally Posted by SamuriHL View Post
Yea, it's not the SSD. It's a much more complicated problem, unfortunately, which may end up ultimately coming down to my RTX 2070. I spent too much time this morning debugging the issue already so I have to set it aside til tonight. The issue is more bizarre than anything I've ever seen on a PC, though, which troubles me as everything is brand new within the last 45-60 days. The SSD, however, is not the issue and has been ruled out.
Have you ruled out the Ram sticks or the sockets?
gonca is offline   Reply With Quote
Old 11th June 2019, 20:27   #388  |  Link
SamuriHL
Registered User
 
SamuriHL's Avatar
 
Join Date: May 2004
Posts: 4,121
Yea, I've narrowed it down to video related issues. I've pulled the 2070 right now and am reinstalling windows with just the built in Intel whatever on the 9900k. madvr isn't going to love that but this should only be temporary until I can determine if it's a defective card and get it replaced.
__________________
HTPC: Windows 10, I9 9900k, RTX 2070 Founder's Edition, Pioneer Elite VSX-LX303, LG C8 65" OLED
SamuriHL is offline   Reply With Quote
Old 12th June 2019, 00:49   #389  |  Link
hotripper
Registered User
 
Join Date: Apr 2019
Posts: 37
@el Fijou
Thanks. works, So far so good! Its annoying how my 5.1 through dvi/hdmi sleeps but stereo hdmi through tvARC never sleeps so power concern is none for me, I just want both outputs to act the same. Awesome tip!
__________________
4790K - RTX2070 - 970EVO - EVGA Supernova 750W Gold - Sony KD55X720E
hotripper is offline   Reply With Quote
Old 12th June 2019, 01:14   #390  |  Link
SamuriHL
Registered User
 
SamuriHL's Avatar
 
Join Date: May 2004
Posts: 4,121
Alright, my issue is on its way to being solved. After so much troubleshooting it has been narrowed down to a hardware issue with the 2070. nVidia is RMA'ing it and my system is running with my 1060 right now. Good thing is I guess the windows clean install? LOL It is a brand new machine.
__________________
HTPC: Windows 10, I9 9900k, RTX 2070 Founder's Edition, Pioneer Elite VSX-LX303, LG C8 65" OLED
SamuriHL is offline   Reply With Quote
Old 12th June 2019, 08:43   #391  |  Link
oldpainlesskodi
Registered User
 
Join Date: Apr 2017
Posts: 156
The banding issue on Win 10 1903 looks like it's been picked up:

https://hub.displaycal.net/forums/to...-windows-1903/

https://www.reddit.com/r/Windows10/c..._strips_issue/

https://www.reddit.com/r/Windows10/c...eople_who_use/
__________________
Strix GTX 1080 OC 8GB (alanfox2000 430.97) , Win 10 x64 (1903), Quad Core @ 4.4ghz, Silverstone LC13B-E, Pioneer SC-LX501 Elite D3, Samsung UE55KS8000, YAMAHA NSF51 speakers, Kodi Dsplayer 17.6 X64

Last edited by oldpainlesskodi; 12th June 2019 at 09:09.
oldpainlesskodi is offline   Reply With Quote
Old 12th June 2019, 12:09   #392  |  Link
ryrynz
Registered User
 
ryrynz's Avatar
 
Join Date: Mar 2009
Posts: 3,130
Yeah users picked it up ages ago, has it been picked up by Nvidia/MS though? It's entirely the reason why I've held off 1903 on my HTPC. Really nice update though apart from this issue.
ryrynz is offline   Reply With Quote
Old 12th June 2019, 12:16   #393  |  Link
el Filou
Registered User
 
el Filou's Avatar
 
Join Date: Oct 2016
Posts: 451
The really depressing part is this: "Iíve reported the issue both to nvidia, and Microsoft multiple times since the issue has been there for months in the insider builds which is now RTM but seems that nothing is being done about it."

They mostly depend on insiders for QA but even when issues are reported officially and widely they don't get fixed before release.
It's like Windows is some video game for them now instead of, you know, a critical part of using your computer.
__________________
HTPC: W10 1809, E7400, 1050 Ti, DVB-C, Denon 2310, Panasonic GT60 | Desktop: W10 1809, 4690K, HD 7870, Dell U2713HM | MediaPortal 1/MPC-HC, LAV Filters, ReClock, madVR
el Filou is offline   Reply With Quote
Old 12th June 2019, 12:29   #394  |  Link
ryrynz
Registered User
 
ryrynz's Avatar
 
Join Date: Mar 2009
Posts: 3,130
That honestly does not surprise me, communication is often poor unless you're dealing with an actual person. Pity Madshi ain't around to help sort it.. providing him all the info and having him forward it on would've been the ideal solution.
Have you spoken with ManuelGuzman or tweeted @windowsdev? Both of them appear to be reasonably useful in making things happen.
ryrynz is offline   Reply With Quote
Old 12th June 2019, 12:34   #395  |  Link
oldpainlesskodi
Registered User
 
Join Date: Apr 2017
Posts: 156
Quote:
Originally Posted by ryrynz View Post
Yeah users picked it up ages ago, has it been picked up by Nvidia/MS though? It's entirely the reason why I've held off 1903 on my HTPC. Really nice update though apart from this issue.
Yeah, true...I guess the more noise created, hopefully the better the chances of it getting fixed.
__________________
Strix GTX 1080 OC 8GB (alanfox2000 430.97) , Win 10 x64 (1903), Quad Core @ 4.4ghz, Silverstone LC13B-E, Pioneer SC-LX501 Elite D3, Samsung UE55KS8000, YAMAHA NSF51 speakers, Kodi Dsplayer 17.6 X64
oldpainlesskodi is offline   Reply With Quote
Old 12th June 2019, 12:37   #396  |  Link
ryrynz
Registered User
 
ryrynz's Avatar
 
Join Date: Mar 2009
Posts: 3,130
It will be fixed, it'll just be better chances of getting it fixed promptly. Wonder if it's even on their radar?
ryrynz is offline   Reply With Quote
Old 12th June 2019, 12:39   #397  |  Link
oldpainlesskodi
Registered User
 
Join Date: Apr 2017
Posts: 156
Quote:
Originally Posted by ryrynz View Post
It will be fixed, it'll just be better chances of getting it fixed promptly. Wonder if it's even on their radar?
I'm not a member on the Nvidia or MS forums, so hopefully those that are (and here) will help flag the issue.
__________________
Strix GTX 1080 OC 8GB (alanfox2000 430.97) , Win 10 x64 (1903), Quad Core @ 4.4ghz, Silverstone LC13B-E, Pioneer SC-LX501 Elite D3, Samsung UE55KS8000, YAMAHA NSF51 speakers, Kodi Dsplayer 17.6 X64
oldpainlesskodi is offline   Reply With Quote
Old 12th June 2019, 18:10   #398  |  Link
el Filou
Registered User
 
el Filou's Avatar
 
Join Date: Oct 2016
Posts: 451
Quote:
Originally Posted by huhn View Post
i personally would just ignore this "issue" an audio pop with an resync is sadly relative normal with all kinds of devices.
I know but I'm hypersensitive to harsh noises and it's really quite a loud pop if the AVR volume is set to movie listening level. I'm also afraid it may damage my speakers in the long run but maybe I'm being paranoid.

You're right that it's due to a change in Windows because I've just cleaned my system of all traces of NVIDIA audio driver and registry settings and went back to the generic MS HD Audio driver and it's still happening. It's probably a change on the graphics side, it must force the GPU to reset the whole HDMI connection when changing refresh rate or something like that and it probably is doing it dirty without cleanly cutting the audio channel first.
I wish if HDMI QMS eventually comes to PCs one day that it will fix this again.
I'm now manually muting the global sound output of Windows before changing my display refresh rate to avoid it, it's bothersome but it's a workaround.
__________________
HTPC: W10 1809, E7400, 1050 Ti, DVB-C, Denon 2310, Panasonic GT60 | Desktop: W10 1809, 4690K, HD 7870, Dell U2713HM | MediaPortal 1/MPC-HC, LAV Filters, ReClock, madVR
el Filou is offline   Reply With Quote
Old 13th June 2019, 17:44   #399  |  Link
janos666
Registered User
 
Join Date: Jan 2010
Posts: 447
Did anybody find an AMD driver that works with 1903 (no banding)?
Edit: This is madness. I decided to run DDU and try the latest 19.6.1 (WDDM 2.6) for one last time (before trying to revert to 1809) and now it's all fine. This leaves me wondering what really triggers the banding (or if running DDU changed anything).

Last edited by janos666; 13th June 2019 at 20:50.
janos666 is offline   Reply With Quote
Old 14th June 2019, 07:08   #400  |  Link
oldpainlesskodi
Registered User
 
Join Date: Apr 2017
Posts: 156
Finally managed to use a wddm 2.6 driver....and such a simple fix (I had done this on a previous windows build, but didnt even think to check on 1903 build).

Credit to acesko92 from the nvidia forum:

"I managed to find a fix for the broken gamma, and nvidia dithering in windows 1903: you need to go to Task Scheduler > Microsoft > Windows > WindowsColorSystem, and delete the task called WindowsColorSystem Calibration Loader."


I just disabled the service and rebooted, but each to their own.
__________________
Strix GTX 1080 OC 8GB (alanfox2000 430.97) , Win 10 x64 (1903), Quad Core @ 4.4ghz, Silverstone LC13B-E, Pioneer SC-LX501 Elite D3, Samsung UE55KS8000, YAMAHA NSF51 speakers, Kodi Dsplayer 17.6 X64

Last edited by oldpainlesskodi; 14th June 2019 at 07:19.
oldpainlesskodi is offline   Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +1. The time now is 10:45.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2019, vBulletin Solutions Inc.