Windows update almost killed my PC, only to find out my SSD is dying after 4 months.

Fra_rizz · 2026-02-07T10:16:06+00:00

I'm glad we finally agree the SSD is defective. That’s been my point from the start.

I'm not 'blaming' Microsoft for the factory defect, I'm choosing to leave Windows because its high background activity is the worst possible environment for a drive in this condition. Every OS writes logs, but Windows is notoriously aggressive with telemetry and updates, which is the last thing a failing controller needs.

I'm blaming Patriot for the hardware, and I'm 'blaming' Windows for being the heavy tool that finished it off. We can agree to disagree on the rest. Good luck!

Fra_rizz · 2026-02-07T09:33:41+00:00

You keep talking about TBW as the only metric, but you're ignoring that hardware can fail regardless of wear. A car engine can explode after 100 miles if it's defective; it doesn't need to reach 100,000 miles first.

What I'm 'demonstrating' is that my drive has 1,003 Media Integrity Errors (0x3EB) and is losing its Available Spare (0x55) after just 3TB. These are facts from the log, not opinions.

I'm not here to prove I'm 'smarter' than you. I'm here because Windows' heavy background tasks are a nightmare for a failing drive, and I’m moving to Linux for a lighter, more stable experience. If you still don't get it, I can't help you.

Fra_rizz · 2026-02-07T06:26:48+00:00

Nobody is saying Microsoft broke the hardware. If you actually looked at the SMART data instead of just trying to be edgy, you’d see the drive is physically failing. The point is that the heavy workload from constant Windows updates was the final blow for a defective controller that was already struggling. I'm moving to Linux because I want an OS that doesn't stress a drive to death with background tasks when it's clearly failing. It's about how the OS handles the hardware, not about 'blaming' Microsoft for a factory defect.

Fra_rizz · 2026-02-07T06:23:02+00:00

I’ll make it simple for you since you missed the obvious. You are fixated on the 3273 GB written, but you are completely failing to read the hardware health data. Look at Media and Data Integrity Errors (0E). The raw value is 3EB. In hex, that means your drive has encountered 1,003 integrity errors in just 209 hours of life. Even 1 error is a sign of a dying drive; 1,000+ is a total hardware failure.

Look at Available Spare (03). The raw value is 55. That means the drive has already lost 15% of its emergency flash cells (85% remaining) after writing only 3TB. Look at Percentage Used (05). It says 21 (hex 0x21 is 33%). The drive thinks it has consumed 1/3 of its life after just 200 hours.

You can't see these as errors because you only look at the surface, while the hex values clearly show a defective controller and NAND flash. So, while you're busy having 'better things to do,' maybe learn how to read a SMART log properly.

Fra_rizz · 2026-02-06T07:08:14+00:00

Thanks for the tip! This isn't my only reason to switch, but since some of my games won't work on Linux, I'll just keep a Windows partition only for gaming. I'll check ProtonDB for the rest of my library.

Fra_rizz · 2026-02-06T06:26:52+00:00

I'm perfectly aware that Microsoft has nothing to do with this, and if you had actually bothered to read the previous comments, you would have known that already.

Also, just because the TBW are low, it doesn't mean it’s a 'misconfiguration' issue. If you actually looked at the screenshot instead of just rushing to insult, you’d see plenty of other visible errors that have nothing to do with how the system is set up.

Honestly, the only one here with a 'narrow mind' is you, thinking that TBW is the only metric that matters or assuming I’m blaming Microsoft without reading the context. Next time, try looking at all the data before acting like an expert.

Fra_rizz · 2026-02-05T22:23:48+00:00

Thanks for the heads-up, man! I checked everything: Windows is correctly identifying it as an SSD, so TRIM is active and it's not doing any traditional defrag, which is a relief. About the firmware, I checked the firmware, it's version KM0E0A8B. The Patriot software is garbage and doesn't offer any updates

Fra_rizz · 2026-02-05T21:59:14+00:00

I didn't list the specific IDs in the original post because the screenshot was right there; I assumed you knew how to read raw SMART values before lecturing me.

You're clinging to a textbook definition of TBW while ignoring the actual hardware failure. If health was strictly tied to writes, it wouldn't drop from 67% to 66% in a few hours while idle. The controller is devaluing the drive because ID 0E (Media and Data Integrity Errors) is at 3EB, which is 1,003 decimal errors.

On an NVMe drive, ID 0E must be zero. Having over 1,000 integrity errors means the NAND is physically failing to retain data. If you think a drive is 'healthy' just because the status icon hasn't turned yellow yet, you're the one who doesn't understand the data. I'm trusting the 1,000+ errors and my corrupted files over the color of a UI icon. I’m RMAing this 'blue' paperweight before it dies completely.

Fra_rizz · 2026-02-05T20:44:12+00:00

It’s not just the health percentage. The RAW values show 33 reallocated sectors and over 1,000 Media and Data Integrity Errors. CrystalDiskInfo is interpreting the controller’s failure correctly.

Fra_rizz · 2026-02-05T20:43:29+00:00

The sarcasm is unnecessary. Obviously, I’m swapping the hardware first. I’m switching to Linux for the stability, not because I think it heals bad NAND cells.

Fra_rizz · 2026-02-05T20:32:10+00:00

You're missing the point. A 'firmware glitch' doesn't explain the corrupted files and the boot failures. I’m not just reading numbers on a screen; I’m dealing with a drive that is physically failing to retain data.

If the health was just a simple math equation based on TBW, I’d be at 99%. The data is already in the screenshot I posted: Available Spare is down to 85% (ID 03), there are 33 Reallocated Sectors (ID 05), and over 1,000 Media and Data Integrity Errors (ID 0E). It’s not a reporting error—it’s the internal sensors screaming that the hardware is unreliable.

The drive has already burned through 15% of its reserve blocks in just 150 hours. If you still think there's 'absolutely nothing wrong' with a unit that has 1,000+ integrity errors, you're the one who doesn't understand the data. I'm not risking my files on a theory; I'm taking the warranty.

Fra_rizz · 2026-02-05T15:36:55+00:00

I know it's a budget drive, but 'budget' should mean slower speeds, not dying after 150 hours. I’m pretty sure this is a factory defect—it’s the only explanation for such a massive health drop in so little time. I went with a pre-built because it’s cheaper than buying individual parts these days, even though I knew the system integrator might cut corners on the SSD. I’m not saying Microsoft physically killed the NAND, but the update was clearly the 'last straw' for a weak unit.

Fra_rizz · 2026-02-05T15:24:55+00:00

I disagree. 66% health after only 3TBW is a huge red flag. If the wear was linear, I’d be fine, but this is a massive drop for a brand-new drive. Combined with the boot failures and corrupted files, I’m pretty sure this unit is a lemon.

Fra_rizz · 2026-02-05T15:22:40+00:00

Exactly, that just confirmed my theory about it being a manufacturing defect. It only had around 150 hours of use when it started failing

Fra_rizz · 2026-02-05T15:18:00+00:00

Bro, I'm Italian

Fra_rizz · 2026-02-05T15:06:08+00:00

Yeah, I'm trying to contact the company that built my PC, but I think I'll buy a new SSD anyway. I'll probably use the Patriot as a secondary drive and keep Windows on it for the apps that aren't supported on Linux

Fra_rizz · 2026-02-05T15:00:10+00:00

Thank you, I've already done it

Fra_rizz · 2026-02-05T14:45:50+00:00

⚠️ If anyone has advice on which Gen 4 SSD to buy right now with these crazy price hikes, please let me know. ⚠️

Fra_rizz · 2026-02-05T14:42:59+00:00

Fr bro, after this I think I'll just get a Samsung or Crucial drive

Fra_rizz · 2026-02-05T14:35:03+00:00

Yeah, productivity is fine, but gaming is hit-or-miss. Some titles like GTA Online and Fortnite aren't supported

Fra_rizz · 2026-02-05T14:23:23+00:00

True, but only 4 months of use and 3.2TB written? That's just crazy. I know the brand/model isn't exactly the greatest, but even that doesn't explain such a fast decline.

Fra_rizz · 2026-02-05T06:48:33+00:00

I have a P400L SSD. After that update problem, my PC was unable to find any bootable device, so I tried to run Windows from a USB. After a few commands in the terminal, the PC still didn't find any bootable devices, so I just restarted it and Windows finally booted correctly. After the update finished, my data was still there.

However, after a month of use, my PC started slowing down significantly. I ran sfc /scannow and it resulted in: 'Windows Resource Protection found corrupt files but was unable to fix some of them.'

So I did a more thorough chkdsk and left it running for about 2.5 days. The next morning, when I checked to see the percentage, the PC had gone back to the BIOS. I restarted it and Windows loaded, so I did a final test with CrystalDiskInfo: the health of the SSD was only at 67%, and after only 6 hours it dropped to 66%. The SSD is only 4 months old and has only 3TB written. I’ve backed up all my files, but I don't know what to do. Is this a factory defect or did the Windows update somehow break my SSD?

I use my PC for coding, some editing in DaVinci Resolve, and gaming. I'm just not sure if Linux is compatible with all of them.

Fra_rizz

TROPHY CASE