I have encountered my fair share of glitches so here is what I know so far:
Texture Bug
From my experience, I did not have this glitch until today, with which I had only played off the disc up until this point. I installed it to test the theories of what causes it and after going into my menu then map and coming back out, the glitch appeared clear as day. Now I don't know if this will work for you but I just quit to dashboard and uninstalled the game, I did not clear the cache but when I went back into the game the glitch was gone, 10 hours later and it's nowhere to be seen so this fix worked for me.
Arrow Bug
A few reports of this bug have been cropping up since release. It's where arrows stay stuck in your body long after getting shot. The fix I found for this is to just get shot a few more times, the on-screen arrow count will reach its limit and the glitched arrows will disappear.
Third Person Camera "bug"
A few people have posted about the third person camera being too close/far to/from the player character. All you have to do is stay still, click and hold the right thumbstick and move the left thumbstick up/down to adjust zoom. This can be done for combat and non-combat stances respectively.
I will post more as I find and figure out solutions for them. In the meantime, be patient and civil, I assure you that raging in a thread will not help your cause, Bethesda is working on the glitches so just be patient.
Slow Motion blocking perk glitch
I discovered this one myself today. If you have the Block perk which makes the game go in slow-motion when enemies use a power attack, sometimes it stays in slow motion until you use this fix. There are two ways to fix, either save your game or just switch weapon to one where you don't use a shield, this will put the game back into normal-motion.
Shooting arrows over long distance bug
Some reports of arrows not hitting distant targets regardless of how precise you aim them. While I don't know of any fix for this, for the meantime just get closer to your target and hope Bethesda acknowledges this bug.
Hope this helps some of your problems.
