Nvidia Game Ready Driver 456.38 - Download and Discussion

This must be the location for DCH, its not there in Standard.

nice find, i was looking for an etw rather than a log and db file.

Theres no concrete idea's on whats the trigger, some of us can have the file present just fine but not experience issues, people with the same hardware - one might be affected, the other not.

Amaze and Toyo both have 1070Ti's (unless Toyo's profile is outdated) and Amaze doesn't seem to have the issue.

 

check out the log file "C:\ProgramData\NVIDIA Corporation\nvtopps\nvtopps.log"
ever day I see a bunch of warnings and errors, here a one day cut and paste.
Since I have GTX970 non of the OC scanner stuff is supported.

PS: I don't have an issue with CPU usage.

Spoiler: nvtoppd.log

[00:18:23.330 2020/09/19]INFO: PmuDataMonitor::stop: gpu=0000000000000100
[06:39:01.311 2020/09/19]INFO: nvtopps initialize...
[06:39:01.311 2020/09/19]INFO: Num GPUs: 1
[06:39:01.311 2020/09/19]INFO: NvapiAdapter initialize succeeded
[06:39:01.311 2020/09/19]INFO: [NvModel::Model::initialize]INFO: NvTOPPS DB opened as C:\ProgramData\NVIDIA Corporation\nvtopps\nvtopps.db3
[06:39:01.327 2020/09/19]INFO: [NvModel::Model::initialize]INFO: NvTOPPS read-only DB opened as C:\Program Files\NVIDIA Corporation\Display.NvContainer\nvtopps.db3
[06:39:01.327 2020/09/19]INFO: model initialize succeeded
[06:39:01.327 2020/09/19]INFO: INFO! osPortGetNvContainerInstallPath: NvContainer install path: C:\Program Files\NVIDIA Corporation\Display.NvContainer\
[06:39:01.327 2020/09/19]INFO: INFO! osPortGetMessageBusConfigFilePath: MessageBus config path: C:\Program Files\NVIDIA Corporation\Display.NvContainer\messagebus_client.conf
[06:39:01.546 2020/09/19]INFO: PmuDataMonitor::initialize: gpu=0000000000000100
[06:39:01.640 2020/09/19]ERROR! Failed to initialize a worker
[06:39:01.640 2020/09/19]INFO: workerManager initialize succeeded
[06:39:01.655 2020/09/19]INFO: IpcDispatcher start 1
[06:39:01.655 2020/09/19]INFO: PmuDataMonitor::start: gpu=0000000000000100
[06:39:01.655 2020/09/19]WARNING! WARNING!PmuDataMonitor::setupPmumonClkdomains: clock domain sample monitoring not supported -104
[06:39:01.655 2020/09/19]WARNING! WARNING!PmuDataMonitor::setupPmumonVoltRails: volt raile sample monitoring not supported -104
[06:39:01.671 2020/09/19]WARNING! WARNING!PmuDataMonitor::setupPmumonPerfCfTopologies: utilization sample monitoring not supported -104
[06:39:01.671 2020/09/19]WARNING! WARNING!PmuDataMonitor::setupPmumonThermChannels: therm channel sample monitoring not supported -104
[06:39:01.671 2020/09/19]WARNING! WARNING!PmuDataMonitor::setupPmumonFanCoolers: fan cooler sample monitoring not supported -104
[06:39:01.671 2020/09/19]WARNING! WARNING!PmuDataMonitor::setupPmumonPerfPolicies: perf policy sample monitoring not supported -104
[06:39:01.671 2020/09/19]WARNING! WARNING!PmuDataMonitor::setupPmumonPwrChannels: power channel sample monitoring not supported -104
[06:39:01.671 2020/09/19]INFO: workerManager start 1
[06:39:01.671 2020/09/19]ERROR! NVAPI ERROR, Error code -104
[06:39:01.671 2020/09/19]ERROR! NVAPI ERROR message NVAPI_NOT_SUPPORTED
[06:39:01.843 2020/09/19]ERROR! NVAPI ERROR, Error code -104
[06:39:01.843 2020/09/19]ERROR! NVAPI ERROR message NVAPI_NOT_SUPPORTED
[06:39:01.843 2020/09/19]ERROR! NVAPI ERROR, Error code -104
[06:39:01.843 2020/09/19]ERROR! NVAPI ERROR message NVAPI_NOT_SUPPORTED
[06:39:01.858 2020/09/19]INFO: ScannerManager changing state to 4

 

so it tries 3 times, then determines the system isn't capable of OCScanner and shuts down.

@Amaze @toyo
Are your profiles up to date, Pascal should go to the same state as EdKiefers 970 after a few attempts.

if its constantly active though, it means someone forgot to change the logging level from "Informational" to "Warning/Error"

Do those affected have AfterBurner running?

 

It's a 1070ti, that log looks like this for today on my PC:

Code:

[05:17:46.477 2020/09/19]INFO: ScannerManager changing state to 4
[05:17:46.492 2020/09/19]INFO: PmuDataMonitor::stop: gpu=0000000000000100
[14:33:45.736 2020/09/19]INFO: nvtopps initialize...
[14:33:45.736 2020/09/19]INFO: Num GPUs: 1
[14:33:45.752 2020/09/19]INFO: NvapiAdapter initialize succeeded
[14:33:45.752 2020/09/19]INFO: [NvModel::Model::initialize]INFO: NvTOPPS DB opened as C:\ProgramData\NVIDIA Corporation\nvtopps\nvtopps.db3
[14:33:45.752 2020/09/19]INFO: [NvModel::Model::initialize]INFO: NvTOPPS read-only DB opened as C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_edf184f24a37bacd\Display.NvContainer\nvtopps.db3
[14:33:45.752 2020/09/19]INFO: model initialize succeeded
[14:33:45.752 2020/09/19]INFO: INFO! osPortGetNvContainerInstallPath: NvContainer install path: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_edf184f24a37bacd\Display.NvContainer\
[14:33:45.752 2020/09/19]INFO: INFO! osPortGetMessageBusConfigFilePath: MessageBus config path: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_edf184f24a37bacd\Display.NvContainer\messagebus_client.conf
[14:33:45.939 2020/09/19]INFO: PmuDataMonitor::initialize: gpu=0000000000000100
[14:33:46.189 2020/09/19]ERROR! Failed to initialize a worker
[14:33:46.189 2020/09/19]INFO: workerManager initialize succeeded
[14:33:46.189 2020/09/19]INFO: IpcDispatcher start 1
[14:33:46.189 2020/09/19]INFO: PmuDataMonitor::start: gpu=0000000000000100
[14:33:46.189 2020/09/19]WARNING! WARNING!PmuDataMonitor::setupPmumonClkdomains: clock domain sample monitoring not supported -104
[14:33:46.189 2020/09/19]WARNING! WARNING!PmuDataMonitor::setupPmumonVoltRails: volt raile sample monitoring not supported -104
[14:33:46.189 2020/09/19]WARNING! WARNING!PmuDataMonitor::setupPmumonPerfCfTopologies: utilization sample monitoring not supported -104
[14:33:46.189 2020/09/19]WARNING! WARNING!PmuDataMonitor::setupPmumonThermChannels: therm channel sample monitoring not supported -104
[14:33:46.189 2020/09/19]WARNING! WARNING!PmuDataMonitor::setupPmumonFanCoolers: fan cooler sample monitoring not supported -104
[14:33:46.189 2020/09/19]WARNING! WARNING!PmuDataMonitor::setupPmumonPerfPolicies: perf policy sample monitoring not supported -104
[14:33:46.189 2020/09/19]WARNING! WARNING!PmuDataMonitor::setupPmumonPwrChannels: power channel sample monitoring not supported -104
[14:33:46.189 2020/09/19]INFO: workerManager start 1
[14:33:46.517 2020/09/19]ERROR! NVAPI ERROR, Error code -104
[14:33:46.517 2020/09/19]ERROR! NVAPI ERROR message NVAPI_NOT_SUPPORTED
[14:33:46.533 2020/09/19]ERROR! NVAPI ERROR, Error code -104
[14:33:46.533 2020/09/19]ERROR! NVAPI ERROR message NVAPI_NOT_SUPPORTED
[14:33:47.236 2020/09/19]INFO: ScanStatusReporting initialize succeeded
[14:33:47.236 2020/09/19]INFO: ScanStatusReporting uninitialize succeeded

 

So if its not writing to the log, it must be the db3 file is being written reading constantly.

@toyo do you have the new afterburner beta, or gfe installed with experimental features enabled?

 

Just a heads up, this driver lacks the Divinity HAGS fix, Manuel has already seen feedback for it.

 

I have the last Beta but it's not running, doesn't start at boot etc.
GFE now has Share turned off completely from its toggle and nothing changes, still the same pattern. It's the beta, yes, and I rebooted a few times since Share is off.
And it's reads that are accumulating and cause those patterns, I replied on Unwinder's thread.

 

You know, I was going to go with reading based on the fact one of the 2 db3 files is opened as read only, but it threw me when the programdata copy wasn' opened as read only in the log.

 

Hi.. Guys..

Any RTX 3080 user here has the same issue with me?

- First time boot up after long shut down
once boot up to Windows then Black Screen (no Display output).
Need to power off then on again to be able to
boot up to Windows and have display on.

- World of Tanks total black screen (no Display output) with G-Sync on.
Need to turn off G-Sync in order to play.

- Horizon Zero Dawn blackscreen with Full screen mode
and bad screen flickering with Borderless mode.
It's not playable at all.

- Windows Desktop sometime show artifact on the screen.


Spec.
CPU: AMD Ryzen 7 3800X
MB: MSI MEG X570 ACE.
GPU: Zotac Gaming RTX 3080 Trinity 10GB
OS: Windows 10 Pro 2004 with HDR enabled.
Deplay: LG C9 55" OLED TV with Instant Response on.

 

A merge was missed on this driver regarding various Freesync and VRR displays, its fixed on the next one.

in the mean time turn off freesync/vrr on the tv side.

 

Forza Motsport 7 crashes now every time, it even crashes in the car select screen.
But the crashes are fixed with Soras nv Profile for FM7. https://forums.guru3d.com/threads/n...ownload-discussion.433202/page-7#post-5808276

So i guess the guys at nv are working on it

 

you should only need the 452 version of the nip file i made,

Setting ID_0x00acfcc0 = 0 is now in there as default, but 0x006D6197 = 0xA2B53761 is not

 

ya i only use this since the stutter fix in the driver

Code:

<?xml version="1.0" encoding="utf-16"?>
<ArrayOfProfile>
  <Profile>
    <ProfileName>Forza Motorsport 7</ProfileName>
    <Executeables>
      <string>microsoft.forzamotorsport7demo_8wekyb3d8bbwe</string>
      <string>microsoft.apollobasegame_8wekyb3d8bbwe</string>
    </Executeables>
    <Settings>
        <ProfileSetting>
        <SettingNameInfo />
        <SettingID>7168407</SettingID>
        <SettingValue>2729785185</SettingValue>
        <ValueType>Dword</ValueType>
      </ProfileSetting>
    </Settings>
  </Profile>
</ArrayOfProfile>

 

I noticed the issue with the two threads being hit 24/7 was back even though i used nvSlimmer, so i just deleted the topps.dll or whatever it's called and all seems well again.

 

Cheers.

Yup.
Cheers folks!

 

Thanks... That solved the in-game No Display output and Bad Screen Flickering issues
but 1st boot no display output after long shutdown still there.

 

Right click on your desktop, then left click on NVIDIA Control Panel. When the control panel opens, click on System Information (it's down in the lower left corner of the control panel); it will then show which version you are using.

Generally it is not a good idea to install DCH drivers over Standard drivers. DCH is a driver convention that Microsoft has been recommending (pushing), and Nvidia rolled over in a rather compliant manner. As far as I'm concerned, I always install the standard driver. And thankfully the standard drivers are still being made available. Additionally, it would seem that the DCH type drivers are being used (installed) by OEM computer manufacturers; so if you buy a new computer, more than likely DCH drivers have been preinstalled.

 

Shadow of the Tomb Raider crashes every time in DX12, RTX/DLSS/HAGS on or off don't matter at all, I can play for hours in DX11.

 

He was asking for advise - which drivers to install DCH or legacy.

 

Legacy gives you the full thing sans possibly some component slimming from third party utilities or doing it on your own for whatever bits can be removed and why.
DCH gives you the core driver and I think the idea is that the control panel is then handled as a Universal Windows Platform (UWP) package through the Microsoft Windows Store.

I like DCH myself but I prefer the traditional Windows32 software without splitting it up into app components though AMD doesn't do that despite supporting this model.
(Their driver installer also bundles both versions and on Redstone3 and newer builds of Windows 10 on a clean install DCH is the preferred that gets installed unless the user manually installs the standard or "legacy" driver variant.)

Going forward it sounds like Microsoft is tweaking it a bit but that's a gradual change over upcoming newer Win10 builds eventually I assume to entirely replace the current driver model with vendors like Intel and Realtek already onboard with this.
But for now classic/legacy mode seems like the most easy to use although once installed functionality should be identical.

EDIT: I am also not 100% on what parts NVIDIA has split the DCH driver model into aside from the way the control panel packaging is handled but aside from Microsoft guidelines and routines I would expect the core part to be mostly the same.

Though GeForce Experience and PhysX might be sidelined a bit maybe.
(Someone else will have a better answer for this I'm sure.)

There's also the Vulkan runtime but other than some log files it already installs to the Windows folder.
(Most of these can also be installed separately after the core driver installation.)

EDIT: And well UWP does support Win32 too now but the packages and paths and such is still kinda nested into the OS along with the sandboxing and encryption stuff.