- Windows 11’s August update would have introduced an SSD rupture bug
- It has been suggested that SSDs using pHison controllers are more likely to be affected
- Phison has carried out in -depth tests, but could not reproduce the bug only once, adding that its customers did not report the problem either
The bug that recently emerged in Windows 11, which would have broken certain SSDs, is the subject of a survey by Microsoft and its partners – and now we have heard of one of the parties involved.
This is Phison, which manufactures SSD controllers used in a wide range of disks from various manufacturers, and is involved in this controversy because certain reports suggest that SSDs using these controllers were more likely to be affected by the bug.
Phison has now shared the results of its in -depth tests concerning this question, as reported by Neowin, issuing the following statement: “Phison dedicated more than 4,500 hours of cumulative tests to the disks reported as potentially impacted and carried out more than 2,200 test cycles. We could not reproduce the reported problem, and no partner or customer has reported that the problem has affected their drives at that time.”
So Phison believes that it is clear, with many tests having revealed anything, and no report coming to the business of its customers either. Of course, individual consumer reports will go directly to the SSD maker (not those responsible for the controller), but when Phison says “partners or customers”, these are these reader manufacturers (and others too, without a doubt, Microsoft included).
What did not help the cause of Phison here is a false document that made the rounds online just after the bug was revealed in the August update of Windows 11. This claims to contain a list of Phison controllers affected, but was completely manufactured because the company quickly indicated.
Analysis: Microsoft’s results are still to come
Although Phison has carried out in -depth tests, this cannot be considered as a final conclusion. Microsoft’s investigation into this SSD break -up bug in Windows 11 is still in progress, and until we saw the result, there is any doubt about exactly what is happening here.
SSD failure reports remain dispersed. It should therefore be noted that this seems to be a rare problem. In any case, I hope that Microsoft will make its conclusions known as soon as possible, and will clarify this question – because it is only confusing with this last episode of the saga.
Phison has also nailed on certain advice with his declaration on best practices to “take charge of high performance storage devices” during extended workloads, such as the change in large files – like prolonged writing operations which have apparently triggered the Windows 11 bug. Phison observes that an “thermal box or an appropriate thermal cushion” will help in terms of optimal temperatures To ensure that the reader does not become too hot (or the throttes accordingly).
Note that the transmission of these tips is not directly linked to the bug – which means that Phison does not say that you should use a thermal dissipator to avoid getting out of the rails with this Windows 11 problem. These are just general advice intended for all high -end SSD owners, which lets them know that if they perform intense workloads on long durations, the use of additional cooling is recommended.
Be careful, if your SSD does not already have a thermal dissipator, adding one is a somewhat delicate affair, especially for the least informed of the technology (although they are less likely to organize training in the solid high performance state, certainly).
