Game crashed, killed M2 SSD (no bootable device)

Not to get away from the performance issues that BF6 is having, but there was an issue recently with some M.2 drives "dying" and or disappearing/disconnecting from the PC. That may be part of your issue here.

https://www.youtube.com/watch?v=YjcMM5hZqmA

I did see that a lot of forum posts popped up recently regarding win 11, AMD and NVMe drives. I do still have 4.5 years of warranty, so Ill try to contact the supplier today. Still sucks that one can't really play games without the fear of just erasing an entire drive :/

LesserChaos​ having a storage drive fail is something I worry about. I'm still traumatized from having multiple IBM Deskstar (Deathstar) hard drives fail on me in the early 2000's.

The SSD was probably faulty and going to fail no matter what.

I run windows on a separate NVMe, this would be why...

You can only write so much information to it. 

Then it's gone.

Apparently, it will be read only now, and you can recover information using a m2 to usb adapter.

Check how much read/write the drive is built for, then keep that in mind while using it and or keep track in your ssd health care software.

There's no way the game "killed the ssd". A faulty SSD died while you happened to be running the game.

RMA the drive.

The TBW (Terabytes Written) spec of SSD's is interesting. I looked up the spec for Samsung 9100 PRO 2 TB.

https://images.samsung.com/is/content/samsung/p6pim/us/mz-vap2t0b-am/specsheet/us-specsheet-mz-vap2t0b-am-548821014.pdf

It's rated for 1,200 TBW. Meaning the drive is rated for 1,200 terabytes of data being written to it.

I plugged that number into Google AI and it came back with this.

writing 12 terabytes per year would take 100 years to reach 1,200 TBW.

There's 12,000 GB in 12 TB. The SSD stores 2 GB of data.

The drive can be completely filled 6,000 times per year for the next 100 years.

( 12,000 GB ÷ 2 GB = 6,000 )

I find technical specs like this interesting. I personally find these specs hard to believe but Samsung claims to have carried out testing to verify these numbers.

Of course that's only if the SSD doesn't suddenly fail. The specs also claim the SSD can can run for 171 years 24/7, but it only comes with a 5 year warranty.

I'm finding these manufacturer specs harder and harder to believe!

I learned my lesson about backing up important data. The final straw was when my password manager database suddenly became corrupt and I didn't have a backup. There went all my passwords!

I always keep backups now. The 3-2-1 Backup Rule is the gold standard for a backup plan.

Your math is a little out there.

It's a 2TB drive and the endurance is 1200TB, so you can erase the drive at best 600 times before you have reached the endurance level. However taking write amplification into account, even at 1.2 would put it at more like 500 erase cycles.

There is a tremendous amount of grey around this issue, but the testing methodology is kind of off too (the JEDEC testing standard for CONSUMER SSD's). From memory it's something like  when the writes are 10 degrees celsius hotter than the storage temperature (40 working/30 storage), how many times you can erase the drive before 3% of the drives lose data after 1 year. 

So, what that means to consumers, if you are near the write endurance, what the endurance is telling you is that if you store the drive at 30 degrees for a year there should be about a 3% chance that it will lose data. Most consumers would probably go ??? to that.

I used the word erase because that's actually what causes the degradation, it's not the writes. That's why write amplification is a thing. And a hot write temp and cold storage temp retains data for longer. If you were to take a drive at the endurance level and store it for a year at 30 degrees, it should retain data. I think it was like 10 degrees halves the retention rate, so if you stored it at 40 degrees you'd only expect 6 months...

The enterprise test is even crazier, enterprise drives are only tested to retain data for 3 months.

Most likely not, I am leaning towards faulty SSD too, but want to document this as an issue still in case of other instances popping up regarding this. Might be coincidence. But still, the game was running whilst it died, so I am not ruling out the possibility 

Drives die early, typical figures for SSD's are around 1% unless there's some design/manufacturing/firmware defect on the model. Just one of the unlucky 1% really.

It's not even a NAND problem, as in too much data written, just sounds like the controller died on the drive. Don't know of any way an app could do that unless it was specifically trying to be malicious, just bad luck...