User Profile

Macbook Pro 13"Mojave 10.14.62.3 GHz intel i5 (quad core)8 GB RAM 512 GBYesterday I stupidly and accidentally deleted a folder labeled OS X. Now my CPU has been riding sky high, the idle wake ups in the activity monitor are in the thousands, once going as high as 1.4 million idle wake ups for kernel task.I took it into Apple care and they did a full restore and it seemed to be fine there, but as I'm home again it's happening all over again.In the system log I've found (and apologies for the lack of code block, it seems to not be working for me):BUG in libdispatch client: mach_recv, monitored resource vanished before the source cancel handler was invoked { 0x7f7edd4233e0[source], ident: 162823 / 0x27c07, handler: 0x105b5040e }Feb 1 12:32:23 MacBook-Pro systemstats[36]: DEPRECATED USE in libdispatch client: dispatch source activated with no event handler set; set a breakpoint on _dispatch_bug_deprecated to debugFeb 1 12:32:59 MacBook-Pro airportd[152]: DEPRECATED USE in libdispatch client: dispatch source activated with no event handler set; set a breakpoint on _dispatch_bug_deprecated to debugFeb 1 12:33:03 MacBook-Pro kcm[323]: DEPRECATED USE in libdispatch client: Setting timer interval to 0 requests a 1ns timer, did you mean FOREVER (a one-shot timer)?; set a breakpoint on _dispatch_bug_deprecated to debugFeb 1 12:33:04 MacBook-Pro usernoted[367]: DEPRECATED USE in libdispatch client: dispatch source activated with no event handler set; set a breakpoint on _dispatch_bug_deprecated to debugFeb 1 12:33:30 MacBook-Pro nsurlsessiond[130]: DEPRECATED USE in libdispatch client: Setting timer interval to 0 requests a 1ns timer, did you mean FOREVER (a one-shot timer)?; set a breakpoint on _dispatch_bug_deprecated to debugFeb 1 12:33:30 MacBook-Pro nsurlsessiond[365]: DEPRECATED USE in libdispatch client: Setting timer interval to 0 requests a 1ns timer, did you mean FOREVER (a one-shot timer)?; set a breakpoint on _dispatch_bug_deprecated to debugFeb 1 12:33:04 MacBook-Pro com.apple.xpc.launchd[1] (com.apple.soagent): Invalid type for event eventsFeb 1 12:33:04 MacBook-Pro com.apple.xpc.launchd[1] (com.apple.soagent): Invalid type for event bundleidFeb 1 12:33:05 MacBook-Pro xpcproxy[414]: libcoreservices: _dirhelper_userdir: 529: bootstrap_look_up returned (ipc/send) invalid destination portFeb 1 12:33:06 MacBook-Pro xpcproxy[416]: libcoreservices: _dirhelper_userdir: 529: bootstrap_look_up returned (ipc/send) invalid destination portFeb 1 12:33:29 MacBook-Pro xpcproxy[461]: libcoreservices: _dirhelper_userdir: 529: bootstrap_look_up returned (ipc/send) invalid destination portFeb 1 12:33:30 MacBook-Pro xpcproxy[463]: libcoreservices: _dirhelper_userdir: 529: bootstrap_look_up returned (ipc/send) invalid destination portFeb 1 12:33:30 MacBook-Pro xpcproxy[469]: libcoreservices: _dirhelper_userdir: 529: bootstrap_look_up returned (ipc/send) invalid destination portFeb 1 12:34:42 MacBook-Pro xpcproxy[516]: libcoreservices: _dirhelper_userdir: 529: bootstrap_look_up returned (ipc/send) invalid destination portFeb 1 12:34:56 MacBook-Pro xpcproxy[528]: libcoreservices: _dirhelper_userdir: 529: bootstrap_look_up returned (ipc/send) invalid destination portFeb 1 12:33:04 MacBook-Pro com.apple.xpc.launchd[1] (com.apple.xpc.launchd.user.domain.248.100011.Aqua): com.apple.ReportCrash (lint): Unrecognized MachService property: DrainMessagesOnCrashCould use an experienced tech to help me out. The idle wake ups in the activity moniter are hundreds of thousands at the moment, and I know this is the beginning of something bad for my laptop's health. Any help is appreciated!