It's 2025, why does Windows 10 crash trying to copy files ?? - Page 1
Forum section: electronics / general

author: MathWizard
author_rank: Super Contributor
timestamp: June 19, 2025, 01:18:28 am
content: I have an lean and fast i-14900K PC, and my main storage SSD is a TeamForce 2TB, it's not great at small file transfers. I also have a fast Samsung Evo 870 SSD or NMVE, that I'm trying to copy some files onto, both are pretty new.Today trying to copy 15GB of of program applications, like KiCad, it just can't do it. It hits 4%, and hangs for many minutes, then it does somehow jump to 18% when it's copying the KiCad installer, but then other programs start failing like firefox, VLC, and taskmanger can't close anything, or even itself, and the time estimate for copying the files is over 1 day. I've left it for upto ~20mins, before having to reboot. 1 day I tried to copy a bunch of movies, and I also had to reboot in no time, it froze.I looked around and so far did "Disable Remote Differential Compression (RDC)", and that didn't work. Should try "Enable the AHCI Mode" ? IDK what they are these days by default.So any idea's, and it's pretty bad in 2025 when you can't copy files between your drives.

author: IanB
author_rank: Super Contributor
timestamp: June 19, 2025, 01:26:58 am
content: Not really sure, but you might want to open up a command prompt and investigate xcopy?Be sure to use the /L flag first with the /F flag, so you can see what the command is going to do before you run the copy for real.

author: coromonadalix
author_rank: Super Contributor
timestamp: June 19, 2025, 01:30:35 am
content: could even be you av who crash your system, i move tons of huge files like you, av disabled, nothing else ... it does the jobinternals to usb3 devices, to usb keys 512gb ones, usb to usb ... no problemsone thing to consider is : widows suck real time when it says finished copying, but in the background it continuesdo not change your once installed drive to ahci or ahci to else, once your system is running, it could mess big timecheck you device manager, does it miss some drivers for some hardware peripherals, mostly Intel IRST driver, Intel Chipset, Intel ME .... or updated ones ...

author: IanB
author_rank: Super Contributor
timestamp: June 19, 2025, 01:40:38 am
content: Solid state drives can sometimes overheat when writing large amounts of data onto them, which could cause them to do thermal throttling, or even cause the drive controller to lock up. Depends on the quality of the drive, and if it has a good heat sink.

author: IanB
author_rank: Super Contributor
timestamp: June 19, 2025, 01:45:01 am
content: Also, 15 GB is not a lot. I can copy 1 GB of files from source to destination in a few seconds. So 15 GB should take very little time at all.There's something fundamentally not right somewhere.

author: DimitriP
author_rank: Super Contributor
timestamp: June 19, 2025, 01:51:28 am
content: terse version:Try a benchmark and pay attention to 4k and 8k size transfers.Are they both good, both bad or you have one of each ?IDE drivers. Update to the lataest and if running the latest, go back one or twothen try the benchmark again.Whadayasee?

author: MathWizard
author_rank: Super Contributor
timestamp: June 19, 2025, 02:02:48 am
content: I would have setup both drives with the default settings in win10, and the TeamF is 1/2 empty, and the EVO is mostly empty. Neither have partitions. It only takes a few seconds to copy a 2GB movie.

author: MathWizard
author_rank: Super Contributor
timestamp: June 19, 2025, 03:15:44 am
content: Now I'm starting to think the EVO 870 is screwed up. Earlier when I was copying files, they where in a directory called prog. And after cancelling and rebooting in the middle of all that, I can't access the prog folder, and the PC is lagging when trying to do stuff with the drive. There's barely anything on there, so I'm trying to quick format it, only nothing seems to be happening. The progress bar hasn't shown anything after a few minutes, and trying to cancel it, doesn't work, win10 say it can't cancel in the middle of formatting, it gave a retry option, I clicked it, and now a while later I was able to close the format box. But now clicking on that drive, I get an in accessible drive error.I can run Crystaldiskinfo, and it looks ok, but it's 99% life already, IDK how they calculate that, but I only bought this winter, and only had a 100GB or so put on there.And windows is not happy, certain things seem to lag, like opening programs. If it's still wacky after rebooting, I'll hvave to remove the drive, and test it in another PC. At least it's under warranty.The TF is a cheap, low performance storage type drive, it's temp sits at 64C, IDK how much of that is from my GPU, but it reads at 100% good, and it probably 1yro or more. I should try copying that 15GB from it to another drive, hopefully the TF and win10 won't still crash, and it's just the samsung.

author: Simmed
author_rank: Frequent Contributor
timestamp: June 19, 2025, 03:21:59 am
content: its happening again ?https://www.techpowerup.com/forums/threads/samsung-870-evo-beware-certain-batches-prone-to-failure.291504/https://forums.servethehome.com/index.php?threads/all-my-samsung-500gb-ssd-870-evo-failed-ecc-error.41548/from LTT forumhttps://linustechtips.com/topic/1609050-samsung-ssd-870-evo-1tb-had-multiple-bad-blockssectors-after-a-full-format-is-now-showing-only-good-sectors-is-it-still-usable/

author: wraper
author_rank: Unknown
timestamp: June 19, 2025, 04:02:05 am
content: Quote from: MathWizard on June 19, 2025, 03:15:44 amTry to secure erase it by Samsung Magician.

author: Analog Kid
author_rank: Super Contributor
timestamp: June 19, 2025, 05:29:10 am
content: Thanks for all this.I think I'll stick with good old magnetic disk drives for the foreseeable future.

author: Monkeh
author_rank: Super Contributor
timestamp: June 19, 2025, 05:33:26 am
content: Quote from: Analog Kid on June 19, 2025, 05:29:10 amAs someone with a few decades of experience with 'good old' magnetic drives.. thanks for the laugh.

author: Ranayna
author_rank: Super Contributor
timestamp: June 19, 2025, 06:46:41 am
content: Quote from: MathWizard on June 19, 2025, 03:15:44 amCheck your cabling. High numbers of CRC errors (SMART Attribute C7) are an indicator for bad cables in many cases.The 99% lifetime is simply a count of remaining reserve sectors (likely in this case an inverse of "Wear Leveling Count", SMART Attribute B1) , rounded down. A new drive will go to 99% very quickly, even on low usage.

author: Haenk
author_rank: Super Contributor
timestamp: June 19, 2025, 07:13:17 am
content: This certainly sounds like bad blocks; 15GB should not lead to overheating.Don't trust SMART values, as the SSDs do auto-reallocate damaged blocks.However, the reallocation does hit the performance, so I suggest using e.g. Hard Disk Sentinel and do a full write/re-read reformat of the drives. While that could be done with other software, HDS creates a performance map of the drive - you will easily see, if there are problematic patterns or areas.

author: tszaboo
author_rank: Super Contributor
timestamp: June 19, 2025, 07:49:12 am
content: I had issues copying, but it rarely was an issue with Windows. It turned out to be a deteriorated SSD.The same was the last time I had bluescreen, it was badly written drivers.When it was slow, it was trying to copy 1kB files to a flash drive with gigantic page size. I placed it into a zip file, and then the entire process were seconds.So Zip the files, and copy like that. And if you really need to copy a bunch of small files, use Teracopy. You can pause it, batch commands, check CRC and so on.

author: Jeroen3
author_rank: Super Contributor
timestamp: June 19, 2025, 08:07:56 am
content: Windows is unable to handle stalled or misbehaving IO. It does not tell you a disk is failing, it does not unmount or offline it either, and IO timeout are set ridiculously long.All the time it is waiting, it will just stall all IO operation related to that disk/controller. Causing the behaviour you're having.See the system event log for IO errors, there probably are some.You may have encounted this behaviour when you inserted a damaged SD card, windows will just stall until you remove the card again.Problems in the transaction between disk and sata controller should be invisible for Windows, but it will cause an IO operation to take longer.Your C7 value is high, indicating a problem.I would recommend using HD Sentinel for monitoring as it shows you the values over time. (it stores history for you)

author: Psi
author_rank: Super Contributor
timestamp: June 19, 2025, 08:21:44 am
content: How does your device manager look, any devices without drivers or not working?It's pretty common for people to forget to install their motherboard chipset drivers for things and windows falls back on built-in drivers which are not always very good. Especially if the hardware is high-end and running at high speed.

author: Haenk
author_rank: Super Contributor
timestamp: June 19, 2025, 09:22:28 am
content: I just compared the stats with my 100000h+ Samsung 840 Pro - your SSD is defective; mine has stated zero ECC errors and zero bad blocks, even though wear level is down to 86%.Replace immediatly.

author: MathWizard
author_rank: Super Contributor
timestamp: June 19, 2025, 09:37:07 am
content: I bought it in January from Amazon.ca. This is the 2nd SSD I've had had fail over the years, so still not too bad. Yeah I'll try SamsungMagician, and maybe a benchmark if it's still capable of doing anything. It's the 2.5" version, not NMVE. I'll try it on another PC.There was a critical error in the WindowsEventViewer, twice last night it tried to do defragging, but it failed. Besides that, I just see a bunch of warnings, I think when I was trying to use it. Or it could be when windows started lagging, because right now my main C: drive is called disk1.

author: Psi
author_rank: Super Contributor
timestamp: June 19, 2025, 09:40:19 am
content: Quote from: MathWizard on June 19, 2025, 09:37:07 amTry a different SATA cable and port on the motherboard.They can be randomly faulty.

author: wraper
author_rank: Unknown
timestamp: June 19, 2025, 09:48:37 am
content: Quote from: MathWizard on June 19, 2025, 09:37:07 amTry changing SATA port, cable. Ports and cables sometimes go bad. I once had a hard to catch issues due to a bad SATA cable myself, took many months to figure out it was due to a cable.

author: Jeroen3
author_rank: Super Contributor
timestamp: June 19, 2025, 09:54:54 am
content: Those warnings are a big red flag something is wrong with the hardware.

author: tom66
author_rank: Super Contributor
timestamp: June 19, 2025, 10:31:04 am
content: To be fair to Windows, Linux does much the same thing when IO ops fail. Write ops block subsequent read ops, and if a drive is used to store programs or libraries, a failing SSD can easily cause a system lockup.

author: Jeroen3
author_rank: Super Contributor
timestamp: June 19, 2025, 10:32:31 am
content: No, in Linux only the affected device locks up, not the entire IO subsystem.This is why you can use ddrescue like tools, and why data recovery on windows is basically impossible.

author: rsjsouza
author_rank: Super Contributor
timestamp: June 19, 2025, 10:53:40 am
content: I also suspect that one of your drives is failing indeed. Over the years I had similar issues with various versions of the Windows OS and types of media: magnetic HDDs, USB flash, SD cards, etc.For secure copies meant for backup, I have been using Teracopy for many years. When used with verification, I haven't detected any failing discrepancies between the source and the copied files.

author: tom66
author_rank: Super Contributor
timestamp: June 19, 2025, 11:06:07 am
content: Quote from: Jeroen3 on June 19, 2025, 10:32:31 amDidn't realise you meant whole IO system... maybe the case for Windows, I am not sure, but it is certainly the case that IO operations can spin nearly forever on Linux too, as the timeouts seem very pessimistic. I have had cases where IO blocking on one drive makes a Linux system almost unusable as the kernel queue seems to fill up with pending operations that never complete. We had embedded Linux systems with eMMC device that was only used for storage of video, NAND chip for main filesystem, but the box would lock up if you tried to access bad eMMC, and reboot was the only option. You could not even SSH into a unit in that condition.

author: shapirus
author_rank: Super Contributor
timestamp: June 19, 2025, 11:19:43 am
content: There are no SMART fields having bad values other than the CRC error count, so there is no reason at this point to suspect anything but a bad SATA cable or bad contacts in the connectors (provided that all the necessary drivers are installed, but I doubt that even that would affect it).Step one: replace the SATA cable, use a different SATA port on the motherboard. See if the issue persists and if the CRC error count (raw value) is increasing. If yes, proceed to step two which is to be determined.

author: madires
author_rank: Super Contributor
timestamp: June 19, 2025, 11:27:49 am
content: Counterfeit SSD?Warning! FAKE Samsung 870EVO, 980PRO and 990PRO SSD around. -https://www.techpowerup.com/forums/threads/warning-fake-samsung-870evo-980pro-and-990pro-ssd-around.316801/Heads up: Fake Samsung SSDs are making the rounds -https://www.pcworld.com/article/1666132/heads-up-fake-samsung-ssds-are-making-the-rounds.html

author: SteveThackery
author_rank: Super Contributor
timestamp: June 19, 2025, 01:26:39 pm
content: Quote from: Jeroen3 on June 19, 2025, 10:32:31 amNot in my experience. I've had system-wide freezes in Linux. Basically, hardware faults can bring down pretty much any system, except possibly the hyper-resilient software we put in spacecraft.

author: iMo
author_rank: Super Contributor
timestamp: June 19, 2025, 01:49:44 pm
content: Some ssd testing guys are using these utilities to see very details on their ssd/sata/nvme internals:http://vlo.name:3000/ssdtool/PS: I've never used that, thus handle with care..

author: asmi
author_rank: Super Contributor
timestamp: June 19, 2025, 02:48:17 pm
content: "There are two kinds of engineers - those who make backups, and those who WILL be making them." (C)Any media can fail. Which is why everyone should always follow 3-2-1 rule for any data that they don't want - or can't afford - to lose.

author: u666sa
author_rank: Frequent Contributor
timestamp: June 19, 2025, 08:45:02 pm
content: Sounds like anti-virus problem to me. Windows defender thing.

author: MathWizard
author_rank: Super Contributor
timestamp: June 20, 2025, 12:05:07 am
content: I put the SSD in my backup PC, and it showed up right away in explorer, but then once I started 1 of the harddrive programs, it disappeared, which is strange to me. But then I restarted explorer, it was there, and I quick formatted, which only took seconds. I moved a few files onto w/o any problem. I ran a benchmark w/ Samsung Magician, and it looks fine. So IDK, I'll put it back in my main rig and try it again.My other drives had no problem copying that 15GB of installers and zip files, and it took no time. Copying the 1.2GB KiCad file, on my good drives, the copy window just blinks on screen or not at all, it's done so quick.AHCI or is it ACHI, is what it's using or doing...I'll try some of the longer tests too.

author: David Hess
author_rank: Super Contributor
timestamp: June 20, 2025, 12:43:41 am
content: Quote from: MathWizard on June 19, 2025, 01:18:28 amYou should be using AHCI, but it will not fix your problem.Windows having problems copying files usually means a mostly recoverable hardware problem, like CRC errors on the SATA interface. Windows gets really perturbed if the page file is stored on such a device.On the other hand, the one SSD I have had trouble with was a Samsung 870, but I could copy files just fine to it. They just became corrupted.

author: IanB
author_rank: Super Contributor
timestamp: June 20, 2025, 01:18:47 am
content: Quote from: David Hess on June 20, 2025, 12:43:41 amThat's curious. A long time ago I tried replacing a spinning disk with a Samsung SSD in a notebook computer. It seemed to work OK initially, but when I used Samsung Magician to do a speed test it just stopped working and became unreadable. I took it out and decided never to use it again. How could you trust a disk that might self-destruct at any time?

author: Monkeh
author_rank: Super Contributor
timestamp: June 20, 2025, 01:29:07 am
content: Quote from: IanB on June 20, 2025, 01:18:47 amThat's any type of drive from any manufacturer in any machine.

author: Ranayna
author_rank: Super Contributor
timestamp: June 20, 2025, 07:23:16 am
content: Quote from: Monkeh on June 20, 2025, 01:29:07 amThat is important to keep in mind.Any storage device can fail at any time for any (or apparently no) reason, without any notice.For as long as computers exist now, i would have thought that this should be basic knowledge.Back up your data, people.

author: Haenk
author_rank: Super Contributor
timestamp: June 20, 2025, 07:42:48 am
content: Quote from: shapirus on June 19, 2025, 11:19:43 amUnfortunately, not true.For some of the values you need to look at the raw data. E.g. Bad block count should be 0, but it is not. And if it is already showing up as bad block (and not handled internally) - it *is* bad. As in "replace immediatly, it could completely fail at any time soon".

author: Haenk
author_rank: Super Contributor
timestamp: June 20, 2025, 07:51:07 am
content: Quote from: MathWizard on June 20, 2025, 12:05:07 amJust don't.I *really* advise you to run "Hard Disk Sentinel" with a write/read (destructive) test before installing it back into your work system. A freezing up system due to IO-lock is a pain, I had to do countless hard resets in my lifetime, and these always come with a risk of damaging your filesystem. (Trust me, I sold hundreds of thousands of storage media, with sometimes necessary customer support...)

author: shapirus
author_rank: Super Contributor
timestamp: June 20, 2025, 07:57:18 am
content: Quote from: Haenk on June 20, 2025, 07:42:48 amBut it is. I'm referring topost #7.Reallocated sector count = Uncorrectable error count = 0, these are what we are primarily looking for. All others except CRC error count are looking good, too. Hence the bad cable suspicion.The one shown in post #8 is irrelevant, I assume that's just an example from the internet. In that case, yes of course, a drive with SMART status like that would need to be replaced immediately.

author: Ranayna
author_rank: Super Contributor
timestamp: June 20, 2025, 08:00:07 am
content: Quote from: Haenk on June 20, 2025, 07:42:48 amBad block reporting works differently on SSDs compared to Harddisks.For an SSD, it is expected and normal for blocks to go bad. Thats what the internal overprovisioning is for. Note that in Simmed's screenshot in Post #8, the SMART Attributes 05 (Reallocated Sector Count), B3 (Used Reserve Blocks) and B7 (Runtime Bad Block) are all the same.I agree, if it where an harddrive, it needed to be replaced ASAP. And Crystal Disk Info would show it as such, with a warning even when there is just one reallocated sector. But for an SSD, that CDI screenshot is nothing out of the ordinary.In Mathwizard's post #7, there is barely any wear on the drive, but at lot of CRC errors, pointing to bad cables or maybe ports.

author: Haenk
author_rank: Super Contributor
timestamp: June 20, 2025, 08:04:17 am
content: Quote from: shapirus on June 20, 2025, 07:57:18 amLook at raw value "B8" - that is *not* zero, and should be zero.

author: Ranayna
author_rank: Super Contributor
timestamp: June 20, 2025, 08:07:39 am
content: Quote from: Haenk on June 20, 2025, 08:04:17 amUh... What "B8"?

author: shapirus
author_rank: Super Contributor
timestamp: June 20, 2025, 08:09:46 am
content: Quote from: Haenk on June 20, 2025, 08:04:17 amThere is no raw value "B8" on that screenshot.The only "B8" found there is a SMART field ID. That's, well, a field id, not its value. The values are displayed in the rightmost column.

author: Haenk
author_rank: Super Contributor
timestamp: June 20, 2025, 08:15:22 am
content: Quote from: Ranayna on June 20, 2025, 08:00:07 amThe "wear level" is not an indication of present bad blocks or reallocated blocks. I assume the calculation of this value is a trade secret, but likely represents the total blocks written and maybe some other stats.And if the SSD starts to report bad blocks, this *is* bad, as failing blocks are normally handled internally. The manufacturers became pretty good at this...Again, my 100000h+ running time Samsung SSD reports *zero* reallocated sectors or bad blocks; wear leveling is hex 1ED (493), which calculates to 86%.I'm also not completely sold on the "bad cable" theory. Worth checking though, and a replacement cable is cheap anyway.

author: Haenk
author_rank: Super Contributor
timestamp: June 20, 2025, 08:18:21 am
content: Quote from: shapirus on June 20, 2025, 08:09:46 amSo what's the raw value shown for this field ID?(Do you think I'm stupid or what? The program names it "B8", and you had no problem finding that in the shreenshot, did you?)Edit: Well. I'm out. I can only offer my advice, after 30 years of experience selling all types of hundreds of thousands of storage devices. Maybe I know a thing or two, but there are plently of people here who are *real* experts, better listen to them.

author: shapirus
author_rank: Super Contributor
timestamp: June 20, 2025, 08:21:03 am
content: Quote from: Ranayna on June 20, 2025, 08:00:07 amThat is why the best course of action is methodical troubleshooting rather than trying various unrelated things at once, not having any clue about expected results and hoping that something magically helps.Which is, in the order of decreasing probability of the cause:1) try a different SATA cable -- confirm or rule out the bad cable;- else -2) try a different SATA port -- same for the port;- else -3) try a different computer or an external SATA to USB adapter -- confirm or rule out the bad SATA controller or controller drivers;- else -4) only at this point it can be reasonable to start thinking that there's something wrong with the drive itself.

author: shapirus
author_rank: Super Contributor
timestamp: June 20, 2025, 08:24:46 am
content: Quote from: Haenk on June 20, 2025, 08:18:21 amAre you kidding or what? It's zero of course.p.s. it's actually field number BB, not B8: easy to overlook on such a tiny ass image.

author: David Hess
author_rank: Super Contributor
timestamp: June 20, 2025, 11:38:57 am
content: Quote from: Monkeh on June 20, 2025, 01:29:07 amIt is, but Samsung 970 EVO drives, and maybe some other Samsung drives, have been having production runs with data corruption going back years now.Quote from: shapirus on June 19, 2025, 11:19:43 amIn my case there was a SMART field which returned the number of UltraDMA errors, which had to do with the SATA interface, and this was the clue which led to resolution of the problem.Quote from: Haenk on June 20, 2025, 08:15:22 amWhen I had this problem, it was not the hardware. There was some kind of incompatibility between a new modern SSD and a 10+ year old Marvell 9123/9120 SATA3 controller built into the motherboard. The result was large numbers of CRC errors at the interface. Moving the SSD to the slower south bridge SATA port fixed it.

author: shapirus
author_rank: Super Contributor
timestamp: June 20, 2025, 12:01:20 pm
content: Quote from: David Hess on June 20, 2025, 11:38:57 amYes. Those errors were indicative of something wrong with the interface as a whole, which includes the cable, connectors, host and device interfaces and the host interface OS drivers. Naturally, it's reasonable in this case to troubleshoot it by eliminating possible causes one by one starting with the most probable or the easiest to check: cable -> port -> interface.

author: David Hess
author_rank: Super Contributor
timestamp: June 20, 2025, 12:43:32 pm
content: Quote from: shapirus on June 20, 2025, 12:01:20 pmWhich is what I did. First I replaced the cable, then I changed the port, then I changed to the other SATA controller.

author: shapirus
author_rank: Super Contributor
timestamp: June 20, 2025, 12:52:14 pm
content: Quote from: David Hess on June 20, 2025, 12:43:32 pmRational thinking in action. Always good to see it these days. Sadly it seems like it's slowly becoming another forgotten feat (or maybe it's just signs of me becoming older).

author: Monkeh
author_rank: Super Contributor
timestamp: June 20, 2025, 01:12:45 pm
content: Quote from: Haenk on June 20, 2025, 08:18:21 amCalm down and take a step back. You're looking at the wrong image, for a start.

author: themadhippy
author_rank: Super Contributor
timestamp: June 20, 2025, 01:52:28 pm
content: maybe totally of bat here,but every motherboard manual ive seen gives dire warnings about sharp bents or twists in the sata cables, might be worth looking at there routing

author: thm_w
author_rank: Super Contributor
timestamp: June 20, 2025, 10:51:31 pm
content: https://www.techpowerup.com/forums/threads/samsung-870-evo-beware-certain-batches-prone-to-failure.291504/page-26Quote from that thread:QuoteI would not use the drive.

author: shapirus
author_rank: Super Contributor
timestamp: June 21, 2025, 07:00:00 am
content: Quote from: thm_w on June 20, 2025, 10:51:31 pmLast line of what you had quoted is not true. At least one of the fields (CRC errors) doesn't necessarily mean a bad drive, as far as I know.(and it's not 870 Evo specific btw, you wouldn't want to see any of those being non-zero on any drive.)

author: MathWizard
author_rank: Super Contributor
timestamp: June 21, 2025, 07:29:27 am
content: Quote from: thm_w on June 20, 2025, 10:51:31 pmI never heard of any pf these Samsung issues before, this is my 1st drive from them, I know everyone speaks highly of their RAM chips.I'll use a different SATA cable, and if it still can't copy stuff, I'll try another port, before giving up on the drive. But yeah it's whole point is to be a backup drive, and now I don't trust it much.

author: alex843
author_rank: Contributor
timestamp: June 22, 2025, 11:21:35 am
content: There is something going on here with that field BB (decimal 187). My drive is a little bit older and I don't see those sort of numbers.Code:$ smartctl -a /dev/disk0 | grep -e Power_On -e Reported_Uncorr9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 24659187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0

author: shapirus
author_rank: Super Contributor
timestamp: June 22, 2025, 11:33:41 am
content: Quote from: alex843 on June 22, 2025, 11:21:35 amThe drive in question (which is shown in post #7, NOT post #8) has the same value in that field as yours.

author: alex843
author_rank: Contributor
timestamp: June 22, 2025, 12:23:40 pm
content: Quote from: shapirus on June 22, 2025, 11:33:41 amYou're right, I was looking at the wrong post, sorry for the confusion. In that case, perhaps the CRC Error count (attribute 199, or C7 Hex) is more of an issue here. I also have some, but less than one CRC Error per power on hour.Code:ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE1 Raw_Read_Error_Rate 0x002f 100 100 000 Pre-fail Always - 445 Reallocate_NAND_Blk_Cnt 0x0033 100 100 000 Pre-fail Always - 19 Power_On_Hours 0x0032 100 100 000 Old_age Always - 2466012 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 19629171 Program_Fail_Count 0x0032 100 100 000 Old_age Always - 0172 Erase_Fail_Count 0x0032 100 100 000 Old_age Always - 0173 Ave_Block-Erase_Count 0x0032 042 042 000 Old_age Always - 1758174 Unexpect_Power_Loss_Ct 0x0032 100 100 000 Old_age Always - 32180 Unused_Reserve_NAND_Blk 0x0033 000 000 000 Pre-fail Always - 4065183 SATA_Interfac_Downshift 0x0032 100 100 000 Old_age Always - 0184 Error_Correction_Count 0x0032 100 100 000 Old_age Always - 0187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0194 Temperature_Celsius 0x0022 067 053 000 Old_age Always - 33 (Min/Max 20/47)196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 1197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 0198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0199 UDMA_CRC_Error_Count 0x0032 100 100 000 Old_age Always - 16067202 Percent_Lifetime_Remain 0x0031 042 042 000 Pre-fail Offline - 58206 Write_Error_Rate 0x000e 100 100 000 Old_age Always - 0210 Success_RAIN_Recov_Cnt 0x0032 100 100 000 Old_age Always - 0246 Total_LBAs_Written 0x0032 100 100 --- Old_age Always - 226586727891247 Host_Program_Page_Count 0x0032 100 100 --- Old_age Always - 2777681442248 FTL_Program_Page_Count 0x0032 100 100 --- Old_age Always - 3087980818

author: Monkeh
author_rank: Super Contributor
timestamp: June 22, 2025, 12:33:12 pm
content: Quote from: alex843 on June 22, 2025, 12:23:40 pmThat's still a lot. One of my machines currently has a combined total of 477,030 runtime hours and.. one CRC error.

author: shapirus
author_rank: Super Contributor
timestamp: June 22, 2025, 01:06:38 pm
content: Quote from: Monkeh on June 22, 2025, 12:33:12 pmYeah, I've got this in my desktop computer right now:Code:Device Model: Samsung SSD 850 EVO 500GB5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 09 Power_On_Hours 0x0032 086 086 000 Old_age Always - 7044012 Power_Cycle_Count 0x0032 099 099 000 Old_age Always - 486177 Wear_Leveling_Count 0x0013 092 092 000 Pre-fail Always - 170187 Uncorrectable_Error_Cnt 0x0032 100 100 000 Old_age Always - 0195 ECC_Error_Rate 0x001a 200 200 000 Old_age Always - 0199 CRC_Error_Count 0x003e 100 100 000 Old_age Always - 0So far so good *knocks on wood*. Of course I have backups, but considering the time it would require to restore those backups I'm thinking of getting two new drives and making a RAID1 on them to save on recovery time, of course in addition to backups, not to make them unnecessary.Anyway, it'll be very interesting and useful to hear if replacing the SATA cable and trying a different port will solve the OP's problem and if the CRC error count will stop increasing.

author: alex843
author_rank: Contributor
timestamp: June 22, 2025, 11:49:40 pm
content: Quote from: Monkeh on June 22, 2025, 12:33:12 pmPerhaps I should mention that the SMART data posted is from an old Macbook Pro from early 2012 (actually a late 2011 model) and not my main computer.Some people on forums have suggested that the SATA cable on these machines is not good for SATA-3, but Apple didn't care because the original hard drive was SATA-2, and the optional SSD from Apple was also SATA-2. So these were never supported with SATA-3 drives.I've been running virtual machines (in 16GB of RAM) and never had major performance problems, except when I have a stupid number of tabs open in my browser.However I do agree with the comments that the OP should check their SATA cable. These are not expensive to replace and at worse you might end up with a spare cable.

author: Simmed
author_rank: Frequent Contributor
timestamp: June 23, 2025, 01:50:33 am
content: the AFR chart from backblazethey dont use samsung SSD for some reasonhttps://www.backblaze.com/blog/category/cloud-storage/hard-drive-stats/

author: wraper
author_rank: Unknown
timestamp: June 23, 2025, 03:01:17 pm
content: Quote from: Simmed on June 23, 2025, 01:50:33 amIt's because they mostly use the cheapest drives available, Samsung SSDs are relatively expensive.

author: Jeroen3
author_rank: Super Contributor
timestamp: June 25, 2025, 05:54:41 am
content: Quote from: iMo on June 19, 2025, 01:49:44 pmCareful with running programs packaged in rar files from a randomRussianhome server.

author: shapirus
author_rank: Super Contributor
timestamp: June 25, 2025, 06:26:06 am
content: Quote from: Jeroen3 on June 25, 2025, 05:54:41 amIt's funny how rar, once great novel archiver, has since become no more than a good indicator of fishy contents inside the archive.

author: Ranayna
author_rank: Super Contributor
timestamp: June 25, 2025, 06:58:45 am
content: It's not neccessarily that, but at the moment you should be careful, at least if you use an older Version of WinRAR. A security flaw was found a couple of days ago, enabling arbitrary code execution if you try to extract an infected file:https://www.win-rar.com/singlenewsview.html?&L=0&tx_ttnews%5Btt_news%5D=276&cHash=b5165454d983fc9717bc8748901a64f9