Geforce Rtx 3060 Drivers Windows 10

[Yiraika Daimaru]

Sincedriver version 516.94, i am experiencing unconditional random audio dropouts, pops and crackles when working with my audio software.

During my research, i have ruled out any of the common reasons for such behaviour.

Finally, i joined a thread at some forum, where a bunch of people already discussed the issue.

Update #1 (October 7th, 2022): this thread has evolved as we all learned more about the issue. It turns out there appears to be a problem in Windows or the Nvidia drivers that is causing huge DPC spikes, and all of Google has no solutions, though...

I have an identical issue as the user above in terms of audio degradation, which presents itself when the nvidia driver is installed (for my 3060ti card). It seems that the drivers have an nvlddmkm.sys file that exhibits a high DPC which causes these latency/audio degradation issues.

Please can you investigate this issue seriously, as it seems to be quite a prevalent issue affecting users in slightly different ways. Please see the link in OPs post to the nlite website to see how long some users have been pursuing this (over 6+ months). On Reddit and other sites, people have had this issue for over a year, and it remains unresolved!

I have been looking at the links you shared and tried to get a bit more information. And I tried the (single) tool that most people are using to measure this. I have used it on one Intel system and did not see any issues. I used it on another and the tool showed no issues in one run and 1-2ms latency in another. I used it on three systems with AMD CPUs and saw no issue at all.

This may be helpful. I unplugged all unnecessary USB hardware then benchmarked different drivers and interrupt options. I used the studio drivers as presumably that is what most folks noticing this problem may use. All runs were for 5 minutes for comparability and after a reboot.

The big difference is moving the driver to another core than the default core as DPCs and total execution times drop to less than a third for both drivers. It is non-linear in behaviour so the problem is the 1.35mS DPC because with that delay sound is likely to glitch otherwise unlikely to be noticed. The problem is seen to be in the later drivers because the 10% DPC/ 15% execution time penalty with default core interrupts manifests the problem (at least for me).

Same problem for me, I was using the AMD 5700G with integrated video had no problem, I bought a RTX 3050 and after that the sound from the monitor seems to be bursting with echo, using my soundbar on the Optica output I have no problems. I reversed the monitors and put other cables with the same problem, returning to using my integrated graphics the problem disappears, in addition to noticing that when this happens the DCP has high latency!

The crackling and pops were so constant that I thought I had some sort of grounding issue on my room, I went as far as replacing my entire audio system and isolating the machine from any other electric device.

I tried this with different RAM sticks and NVMe models from different vendors and the results were consistent across all of them. I was able to get less audio cracks with newer DDR5 sticks that have lower latency.

Another way to replicate the issue is trying to use the system with only 1 stick of ram, the audio will be unbearable despite the overall system being responsive (running IDEs, debuggers and other demanding software).

From what I saw, the problems are likely to be linked with task scheduling. Limiting the RAM frequency and capacity seems to be the best way to recreate the problem. Slowing down the drives seems to have a significant impact as well.

For example, you can have a nearly idle system with only few tools open, it will appear responsive but the audio will be unbearable and filled with cracks and pops. Setting the priority of the audio services & processes seems to make the experience better but still noticeably bad.

While playing around with some AI stuff, i tried a variety of CUDA toolkits.

They also include drivers, which are not available from the regular download page.

So i was able to narrow down the versions thing a bit.

As some suspected this is not as simple as just the driver doing something it should not. OS, system drivers, audio drivers all play into this as well. Meaning root causing is extremely hard. I am on CC of the internal bug that is addressing this and lately I receive between 10 and 20 messages on the topic every single day.

Checking NVIDIA Proprietary drivers boots up to black screen it mentions that initcall_blacklist=simpledrm_platform_driver_init should be in the boot command. This does not appear to be the case, as when I run cat /proc/cmdline:

For testing purposes, I removed the nvidia drivers and got back to a functional desktop. When I tried logging out the Wayland session and logging into the X11 session, the screen remained black for 10 seconds and then kicked me back to the login screen. This is unusual as when I was using the Radeon GPU the X11 session worked fine.

The issue with nouveau is that nouveau is a reverse engineered driver for nvidia devices. This means that developers must wait until a new GPU is released then they must make an attempt to determine how to create a driver that allows the kernel to use the new hardware without any information nor support from the manufacturer.

Not all features of the GPU are supported on any of the cards and newer cards have even more changes that the developers of nouveau have not been able to keep up with. As I understand it the 3XXX and 4XXX series of GPUs are supported very poorly if at all. Developers are caught between the rapid pace of kernel development on one side and new hardware development on the other side.

An update to this; Fedora 40 released with changes indicating it would drop X11 and switch wholly to Wayland. I was hesitant but given the situation, I wanted to try updating to see if it would fix this problem. And it did! I upgraded to Fedora 40, and after rebooting I was in a Wayland session in KDE. Great!

I have a very similar issue, except that the black screen and white cursor mostly appear after Fedora boot on Wayland and Gnome Classic. On Gnome on Xorg, which I was using before the last updates, I see the overview of all desktops, just like if I was holding a super-key. I can move the cursor with my mouse, but the cursor is shifted and when clicking it will click not the area the cursor was on, but other spots of the auto-started app (Steam in my case). Once I clicked randomly and succeeded to close not only Steam, but also all other auto-started apps (Thunderbird, Joplin). However, I was never able to open SELinux (its orange icon is showing after every boot in on the top right), Software app or Terminal. Launching these apps did not work by using keyboard, neither. PC shutdown was also never working without a hard reset (holding the computer power button). Booting up old kernels made no difference. The issue is holding me away from using Fedora approximately for one month now. I only can use Windows on my dual-boot Lenovo Legion G5 Desktop with Nvidia RTX 3060.

nando4>> If this topic helps to get your eGPU working, then pls consider completing and submitting a build template to feature on the builds area of the site and give your system & eGPU combo representation there, referencing any specific fixes here that may have been a requirement to do so.

USB4 systems have stricter USB4-certified cable requirements where these are confirmed to give full performance: Anker 515 1m USB4 cable, Belkin Connect USB4 cable, Cable Matters 40Gbps USB4 cable, Orico 2m active TB3, Satechi USB4 Pro cable, Spigen 0.8m USB4 cable, SKY USB4 4k 240w cable, Ultunite USB4 cable.

If you have a Windows 10 or Windows 11 eGPU System and are suffering from blue screens, crashing, system freezes or stuttering, there are a couple of universal solutions you can try. These solutions have helped me on multiple occasions, across a variety of systems. Unlike BIOS options that are device-specific, these are generic solutions that can be applied to any Windows system:

Systems that have an integrated discrete GPU from the same vendor as the external GPU will often BSOD or disable one of the graphics devices due to Driver Conflicts upon eGPU installation. This can be resolved by following the correct installation procedure:

Link State Power Management is a Windows System Policy that mandates power saving for PCIe devices. This can usually be accessed in the Advanced Settings of the Windows Power Options. Details to do this are below:

If you are suffering from microstuttering after applying the above fixes, there is a small chance that disabling dynamicktick will fix it. Dynamicktick is a Windows feature that enables the system to temporarily suspend the system timer when it is not under load to conserve power. Details below:

If you are having a stuttering issue with a specific game and a modern Nvidia GPU, a possible solution is to use the third party application Nvidia Profile Inspector to disable Resizable BAR for that title:

TH3P4 Thunderbolt GPU Dock Review

TH3P4G2 Thunderbolt GPU Dock Review

Wikingoo Thunderbolt GPU Dock Review

DIY Portable Custom Water Cooled Thunderbolt 3 eGPU

OSMETA GK01 OCuLink eGPU Review and Installation Guide

Thunderbolt 4 Docks, eGPU Daisy Chaining and the One-Cable Dream

Windows 10/11 Solutions for eGPU BSOD, Crashing, System Freezing and Stuttering

Adding Advanced Power Management Options to Windows Laptops for Performance, Thermal Throttling & Power Management

Conversely, same issue but no luck with the same setup on my previous host, a Razer Stealth 12.5" 7500U on which I had tried pretty much anything mentioned above, and more (including swapping PSU/enclosure/GPU, updating BIOS, using a UPS, DCH Vs. non-DCH drivers, disabling fast startup, enabling Ultimate Perf power plan, etc. etc. you name it).

So I guess with some hardware it might just be unavoidable.

3a8082e126