USB Slots cause input lag

[icancanakci]

Hey. I've recently bought an Alienware 17 R4 with 120hz QHD screen. I'm happy with the performance but there are some weird things that happen. First of all, after a few hours, I notice a little performance loss. It only happens in certain games: Overwatch and Black Ops 3 and a few indie titles. There is no throttling, the max heat my gpu gets is 65c and cpu gets max 60c. There is something else %100, when I restart the pc it goes away for another 2-3 hours. My real problem is that my USB slots seem to cause MOUSE DELAY or INPUT LAG, which is annoying in Overwatch for exemple. when I move the USB connection a little bit, it changes the delay. There is a sweetspot, if I move it even a little bit I get lag in my mouse. This applies for both of the USB slots.

I have v sync off
My mouse's polling rate is fine
Resolution is native
Drivers are up to date

 

[webworkings]

If this is happening on a new device, there is either something wrong with the mouse you have connected, or there is something wrong with the port. If it is the port, then it is under warranty and I would contact the manufacturer.

 

[icancanakci]

MERGED QUESTION
Question from icancanakci : "Moving the USB cable causes input lag"

I've already created 2 threads about kind of the same issue but 2 months later no suggestions except "sending it to service"

Here's the problem, this time I'll try to make it clearer. When I move the mouse's USB entrance, I get huge input lag (mouse lag) spikes. It's so frustrating to try and find a sweetspot and even then it's not perfect. There are 2 USB A ports and one USB C port in my laptop, tried all of them except the USB C slot since the mice that I used are all using USB A. I've tried with 5-6 different surfaces including 3 different mouse pads, 3 different mice that are all high-end, same issue. Now what I'm asking first, is it possible for a USB slot to have connectivity issues but still dedect the device and work almost properly? I mean the mouse is usable but there is high latency. If not, what causes extra delay when I physically move the USB cable. Any help except "send it to service pffs" is appreciated.

PS. Please don't bind this with the other 2 threads since I talked about different stuff on the other threads.

 

[fagetti]

Try with another mouse and report back. Are both USB-A ports side By side? I mean close to each other. Sometimes USB board is gone bad like this : https/www.aliexpress.com/item/Original-laptop-USB-interface-board-Sound-card-board-with-cable-for-HP-ProBook-450-G2-455/32804401378.html

 

[fagetti]

if USB A ports are other sides of laptop then USB board going bad is not the problem. try reinstalling mouse drivers

 

[icancanakci]

As I said before, I've tried with 3 different mice now. They are all high-end "gaming" mice so they should have no delay normally. Also no, one of the USB A is on the left side with the USB C and the other USB A is on the right side.

 

[fagetti]

Download latencymon search it google. It shows what driver exactly is causing the latency. Start it and check for high latencys ( red)

 

[fagetti]

It could already register lag when you cant feel it but defindetly when it happens keep it backround and check afterwards. send screenshots if needed

 

[icancanakci]

Ok. I ran the software and here is the STATS page after running a 2 minute test.

CONCLUSION
_________________________________________________________________________________________________________
Your system seems to have 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. At least one detected problem appears to be network related. In case you are using a WLAN adapter, try disabling it to get better results. 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:02:57 (h:mm:ss) on all processors.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: DESKTOP-6P2SC6D
OS version: Windows 8 , 6.2, build: 9200 (x64)
Hardware: Alienware 17 R4, Alienware
CPU: GenuineIntel Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
Logical processors: 8
Processor groups: 1
RAM: 16253 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 2808.0 MHz
Measured CPU speed: 3160.0 MHz (approx.)

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): 541.172704
Average measured interrupt to process latency (µs): 4.126603

Highest measured interrupt to DPC latency (µs): 538.620002
Average measured interrupt to DPC latency (µs): 1.529797


_________________________________________________________________________________________________________
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): 321.352564
Driver with highest ISR routine execution time: ndis.sys - Network Driver Interface Specification (NDIS), Microsoft Corporation

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

Total time spent in ISRs (%) 0.083449

ISR count (execution time <250 µs): 138342
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 1
ISR count (execution time 1000-1999 µs): 0
ISR count (execution time 2000-3999 µ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): 1840.586895
Driver with highest DPC routine execution time: DDDriver64Dcsa.sys - DDDriver.sys, Dell Inc.

Highest reported total DPC routine time (%): 0.131680
Driver with highest DPC total execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

Total time spent in DPCs (%) 0.458450

DPC count (execution time <250 µs): 1053828
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 764
DPC count (execution time 1000-1999 µs): 8
DPC count (execution time 2000-3999 µ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.


Process with highest pagefault count: none

Total number of hard pagefaults 0
Hard pagefault count of hardest hit process: 0
Highest hard pagefault resolution time (µs): 0.0
Total time spent in hard pagefaults (%): 0.0
Number of processes hit: 0


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 11.763935
CPU 0 ISR highest execution time (µs): 201.273504
CPU 0 ISR total execution time (s): 0.735121
CPU 0 ISR count: 76955
CPU 0 DPC highest execution time (µs): 1840.586895
CPU 0 DPC total execution time (s): 3.444357
CPU 0 DPC count: 842357
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 7.424304
CPU 1 ISR highest execution time (µs): 321.352564
CPU 1 ISR total execution time (s): 0.444526
CPU 1 ISR count: 61081
CPU 1 DPC highest execution time (µs): 526.977920
CPU 1 DPC total execution time (s): 1.213125
CPU 1 DPC count: 67869
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 5.948449
CPU 2 ISR highest execution time (µs): 126.629274
CPU 2 ISR total execution time (s): 0.003133
CPU 2 ISR count: 307
CPU 2 DPC highest execution time (µs): 1315.971510
CPU 2 DPC total execution time (s): 0.914467
CPU 2 DPC count: 42978
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 6.013804
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): 496.972222
CPU 3 DPC total execution time (s): 0.136731
CPU 3 DPC count: 24773
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 4.811641
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): 511.782764
CPU 4 DPC total execution time (s): 0.157381
CPU 4 DPC count: 23012
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 5.868225
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): 559.068376
CPU 5 DPC total execution time (s): 0.328842
CPU 5 DPC count: 17064
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 4.332964
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): 533.790242
CPU 6 DPC total execution time (s): 0.188018
CPU 6 DPC count: 22845
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 4.808388
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): 472.535969
CPU 7 DPC total execution time (s): 0.115008
CPU 7 DPC count: 13702

 

[icancanakci]

Just ran another 2 min test, I changed nothing. Also played Overwatch for like 5 mins after each test and I can say that the input lag still exists. I think a software like this couldn't detect the latency I'm having because I think it's some connectivity issue within the USB slots, so the lag is BEFORE a signal goes into the system from the mouse. But Im not sure if that is possible. As I said, is it possible to have a USB slot working properly but having latency caused by the connectivity? Anyways, here is the second test:

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:02:00 (h:mm:ss) on all processors.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: DESKTOP-6P2SC6D
OS version: Windows 8 , 6.2, build: 9200 (x64)
Hardware: Alienware 17 R4, Alienware
CPU: GenuineIntel Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
Logical processors: 8
Processor groups: 1
RAM: 16253 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 2808.0 MHz
Measured CPU speed: 3566.0 MHz (approx.)

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): 335.497903
Average measured interrupt to process latency (µs): 4.349541

Highest measured interrupt to DPC latency (µs): 305.230157
Average measured interrupt to DPC latency (µs): 1.221174


_________________________________________________________________________________________________________
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): 17.954060
Driver with highest ISR routine execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

Highest reported total ISR routine time (%): 0.000091
Driver with highest ISR total time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

Total time spent in ISRs (%) 0.000091

ISR count (execution time <250 µs): 501
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 0
ISR count (execution time 1000-1999 µs): 0
ISR count (execution time 2000-3999 µ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): 744.665242
Driver with highest DPC routine execution time: ndis.sys - Network Driver Interface Specification (NDIS), Microsoft Corporation

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

Total time spent in DPCs (%) 0.105384

DPC count (execution time <250 µs): 360236
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 96
DPC count (execution time 1000-1999 µs): 0
DPC count (execution time 2000-3999 µ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.


Process with highest pagefault count: none

Total number of hard pagefaults 0
Hard pagefault count of hardest hit process: 0
Highest hard pagefault resolution time (µs): 0.0
Total time spent in hard pagefaults (%): 0.0
Number of processes hit: 0


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 6.777684
CPU 0 ISR highest execution time (µs): 17.954060
CPU 0 ISR total execution time (s): 0.000877
CPU 0 ISR count: 501
CPU 0 DPC highest execution time (µs): 466.388533
CPU 0 DPC total execution time (s): 0.761503
CPU 0 DPC count: 331016
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 6.752642
CPU 1 ISR highest execution time (µs): 0.0
CPU 1 ISR total execution time (s): 0.0
CPU 1 ISR count: 0
CPU 1 DPC highest execution time (µs): 437.447293
CPU 1 DPC total execution time (s): 0.021152
CPU 1 DPC count: 2978
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 5.112717
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): 738.614316
CPU 2 DPC total execution time (s): 0.093202
CPU 2 DPC count: 7501
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 7.558811
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): 331.371439
CPU 3 DPC total execution time (s): 0.010165
CPU 3 DPC count: 1515
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 3.725843
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): 502.511396
CPU 4 DPC total execution time (s): 0.070269
CPU 4 DPC count: 9026
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 8.100787
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): 57.660969
CPU 5 DPC total execution time (s): 0.002138
CPU 5 DPC count: 602
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 4.460881
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): 744.665242
CPU 6 DPC total execution time (s): 0.049354
CPU 6 DPC count: 6739
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 7.964367
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): 257.800926
CPU 7 DPC total execution time (s): 0.004695
CPU 7 DPC count: 955
_________________________________________________________________________________________________________

 

[fagetti]

go to device manager, and open system devices. There should be something called "Dell Diag Control Device" and "Dell System Analyzer Control Device" disable those and go gaming or do another test.

 

[fagetti]

Also go to control panel and unstall a program. Delete all Dell related programs from there.

EDIT: Post another latencymon report afterwards

 

[icancanakci]

Alright uninstalling all of them. Will try the latencymon in like 10 mins

 

[fagetti]

just came from work im here for couple of hours and can help

 

[fagetti]

If this is the solution you might update them back accidentally by dell updates or windows update, disabling dell updates is possible but you can miss on something like new bios updates which can be helpful so you need to check those manually. Here is how :

https/www.dell.com/community/Windows-10/how-to-disable-Dell-Updates/td-p/5072443

Dont disable windows update completely but change it to download updates but ask you before installing. In time you will see if those dell programs are recommended or optional updates. If only optional you can put automatic install and update in windows update

 

[icancanakci]

Ok so here it is. Now I must say, I was browsing web while running this test but I don't think that would affect the test much. The test states that I should disable WLAN adapter, but since this is a laptop that I use in many different places, disabling WLAN will make it a lot harder for me to stay connected to internet.


CONCLUSION
_________________________________________________________________________________________________________
Your system seems to have 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. At least one detected problem appears to be network related. In case you are using a WLAN adapter, try disabling it to get better results. 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:03:01 (h:mm:ss) on all processors.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: DESKTOP-6P2SC6D
OS version: Windows 8 , 6.2, build: 9200 (x64)
Hardware: Alienware 17 R4, Alienware
CPU: GenuineIntel Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
Logical processors: 8
Processor groups: 1
RAM: 16253 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 2808.0 MHz
Measured CPU speed: 3579.0 MHz (approx.)

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): 496.319541
Average measured interrupt to process latency (µs): 4.654477

Highest measured interrupt to DPC latency (µs): 427.031728
Average measured interrupt to DPC latency (µs): 1.426455


_________________________________________________________________________________________________________
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): 57.164530
Driver with highest ISR routine execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

Highest reported total ISR routine time (%): 0.002532
Driver with highest ISR total time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

Total time spent in ISRs (%) 0.002543

ISR count (execution time <250 µs): 20383
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 0
ISR count (execution time 1000-1999 µs): 0
ISR count (execution time 2000-3999 µ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): 1342.805912
Driver with highest DPC routine execution time: ndis.sys - Network Driver Interface Specification (NDIS), Microsoft Corporation

Highest reported total DPC routine time (%): 0.044382
Driver with highest DPC total execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

Total time spent in DPCs (%) 0.176527

DPC count (execution time <250 µs): 406646
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 199
DPC count (execution time 1000-1999 µs): 1
DPC count (execution time 2000-3999 µ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.


Process with highest pagefault count: none

Total number of hard pagefaults 0
Hard pagefault count of hardest hit process: 0
Highest hard pagefault resolution time (µs): 0.0
Total time spent in hard pagefaults (%): 0.0
Number of processes hit: 0


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 6.040922
CPU 0 ISR highest execution time (µs): 57.164530
CPU 0 ISR total execution time (s): 0.034375
CPU 0 ISR count: 18778
CPU 0 DPC highest execution time (µs): 690.319801
CPU 0 DPC total execution time (s): 1.819668
CPU 0 DPC count: 332044
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 3.946433
CPU 1 ISR highest execution time (µs): 27.550214
CPU 1 ISR total execution time (s): 0.002579
CPU 1 ISR count: 1605
CPU 1 DPC highest execution time (µs): 462.076211
CPU 1 DPC total execution time (s): 0.088148
CPU 1 DPC count: 7354
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 3.391836
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): 1342.805912
CPU 2 DPC total execution time (s): 0.181089
CPU 2 DPC count: 15883
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 4.378640
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): 590.311610
CPU 3 DPC total execution time (s): 0.044477
CPU 3 DPC count: 4686
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 3.375890
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): 795.482194
CPU 4 DPC total execution time (s): 0.099724
CPU 4 DPC count: 13026
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 3.508475
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): 661.794872
CPU 5 DPC total execution time (s): 0.060190
CPU 5 DPC count: 7204
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 3.202080
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): 848.339031
CPU 6 DPC total execution time (s): 0.201693
CPU 6 DPC count: 20077
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 4.443230
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): 887.092593
CPU 7 DPC total execution time (s): 0.069943
CPU 7 DPC count: 6572
_________________________________________________________________________________________________________

 

[icancanakci]

I'll try it with Overwatch for like 10 mins, will report back here.

 

[fagetti]

Remember to reboot after uninstalling programs and did you disable "Dell Diag Control Device" and "Dell System Analyzer Control Device" both in device manager under system devices?

 

[fagetti]

you can leave latencymon in the backround just start with play button after opening it. Hmm ndis is networking driver. Are you using Wifi or ethernet cable connected? Are you using VPN of any sort ?

 

[fagetti]

also download malwarebytes root kit beta and malwarebytes, boot into safe mode and run those