You are pointing a virgin install of moodle at an empty database and it still happens. I can only conclude that either the latest download is buggered (not likely since i am using it myself), or your database is one basket short of a picnic.
The 'mdl_course' table keeps tabs on what activities/resources are present on a course page (i think). Errors with that table can really mess things up.
Double check that your new moodle is pointing to the new database. I clicked through an install too fast once and ended up pointing at an old database and made a royal mess of things.
The following may not be the best solution (or a solution at all) but its what I'd try in your situation...
- Create a backup of your database (y'know, just in case)
- Backup your 'moodledata' folder (y'know, just in case)
- Delete/drop your entire moodle database
or
Drop database and reinstall mySQL - Delete everything moodle-like from your server.
- Create database and reinstall moodle as per usual
Disclaimer: This post was written by someone whos drugs are making their head all fluffy. Follow the advice at your own risk