Gom Player Error 0x00000051 - Page 2
Forum Index > Tech Support |
arbitrageur
Australia1202 Posts
| ||
archdevilz
91 Posts
| ||
Poststrata
United States110 Posts
| ||
gaizka
United States991 Posts
| ||
leser
Croatia239 Posts
tried reinstalling, pressing play after the error message etc but nothing seems to work i am sad | ||
eGoTricKShoT
United States46 Posts
| ||
Poststrata
United States110 Posts
| ||
Arcanewinds
United Kingdom197 Posts
Hit the play button a half dozen more times after it told me it didnt work.. and it decided to work all of a sudden. I've been unable to watch live matches for ~2 weeks because of this.. And all it took was to spam play a more times. :/ Rageface. Ah well, I've watched the vods now and know how to deal with gomplayer. For those having the same problem, just keep hitting play | ||
graNite
Germany4434 Posts
| ||
zhurai
United States5660 Posts
| ||
treekiller
United States236 Posts
| ||
Pasado
United States142 Posts
| ||
Poststrata
United States110 Posts
On March 01 2011 19:21 treekiller wrote: Yeah Im guessing those that had this problem are using chrome. I tried launching it through firefox and it worked. Nope, browser has nothing to do with it. I used both firefox then Chrome same problem. I even went direct through the gomplayer with the GSL link. I believe its a server issue on their part or internet connection issue on our part... or even software issue (gom Player). Anyway, its working now. | ||
HellGreen
Denmark1146 Posts
I have experienced the same error many times and mostly fixed it by hitting "play" till it works. This I believe is related to a short-term disconnect of the stream (ie. poor wifi, lag, network timeout or bottleneck). But whenever GomTV experiences a major break down (ie. too many simultaneous users), I believe that after they reset their streaming equipment, they post a new stream URL (to avoid another crash from users hitting play). The users clicking the pre-loaded/cached web page, will now get the error. And since most browser cache the recent pages, the users must do a hard refresh (or switch browser) which explains the part about why it sometimes works in other browsers. My conclusion is, there is no one step solution to fix this, but try with a little patience and methodical ruling out elements. It usually works for me. I hope this post may cast a little light on the problem and possible solutions to it. | ||
terranghost
United States980 Posts
| ||
double1185
Vietnam211 Posts
| ||
skyR
Canada13817 Posts
On March 12 2011 15:28 double1185 wrote: I just wonder only people without premium ticket get this kind of error or even the one who bought it? Even premium ticket holders get it. Me and my friend gets it all the time and its quite annoying. | ||
GriMeR
United States148 Posts
| ||
Signus
United States269 Posts
| ||
kanix
Sweden67 Posts
| ||
| ||