6k Pro USB-C issues: Freezing/Drop frames/SSD not detected

After a year and half from purchase we currently have severe recording issues with the BMPCC 6K Pro. The camera fails to read the SSD drives most of the times...
Once you're lucky and the SSD gets detected the camera either drop frames after few seconds and quits recording. While shooting longer takes it can freeze when hit the rec button to stop the recording (subsequently losing the video clip)
Firmware: 8.6
For three years we have shot exclusively with SanDisk Extreme Portable pro V2 SSDs USB-C drives almost flawlessly both on 6kPro and Ursa Mini Pro 12k.
- 1x 4TB,
- 3x 2TB,
- 1x 1TB
- Recently, following Blackmagic Support suggestion, we purchased a Samsung T7 Shield Portable SSD 2TB, a drive that is on the approved media list for Blackmagic cameras, but the problem persist.
- I am currently waiting for a CFAST 2.0 card to run more tests.
The only issue that occurred periodically, is that sometimes the SSD is not recognized: when this happens, we change the usb-C cable or format the SSD and it's all back to normal...
This is not the case anymore...
ISSUES in detail:
Case 1 - SSD is not detected 80% of the time after boot. (we have tried original Sandisk cables, Kondor Blue, Smallrig, YIWENTEC USB C 3.2) Sometimes it gets recognized, sometimes it doesn't. Same SSDs work great with the URSA Mini and gets detected instantly!
WORKAROUND:
When the SSD is not recognized, a workaround is to turn off the camera, disconnect the drive then turning on the camera and plugging the SSD back again. This old trick doesn't work anymore...
Once the camera manages to read the drive:
Case 2 - Drop frames after a few frames or seconds (depending on FPS / Codec and compression quality). Switching to another SSD the problem still happens.
Case 3 - The camera can freeze after hitting the rec button to stop the recording. The only way to unfreeze it is to turn it off with no assurance that the file has been saved fully.
(I recorded a 1h20min concert but when I got back I only found the first 20 min of footage. During the recording the timecode would keep going colored in red and the interface showed that the camera was effectively in rec. This had never happened before with BMD cameras)
Case 4 - The camera works fine.
This behaviour is totally random as I need to turn on and off the camera dozens and dozens of times before it manages to read the ssd and keep it up with long time recording without failing.
We tested different powering solutions to power up the 6kPro
- Blackmagic Design NP-F570 Battery,
- AC Power Adapter,
- SmallRig V Mount Battery Adapter Plate with Dtap
Before shooting we format the drives in camera or through Video Assist 12G in exFAT format. The camera has been resetted to factory settings many times.
The situation it's getting worse and the camera turns to be unfit for professional work. Furthermore, it is difficult to reproduce the error with certainty, as the camera can work great for a few hours and then behave like described.
IMO the usb-c port is about die, and I need to send the camera back for assessment, but I'm curious to hear other users' feedback. Have any of you had this problem and found a solution?
Once you're lucky and the SSD gets detected the camera either drop frames after few seconds and quits recording. While shooting longer takes it can freeze when hit the rec button to stop the recording (subsequently losing the video clip)
Firmware: 8.6
For three years we have shot exclusively with SanDisk Extreme Portable pro V2 SSDs USB-C drives almost flawlessly both on 6kPro and Ursa Mini Pro 12k.
- 1x 4TB,
- 3x 2TB,
- 1x 1TB
- Recently, following Blackmagic Support suggestion, we purchased a Samsung T7 Shield Portable SSD 2TB, a drive that is on the approved media list for Blackmagic cameras, but the problem persist.
- I am currently waiting for a CFAST 2.0 card to run more tests.
The only issue that occurred periodically, is that sometimes the SSD is not recognized: when this happens, we change the usb-C cable or format the SSD and it's all back to normal...
This is not the case anymore...
ISSUES in detail:
Case 1 - SSD is not detected 80% of the time after boot. (we have tried original Sandisk cables, Kondor Blue, Smallrig, YIWENTEC USB C 3.2) Sometimes it gets recognized, sometimes it doesn't. Same SSDs work great with the URSA Mini and gets detected instantly!
WORKAROUND:
When the SSD is not recognized, a workaround is to turn off the camera, disconnect the drive then turning on the camera and plugging the SSD back again. This old trick doesn't work anymore...
Once the camera manages to read the drive:
Case 2 - Drop frames after a few frames or seconds (depending on FPS / Codec and compression quality). Switching to another SSD the problem still happens.
Case 3 - The camera can freeze after hitting the rec button to stop the recording. The only way to unfreeze it is to turn it off with no assurance that the file has been saved fully.
(I recorded a 1h20min concert but when I got back I only found the first 20 min of footage. During the recording the timecode would keep going colored in red and the interface showed that the camera was effectively in rec. This had never happened before with BMD cameras)
Case 4 - The camera works fine.
This behaviour is totally random as I need to turn on and off the camera dozens and dozens of times before it manages to read the ssd and keep it up with long time recording without failing.
We tested different powering solutions to power up the 6kPro
- Blackmagic Design NP-F570 Battery,
- AC Power Adapter,
- SmallRig V Mount Battery Adapter Plate with Dtap
Before shooting we format the drives in camera or through Video Assist 12G in exFAT format. The camera has been resetted to factory settings many times.
The situation it's getting worse and the camera turns to be unfit for professional work. Furthermore, it is difficult to reproduce the error with certainty, as the camera can work great for a few hours and then behave like described.
IMO the usb-c port is about die, and I need to send the camera back for assessment, but I'm curious to hear other users' feedback. Have any of you had this problem and found a solution?