ATI Radeon 4350 no hi-def?

[pBS]

sounds kinda like defective card or memory on card...
but i've had some lockups on 4xxx's too....but i think i solved it by turning off all ccc stuff...
[haven't had any since]
i unchecked all ati stuff from startup, as it isn't necessary to run, ccc only sets registry settings,so doesn't need to be running..
video isn't affected at all....
[it maybe the new stupid menu system locking up]
disable mom and ccc and any atievxxx's etc...
look in services also..[atismart,etc.]

[keith_leitch]

sounds kinda like defective card or memory on card...

Maybe...but it seems to only occur in spots on the video that are known to be "bad". (Usually, some corruption is visible before the problem occurs).

but i've had some lockups on 4xxx's too....but i think i solved it by turning off all ccc stuff...

Really? Isn't it needed for things like controlling LCD overdrive and keeping the ITC in place?

[keith_leitch]

OK, I am taking your advice and will let you know how this goes. I ran some visual tests to see if I could see any differences with and without CCC running (in terms of judder, tearing, etc.) I could not. I still have concerns that perhaps VPU recovery won't function without CCC resident, but I will have to run into an error before I can determine that.

I've added lines to a number of my batch processes to kill CCC and MOM before executing their programs. If you don't mind giving me some advice:

When I DO need to change resolutions, do you think I should be using a third-party program to do so, like I am now? My concern is that it might not load "other" settings, such as colour, lcd overdrive, the second SD video card, etc. A catalyst profile is sure to get them all. I think this might be particularly important when I am giving the video card a poke after it goes to sleep (as it does occasionally).

The alternative to a third-party program is a batch file to start the catalyst CLI, wait five seconds, load a profile, wait another five seconds, then kill CCC and MOM. There's nothing wrong with this, exactly, except that it takes ten seconds to run.

[JonnyCam]

Maybe...but it seems to only occur in spots on the video that are known to be "bad". (Usually, some corruption is visible before the problem occurs).

Yeah, I had the same thing when I first tried playing HD DVB-T on my ATI card.
(Along with some green screens on SD channels)
After putting an Nvidia card in thee, no issues (I only changed my card out recently as I wanted a silent model)

[keith_leitch]

Yeah, I had the same thing when I first tried playing HD DVB-T on my ATI card.
(Along with some green screens on SD channels)
After putting an Nvidia card in thee, no issues (I only changed my card out recently as I wanted a silent model)

Ew, not what I wanted to read...but potentially useful data. This has occurred once on HD-DVB-T and twice on SD-DVB-T. (When I say "twice", I mean in occurred many times as I tried it again and again in the same two spots on the same two recordings). With VPU Recovery switched on in Catalyst, it does not reboot the system, but I have to feel around in the dark until I can reset the video card. With VPU Recovery off, the system restarts (presumably because I have it set to "restart" instead of "BSOD"). pBS advised to unload Catalyst from memory to avoid this, and I haven't run into the problem yet with it unloaded...but it hasn't been that long, either.

When you say you changed your card out, do you mean to another NVidia?