Why is the Task Manager acting sluggish or slow in this situation?
Why is the Task Manager acting sluggish or slow in this situation?
I've been experiencing this issue since day one, across multiple versions of Windows 11 (22H2, 23H2, 24H2).
The
Task Manager
becomes slow and unresponsive whenever I use
USB-tethering
from my phone. This doesn't happen immediately after enabling tethering, it usually takes 1 to 5 minutes. After that, it stays sluggish and buggy until I disconnect the tethering. During this time, the Task Manager is almost unusable.
In the first video, you can see that the
performance graphs
are not updating in real time, and there's a noticeable
delay
when trying to close the Task Manager. The
Ethernet graph
is also missing.
Video: Has Lag/Delay
(or)
Video: Has Lag/Delay
The second video was recorded right after connecting via Ethernet, before the Task Manager begins to act up.
Video: No Lags/Delay
(or)
Video: No Lags/Delay
Do you have a connection to either the front or back panel USB port?
This part is clear. What model and make of your laptop are you asking about?
It's a Lenovo IdeaPad Gaming 3 15ARH7 with Ryzen 5-7535HS, RTX 3050 6GB, 16 GB RAM, 120 Hz.
My earlier laptop, Lenovo IdeaPad Gaming 3 15IMH05, i5-10300H, GTX 1650 4GB, 16 GB RAM, 120 Hz, also faced the same issue (just in case it's relevant).
I've experimented with various phones and cables, but nothing worked.
I've noticed comparable problems when connected USB devices draw excessive power from the USB port.
Your experience with several phones and laptops, along with multiple Windows installations, seems unusual.
With your present laptop, do you think you've tested different USB ports? Accurate?
Additionally, how many other USB devices are connected during tethering?
If you rely on Wi-Fi tethering, does the issue disappear? Correct?
Yes, I have tried USB Type-A as well as Type-C ports present on the laptop.
Most of the time, I use a wired mouse. But then again, I have 2 of them and have tried both of them on both the laptops.
Sometimes an HDD too. Other times I just use the touchpad with only the USB-tethering enabled.
Yes, the problem goes away as soon as I disconnect the cable
OR
turn off tethering and switch to something else like MTP (file transfer).
I haven't noticed any patterns yet. But I have tried using 2 different drivers for the RNDIS (USB-Tethering). One of them is the default Windows-provided "
Remote NDIS based Internet Sharing Device
" driver (which is the default one that is used after a fresh Windows install or in similar setups). This driver for some reason gave me BSOD today (
for the first time, and this BSOD has never happened on the older laptop
). I managed to pull the details from the dump.
Spoiler:
Contents of the BSOD dump file:
Code:
11: kd> !analyze -v
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
...................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught. This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, BugChecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 0000000000000062, A driver has forgotten to free its pool allocations prior to unloading.
Arg2: ffff898fcd3062f0, name of the driver having the issue.
Arg3: ffff898faf6c3dd0, verifier internal structure with driver information.
Arg4: 0000000000000001, total # of (paged+nonpaged) allocations that weren't freed.
Type !verifier 3 drivername.sys for info on the allocations
that were leaked that caused the bugcheck.
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1796
Key : Analysis.Elapsed.mSec
Value: 5504
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 1
Key : Analysis.IO.Write.Mb
Value: 0
Key : Analysis.Init.CPU.mSec
Value: 281
Key : Analysis.Init.Elapsed.mSec
Value: 46784
Key : Analysis.Memory.CommitPeak.Mb
Value: 108
Key : Analysis.Version.DbgEng
Value: 10.0.27871.1001
Key : Analysis.Version.Description
Value: 10.2505.01.02 amd64fre
Key : Analysis.Version.Ext
Value: 1.2505.1.2
Key : Bugcheck.Code.LegacyAPI
Value: 0xc4
Key : Bugcheck.Code.TargetModel
Value: 0xc4
Key : Failure.Bucket
Value: 0xc4_62_VRF_LEAKED_POOL_IMAGE_RNDISMP6.SYS
Key : Failure.Hash
Value: {7eff5a6a-1a45-b6e6-cf67-aac94dd1d3c5}
Key : Hypervisor.Enlightenments.ValueHex
Value: 0x1497cf94
Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 1
Key : Hypervisor.Flags.ApicEnlightened
Value: 1
Key : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 0
Key : Hypervisor.Flags.AsyncMemoryHint
Value: 0
Key : Hypervisor.Flags.CoreSchedulerRequested
Value: 0
Key : Hypervisor.Flags.CpuManager
Value: 1
Key : Hypervisor.Flags.DeprecateAutoEoi
Value: 0
Key : Hypervisor.Flags.DynamicCpuDisabled
Value: 1
Key : Hypervisor.Flags.Epf
Value: 0
Key : Hypervisor.Flags.ExtendedProcessorMasks
Value: 1
Key : Hypervisor.Flags.HardwareMbecAvailable
Value: 1
Key : Hypervisor.Flags.MaxBankNumber
Value: 0
Key : Hypervisor.Flags.MemoryZeroingControl
Value: 0
Key : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0
Key : Hypervisor.Flags.NoNonArchCoreSharing
Value: 1
Key : Hypervisor.Flags.Phase0InitDone
Value: 1
Key : Hypervisor.Flags.PowerSchedulerQos
Value: 0
Key : Hypervisor.Flags.RootScheduler
Value: 0
Key : Hypervisor.Flags.SynicAvailable
Value: 1
Key : Hypervisor.Flags.UseQpcBias
Value: 0
Key : Hypervisor.Flags.Value
Value: 4853999
Key : Hypervisor.Flags.ValueHex
Value: 0x4a10ef
Key : Hypervisor.Flags.VpAssistPage
Value: 1
Key : Hypervisor.Flags.VsmAvailable
Value: 1
Key : Hypervisor.RootFlags.AccessStats
Value: 1
Key : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 1
Key : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 1
Key : Hypervisor.RootFlags.DisableHyperthreading
Value: 0
Key : Hypervisor.RootFlags.HostTimelineSync
Value: 1
Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0
Key : Hypervisor.RootFlags.IsHyperV
Value: 1
Key : Hypervisor.RootFlags.LivedumpEnlightened
Value: 1
Key : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 1
Key : Hypervisor.RootFlags.MceEnlightened
Value: 1
Key : Hypervisor.RootFlags.Nested
Value: 0
Key : Hypervisor.RootFlags.StartLogicalProcessor
Value: 1
Key : Hypervisor.RootFlags.Value
Value: 1015
Key : Hypervisor.RootFlags.ValueHex
Value: 0x3f7
Key : WER.OS.Branch
Value: ni_release_svc_prod3
Key : WER.OS.Version
Value: 10.0.22621.2506
BUGCHECK_CODE: c4
BUGCHECK_P1: 62
BUGCHECK_P2: ffff898fcd3062f0
BUGCHECK_P3: ffff898faf6c3dd0
BUGCHECK_P4: 1
FILE_IN_CAB: 083125-25734-01 - Copy.dmp
TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b
FAULTING_THREAD: ffff898fb86950c0
IMAGE_NAME: RNDISMP6.SYS
MODULE_NAME: RNDISMP6
FAULTING_MODULE: fffff80247470000 RNDISMP6
VERIFIER_DRIVER_ENTRY: dt nt!_MI_VERIFIER_DRIVER_ENTRY ffff898faf6c3dd0
Symbol nt!_MI_VERIFIER_DRIVER_ENTRY not found.
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
PROCESS_NAME: System
LOCK_ADDRESS: fffff8021b275c20 -- (!locks fffff8021b275c20)
Resource @ nt!PiEngineLock (0xfffff8021b275c20) Exclusively owned
Contention Count = 30
Threads: ffff898fb86950c0-01<*>
1 total locks
PNP_TRIAGE_DATA:
Lock address : 0xfffff8021b275c20
Thread Count : 1
Thread address: 0xffff898fb86950c0
Thread wait : 0x4b86
STACK_TEXT:
ffffc10d`ab8feda8 fffff802`1abeecfb : 00000000`000000c4 00000000`00000062 ffff898f`cd3062f0 ffff898f`af6c3dd0 : nt!KeBugCheckEx
ffffc10d`ab8fedb0 fffff802`1abed937 : 00000000`00000000 fffff802`1aa54a80 fffff802`1aa54a80 00000000`00000000 : nt!CarInitiateBugcheck+0x47
ffffc10d`ab8fedf0 fffff802`1b0e734c : 00000000`000000c4 00000000`00000002 00000000`b574cb00 00000001`00000001 : nt!CarReportRuleViolationForTriage+0x147
ffffc10d`ab8fee70 fffff802`1b0f40d8 : ffff898f`af6c3dd0 ffffc10d`ab8fefc0 ffff898f`cd306190 ffff898f`c57f7b40 : nt!VerifierBugCheckIfAppropriate+0xc8
ffffc10d`ab8fef10 fffff802`1aa8b11f : ffff898f`af6c3dd0 00000000`00000001 00000000`00000001 ffff898f`c57f7b20 : nt!VfPoolCheckForLeaks+0x4c
ffffc10d`ab8fef50 fffff802`1b0d6f12 : 00000000`00012000 ffff898f`cd306190 fffff802`1b250070 fffff802`1b250070 : nt!VfTargetDriversRemove+0x267923
ffffc10d`ab8fefd0 fffff802`1acaf61e : ffff898f`cd306190 ffffc10d`ab8ff100 00000000`ffffffff 00000000`00000001 : nt!VfDriverUnloadImage+0x3e
ffffc10d`ab8ff000 fffff802`1ae02712 : ffff898f`00000001 00000000`ffffffff 00000000`00000012 fffffb7c`0123a380 : nt!MiUnloadSystemImage+0x322
ffffc10d`ab8ff1e0 fffff802`1acaf687 : 00000000`00000000 ffff898f`cd305a90 ffffc10d`ab8ff310 00000000`00000001 : nt!MiDereferenceSingleImport+0x2a
ffffc10d`ab8ff210 fffff802`1acaf061 : 00000000`00000001 ffffd40e`ffffffff 00000000`0000000e fffffb7c`0123a300 : nt!MiUnloadSystemImage+0x38b
ffffc10d`ab8ff3f0 fffff802`1ae77830 : 00000000`00000000 00000000`fffffff7 00000000`00000000 ffff898f`8d4fa740 : nt!MmUnloadSystemImage+0x41
ffffc10d`ab8ff420 fffff802`1ad427ce : 00000000`00000000 ffff898f`b6885e00 00000000`00000000 ffff898f`b6885e00 : nt!IopDeleteDriver+0x40
ffffc10d`ab8ff470 fffff802`1a84a603 : 00000000`00000000 00000000`00000000 00000000`fffffff7 ffff898f`b6885e30 : nt!ObpRemoveObjectRoutine+0x7e
ffffc10d`ab8ff4d0 fffff802`1ada740f : ffff898f`94254020 00000000`00000000 ffffd40e`b4d80d20 fffff802`1a842662 : nt!ObfDereferenceObject+0x93
ffffc10d`ab8ff510 fffff802`1ad427ce : ffff898f`94254020 ffff898f`a9850860 ffff898f`a9850860 ffff898f`8d4fa740 : nt!IopDeleteDevice+0x4f
ffffc10d`ab8ff540 fffff802`1a84a603 : 00000000`00000000 00000000`00000000 00000000`fffffff7 ffff898f`94254050 : nt!ObpRemoveObjectRoutine+0x7e
ffffc10d`ab8ff5a0 fffff802`1a9cf83d : ffff898f`b5775b70 00004a7f`5bc3d330 00000000`00000200 00000000`0000000a : nt!ObfDereferenceObject+0x93
ffffc10d`ab8ff5e0 fffff802`1ae8140a : ffff898f`a9850860 ffff898f`b5775b70 00000000`00000000 00000000`00000000 : nt!PnpRemoveLockedDeviceNode+0x251
ffffc10d`ab8ff640 fffff802`1ae8118b : ffff898f`b5775b70 ffffc10d`ab8ff6c0 ffff898f`a9850860 fffff802`1b275c00 : nt!PnpDeleteLockedDeviceNode+0x52
ffffc10d`ab8ff680 fffff802`1ae9a811 : ffff898f`b8cc0d40 00000000`00000002 ffff898f`9b241dd0 00000000`00000001 : nt!PnpDeleteLockedDeviceNodes+0xd3
ffffc10d`ab8ff700 fffff802`1ae9a734 : ffff898f`9b241d90 ffffc10d`ab8ff780 ffff898f`b8cc0d40 00000000`00000000 : nt!PipRemoveDevicesInRelationList+0x95
ffffc10d`ab8ff750 fffff802`1ae9a431 : ffff898f`9b241d90 00000000`00000001 ffffd40e`ea1f9e30 ffffc10d`ab8ff8a9 : nt!PnpDelayedRemoveWorker+0x114
ffffc10d`ab8ff790 fffff802`1a9ec8d2 : 00000000`00000001 00000000`00000000 00000000`00000000 fffff802`1b275c80 : nt!PnpChainDereferenceComplete+0xf9
ffffc10d`ab8ff7c0 fffff802`1ae80699 : 00000000`00000002 ffffc10d`ab8ff800 00000000`00000003 00000000`00000001 : nt!PnpIsChainDereferenced+0xb2
ffffc10d`ab8ff830 fffff802`1adad475 : ffffc10d`ab8ff970 ffff898f`b898db00 ffff898f`95ef2700 ffffd40e`00000002 : nt!PnpProcessQueryRemoveAndEject+0x291
ffffc10d`ab8ff910 fffff802`1ad9fafa : ffffd40e`f3e91ad0 ffffd40e`dd42a050 ffff898f`87d1ea00 00000000`00000000 : nt!PnpProcessTargetDeviceEvent+0x109
ffffc10d`ab8ff940 fffff802`1a8d7bc5 : ffff898f`87d1eaa0 ffff898f`b86950c0 ffffc10d`ab8ffac0 fffff802`00000000 : nt!PnpDeviceEventWorker+0x2ca
ffffc10d`ab8ff9c0 fffff802`1a924777 : ffff898f`b86950c0 00000000`00000af5 ffff898f`b86950c0 fffff802`1a8d7a70 : nt!ExpWorkerThread+0x155
ffffc10d`ab8ffbb0 fffff802`1aa3c154 : ffffc201`35451180 ffff898f`b86950c0 fffff802`1a924720 bdbdbdbd`bdbdbdbd : nt!PspSystemThreadStartup+0x57
ffffc10d`ab8ffc00 00000000`00000000 : ffffc10d`ab900000 ffffc10d`ab8f9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34
IMAGE_VERSION: 10.0.22621.4034
STACK_COMMAND: .process /r /p 0xffff898f87db2040; .thread 0xffff898fb86950c0 ; kb
FAILURE_BUCKET_ID: 0xc4_62_VRF_LEAKED_POOL_IMAGE_RNDISMP6.SYS
OS_VERSION: 10.0.22621.2506
BUILDLAB_STR: ni_release_svc_prod3
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {7eff5a6a-1a45-b6e6-cf67-aac94dd1d3c5}
Followup: MachineOwner
Spoiler:
Driver details:
Code:
11: kd> lm vm RNDISMP6
Browse full module list
start end module name
fffff802`47470000 fffff802`47482000 RNDISMP6 # (export symbols) RNDISMP6.SYS
Loaded symbol image file: RNDISMP6.SYS
Mapped memory image file: C:\ProgramData\Dbg\sym\RNDISMP6.SYS\6DA940D612000\RNDISMP6.SYS
Image path: \SystemRoot\System32\drivers\RNDISMP6.SYS
Image name: RNDISMP6.SYS
Browse all global symbols functions data Symbol Reload
Image was built with /Brepro flag.
Timestamp: 6DA940D6 (This is a reproducible build file hash, not a timestamp)
CheckSum: 0001E1C9
ImageSize: 00012000
File version: 10.0.22621.4034
Product version: 10.0.22621.4034
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.6 Driver
File date: 00000000.00000000
Translations: 0409.04b0
Information from resource tables:
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: RNDISMP6.SYS
OriginalFilename: RNDISMP6.SYS
ProductVersion: 10.0.22621.4034
FileVersion: 10.0.22621.4034 (WinBuild.160101.0800)
FileDescription: Remote NDIS Miniport
LegalCopyright: © Microsoft Corporation. All rights reserved.
Then the other times I have used the Samsung's USB drivers (
SAMSUNG Mobile USB Remote NDIS Network Device
) which gets auto-installed via Windows Updates when it detects the phone connected. It has never crashed. But the task manager lag is more frequent on this one.
Thanks
I've tested two different phones as well. I also enabled and disabled the fast-charging option in the settings.
This might help, Comment #8