Screenshots 1, 2, 3, 5 all point to some sort of a memory problem. This could be:
1) A bug in the Silverlight application causing the error
2) A bad memory chip (though less likely since two machines are doing the same thing) - Test Studio is heavy on memory use that can cause bad memory problems to show up more than when using other applications.
3) Insufficient memory - If you have less than 1GB of memory installed we could just be running out of memory and running into problems as a result
4) A bug in Test Studio such that it's not correctly handling your Silverlight application. If this is the case we'll need a way of reproducing the problem locally in our development environment
Screenshot 4 sounds expected to me. The recorder must connect to the browser window prior to the browser loading your Silverlight application into it. This is a known limitation of Test Studio.
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Telerik Public Issue Tracking
system and vote to affect the priority of the items