1.

Solve : How to turn off error messages for ogm files??

Answer»

I've been trying to open an ogm video file in vlc PLAYER and everytime I CLICK on the file without opening it I get this strange error message I'll paste below.  I've never seen this error before and I do not know how it happened.  How do I change settings to TURN it off?

Heres the error message below (I can't tell what is wrong here)

OS: Windows XP Home Edition, SP2
CPU: AuthenticAMD, AMD AMD Athlon(tm) XP 3000+, MMX 2166 MHz

Application data:
VmVyc2lvbjogVVVKZFExQlRWbHRFVFVOSFF5c29 PU2M1QndBNkpUOCt
MVzk3WjJOck1DRWpQeU1rTTBGeGVIQjBaWE01DQ pJbWFnZUJhc2U6ID
E5RTkwMDAwDQpFaXA6IEZGOTdFMzANCkVheDogM Tg4RTAwMDANCkVje
DogMA0KRWR4OiAxOEY3QTcyMA0KRWJ4OiAwDQpF c2k6IDE5QjY3M0VD
DQpFZGk6IDE4RjUwMDAwDQpFYnA6IDQ1MEU2NEM NCkVzcDogNDUwRTU
yMA0KLTENCkNvZGUgPSBbMjA0XQ0KLSAwDQotID IwNA0KLSAyMjcNCi
0gMA0KLSBbXQ0KPiBDOlx3aW5kb3dzXEV4cGxvc mVyLkVYRQ0KPiBDO
lx3aW5kb3dzXHN5c3RlbTMyXG50ZGxsLmRsbA0K PiBDOlx3aW5kb3dz
XHN5c3RlbTMyXGtlcm5lbDMyLmRsbA0KPiBDOlx 3aW5kb3dzXHN5c3R
lbTMyXG1zdmNydC5kbGwNCj4gQzpcd2luZG93c1 xzeXN0ZW0zMlxBRF
ZBUEkzMi5kbGwNCj4gQzpcd2luZG93c1xzeXN0Z W0zMlxSUENSVDQuZ
GxsDQo+IEM6XHdpbmRvd3Ncc3lzdGVtMzJcR0RJMzIuZGxsDQo+IEM6
XHdpbmRvd3Ncc3lzdGVtMzJcVVNFUjMyLmRsbA0 KPiBDOlx3aW5kb3d
zXHN5c3RlbTMyXFNITFdBUEkuZGxsDQo+IEM6XHdpbmRvd3Ncc3lzdG
VtMzJcU0hFTEwzMi5kbGwNCj4gQzpcd2luZG93c 1xzeXN0ZW0zMlxvb
GUzMi5kbGwNCj4gQzpcd2luZG93c1xzeXN0ZW0z MlxPTEVBVVQzMi5k
bGwNCj4gQzpcd2luZG93c1xzeXN0ZW0zMlxCUk9 XU0VVSS5kbGwNCj4
gQzpcd2luZG93c1xzeXN0ZW0zMlxTSERPQ1ZXLm RsbA0KPiBDOlx3aW
5kb3dzXHN5c3RlbTMyXENSWVBUMzIuZGxsDQo+IEM6XHdpbmRvd3Ncc
3lzdGVtMzJcTVNBU04xLmRsbA0KPiBDOlx3aW5k b3dzXHN5c3RlbTMy
XENSWVBUVUkuZGxsDQo+IEM6XHdpbmRvd3Ncc3lzdGVtMzJcV0lOVFJ
VU1QuZGxsDQo+IEM6XHdpbmRvd3Ncc3lzdGVtMzJcSU1BR0VITFAuZG
xsDQo+IEM6XHdpbmRvd3Ncc3lzdGVtMzJcTkVUQVBJMzIuZGxsDQo+I
EM6XHdpbmRvd3Ncc3lzdGVtMzJcV0lOSU5FVC5k bGwNCj4gQzpcd2lu
ZG93c1xzeXN0ZW0zMlxOb3JtYWxpei5kbGwNCj4 gQzpcd2luZG93c1x
zeXN0ZW0zMlxpZXJ0dXRpbC5kbGwNCj4gQzpcd2 luZG93c1xzeXN0ZW
0zMlxXTERBUDMyLmRsbA0KPiBDOlx3aW5kb3dzX HN5c3RlbTMyXFZFU
lNJT04uZGxsDQo+IEM6XHdpbmRvd3Ncc3lzdGVtMzJcVXhUaGVtZS5k
bGwNCj4gQzpcd2luZG93c1xzeXN0ZW0zMlxTaGl tRW5nLmRsbA0KPiB
DOlx3aW5kb3dzXEFwcFBhdGNoXEFjR2VucmFsLk RMTA0KPiBDOlx3aW
5kb3dzXHN5c3RlbTMyXFdJTk1NLmRsbA0KPiBDO lx3aW5kb3dzXHN5c
3RlbTMyXE1TQUNNMzIuZGxsDQo+IEM6XHdpbmRvd3Ncc3lzdGVtMzJc
VVNFUkVOVi5kbGwNCj4gQzpcd2luZG93c1xzeXN 0ZW0zMlxJTU0zMi5
ETEwNCj4gQzpcd2luZG93c1xzeXN0ZW0zMlxMUE suRExMDQo+IEM6XH
dpbmRvd3Ncc3lzdGVtMzJcVVNQMTAuZGxsDQo+IEM6XHdpbmRvd3NcV
2luU3hTXHg4Nl9NaWNyb3NvZnQuV2luZG93cy5D b21tb24tQ29udHJv
bHNfNjU5NWI2NDE0NGNjZjFkZl82LjAuMjYwMC4 yOTgyX3gtd3dfYWM
zZjljMDNcY29tY3RsMzIuZGxsDQo+IEM6XHdpbmRvd3Ncc3lzdGVtMz
JcY29tY3RsMzIuZGxsDQo+IEM6XHdpbmRvd3Ncc3lzdGVtMzJcbXNjd
GZpbWUuaW1lDQo+IEM6XHdpbmRvd3Ncc3lzdGVtMzJcYXBwSGVscC5k
bGwNCj4gQzpcd2luZG93c1xzeXN0ZW0zMlxDTEJ DQVRRLkRMTA0KPiB
DOlx3aW5kb3dzXHN5c3RlbTMyXENPTVJlcy5kbG wNCj4gQzpcd2luZG
93c1xTeXN0ZW0zMlxjc2N1aS5kbGwNCj4gQzpcd 2luZG93c1xTeXN0Z
W0zMlxDU0NETEwuZGxsDQo+IEM6XHdpbmRvd3NcU3lzdGVtMzJcdGhl
bWV1aS5kbGwNCj4gQzpcd2luZG93c1xTeXN0ZW0 zMlxTZWN1cjMyLmR
sbA0KPiBDOlx3aW5kb3dzXFN5c3RlbTMyXE1TSU 1HMzIuZGxsDQo+IE
M6XHdpbmRvd3Ncc3lzdGVtMzJcc2hkb2NsYy5kb GwNCj4gQzpcV0lOR
E9XU1xzeXN0ZW0zMlx1cmxtb24uZGxsDQo+IEM6XHdpbmRvd3Ncc3lz
dGVtMzJcaWVmcmFtZS5kbGwNCj4gQzpcd2luZG9 3c1xzeXN0ZW0zMlx
QU0FQSS5ETEwNCj4gQzpcd2luZG93c1xzeXN0ZW 0zMlx4cHNwMnJlcy
5kbGwNCj4gQzpcV0lORE9XU1xzeXN0ZW0zMlxhY 3R4cHJ4eS5kbGwNC
j4gQzpcV0lORE9XU1xTeXN0ZW0zMlxtc3V0Yi5k bGwNCj4gQzpcV0lO
RE9XU1xTeXN0ZW0zMlxNU0NURi5kbGwNCj4gQzp cd2luZG93c1xzeXN
0ZW0zMlxudHNocnVpLmRsbA0KPiBDOlx3aW5kb3 dzXHN5c3RlbTMyXE
Are you running Nero?

This is becoming a well known problem. When trying to open certain video FILES, you get an error report with application data starting

VmVyc2lvbjogVVVKZFExQlRWbHRFVFVOSFF5c29 PU2M1QndBN kpUOCt

going on for 100s of lines. It happens on Intel & AMD with various different TYPES of video files.

A quick Google found 101 results

http://www.google.com/search?q=VmVyc2lvbjogVVVKZFExQlRWbHRFVFVOSFF3b0NPU2M2T3lwcGZtVmd+&hl=en

Some people are blaming Nero Burning Rom's Nerocheck.exe and saying that disabling it from running at startup stopped the problem.







Discussion

No Comment Found