Problems with 8500 AIW

[jpnelson83]

Ok so, theres going to be some stuff coming up that I want to record and so I figured I'd go and make sure everything worked ok. Thats when the problems started. Everytime I hit record I get an error, it writes to the error log and then I have to restart the program. I found the error log but can't make heads or tails of what its trying to tell me so I figured I'd open it up to you guys to see if you could help me. The error log shows:

*** Log Manager 0: Opened on: 10/12/2004 [13:10:46]
[13:10:47] ResMngr::LoadObject CoCreate Error: ClassNotReg CLSID: {B6761AC7-0F95-4184-8CEE-0E8495BEBD13}
[13:10:48] TvDisp: StartUp: Failed to setup DTV Graph
[13:10:48] CCaptionControl_DS:Setup: Failed to Load & Connect WDM CC Decoder with ATI CC Renderer
[13:10:48] CCap:Caption: StartUp: Failed to initialize Driver
[13:36:12] CSoundControl_DS::SignalHasSAP: GetAvailableTVAudioModes() has failed
[13:37:06] CSoundControl_DS::SignalHasSAP: GetAvailableTVAudioModes() has failed
[13:37:23] CSoundControl_DS::SignalHasSAP: GetAvailableTVAudioModes() has failed
*** Log Manager 0: Closed on: 10/12/2004 [14:00:16]

For the record I'm using MMC v7.6, Catalyst drivers 4.4, umm other hardware includes a soundblaster audigy mp3+, gigabyte GA-7VAXP, 1 gig musking PC2700, and an Athlon XP 2800+ Barton. So I'm wondering if there is going to be any kind of fix for this or if I'm going to have to reformat or something. Oh directx 9.0c has been installed if that has anything to do with it. So any help would be apprecitated. If I'm better off posting this at htpcnews.com let me know and I'll do that. Thanks guys.

 

[CrimandEvil]

I could be totally wrong but it looks like the app is failing to load due to a driver issue. Have you tried uninstalling and then install new drivers? Personally I'd just do a reformat (never hurts to do one every once and a while).

 

[starhawk]

OK, here's the decoded version:

(1) it tries to load something (i suspect a resolution manager given the name) but can't for a reason that it's not prepared for.
(2) because it doesn't know why things are going wrong, it ignores that they are indeed going wrong...
(3) ...so it tries to set up a digital tv graph, and fails because it never loaded the graph generator prog.
(4) it blithely continues on to attempt a connection between the TV decoder and the 3D rendering software, using the prog it never loaded. naturally, that fails.
(5) it then attempts to start up a driver that isn't there.
(6) it tries to get the program list and fails...
(7) ...so it tries again (and fails)...
(8) ...and again (and fails)...
(9) so it tells you that something is wrong.

analysis:

this appears to be an object-oriented programming system. it tries to load an unknown program which, given the name, appears to be a "resolution manager". this fails, for a reason that the system is not prepared to handle. this means that it's a very rare sort of failure that nobody who made it ever expected to happen. expect a lot of brush-offs and "never heard that one before"s from the tech support people if you bug them.

at this point, that should have triggered what is called a "page fault program". this program's purpose is to dig up where the program you're looking for actually is-- and if it can't find the prog, to stop the system from doing anything else. however, the page fault program did not work properly in this case, which is a *major* failure of the programmers who wrote the code for this thing.

instead, due to this insane and crippling error (whose severity I cannot emphasize enough), the system assumes that nothing is wrong and continues to attempt to load things.

it then tries to create what it calls a "DTV graph". I don't know what that would refer to, presumably something to do with the interface of an hdtv, but again, I really do not know. however, it is reasonable to assume that ResMngr was supposed to create that thing. and, as ResMngr was never loaded, the "graph" never gets made.

this is another major failure. the system should have never even gotten to this point, and even if it did, the page fault program should have been triggered. but it wasn't.

deciding that everything is just ducky, the computer happily tries to set up a communications link between the decoder card and what appears to be rendering software of some sort. this probably is corrective software, so that you can run a program recorded for, say, 720x480 resolution on an hdtv at, say, 1350x1200 resolution, with little or no resulting lack of image clarity.

the computer fails to load this. again, another major failure of the page fault program when the system blithely continues to try to load things.

it then tries to load a driver that apparently is simply not there. the driver fails to load. at this point, it's a wonder that the system doesn't simply freeze: the driver should tell it the next step, not the initialization file. but apparently, the tech zombies had too much coffee and not enough sleep, or simply enjoy Quake III Arena too much, and decided to rely on the initialization file to do everything. this also contributes to your system's abysmal failure to run this thing.

next, it tries no less than three times to extract the audio systems your hdtv can handle. at this point, some actual logic sets in, and the system decides it's time to let you know that something is going on that isn't quite right.

so what you have is what's basically your average cascading system failure: one thing fails to load, and that pretty much makes the rest of it fall to peices like a jigsaw puzzle in a high-rise apartment during an earthquake.

i'd say it's time to call Scotty over for a little help, only an engineering miracle will ever get this thing running again... though there is one hope:

did anything, erm... unusual happen right before this did? if so, it's probably your culprit.

if not, I can't really pinpoint a specific problem, as it sounds like basically the whole video system went out for a cruise around saturn and liked the place so much that it decided to stay.

in short... your video system needs a pc coroner, unless you can weed out something unusual that happened *right* before the first failure.

 

[jpnelson83]

umm...Ya...so...I uninstalled the drivers and MMC 7.6, used driver cleaner to clear everything out and then reinstalled using the newest Catalyst drivers and MMC 7.6 and everythings hunky dory...so...starhawk...thanks for the explanation but it was a little over the top.

 

[starhawk]

whoops.

i've been known to need the occasional klonk on the head to get things working right... guess it's about time for another.