Overview
The information message shows that the Windows Kernel call failed to change CPU affinity for a particular instance of the application. This is not an error, as it is expected for the fallback mechanism to initiate shortly.
Event examples
See some examples of the Kernel call fallback Event messages:
- Task "Optimize res" Action "Tweak App" kernel call fallback for "Google Chrome" with PID 3536:0xC000000D.
- Action "Tweak App" kernel call fallback for "Microsoft Edge" with PID 4216:0xC000000D.
Notes
Process identifier and Windows Kernel status code is provided along with the message.
The Kernel call modifies the CPU affinity for the entire process, including newly spawned threads within that process. In contrast, the fallback mechanism affects only the active threads, requiring the reinforcement of CPU affinity for any new threads spawned by the application.
When the Kernel call for changing CPU pinning fails, it usually means that Windows Task Manager also fails with the Access Denied error message. However, Tweak App Action shows a detailed reason for the failure instead of showing a generic Access Denied error.
Help at your fingertips…
If you have any questions, please do not hesitate to contact our support team.