• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

**THE NVIDIA DRIVERS THREAD**

ever since i had the 551.23 driver installed iv noticed the screen go randomly black for 2 seconds then comes back on. didnt happen to me when playing cyberpunk, happens when usually web browsing or sometimes just desktop idle.
anyone else experience this?
whats really odd is that when it happens i check event viewer and there is no record there of a driver tdr crash.
Yes, exactly the same for me, fine in games but browsing seems to trigger it.
 
DPC latency monitoring, it's below 1000 now but it still spikes for the Nvidia driver. Although I see that interrupt to process Latency is much higher, although it doesn't exactly show what caused the high interrupt to process Latency, or is that a total of all metrics and thus the total latency?

WhRmI7G.png


Code:
-------------------------------------
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):   3988.90
Average measured interrupt to process latency (µs):   9.108401

Highest measured interrupt to DPC latency (µs):       666.50
Average measured interrupt to DPC latency (µs):       2.658740


-------------------------------------
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):              499.261496
Driver with highest ISR routine execution time:       HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation

Highest reported total ISR routine time (%):          0.003820
Driver with highest ISR total time:                   HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation

Total time spent in ISRs (%)                          0.005877

ISR count (execution time <250 µs):                   167596
ISR count (execution time 250-500 µs):                0
ISR count (execution time 500-1000 µs):               3
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):              966.746814
Driver with highest DPC routine execution time:       nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 551.46 , NVIDIA Corporation

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

Total time spent in DPCs (%)                          0.041287

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


-------------------------------------
REPORTED HARD PAGEFAULTS
-------------------------------------
Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped file on disk. The process of resolving the hard pagefault requires reading in the memory from disk while the process is interrupted and blocked from execution.

NOTE: some processes were hit by hard pagefaults. If these were programs producing audio, they are likely to interrupt the audio stream resulting in dropouts, clicks and pops. Check the Processes tab to see which programs were hit.

Process with highest pagefault count:                 msmpeng.exe

Total number of hard pagefaults                       1556
Hard pagefault count of hardest hit process:          667
Number of processes hit:                              15
 
Inb4 Nvidia drivers are still dated and ****! :p

About time they done this tbf. I got no issues with the UI and usability but hated having it split across 2 applications essentially.
Yea this mirrors my thoughts. I don't mind it looking dated, it mostly worked. Though I agree with Tim on HUB that control panel can be slow. The biggest and worst thing was as you said - it was spread over 2 different apps. Though I also don't like the fact you needed an account.
Hopefully they don't take as long as say MS has moving stuff out of Control Panel and moving it to settings - or worse moving things about for 'reasons'. It'd happily take control panel modernised to work better but everything left in the same locations, with it being combined with GE.
 
Oh man, video capture in games now does 120fps capture, finally!

At least there will be a smooth motion playback experience capturing at above 60fps when playing back on YouTube etc.
 
Last edited:
All smooth so far, Echoing Ayahuasca's experience, The RTX HDR feature is very nice. Just missing a few things in the control panel now like the RTX Video and a few other bits but very promising so far for a beta.

The stats display is nice but Nvidia still seem to be incapable of showing the user GPU memory usage, Something Afterburner has done for years and GPU temp is incorrect, Showing 31'c with Afterburner showing 51'c.
 
Last edited:
Wonder if people will still use driver control panel as a reason to sticking to certain brand now ;) Also, what happened to gamers are no longer a priority for nvidia since AI is the focus
:p Just goes to show, gamers aren't forgotten as nvidia are still delivering like crazy with likes of ray reconstruction, RTX hdr and now this.

I'll probably give them a go later.
 
Last edited:
  • Haha
Reactions: TNA
Hmm using the new overlay I get a crash in Cyberpunk back to desktop, the crash log states a DX12 call error, so assuming maybe some sort of conflict with the new overlay style or something. Might even be the new driver as I did both at the same time.

BETA testing like a right chump :o
 
Hmm using the new overlay I get a crash in Cyberpunk back to desktop, the crash log states a DX12 call error, so assuming maybe some sort of conflict with the new overlay style or something. Might even be the new driver as I did both at the same time.

BETA testing like a right chump :o

Think I'll hold of on testing now then :p

RTX HDR is an absolute game changer but I can just use the mod version for the time being so in no rush as never go into the CP :p
 
Back
Top Bottom