Jerry Andersen wrote In your host settings, are you writing the event log directly to disk or is it writing to memory then to the database or file?  I had trouble with this because I wasn't writing the log to memory but I had the scheduled PurgeLogBuffer scheduled.  For some reason it didn't like that and you can other topics regarding an issue with the scheduled events causing problems with the portal from 4.7 and up.  If I can find those links I will post them for you.

I hadn't changed these from their default and havn't read much into the schedule issues others were having yet.  I guess I'll have to trust the search more. :)

I did turn off Ajax based on a suggestion somewhere and the crashes seemed to go away, but the Application log is still showing the errors.

Mitch Sellers wrote You might also check your application pool settings to ensure that a memory limit isn't set for the app pool that DNN is running in. Also, if you haven't done so already, enable caching in host settings.

If you are referring to memory recycling, it isn't set.

I was planning on googling some on performance settings for DNN at a later date.  I've tested these before and was not encouraged enough to change the default settings in a fairly dynamic environment (lots of users updating their own pages/sub portals). So I've left the defaults--cache to disk and moderate.  Are you referring to a specific setting here?