okay, since I need to do clean win10 install anyway, I did some testing of different drivers mentioned in this thread

a) standard windows 10 driver - well, it works but latency is just awful as you would expect
b) asio4all - safe choice, good latency but it's annoying to use in daw, as all other soundsources such as web browser or music player are muted
c) UMC-Driver_4-59-0 - it doesn't support umc22, readme says it's for umc202 and higher, umc22 doesn't work after installing this one
d) BEHRINGER_2902_X64_2.8.40 - the best option from my experience, I can get even lower latency without crackles than asio4all while running heavy project. I prefer to use it in relaxed normal mode (selectable in driver control panel), since it gives me good enough latency (12ms) and when cpu is struggling there is way way less audio pops than in faster modes. Allows audio playback in the background as well, bye asio4all

I've also tested "fl studio asio", but it's not very good on my system, latency is basically the same as standard win10 driver

 

1- I think so, I never bothered so much in installing motherboard drivers, but Driver Booster says its ok, I'm gonna search on it site, and thanks for the driver
2-I'm using Windows 10 last update, and I think I did, not really anything running on background unless Nvidia GE and IDM
3- Sadly I don't :c

 

The tools LatencyMon and WhySoSlow from Resplendence sometimes might help pinpoint what might be causing problems. Not always, but at this point I think it's worth a shot.

 

Yeah, I updated some drivers and I definetly am seeing a better performance , now its on 83% on fl studio asio and asio4all
Fl Studio Asio now perform better than ASIO4ALL

 

I found it pretty strange that my CPU in-daw is 90% (98% on the project peak) and in windows it shows not even 50%
Also I found that the main problem on performance is when I try to use a instance of Guitar Rig 6, maybe it doesnt support multi-core processing?

 

I also uploaded this video of the project running with Guitar Rig 6 on and off with FL studio asio
https://we.tl/t-tFKq7LGC2C

 

This is LatencyMon test result after running the entire project as I switch between on and off with Guitar Rig 6 and opening/closing browser

nvm

CONCLUSION
_________________________________________________________________________________________________________
Your system seems to be having difficulty handling real-time audio and other tasks. You may experience drop outs, clicks or pops due to buffer underruns. One or more DPC routines that belong to a driver running in your system appear to be executing for too long. One problem may be related to power management, disable CPU throttling settings in Control Panel and BIOS setup. Check for BIOS updates.
LatencyMon has been analyzing your system for 0:05:43 (h:mm:ss) on all processors.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: DESKTOP-H6KF251
OS version: Windows 10, 10.0, version 2009, build: 19042 (x64)
Hardware: X99-8M-F, HUANANZHI X99
CPU: GenuineIntel Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz
Logical processors: 12
Processor groups: 1
RAM: 16225 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 2394 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): 891,90
Average measured interrupt to process latency (µs): 6,995434

Highest measured interrupt to DPC latency (µs): 887,70
Average measured interrupt to DPC latency (µs): 2,175624


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

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

Total time spent in ISRs (%) 0,069726

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

Highest reported total DPC routine time (%): 0,050102
Driver with highest DPC total execution time: Wdf01000.sys - Tempo de Execução da Estrutura de Driver em Modo Kernel, Microsoft Corporation

Total time spent in DPCs (%) 0,114870

DPC count (execution time <250 µs): 404357
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-10000 µs): 101
DPC count (execution time 1000-2000 µs): 2
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: system

Total number of hard pagefaults 5925
Hard pagefault count of hardest hit process: 1396
Number of processes hit: 44


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 11,541094
CPU 0 ISR highest execution time (µs): 895,291980
CPU 0 ISR total execution time (s): 2,821311
CPU 0 ISR count: 151227
CPU 0 DPC highest execution time (µs): 1029,200501
CPU 0 DPC total execution time (s): 4,208388
CPU 0 DPC count: 337737
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 1,538311
CPU 1 ISR highest execution time (µs): 191,300752
CPU 1 ISR total execution time (s): 0,050293
CPU 1 ISR count: 6353
CPU 1 DPC highest execution time (µs): 824,309524
CPU 1 DPC total execution time (s): 0,203613
CPU 1 DPC count: 13398
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 1,923998
CPU 2 ISR highest execution time (µs): 0,0
CPU 2 ISR total execution time (s): 0,0
CPU 2 ISR count: 0
CPU 2 DPC highest execution time (µs): 273,416040
CPU 2 DPC total execution time (s): 0,071209
CPU 2 DPC count: 12500
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 0,902870
CPU 3 ISR highest execution time (µs): 0,0
CPU 3 ISR total execution time (s): 0,0
CPU 3 ISR count: 0
CPU 3 DPC highest execution time (µs): 59,744361
CPU 3 DPC total execution time (s): 0,012193
CPU 3 DPC count: 2728
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 1,228210
CPU 4 ISR highest execution time (µs): 0,0
CPU 4 ISR total execution time (s): 0,0
CPU 4 ISR count: 0
CPU 4 DPC highest execution time (µs): 295,867168
CPU 4 DPC total execution time (s): 0,038335
CPU 4 DPC count: 7316
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 0,947920
CPU 5 ISR highest execution time (µs): 0,0
CPU 5 ISR total execution time (s): 0,0
CPU 5 ISR count: 0
CPU 5 DPC highest execution time (µs): 56,067669
CPU 5 DPC total execution time (s): 0,010107
CPU 5 DPC count: 2326
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 1,260551
CPU 6 ISR highest execution time (µs): 0,0
CPU 6 ISR total execution time (s): 0,0
CPU 6 ISR count: 0
CPU 6 DPC highest execution time (µs): 362,192982
CPU 6 DPC total execution time (s): 0,039214
CPU 6 DPC count: 6992
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 0,906512
CPU 7 ISR highest execution time (µs): 0,0
CPU 7 ISR total execution time (s): 0,0
CPU 7 ISR count: 0
CPU 7 DPC highest execution time (µs): 51,553885
CPU 7 DPC total execution time (s): 0,010788
CPU 7 DPC count: 2371
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s): 1,068604
CPU 8 ISR highest execution time (µs): 0,0
CPU 8 ISR total execution time (s): 0,0
CPU 8 ISR count: 0
CPU 8 DPC highest execution time (µs): 422,265664
CPU 8 DPC total execution time (s): 0,028944
CPU 8 DPC count: 4527
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s): 1,821769
CPU 9 ISR highest execution time (µs): 0,0
CPU 9 ISR total execution time (s): 0,0
CPU 9 ISR count: 0
CPU 9 DPC highest execution time (µs): 149,560150
CPU 9 DPC total execution time (s): 0,040131
CPU 9 DPC count: 5762
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s): 1,316786
CPU 10 ISR highest execution time (µs): 0,0
CPU 10 ISR total execution time (s): 0,0
CPU 10 ISR count: 0
CPU 10 DPC highest execution time (µs): 72,126566
CPU 10 DPC total execution time (s): 0,037733
CPU 10 DPC count: 5118
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s): 1,084664
CPU 11 ISR highest execution time (µs): 0,0
CPU 11 ISR total execution time (s): 0,0
CPU 11 ISR count: 0
CPU 11 DPC highest execution time (µs): 132,736842
CPU 11 DPC total execution time (s): 0,030192
CPU 11 DPC count: 3685

 

These are the key messages:

"Driver with highest DPC routine execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 461.40 , NVIDIA Corporation"
"Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation"

So graphics drivers both, and a cursory googling says that this is most probably a GPU or chipset issue. Maybe try reinstalling Nvidia and chipset drivers, and then disabling "NVIDIA GE" you say you're using (though I've no clue what that is)?

Some people had BIOS issues, but they were using different mainboards.

 

Also, did you try running WhySoSlow? It can help finding rogue background processes.

 

It just says "No problem detected so far"

 

Nvidia Geforce Experience
Hmmm, I perceived my GTX 770 getting GTA V a little bit laggy, now I'm almost sure that my graphics card is diyng, but could be it whats interfering?

 

It's been a while since I've had a NVidia card but I remember always disabling Experience, can't remember why though.

Do you have any other GPU to try? I know it's a longshot, but something is amiss here.

 

Sadly I don't, Im unnistalling everything from nvidia to see if it changes something

 

Download the latest driver package for your card from Nvidia, then download the NV Slimmer utility to reinstall just the driver and not all the resource greedy Nvidia bloatware - which has telemetry BS too. I did this and my 1070Ti performance is much better now.

EDIT:
I'm sure you have already, but do make sure you've used ShutUp10 etc to remove/turn-off unwanted microsoft shit too.

 

Last edited: Feb 21, 2021

Reinstall your Windows bro, that is the only solution i see so far, none of us have problems like yours with the interface, Latencymon also says that you have problems with the system.

 

these are still the same drivers as listed above, Behringer stuff is inexpensive so didn't bother making specific drivers for each device but made generic ones for many of their devices.I use them for my UCG-102 and they are fine no problems, I use it with guitar amp sims on Win 7 Ultimate for practicing with headphones at night so as not to disturb anyone.

 

Im reliving this thread to say that I bought Scarlett Solo from Focusrite and I tested em both in the things that would make a difference for me, so here is what I think about em:

1- Scarlett drivers are WAY better than UMC22 , not just by the simple fact that they actually exists but because they work great without ASIO, its just plug it into your computer, download the driver on focusrite site and you are done.

2- Scarlett is more responsive and can achieve a lower latency and also a lower buffer size (up to 32, 1ms)

3- Behringer supports both XLR (wich scarlett also supports) and 1/4 inch cable (p10) on it microphone input.

4- Behringer speakers output can go WAY louder than Scarlett

5- Scarlett is smaller than behringer, and have all the inputs/outputs knobs & metters (in fact it has even an "air" button that I think it does a high frequencies boost)

6- Scarlett doesnt let me change it volume on FL Studio withouth using the knob that is in the interface, I can change my volume on windows normally, but not in FL, even that FL and windows are using the same driver

7- None of them really do a improvement in performance, but they in fact have somehow a cleaner high-end compared to 3,5mm jack from motherboard

So, after all, if you are not using it for recording a vocal, theres not really much difference between em other than the drivers and the latency (1ms of difference, but considering that UMC22 have the lowest latency of 2,5ms its more than 50% of latency difference)

 

Last edited: Feb 28, 2021

Thanks for pointing this out, i am searching for a good interface, and i think i will go with the UMC22 this time, i had the UM2 but changed it for a Vocal 300 that now i want to sell because its not so good...
2.5 ms of latency is more than enough anyway, at 1ms of latency you will get issues like noises, high CPU usage, etc. so its not worth it.

 

Incredibly I didnt got heally much spikes at 1ms in a new project, but in a more complex project its really impossible to use it with 1ms of latency