Interesting. None of our testers reported anything like this. I think I know what this is - both of those issues must be related to level streaming, as our level segments are loaded in and out of memory dynamically which is error-prone on slower systems. We can most likely patch these issues out relatively easily.
Anyway, sorry you had a poor experience! Lesson learned there.