Windows 11 cleared of all charges for killing SSDs, the real culprit is faulty firmware

[Loadedaxe]

Armchair firmware ''experts'' with zero firmware coding experience have a argument with people who do not code windows updates ,,, newsz at 11

Yeah, because only people who write firmware updates are allowed to notice when it's broken. By that logic, I guess you need to be a chef to know when your food is burned, too.

 

[RudyBob]

There goes my class action, I was gonna make a pantload of money

 

[Rocky4040]

Whatever was in the updates was the trigger to the problems. MS needs to do whatever is necessary to remove from those updates the trigger and release the updates with the fixes in them. They can say all they want oh it was not the update's fault but to me a fully working system went from well fully working to a dumpster fire after the updates leads me to think the updates were the trigger that started the problems. Whether it was a problem caused from the updates and the system bios not working well together or the SSD firmware and the updates not playing well with each other. For them to sit there and think they are in the clear because they ran a few tests and could not find a problem does not mean the problem is not there.

I will say it again those updates were the trigger point. for reference Jays2Cents has a video on this topic and he had a system that was fully working then the updates got installed and started having problems with the installed NVMe drive and the F1 racing game crashing the drive and the problem was getting worse the longer he tried to find a fix for this problem.

What he ended up doing was updating the mainboard bios 2 revisions newer, and the problem went away. This leads me to be leave MS changed something in the secure boot programing in windows which was messing up the system bios and the way it handles secure boot or the NVMe drive itself. Because a bios update seemed to make the problem better, I am leaning towards the problem being something in the bios needed to be changed. This should have never happened MS should know better than this. This is what happens when you hire a bunch of fresh out of college students or rely on AI to do your programing.

 

[moonbaseNewton]

Well, this time, I was wrong too, it was not windows! Cool! But it does not solve my problem. My SSD crashes when I try to write a large amount of data to it.

But still one question remains: how come I DID NOT HAVE this problem before the windows update on the EXACT same hardware? This is a really interesting question I think...

Do you have the engineering sample firmware on your SSD? That appears to be the root cause.

 

[moonbaseNewton]

The crucial falsification test for the hypothesis that it was caused by MS, and the falsification test that it was caused by firmware, are both missing.

1) Does the crash occur on pre-update Windows with the dodgy firmware?

If not, then it isn't JUST the firmware. This is the most important test IMHO and I see no mention of it in the article.

2) Does the crash occur on updated Windows without the dodgy firmware?

This seems to have been done but isn't clearly communicated, and we don't know what the rate of failure was or how many times the testing was done.

 

[StrikerRocket]

Do you have the engineering sample firmware on your SSD? That appears to be the root cause.

I don't know if it is an engineering sample, it's version 3.M.A.10. Orico is a cheap chinese brand I bought on amazon some time ago. No info on their website. For all I know, maybe it's a rebranded SSD from another manufacturer who flashed the ES version of the firmware.
I retried writing the same data to it without problem though, so I really don't know and won't investigate more. There's enough as it is.