Well in rebuttal to Raven.
If they know about those problems, they don't usually patch with them. Most people have a different hardware and software configuration and it can be very, very difficult to get it right on the first try. You just can't be sure how your code is going to work with every hardware and software configuration.
Sometimes they just screw up. People aren't perfect, even the guys in internal QA aren't perfect. Bugs get through and hopefully we catch and report them.
Big patches like this last one tend to be even worse. Too much stuff in them for something NOT to go wrong. The more complicated you make it, the more things that can potentially go wrong. If you'd waited two more weeks, odds are you would have gotten an even worse patch because there would be so much more in it to go wrong.
Also, some of us have found ways around things. From the earlier bug report thread linked I was getting far in the game myself because of the intense slow down that could make it take 5 minutes to advance a single turn without events. If you can find a workaround though you can make the "game" work and some very useful information for the QA team. A work around is often a very good description of what exactly is causing the bug.
This isn't a game preview, this is real beta testing in all its "glory".