Olevia 532H-B13 - Picture Freezes

[stevekasian]

Hi,

I have an Olevia 532H-B13 LCD TV. Everything works perfectly except the picture freezes (with absolutely no distortion, just a perfect freeze frame of whatever was on the screen) when it warms up (from cold, it takes about 2 minutes or so).

Does anyone know which board would most probably be responsible for this?

(There are no bulging caps visible... yet.)

Thanks!
SK

[tom66]

Re: Olevia 532H-B13 - Picture Freezes

One possible cause is a loose LVDS cable or connector going to the LCD panel, though that usually does introduce some picture glitches.

When frozen, can you turn on/off the set using the buttons or remote control? Does sound continue?

[stevekasian]

Re: Olevia 532H-B13 - Picture Freezes

I'll have to double check and make sure - I've torn the thing down at this point.
SK

[tom66]

Re: Olevia 532H-B13 - Picture Freezes

http://www.youtube.com/watch?v=bnfymg6ip6A

That's what a loose LVDS cable can cause.

Thermal expansion *could* be causing it to disconnect after a few minutes of operation. However, as in the video, when the cable goes loose it's *usually* followed by distortion, like horizontal lines or a change of colour. If you're lucky, just pressing the cable down will fix it for a year or two; maybe there's a more permanent fix.

[cadiman]

Re: Olevia 532H-B13 - Picture Freezes

I would go after the mainboard / video board where the signal starts out.

[stevekasian]

Re: Olevia 532H-B13 - Picture Freezes

Yeah, it's nothing at all like in that video you linked to.

Now I'm noticing that it sometimes freezes on a blue screen when turning it off and on again once it's warm, and sometimes a black screen. But most often, the Olevia logo pops up with a white background first and it freezes on that.

I'm also noticing that sometimes there is weird distortion (almost like ASCII characters) along the very bottom of the screen (up to about 1/4" from the bottom in a horizontal line) just before it freezes. The best way I can describe the distortion is sort of like if you take an old Commodore 64 home computer and POKE53272,xxx (any value between 1 and 255 other than the default value) and watch what happens to the screen. Weird characters randomly populate the screen, some jumping around and randomly paging through CHR$ values at varying speeds.

Don't know if this helps or not.
SK