Services.exe spikes up every so often

Hi! first time poster here.
For the past three or four days, I've been experiencing CPU spikes caused by Services.exe.
It occurs every 10-15 minutes and CPU usage goes up to 80-90%, this lasts 10-20 seconds and it goes back to normal.
I would use restore points but it was not available.
I ran xperf and it clearly shows spikes of services.exe.
It is bearable but annoying nonetheless.
I would really appreciate any help.
The .etl file is here.

Below are my computer specs.
I have not installed 22H2 as most of XPS15 devices are unable to install it due to BIOS issues(?)

Device: XPS15 7590
CPU: Intel(R) Core(TM) i5-9300H CPU @ 2.40GHz 2.40 GHz
RAM: 8.00 GB
Graphics card: Nvidia GeForce 1650X

Windows version
Windows 11 Home
OS build: 22000.1574
Windows Feature Experience Pack 1000.22000.1574.0

I decided to clean install with 22H2 with Virtualized I/O turned OFF in BIOS settings(XPS 15 Problem).
After windows updates, Microsoft Store Updates and essential apps installed, the problem seems to persist though it feels like the spike effect is slightly less severe.
So it could be Windows update problem itself but I am not sure.
I will post my .etl file as soon as I am successful to capture that spike.

Windows Version(Updated):
Windows 11 Home
OS Build 22621.1265
Windows Feature Experience Pack 1000.22638.1000.0

My added startups are:
Autorun Organizer

After clean installing, the problem still persists.
Before, the problem was noticeable no matter what I do (mouse movements stutters, video stops etc).
But this time, it feels like the problem happens only when I am playing Rocket League(the only resource heavy game I regularly play) or only noticeable when I'm playing it.
I suspected Bakkesmod(rocket league mod) to be the root cause but after disabling, the spike still existed.
Second .etl file after clean installing (Playing Rocket League) is here.

The effect was unnoticeable but it did happen when I was not playing games.
Third .etl file is here.
I found a problem. My service called "Dell Techhub" was the main culprit.
Also "Dell Client Management service" was slightly contributing to the problem.
Thank you all for your support!