In that case, I would probably open IIS Manager and stop all websites. Then restart IIS. This will bring IIS backup and then allow you turn each site back on one at a time.
Start one site and try to access it. If you can get to it, look for the items that I mentioned before. If everything looks good then move on to the next site.
If you still can't get to the sites then you probably need to completely disable the scheduler. Restart IIS again. Then bring the sites backup. You can disable the scheduler from the web.config. Find the schedule provider section and add enabled=false to the following line...
add name="DNNScheduler" type="DotNetNuke.Services.Scheduling.DNNScheduling.DNNScheduler, DotNetNuke.DNNScheduler" providerPath="~\Providers\SchedulingProviders\DNNScheduler\" debug="false" maxThreads="1" enabled="false"
If you are still having problems getting into the sites after you try the above, then I would create a new AppPool and trying adding one site at a time.
I have also seen instances where the metabase has become corrupt which would cause the site to never respond. Any easy fix for that problem is to just create a new site under IIS.