cancel
Showing results for 
Search instead for 
Did you mean: 

Drivers & Software

genervter
Journeyman III

RadeonSettings.exe hogging a CPU core after Factory Reset and even for freshly created user accounts

I'm on Win10 20H2 with current WHQL driver 20.11.2. with a VEGA56 on a Threadripper 1920X in 2x32GB NUMA mode.

One CPU core is fully "claimed" (kept busy) by RadeonSettings.exe.

With Process Explorer I see 1 Thread of RadeonSettings.exe eating up CPU cycles of 1 full core.

My setup is fresh and NOT corrupt (see Subject).

ProcessExplorer ***online*** stackdump of Thread is constantly related to Qt5Core.dll!QFileInfo::exists+0x204 with varying functions called from that point (presumably in a loop). There seems to be an endless busy-wait which needs to be fixed via an end-condition and/or intermediate millisecond wait steps!

Following finding might be (REMOTELY!) related (similar kind of bug, but probably different area of code - I have an AMD Vega 56 and full driver suite installed): https://www.techpowerup.com/274967/psa-amds-graphics-driver-will-eat-one-cpu-core-when-no-radeon-ins...

1st refresh of stackdump:

ntoskrnl.exe!KeSynchronizeExecution+0x5b66
ntoskrnl.exe!KeWaitForMutexObject+0x1460
ntoskrnl.exe!KeWaitForMutexObject+0x98f
ntoskrnl.exe!KeWaitForMutexObject+0x233
ntoskrnl.exe!ExWaitForRundownProtectionRelease+0x7dd
ntoskrnl.exe!KeWaitForMutexObject+0x3a29
ntoskrnl.exe!KiCheckForKernelApcDelivery+0x2b
ntoskrnl.exe!MmUnlockPages+0x152f
ntoskrnl.exe!NtLockFile+0xeb6
ntoskrnl.exe!NtSetInformationProcess+0x7c8
ntoskrnl.exe!setjmpex+0x7ce8
ntdll.dll!ZwSetInformationProcess+0x14
KERNELBASE.dll!SetErrorMode+0x4a
Qt5Core.dll!QLockFile::unlock+0x1937
Qt5Core.dll!QFileInfo::exists+0x204
Radeonsoftware.exe+0x237662
Radeonsoftware.exe+0x217163
Radeonsoftware.exe+0x1bdac8
Radeonsoftware.exe+0x1caa45
Radeonsoftware.exe+0x120a39
ucrtbase.dll!configthreadlocale+0x92
KERNEL32.DLL!BaseThreadInitThunk+0x14
ntdll.dll!RtlUserThreadStart+0x21


2nd refresh of stackdump:

ntoskrnl.exe!KeSynchronizeExecution+0x5b66
ntoskrnl.exe!KeWaitForMutexObject+0x1460
ntoskrnl.exe!KeWaitForMutexObject+0x98f
ntoskrnl.exe!KeWaitForMutexObject+0x233
ntoskrnl.exe!ExWaitForRundownProtectionRelease+0x7dd
ntoskrnl.exe!KeWaitForMutexObject+0x3a29
ntoskrnl.exe!KiCheckForKernelApcDelivery+0x2b
ntoskrnl.exe!KeLeaveCriticalRegion+0x38
ReFS.SYS+0x191731
FLTMGR.SYS!FltIsCallbackDataDirty+0xc2d
FLTMGR.SYS!FltQueryInformationFile+0x621
ntoskrnl.exe!NtAllocateLocallyUniqueId+0x244
ntoskrnl.exe!NtDeviceIoControlFile+0x2290
ntoskrnl.exe!SeOpenObjectAuditAlarmWithTransaction+0x58ce
ntoskrnl.exe!ObOpenObjectByNameEx+0x1fa
ntoskrnl.exe!NtCreateFile+0xd5e
ntoskrnl.exe!setjmpex+0x7ce8
ntdll.dll!NtQueryFullAttributesFile+0x14
KERNELBASE.dll!GetFileAttributesExW+0x9c
Qt5Core.dll!QLockFile::unlock+0x197b
Qt5Core.dll!QFileInfo::exists+0x204
Radeonsoftware.exe+0x237662
Radeonsoftware.exe+0x217163
Radeonsoftware.exe+0x1bdac8
Radeonsoftware.exe+0x1caa45
Radeonsoftware.exe+0x120a39
ucrtbase.dll!configthreadlocale+0x92
KERNEL32.DLL!BaseThreadInitThunk+0x14
ntdll.dll!RtlUserThreadStart+0x21


3rd refresh of stackdump:

ntoskrnl.exe!KeSynchronizeExecution+0x5b66
ntoskrnl.exe!KeWaitForMutexObject+0x1460
ntoskrnl.exe!KeWaitForMutexObject+0x98f
ntoskrnl.exe!KeWaitForMutexObject+0x233
ntoskrnl.exe!ExWaitForRundownProtectionRelease+0x7dd
ntoskrnl.exe!KeWaitForMutexObject+0x3a29
ntoskrnl.exe!KiCheckForKernelApcDelivery+0x2b
ntoskrnl.exe!MmUnlockPages+0x152f
ntoskrnl.exe!NtLockFile+0xeb6
ntoskrnl.exe!NtSetInformationProcess+0x7c8
ntoskrnl.exe!setjmpex+0x7ce8
ntdll.dll!ZwSetInformationProcess+0x14
KERNELBASE.dll!SetErrorMode+0x4a
Qt5Core.dll!QLockFile::unlock+0x1b76
Qt5Core.dll!QFileInfo::exists+0x204
Radeonsoftware.exe+0x237662
Radeonsoftware.exe+0x217163
Radeonsoftware.exe+0x1bdac8
Radeonsoftware.exe+0x1caa45
Radeonsoftware.exe+0x120a39
ucrtbase.dll!configthreadlocale+0x92
KERNEL32.DLL!BaseThreadInitThunk+0x14
ntdll.dll!RtlUserThreadStart+0x21

 

0 Likes
0 Replies