Failed rendering video stream

[riekl]

There was a MPEG-2 Video Error in playback. Details:

Failed rendering video stream
ErrCode=0x80040231

Yet I have it using the same NVDVD codec as the previous sage client .. and the same codec plays fine stand alone ..

[falchulk]

I had the same issue when I first installed the .10 beta. Strangely, uninstalling and reinstalling NVDVD fixed it.

[rrussell]

I got that briefly when specifying the intervideo video decoder from WinDVD instead of letting it use "default." I set it back to "default" and all was well, but I don't know which decoder it's using...

[davey_fl]

me too... Is there a solution for this? No matter how many times I re-install, try to change filters and then set it back to default, I get the same error everytime. Any suggestions?

[gplasky]

I experienced this morning on a new reinstall after using it all night. No matter what decoder I picked it gave me this error. I changed it to NVDVD and then quit Sage and rebooted. All is well-don't know if that will help you.


Gerry

EDIT: This was with the Sage TV client.

[davey_fl]

hmm I don't have that in my list, just Sonic and the InterVid one...

[davey_fl]

WARNING: Watch out if you have this problem. It just corrupted the filesystem on my 200GB WD drive, thereby losing all previous recordings.

[gplasky]

Did it corrupt your whole filesystem or was it just a corrupt wiz.bin file? A bad wiz.bin file would of cause all of your recordings to be lost. There might of been a problem with that earlier. There should also be a backup of the wiz.bin file but I would be wary of using it. Whatever was corrupt could also be in the backup.


Gerry

[falchulk]

What? I think you just responded before tou had time to troubleshoot. There is no way it corrupted the filesystem. As I stated, I had the exact same issue and its working fine now. I lost no data whatsoever. I just had to use the intervideo codec until I got it working.

[davey_fl]

I hae a stand-alone E drive for nothing but recording. Everything was fine until I got this message this morning:

Failed rendering video stream
ErrCode=0x80040231

I then uninstalled, re-installed, and tried the different filters with sage sleeps and exits in between, and one reboot. Nothing worked, I went to the E drive (stand alone for sage recordings and livetv) and Windows informed me that the drive was not formatted. I've been using this drive for some time now with no problems, and it had approx 40gb of recorded files on it.

[falchulk]

This is my theory on your problem:

1. Your drive became corrupt.
2. You attempted to play a file that was stored on this drive.

This resulted in the Failed rendering video stream
ErrCode=0x80040231 error. Thats what happens when Sage cannot open the file you are asking for. I think thats a more plausable explanation.

[davey_fl]

I agree, and disagree. This drive is one month old and running fine. I agree that an older drive may become corrupt after thousands of hours of use, but not a new drive. It seems too much of a coincidence that it happened at the same time there was a problem with sagetv...

[falchulk]

Heh heh. I am a network administrator that has been working on PC's for 11 years professionally. We send brand new PC's back all the time with failed harddrives. These things happen all the time.

[davey_fl]

well... I'm a Unix Sys Admin who's been in the field for 30 years, with both a Computing Sci. degree and Molecular Genetics, and I too have seen new drives fail. But if they're going to fail, it's usually within the first 100 hours of using them, or there are problems immediately during installation. I'm chalking this one up to a sage beta problem.

[Opus4]

I recently had one fail after 2 months -- they can fail any time. I would run the mfr's diagnostics on it before using it again to determine if it was worth continuing using. SageTV uses OS system calls to deal with the files, so if there was a problem that caused the drive to be corrupted... that reminds me: how large is the drive? (I may have missed this comment.) There is a Windows patch for drives larger than the old max size. (133GB? whatever it was...)

- Andy

Edit: Oh, 200GB. The patch may be something to look at. I'll see if I can find it when my 2 daughters aren't pulling me away from the computer...

[gplasky]

I would lean more towards the drive went bad and that's why you were seeing that error in Sage. Not the other way around and Sage trashed your disk. We just replaced 700 desktops over a 3 month period and I've seen drives go bad after a month, or 2 or 3. Not a lot, mind you. And you're right, if they last the first 100 hours they usually are good to go. The key word is usually. This is not a Sage beta problem. Reformat it and start using it again. I'd run some disk diagnostics to be sure though.

Gerry

[Opus4]

OK, here's a link to one MS KB article regarding XP support for large drives:

http://support.microsoft.com/default...b;en-us;303013

[Strangely, I posted that link months ago, but it was for the Russian language version... no idea how that happened!]

This 2nd link is for the patch to make sure you have the correct verison of atapi.sys (5.1.2600.1135), if it is the wrong version, your drive can be corrupted:

http://support.microsoft.com/default...b;EN-US;331958

- Andy

[salsbst]

I believe that SageTV uses APIs to cause files to be modified. It doesn't address the hardware directly and thus cannot reasonably be blamed for a corrupted file system.

[falchulk]

"I'm a Unix Sys Admin who's been in the field for 30 years," and you would be familiar with current technology why? That does not impress me at all. We are talking PC's not mainframes. Neither a "Computing Sci. degree" or a "Molecular Genetics" gives you an understanding of hardware. I have a degree in EE and a merit badge in fishing! So what? I was trying to be nice but the comments you are making about sage taking out your HD sounds like something one of my 55+ year old users would say.


BTW, drives usually have no set number of hours such as 100 before they go bad for a system thats always up. Most of the time its going to be a power on /off cycle thats going to trigger it. Not to mention that I have had perfectly good drives just lose all their data. Just reformating and starting over corrected the issue. I am not saying the drive is bad. I was just commenting on your comment about how old it was.

[davey_fl]

yes I'm also talking about PCs. OpenBSD, Linux etc. And I was also a Windows MCSE for 8 year. Anyway this is going nowhere. Xp does have the patch to support > 133gb. I've reformatted and we'll see what happens.