News:

Willkommen im Notebookcheck.com Forum! Hier können sie über alle unsere Artikel und allgemein über Notebook relevante Dinge disuktieren. Viel Spass!

Main Menu

Latest Windows 11 update reportedly triggers SSD failures during heavy file transfers

Started by Redaktion, August 17, 2025, 17:50:20

Previous topic - Next topic

Redaktion

The Windows 11 update KB5063878 is apparently causing SSD failures on PCs while attempting heavy file transfers. Japanese outlet NichePCGamer reports that SSDs from several brands are affected, but Microsoft has yet to verify the issue.

https://www.notebookcheck.net/Latest-Windows-11-update-reportedly-triggers-SSD-failures-during-heavy-file-transfers.1089249.0.html


punmeister

I would not be the least bit surprised that their aggressive, organizational AI push doesn't have any human in the loop guardrails. Microsoft will be making a bunch of vibe coders like this.

Daniel H

I have just bought two new 4tb N2 San controller drives, the first drive hated the mass transfer and corrupts the drive.  Formatted the drive even slowly, and still happens.  Then I thought hmm the drive might be faulty, but tried the second one BUT this time I am actually doing one file at a time and seems to be working fine.  I think also if it has Multiple session writes like two different file sets been transfered at the same time then it bugs out.

Hotz

Quote from: Daniel H on Yesterday at 08:48:39I have just bought two new 4tb N2 San controller drives, the first drive hated the mass transfer and corrupts the drive.  Formatted the drive even slowly, and still happens.  Then I thought hmm the drive might be faulty, but tried the second one BUT this time I am actually doing one file at a time and seems to be working fine.  I think also if it has Multiple session writes like two different file sets been transfered at the same time then it bugs out.

What you describe, sounds like the drive gets too hot (temperature rises fast when doing big file transfers), and then bugs out.


Generally speaking, I also believe this (overheating) is the main cause for most SSD failures. Which makes it even more pathetic that drive speeds are getting faster and faster and faster.

SSDs can at maximum bear PCIE 3.0 speeds (3.500mb/s) without a heatsink and without overheating. Anything faster will result in overheating. When the SSD overheats, it should throttle, but here comes the next problem: some temperature sensors on the SSD do not measure the temperatures correctly either which has been shown in many tests from TechPowerUp and TomsHardware. Thus the throttling probably happens too late and the drive overheats, degrades, bugs out, switches off.

While you can prevent overheating with heatsink, many people do not have appropriate ones. And with questionable temperature sensors on the SSDs any PCIE 4.0 drive (7.000mb/s) is risky to use, and any PCIE 5.0 drives (14.000 mb/s) absolutely crazy and dangerous. And this is precisely why I hate that they are pushing higher and higher SSD speeds (now there's even talk about PCIE 6.0 with 25.000mb/s), but which are absolutely stupid for consumer products, and at the same time remove basically all good (cool) PCIE 3.0 drives from the market (such as SK Hynix P31 Gold or similar ones)...

FriedFrenchFries


RoAlPf

Hello,
I also have a Corsair NVMe in my computer and am struggling with the same problem. I even ordered a new NVMe because I thought it was giving up the ghost, and now I'm reading this crap about an update.
My Windows crashes and then the NVMe can't even be found in the BIOS anymore. You have to turn off the PC for a long time, which is the only way to get the NVMe back. Rolling back the update probably won't work anymore, because then it crashes...

A

Quote from: Hotz on Yesterday at 09:31:21
Quote from: Daniel H on Yesterday at 08:48:39I have just bought two new 4tb N2 San controller drives, the first drive hated the mass transfer and corrupts the drive.  Formatted the drive even slowly, and still happens.  Then I thought hmm the drive might be faulty, but tried the second one BUT this time I am actually doing one file at a time and seems to be working fine.  I think also if it has Multiple session writes like two different file sets been transfered at the same time then it bugs out.

What you describe, sounds like the drive gets too hot (temperature rises fast when doing big file transfers), and then bugs out.


Generally speaking, I also believe this (overheating) is the main cause for most SSD failures. Which makes it even more pathetic that drive speeds are getting faster and faster and faster.

SSDs can at maximum bear PCIE 3.0 speeds (3.500mb/s) without a heatsink and without overheating. Anything faster will result in overheating. When the SSD overheats, it should throttle, but here comes the next problem: some temperature sensors on the SSD do not measure the temperatures correctly either which has been shown in many tests from TechPowerUp and TomsHardware. Thus the throttling probably happens too late and the drive overheats, degrades, bugs out, switches off.

While you can prevent overheating with heatsink, many people do not have appropriate ones. And with questionable temperature sensors on the SSDs any PCIE 4.0 drive (7.000mb/s) is risky to use, and any PCIE 5.0 drives (14.000 mb/s) absolutely crazy and dangerous. And this is precisely why I hate that they are pushing higher and higher SSD speeds (now there's even talk about PCIE 6.0 with 25.000mb/s), but which are absolutely stupid for consumer products, and at the same time remove basically all good (cool) PCIE 3.0 drives from the market (such as SK Hynix P31 Gold or similar ones)...

Most of these SSD speeds are useless anyways, they are for consecutive read/write that only happens on a fresh SSD. With time, the SSD is going to fragment be it normally or through trim.


Quote from: RoAlPf on Yesterday at 12:16:14Hello,
I also have a Corsair NVMe in my computer and am struggling with the same problem. I even ordered a new NVMe because I thought it was giving up the ghost, and now I'm reading this crap about an update.
My Windows crashes and then the NVMe can't even be found in the BIOS anymore. You have to turn off the PC for a long time, which is the only way to get the NVMe back. Rolling back the update probably won't work anymore, because then it crashes...


Consider switching to linux

Microshit Wangblows

Anyone surprised that a company which outsourced the majority of it's "engineering" to cheap third world s*** holes produces failure after failure? Lol..

Quick Reply

Name:
Email:
Verification:
Please leave this box empty:

Shortcuts: ALT+S post or ALT+P preview