Hi Sharyn,
"I can't use 'admin' access to do anything" => this detail makes sense and actually reinforces the point that this isn’t something you can fix yourself without admin rights. The fact that your IT team has already been screen‑sharing and still can’t see the culprit in Task Manager suggests the load is coming from a kernel driver or a scheduled system task that doesn’t show up in user‑mode tools. What they need to do is capture a performance trace with Windows Performance Recorder or xperf during the spike and then analyze it in Windows Performance Analyzer. That will expose the exact thread or driver consuming CPU. Without that trace, they’re guessing.
Since you can’t run those tools, the best way forward is to ask them to check Task Scheduler for recurring jobs around noon, especially under \Microsoft\Windows\Defender and telemetry tasks, and to verify whether endpoint security agents are configured to run scans at that time. If the trace confirms it’s Defender or another agent, the supported fix is to adjust the scan schedule via Group Policy or the vendor’s management console. If it points to kernel time in ntoskrnl.exe without a clear process, then they should investigate memory stability and disk I/O from encryption or DLP agents. The key is: don’t swap hardware again, insist on a proper performance trace so they can stop chasing shadows.
I hope it's helpful to you. Have a nice day!
Harry.