The one about "script may be busy" usually means EITHER you have an old version of a web browser that needs updating, or you have an old version of Java. However, I've also seen that when you have a very old Windows system and a much newer browser. Essentially, Windows is "chugging along" as fast as it can to render something that is a bit advanced (well, anyway newer) than it really can handle. The best option is "Continue" under most circumstances. The other options require you to be a programmer.
The "Not Responding" message can be any one of a number of things but invariably is the result of a program encountering (and badly handling) an unexpected condition.
As to "can you get someone to come fix this?" my answer is that if anyone tells you they CAN fix it and guarantee that it will never happen again, DON'T let that person near your computer. I'm a 40-year computer professional and this sort of thing happens on my machines now and then, despite my best efforts.
These things happen because this is an imperfect world and people are imperfect. Imagine, if you will, that some software developer wanted to make his programs foolproof. So the boss says, "Let's hire some fool to do our testing." To which the next question is, "But what fool would apply for such a job?" Followed by "And what fool would hire such a person?"
That was tongue-in-cheek but in another sense very real. Compex programs may have literally hundreds of thousands of possible outcomes, results, etc. How do you test them all? So when something goes wrong, what you have to do is try to recall what triggered that event and see if you perhaps did something wrong. Then don't do that again.