Routined Keeps Crashing in Big Sur - How Can I Stop It?

I'd definitely try adding a new user account and see if the crash appears there. That's the only thing that's stopped the crashes for me. If you don't see it crash under the new account, that's probably the solution.

I'm still in the process of migrating all of my files over to my new user account, and every time I switch back and forth to transfer something, my old account immediately pops up the routined crash. I have yet to see a single routined crash in my new account.

I meant to include that in my original post and completely forgot; I did try Safe Mode before posting here and saw the crashes there. I tried again just now and had the same results; routined shows up as a crash within about 30 seconds of getting logged in.

Creating a new admin user and logging in as such did not generate the crash. I did a restart after creating the new user, then logged in as the new user, and after getting past all of the various Apple configuration that comes with a new user, I didn't see the crash. I restarted again and logged in as the new user and never saw the crash in the 15 minutes or so I was logged in.

I'm guessing a new account is in my future?

Definitely give it a shot; if that makes the errors go away, you'll find migrating to a new account isn't as bad as it sounds.

I did mine over the course of a week or so; I built a list of the apps I use on a regular basis, then each day I'd do a couple of apps, setting them up in my new account while still working in my old. Once I had everything set up, I moved all of my files over through my account's Public folder (I did have to change permissions, which took a while). Most everything worked without a hitch. Music.app was an absolute pain in the backside (but then, when isn't it?); the new account wouldn't read the library file from my old account, so I had to rebuild from scratch, but once I figured it out, it wasn't that difficult.

But I'm now full-time in my new account without any issues. And I don't miss routined making itself known every ten minutes.

Sorry, didn't even think to update EtreCheck--it's been so long since I've had any issues.

I deleted the orphaned .plists and Cocktail and reran the updated EtreCheck. That's attached, as is the error report generated when I clicked the "Report" button on the error dialog.

Thanks!

The long shot didn't work, but long shots rarely do.

I've got it where I can park the error message in the corner and ignore it, so I might poke at uninstalling for a bit; if I figure out a culprit, I'll come back here and post something for future generations.

Thanks for all the help!

Thanks for that--my hosts file had an entry I'd added a while back while trying to route around something involving accessing my modem (I'd explain more, but I honestly don't remember). I've removed it so that the hosts file is back to the default shown in that link. Crossing my fingers that it fixes things.

I haven't gone so far as to uninstall Little Snitch, but I did disable it and still got the crash, and it was enabled and actively bugging me to allow or deny connections when I logged into the new admin account where routined didn't crash. When this all started, I did add a rule to Little Snitch to allow /usr/libexec/routined to make any outgoing connection (though I now notice I didn't have one set for incoming connections). But I'll definitely try uninstalling before moving on to a new account.

Thanks!