Image corruption

[PhilippeB]

Yes, this is definitly a tsMuxer issue so thread should be mooved accordingly. It will affect, however, most solutions as they all seem to rely on it (that's what happen when you put all you eggs in the same basket).

For the torrent thing, i understand this might go against forum rules though it always make me smile to have such rules in an environment where it's obious purpose it to duplicate discs otherwise why giving so much trouble (please don't mention the scientific challenge). I was just trying to pull some heads out of the sand. Sorry for that. Delete my post if it go against some rules.

I don't think Win7RC7100 is a so unusual install, actually, this is probably the OS most power user enthusiasts have been experiencing during 2009.
March is when the trial will be over. I plan to get my RTM version before that, probably next month.

Thanxs again everyone, especially Deank for helping me pointing out where the problem was lying. Meanwhile i have a couple of plans to try (like slowing down my machine a bit) etc.

:thanks:

[GaPony]

Forgive me if I'm skeptical about the possibility that your machine is too fast... I'm sure if that were the case, there would be headlines in the New York Times, not to mention floods of "Intel creates monster" blogs all over the internet. That just isn't happening.

Perhaps a more conventional approach to problem solving may work better for you, since you live on a round world. :)

[Guest]

@PhilippeB

Please stop talking about torrent downloads (rule 6) and musing about the rules (rule 17), else strikes can follow. Thank you.

[PhilippeB]

Everybody, just wanted to give some positive updates.

I went back to the drawing board and found some compatibility issues between my RAM and my motherboard. Problems that i though were fixed due to previous successfull and intensive tests with memtest86+, but it look like it came back.

After tweaking manually (and with a few tips from Mushkin) i was successfull.

Now tsMuxer doesn't seems to be a problem anymore. Though i still don't understand why this was affecting only this program, i had much heavier environments like visual studio + platform builder + CE6 working like a charm. Oh well..

The important thing is now tsMuxer seems to work fine.

:thanks:

[jdobbs]

Everybody, just wanted to give some positive updates.

I went back to the drawing board and found some compatibility issues between my RAM and my motherboard. Problems that i though were fixed due to previous successfull and intensive tests with memtest86+, but it look like it came back.

After tweaking manually (and with a few tips from Mushkin) i was successfull.

Now tsMuxer doesn't seems to be a problem anymore. Though i still don't understand why this was affecting only this program, i had much heavier environments like visual studio + platform builder + CE6 working like a charm. Oh well..

The important thing is now tsMuxer seems to work fine.

:thanks:I'm guessing TSMUXER must have been requiring more memory than the other software typically does... you see that a lot in muxing and encoding.

[setarip_old]

@PhilippeB

Congratulations on apparently solving your "unique" problem.

In light of this, it's hard to resist re-posting things from very much earlier in this thread (that you initially resisted), such as:Check for overheating (and gunk/dust bunnies) and/or less than perfect connections and seating of cards...and I'm sure that with your 20 years' experience, you are very familiar with both "Murphy's Law" and the phrase, "Better safe than sorry".

Again, congratulations ;>}

[GaPony]

Its amazing what we find when we start looking at our own systems...