GeForce Hotfix Driver Version 461.81

2 systems that have inherent DPC issues because of the mainboards used (confirmed back when they were originally reviewed)

Back off on the cpu overclock or raise the voltage.

 

I thought we were past DCH/etc 'branches'? Does it matter in any way, at all? Are there still glitches when installing one type over another, where the control panel would 'stick' and could have very minor changes causing buggy 'per app' stuff?

 

There are no issues with the DCH control panel. It's people that refuse to use Microsoft connections and do things like blocking the store. Or people that don't want to have a Microsoft account.

 

461.72 driver info:

https://www.guru3d.com/files-details/geforce-46721-40-whql-driver-download.html

If you read the last line of the second paragraph: “We recommend the normal driver and not DCH.”
Appears this line is only included in the WHQL drivers and not the hotfix drivers.

 

Im using MS store and I don't mind it anymore, actually prefer DCH now.

One time I installed it by accident and after that I saw there is no fuss about it.. lol I avoided it like the plague at first

 

I have used the DCH driver since it first became available with no problems/regrets. MS store was never a factor. Just curious why it is not recommended.

 

Me too. I would think the only reason to not recommed it is just to avoid potential Store problems in getting the control panel. Like when people disable the Store, or the Store itself has issues, or it has app installation issues, or the internet goes down, etc. Otherwise the driver and included crap is exactly the same.

 

465.42 is definitely faster by heavy fights @ destiny2. Now I was able to keep ao 3d and still get somewhat good fps, also more consistent.

 

I didn't know that about HDMI, thanks. And i wasn't demanding anything or from Nvidia specifically - it was hoping someone would say something along the lines of "yeah sure you can use CRU to hack out the video part of a display like this...".

 

No idea, that's not Nvidia saying it. @Hilbert Hagedoorn Any opinion you want to provide on this?

 

If for what ever reason you don't like DCH you still got the option getting the standard driver.

 

Ah OK, thanks! Thing is for the last couple of weeks I've heard some popping when I wear my headphones (HyperX Cloud II) and there is no sound playback. It's very quiet which is why I cannot hear it when playing games or listening to Youtube. Also I only hear it sometimes which is why I thought that my headphones were simply going bad.

 

DCH works just fine. Even slimming it down is becoming pointless. And blocking a lot of that stuff will almost always lead to problems with your OS. Sucks but it's the way things are. Big info gonna be big info until we reign them in with some universal standards.

 

Hmm, I tested 461.51 with Latencymon just now. 0.485ms is all I get. Been on them for a good month. Never encountered any sound popping. About to test the latest driver...


_________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system appears to be suitable for handling real-time audio and other tasks without dropouts.
LatencyMon has been analyzing your system for 0:07:31 (h:mm:ss) on all processors.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name:
OS version: Windows 10, 10.0, version 2009, build: 19042 (x64)
Hardware: Z490 AORUS XTREME, Gigabyte Technology Co., Ltd.
CPU: GenuineIntel Intel(R) Core(TM) i9-10900K CPU @ 3.70GHz
Logical processors: 20
Processor groups: 1
RAM: 65453 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 3696 MHz

Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N
Quiet in the BIOS setup for more accurate results.


_________________________________________________________________________________________________________
MEASURED INTERRUPT TO USER PROCESS LATENCIES
_________________________________________________________________________________________________________
The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the moment the
interrupt service routine started execution. This includes the scheduling and execution of a DPC routine, the signaling of an event and the waking up of a
usermode thread from an idle wait state in response to that event.

Highest measured interrupt to process latency (µs): 426.70
Average measured interrupt to process latency (µs): 7.061015

Highest measured interrupt to DPC latency (µs): 385.50
Average measured interrupt to DPC latency (µs): 2.418278


_________________________________________________________________________________________________________
REPORTED ISRs
_________________________________________________________________________________________________________
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): 318.517316
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

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

Total time spent in ISRs (%) 0.003635

ISR count (execution time <250 µs): 14326
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-1000 µs): 6
ISR count (execution time 1000-2000 µs): 0
ISR count (execution time 2000-4000 µs): 0
ISR count (execution time >=4000 µs): 0


_________________________________________________________________________________________________________
REPORTED DPCs
_________________________________________________________________________________________________________
DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted
until the DPC has finished execution.

Highest DPC routine execution time (µs): 485.399892
Driver with highest DPC routine execution time: CLASSPNP.SYS - SCSI Class System Dll, Microsoft Corporation

Highest reported total DPC routine time (%): 0.001913
Driver with highest DPC total execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 461.51 , NVIDIA Corporation

Total time spent in DPCs (%) 0.004149

DPC count (execution time <250 µs): 46811
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-10000 µs): 8
DPC count (execution time 1000-2000 µs): 0
DPC count (execution time 2000-4000 µs): 0
DPC count (execution time >=4000 µs): 0

________________________________________________________________________



Results from 461.81. 0.221856 ms nvldmkm.sys, 1096 DPC count.
_________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system appears to be suitable for handling real-time audio and other tasks without dropouts.
LatencyMon has been analyzing your system for 0:11:02 (h:mm:ss) on all processors.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name:
OS version: Windows 10, 10.0, version 2009, build: 19042 (x64)
Hardware: Z490 AORUS XTREME, Gigabyte Technology Co., Ltd.
CPU: GenuineIntel Intel(R) Core(TM) i9-10900K CPU @ 3.70GHz
Logical processors: 20
Processor groups: 1
RAM: 65453 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 3696 MHz

Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N
Quiet in the BIOS setup for more accurate results.


_________________________________________________________________________________________________________
MEASURED INTERRUPT TO USER PROCESS LATENCIES
_________________________________________________________________________________________________________
The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the moment the
interrupt service routine started execution. This includes the scheduling and execution of a DPC routine, the signaling of an event and the waking up of a
usermode thread from an idle wait state in response to that event.

Highest measured interrupt to process latency (µs): 442.70
Average measured interrupt to process latency (µs): 6.289455

Highest measured interrupt to DPC latency (µs): 402.10
Average measured interrupt to DPC latency (µs): 2.060894


_________________________________________________________________________________________________________
REPORTED ISRs
_________________________________________________________________________________________________________
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): 189.053571
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

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

Total time spent in ISRs (%) 0.000291

ISR count (execution time <250 µs): 1703
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-1000 µs): 0
ISR count (execution time 1000-2000 µs): 0
ISR count (execution time 2000-4000 µs): 0
ISR count (execution time >=4000 µs): 0


_________________________________________________________________________________________________________
REPORTED DPCs
_________________________________________________________________________________________________________
DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted
until the DPC has finished execution.

Highest DPC routine execution time (µs): 421.472944
Driver with highest DPC routine execution time: ndis.sys - Network Driver Interface Specification (NDIS), Microsoft Corporation

Highest reported total DPC routine time (%): 0.000599
Driver with highest DPC total execution time: ndis.sys - Network Driver Interface Specification (NDIS), Microsoft Corporation

Total time spent in DPCs (%) 0.002342

DPC count (execution time <250 µs): 69480
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-10000 µs): 31
DPC count (execution time 1000-2000 µs): 0
DPC count (execution time 2000-4000 µs): 0
DPC count (execution time >=4000 µs): 0

 

Try the same playing Warzone or black ops ^

 

Fix your computer Neil, nobody else is going to.

 

Idk what pixelated black dots issue has been fixed in rdr2 (single player) in this driver, but i still got fast artifact-like black glitches when moving cursor (choosing between outfits) in outfits menu no matter where: at the camp, shop or hunter and sometimes when skinning animals when moving a mouse.
6700k
gtx1080
aoc G2260VWQ6 freesync (g-sync compatible's working)
win10pro 2004
Vulkan
been on 461.09 before, it was the same, other than that everything seems fine.

 

This will be fixed in the next branch, the next driver is the last of 461.

 

Nvidia can take their telemetry, and a broken light bulb, and shove it up their collective urethras. As for GFE and all that other nonsense, *those* are the things that 'lead to problems with your OS'. You can always do everything better with Reshade and other assorted tools.

 

Yeah, got in a little bit of a hurry when I said that everything seems fine, not fine, in this driver 461.81 in RDR2 horse's mane started to disappear when moving camera or simply walking around - https://imgur.com/a/bnO7MmF - couple of comparisson shots


Thankfully rolling back to 461.01 fixed it, as I thought, cuz like for over 150 hours in game I haven't seen this bug before. Nice evening to u 2 nvidia thumbs up lol