Corrupted/damaged video files

[Komenjoka]

Hi everyone 

 

Link to video: https://photos.app.goo.gl/4VCzoAWPawE1my5g8

 

A friend of mine is having a weird problem where I don't even know what could be to blame, I'll explain everything in the form of a timeline of what happened before and after, the events:

 

(start, without direct problem description to understand the context)

1. My friend and I are passionate about the video and photo industry, we actively film, photograph and edit.

2. We both own Sony A6300 and A6600 cameras (basic video specification: 4K@30fps, 8-bit, 4:2:0, H.264, max 100Mbps)

3. I told my friend and recommended him to buy Sony FX30 (specifications: 4K@60fps, 10-bit, 4:2:2, H.264 and H.265, max 600Mbps) + Lexar SD 256GB V90.

4. 3 months ago I assembled the following stationary computer for a friend (R 7 7700, Gigabyte B650 Eagle, 64GB DDR5, Koaxia 1T pcie(C:), 2xLexar M620 1T pcie(games and renderer), 2xSeagate 4T 3.5 HDD(for archive), at the beginning I installed Win 10, but a friend reinstalled it to Win 11) to be able to easily edit FX30 files, because until then he had a laptop (i7-8xxxH, 16GB DDR4, GTX 1070, 1TB SSD+1TBHDD).

(listing of problems in court begins)

5. About 2 months ago, a friend filmed footage, where when put into the new computer, the first clips had this visual problem (see the link to the video with this problem), at first I thought that the fault should be the FX30 (specific video formats) or the SD card, friend continued filming with other settings, and until yesterday (31.01.2025) nothing like that happened again.

6. The day before the problem (30.01.2025) I talked with a friend through discord, he show the footage to me (which is saved on one of the Lexar M620 SSDs) and is trying colorgrading to see if everything worked, and no problems.

7. Yesterday (31.01.2025) he sits for serious video editting and sees this problem on the same material that he watched yesterday and where there were no errors, now I thought that it should be the SSD's fault, but ...

8. He opened even older (September 2024) video files that were captured with the A6600 and stored on one of the Seagate 4TB HDDs, and the same error - these pixelated blocks, now I think the problem is neither the camera nor the storage devices, but in some software (OS, malware).

 

Sorry for my bad English. And if someone need more info, just let me know.

 

Edited February 1, 2025 by Komenjoka

[porina]

26 minutes ago, Komenjoka said:

7. Yesterday (31.01.2025) he sits for serious video editting and sees this problem on the same material that he watched yesterday and where there were no errors, now I thought that it should be the SSD's fault, but ...

8. He opened even older (September 2024) video files that were captured with the A6600 and stored on one of the Seagate 4TB HDDs, and the same error - these pixelated blocks, now I think the problem is neither the camera nor the storage devices, but in some software (OS, malware).

Because of these, I wonder if the PC is unstable. For example, if the ram is unstable then errors could be shown for anything in a random manner depending on where the data is loaded into ram. I would do a full ram test first. At the least something like memtest.

 

What is the exact ram in the system, and what speed is it running at?

[Komenjoka]

2 hours ago, porina said:

Because of these, I wonder if the PC is unstable. For example, if the ram is unstable then errors could be shown for anything in a random manner depending on where the data is loaded into ram. I would do a full ram test first. At the least something like memtest.

 

What is the exact ram in the system, and what speed is it running at?

Thanks for your message!

 

RAM info: 2xG.Skill f5-5600J3036D32G .

 

I have set "XMP" profile to 5600 MHz

[porina]

2 minutes ago, Komenjoka said:

RAM info: 2xG.Skill f5-5600J3036D32G .

Should be ok in general. Still do run the full ram test. If that shows errors, try turning off EXPO and repeating. Can I assume the mobo was on latest bios at the time of building?

[Komenjoka]

7 minutes ago, porina said:

Should be ok in general. Still do run the full ram test. If that shows errors, try turning off EXPO and repeating. Can I assume the mobo was on latest bios at the time of building?

Oky. No, i updated BIOS version 1-2 weeks after build.

 

I'm on my way to friends place to do this troubleshooting and will update.

[porina]

19 minutes ago, Komenjoka said:

Oky. No, i updated BIOS version 1-2 weeks after build.

That's fine, I was checking it wasn't really ancient.

 

20 minutes ago, Komenjoka said:

I'm on my way to friends place to do this troubleshooting and will update.

My comments earlier on checking the ram in that was is to see if that is the problem. If so, if it is just stability or possibly faulty. Try CPU tests if ram comes back clean.

 

Given your comments on the problem varying like this, I do feel it unlikely to be the storage, but it never hurts to check them too as a lower priority.

[Komenjoka]

20 hours ago, porina said:

That's fine, I was checking it wasn't really ancient.

 

My comments earlier on checking the ram in that was is to see if that is the problem. If so, if it is just stability or possibly faulty. Try CPU tests if ram comes back clean.

 

Given your comments on the problem varying like this, I do feel it unlikely to be the storage, but it never hurts to check them too as a lower priority.

Yesterday, after 7 h memotest86and results shows its fine with ram, no errors (there was 2nd screen with 12 memo test types and all of them got 0 errors).

 

Conclusion for now: RAM modules is not the problem.

 

Next step: run storage (HDD and SSD) test, and CPU, i will update!

 

My knowledge of IT is sufficient (especially in hardware), I know that in the days of DDR3, modules were produced that were designed for either Intel or AMD CPUs, now I understand that the new DDR5 has the same feature, because memotest86 wrote "Intl" next to the RAM description. is this somehow related to this problem i think not but maybe someone has another version.

[porina]

1 hour ago, Komenjoka said:

Yesterday, after 7 h memotest86and results shows its fine with ram, no errors (there was 2nd screen with 12 memo test types and all of them got 0 errors).

 

Conclusion for now: RAM modules is not the problem.

At least that gives some confidence the ram is not obviously faulty. There is still some risk the memory controller is unstable as I have had situations in the past where memtest came clean but Prime95 gave an error quite quickly, and I knew it wasn't the execution in that case. Try a Prime95 blend for a bit, say 10 minutes. This uses some large FFT sizes which have a mixed read/write pattern which might stress the controller more than just doing one of the other that memtest does. To separately test for execution, a small FFT test can be run since this can work out of cache and doesn't really hit memory. However for AMD CPUs, Prime95 doesn't stress it the same way it does to Intel CPUs, so I'm not suggesting it as a CPU stress test. Again, this is more to exercise the memory controller.

 

One quick question, the screenshot lists 4800MT/s where the modules mentioned before were 5600. Is it running at 4800 or 5600?

 

1 hour ago, Komenjoka said:

My knowledge of IT is sufficient (especially in hardware), I know that in the days of DDR3, modules were produced that were designed for either Intel or AMD CPUs, now I understand that the new DDR5 has the same feature, because memotest86 wrote "Intl" next to the RAM description. is this somehow related to this problem i think not but maybe someone has another version.

Early DDR5 kits were marketed at Intel since AMD did not join for a long time afterwards. Now I'm not sure there is a difference. I bought two kits marketed as EXPO supporting for AMD mobos. The modules report both XMP and EXPO profiles. I suspect it might just be a packaging difference.

 

For DDR3, or was it even DDR2 era, there was a time where one side supported certain module configurations that the other side didn't, so those modules ended up being listed for one only.

[Komenjoka]

On 2/2/2025 at 11:34 AM, porina said:

 

One quick question, the screenshot lists 4800MT/s where the modules mentioned before were 5600. Is it running at 4800 or 5600?

Sorry for waiting, beasy week, about XMP it was not on enable, I thought that "DDR5 auto boost" turned it on, but I understand that it does not, since this was my first experience with a DDR5 system.

 

Soon i will update after Prime95 test.

 

And one "dumb" question: my friend likes to use MPC player (with all codec: H.264, H.265 e.c.), maybe could this be the reason ?

 

By the way, thank you for your involvement!

[porina]

8 minutes ago, Komenjoka said:

And one "dumb" question: my friend likes to use MPC player (with all codec: H.264, H.265 e.c.), maybe could this be the reason ?

Try another player if the glitches happen. VLC is a popular one that plays (almost) anything. Are they in the same place?

[Komenjoka]

On 2/5/2025 at 10:59 AM, porina said:

Try another player if the glitches happen. VLC is a popular one that plays (almost) anything. Are they in the same place?

Hello!

 

It's been a long time, unfortunately, I haven't had time to run the last recommended test (Prime95), but yes, I already somehow blamed the MPC player, I advised my friend to remove(uninstall) it from the computer and test it using VLC, and we also read on the Internet about other people experience's with the MPC player and some also had the same situation (corrupted video files), one even had a damaged downloaded movie file.

 

Probably (80%) the problem was with this program - MPC player. I advised a friend to test it for a while - from now to store and process video projects without MPC player.

 

I will post the end result as soon as possible.

 

Thank you - @porina - very much for your involvement and suggestions, my friend and I really appreciate it!

[Komenjoka]

On 2/13/2025 at 10:19 AM, Komenjoka said:

 

 

Probably (80%) the problem was with this program - MPC player. I advised a friend to test it for a while - from now to store and process video projects without MPC player.

MPC player was not and is not the problem, my friend still have the same problem.

 

Soon will run a Prime95 test.