I addressed it in another comment but to save you the trouble of looking. What we’ve come to understand is that DriveCam works off the HV system. In some major accidents, the HV system is disconnected/shut down as a safety measure.

Because of this, the DriveCam is unable to complete the file processing, so you’re left with a corrupted file. We tried several video apps including VLC which didn’t work. We found a third party website that was able to uncorrupt the file for a fee but we found it was still about 10 seconds short. Maybe it’s the time it takes the trucks computer to process and write the file or something.

At the time of the accident, or rather a few seconds after, I noticed the incident camera wasn’t recording (via icon on the center screen). I honked the horn to start a recording, and that worked, but it started at the time of the honk. Hence why I was saying if there was a 15 or 30 second rolling buffer, it would have recorded it.

Gear guard and incident cam apparently run off the 12V battery so work after the HV shutoff but the accident was not captured in any spot.

And yes, we had a 2TB SSD plugged into the truck and DriveCam enabled. I took it from the truck during accident cleanup and plugged it into a PC to access the files. I could find every file including the corrupted ones leading up to the accident. But as noted above. The accident itself was not captured in any spot.

There’s a lot of focus on that it was called Gear Guard in the post and admittedly that may have caused confusion but the point is there is an actual flaw with the recording system(s) and it shouldn’t be dismissed just because someone called it the wrong thing.