The one thing I've seen in common with the errors is that they all refer to an exception in the code -- so it would seem there is something in your code that causes an exception when it runs in the browser but not in the client.
I know that probably sounds obvious -- and the question is obviously "But WHAT is causing the exception???" And I don't have an answer for that, but I do know that in the past one way I've worked out where the issue is in the browser is by commenting out parts of my code and seeing if I still get an error, then gradually re-enabling things, so I can narrow down WHERE the error is. Then you'll have something more specific to search out than a rather unhelpful error code.
You should also check your server logs, to see if you can get more info. These logs are located on the server, generally at: C:\Program Files\Common Files\Microsoft Shared\web server
extensions\12\LOGS. I normally try to provoke an error RIGHT before I open the latest log file, to make it easier to find.