AMD, Intel and Nvidia driver issues and last recommended version - Page 10

hotripper · 25th April 2019, 23:17

Quote:

Originally Posted by Nicog

Yesterday when I installed it it worked (no stuttering). Today it's dead (like previous drivers in fact, and also on non HDR content).

I'm back to 418.91, and now it's works fine...

I'm the only guy who has this issue?

What issue stutter? I have it stutter issues too. I found a workaround for now though.

sat4all · 26th April 2019, 09:34

Guys,

Carefull with the new driver it cause high cpu usage, nvidia Container LS alone take about 30% from my cpu, had to stop it and disable auto start.

Nicog · 26th April 2019, 09:35

Massive stutter (different of what I had without FSE ou without sync ON on HDR).

Maybe an issue with my config...

What workaround are you speaking about Hotripper?

SirMaster · 26th April 2019, 14:19

Quote:

Originally Posted by clsid

You can use the NvidiaProfileInspector tool to view all application profiles on your system. The .bat file adjusts the settings of the "Media Player Classic" profile. It doesn't change your global defaults.

Oh yeah that makes sense, thanks.

I'll just have to apply them manually then I think as I use MPC-BE rather than MPC-HC.

For some reason with madVR in MPC-HC I get crashing all the time (like when going fullscreen or resizing the window), but I do not ever with MPC-BE. I suspect it's some conflict with LAV filters being used by default in MPC-HC compared to internal filters included with MPC-BE, but the errors are beyond my debugging capabilities.

I also get some massive posturization when switching to full-screen often with MPC-HC, but never with MPC-BE.

Sorry doesn't belong in this thread anyways.

clsid · 26th April 2019, 14:49

The profile works for MPC-BE as well.

The crash dialog should usually indicate where the crash happened. Post screenshots.

I doubt it is because of LAV Filters. Most likely a driver issue.

SirMaster · 26th April 2019, 14:55

Quote:

Originally Posted by clsid

The profile works for MPC-BE as well.

The crash dialog should usually indicate where the crash happened. Post screenshots.

I doubt it is because of LAV Filters. Most likely a driver issue.

I can if it's something you think you or someone else would want to troubleshoot.

Though driver wasn't my first guess because it only happens in HC and not BE, but you know way more about this stuff than I do. Happens with both the 417 and 430 driver I had on that system. I know it's some madVR .ax file that it says is the "cause", but again, madVR is running exactly the same in BE heh.

I shall post it in the MPC-HC thread? I won't be able to until Sunday night anyways.

hotripper · 26th April 2019, 19:00

Quote:

Originally Posted by Nicog

Massive stutter (different of what I had without FSE ou without sync ON on HDR).

Maybe an issue with my config...

What workaround are you speaking about Hotripper?

Here: https://forum.doom9.org/showpost.php...ostcount=55968

So far this makes 3 of us with 2070s and stutter

cremor · 27th April 2019, 08:52

Quote:

Originally Posted by clsid

This is NVIDIA Profle Inspector tool with an optimized profile for MPC-HC/BE.

Download

Most important settings it uses:
Power management mode = Adaptive
VSync = on
GSync = off
SLI = off
Prefer NVIDIA on Optimus systems

Why did you set "Maximum pre-rendered frames" to 3 in the Nvidia profile? I thought the recommended value for madVR was "application preferred"?

clsid · 27th April 2019, 13:30

Yes, that should be fine too.

Manni · 27th April 2019, 13:47

I'm back to 385.28 for now as I needed 3D to calibrate my PJ

Until a new version of windows forces me to upgrade, I don't see why I should lose such an important functionality for no benefit (I have a 1080ti).

Hopefully nVidia with put HDMI 3D support back (I did request it), but I'm not holding my breath.

It might be more realistic to prevent an OS upgrade from 1809. Unfortunately MS doesn't make that easy, even when editing group policies. You can delay it, but you can't stop it.

chros · 27th April 2019, 15:13

Yes you can, use LTSB. (see my signature)

Manni · 27th April 2019, 15:40

Quote:

Originally Posted by chros

Yes you can, use LTSB. (see my signature)

I thought LTSB only delayed updates for 2-3 years? It's better than six months, but you still can't stop the upgrades, unless it has changed since I last looked at it.

Anyway I don't really want to do a full re-install, my HTPC has Pro x64, I don't have an Enterprise license.

huhn · 27th April 2019, 18:49

do you really want to run a 2-3 year old OS?

if intel 3D playback works i have a theoretical workaround in my head.
and there is still navi.

Manni · 27th April 2019, 20:20

Quote:

Originally Posted by huhn

do you really want to run a 2-3 year old OS?

if intel 3D playback works i have a theoretical workaround in my head.
and there is still navi.

All the security updates are applied. And yes, frankly I would be happy with 1809 in three years for a HTPC. What's wrong with that? The only need to update is to try to fix what they have broken over time.

If 385.28 had the better 3D that later drivers have, it would really be perfect.

Anyway I'm in the process of moving away from the HTPC altogether for film playback, provided that Envy delivers what we expect. Too much hassle really between OS, drivers and other issues.

Klaus1189 · 27th April 2019, 20:30

I understand fully your point, but all that is needed, is a graphics chip manufacturer that supplies drivers with 3D support and all other features working which is updated to run on actual and future OS versions. Sounds easy in theory ...

huhn · 27th April 2019, 20:31

so you don't want to replace hardware ever?

el Filou · 27th April 2019, 22:39

Quote:

Originally Posted by sat4all

Carefull with the new driver it cause high cpu usage, nvidia Container LS alone take about 30% from my cpu, had to stop it and disable auto start.

I can confirm. Here it takes up 100% of one CPU core.
I prefer to restart the service. Anyone knows what disabling that service does exactly?
I know the Telemetry isn't necessary, but I thought the Display Container was needed.
Edit: answering myself: NVIDIA Control Panel won't open if this service is not running. Display mode change via other means, reading GPU sensors, and NvAPI still seem to work fine. I guess you can still manually restart the service if you need to access NVIDIA Control Panel.

Manni · 27th April 2019, 22:53

Quote:

Originally Posted by Klaus1189

I understand fully your point, but all that is needed, is a graphics chip manufacturer that supplies drivers with 3D support and all other features working which is updated to run on actual and future OS versions. Sounds easy in theory ...

And when did that last happen?

What makes you think it will be any different in the future?

This thread really show the poor state of drivers/OS incompatibilities.

Frankly, they could have released a driver with everything working (HDR passthrough and HDR API in 8bits) before axing 3D... but they didn't.

semi70 · 27th April 2019, 23:10

Quote:

Originally Posted by hotripper

Here: https://forum.doom9.org/showpost.php...ostcount=55968

So far this makes 3 of us with 2070s and stutter

I have a 2080 and I have the stutter issue too. I have no problems at all when im on the 418.91 driver. everything after that version I have the stutter issue. madvr is not reporting any problems and I tried every proposed fix posted here with no improvements.
when im in windowed mode there is no stutter too. it seems to be a full screen exclusive mode issue.
its a shame Im stuck on this driver now that they have released a HDR fix on the latest too.

j82k · 27th April 2019, 23:53

Quote:

Originally Posted by sat4all

Guys,

Carefull with the new driver it cause high cpu usage, nvidia Container LS alone take about 30% from my cpu, had to stop it and disable auto start.

Yep, every single time my PC wakes up from sleep 'NVDisplay.Container.exe' fully utilizes one cpu core and I have to kick it via task manager.

But this problem already existed with previous newish drivers I think.

26th April 2019, 09:34	#182 \| Link
sat4all Registered User Join Date: Apr 2015 Posts: 62	Guys, Carefull with the new driver it cause high cpu usage, nvidia Container LS alone take about 30% from my cpu, had to stop it and disable auto start. __________________ ZOTAC MAGNUS EN1060K: Win 10 x64 + Kodi DSPlayer x64 LG OLED65C8 / Denon AVR-X3200W / KEF E305+ONKYO SKH-410 / Synology DS2415+ / Logitech Harmony 950

26th April 2019, 09:35	#183 \| Link
Nicog Registered User Join Date: Jan 2019 Posts: 17	Massive stutter (different of what I had without FSE ou without sync ON on HDR). Maybe an issue with my config... What workaround are you speaking about Hotripper? __________________ JRiver 25 in a Custom PC with i7 7700, Nvidia RTX 2070 (Zotac mini), Windows 10 1809, JVC X7900 in a dedicated black room :-)

27th April 2019, 13:47	#190 \| Link
Manni Registered User Join Date: Jul 2014 Posts: 942	I'm back to 385.28 for now as I needed 3D to calibrate my PJ Until a new version of windows forces me to upgrade, I don't see why I should lose such an important functionality for no benefit (I have a 1080ti). Hopefully nVidia with put HDMI 3D support back (I did request it), but I'm not holding my breath. It might be more realistic to prevent an OS upgrade from 1809. Unfortunately MS doesn't make that easy, even when editing group policies. You can delay it, but you can't stop it. __________________ Win11 Pro x64 b23H2 Ryzen 5950X@4.5Ghz 32Gb@3600 Zotac 3090 24Gb 551.33 madVR/LAV/jRiver/MyMovies/CMC Denon X8500HA>HD Fury VRRoom>TCL 55C805K

27th April 2019, 15:13	#191 \| Link
chros Registered User Join Date: Mar 2002 Posts: 2,323	Yes you can, use LTSB. (see my signature) __________________ Ryzen 5 2600,Asus Prime b450-Plus,16GB,MSI GTX 1060 Gaming X 6GB(v398.18),Win10 LTSC 1809,MPC-BEx64+LAV+MadVR,Yamaha RX-A870,LG OLED77G2(2160p@23/24/25/29/30/50/59/60Hz) \| madvr config

26th April 2019, 14:49	#185 \| Link
clsid ***** Join Date: Feb 2005 Posts: 5,647	The profile works for MPC-BE as well. The crash dialog should usually indicate where the crash happened. Post screenshots. I doubt it is because of LAV Filters. Most likely a driver issue.

27th April 2019, 13:30	#189 \| Link
clsid ***** Join Date: Feb 2005 Posts: 5,647	Yes, that should be fine too.

27th April 2019, 18:49	#193 \| Link
huhn Registered User Join Date: Oct 2012 Posts: 7,926	do you really want to run a 2-3 year old OS? if intel 3D playback works i have a theoretical workaround in my head. and there is still navi.

27th April 2019, 20:30	#195 \| Link
Klaus1189 Registered User Join Date: Feb 2015 Location: Bavaria Posts: 1,667	I understand fully your point, but all that is needed, is a graphics chip manufacturer that supplies drivers with 3D support and all other features working which is updated to run on actual and future OS versions. Sounds easy in theory ...

27th April 2019, 20:31	#196 \| Link
huhn Registered User Join Date: Oct 2012 Posts: 7,926	so you don't want to replace hardware ever?