- Joined
- Jul 25, 2006
- Messages
- 12,137 (1.87/day)
- Location
- Nebraska, USA
| System Name | Brightworks Systems BWS-6 E-IV |
|---|---|
| Processor | Intel Core i5-6600 @ 3.9GHz |
| Motherboard | Gigabyte GA-Z170-HD3 Rev 1.0 |
| Cooling | Quality case, 2 x Fractal Design 140mm fans, stock CPU HSF |
| Memory | 32GB (4 x 8GB) DDR4 3000 Corsair Vengeance |
| Video Card(s) | EVGA GEForce GTX 1050Ti 4Gb GDDR5 |
| Storage | Samsung 850 Pro 256GB SSD, Samsung 860 Evo 500GB SSD |
| Display(s) | Samsung S24E650BW LED x 2 |
| Case | Fractal Design Define R4 |
| Power Supply | EVGA Supernova 550W G2 Gold |
| Mouse | Logitech M190 |
| Keyboard | Microsoft Wireless Comfort 5050 |
| Software | W10 Pro 64-bit |
It hasn't changed. If it finished extremely quickly, something was amiss. Either the wrong switch was used, the scan aborted for some reason, it was a tiny partition, a small drive, or maybe a SSD instead of HD.
Either way, the error checking program has not changed in many years. Other than to add support for NTFS (in the mid 1980s), and add a few extra switches, it has remained basically the same for the last 40+ years! And this is because hard drive technologies have not changed. You have a R/W head that manipulates magnetic particles on platters (writes), then goes back and senses the orientation of those particles (reads). The rest is in the controller.
BTW, while running chkdsk on a SSD, in theory, is fine, it is often not recommended. But, sadly, for the wrong reasons.
Some incorrectly claim it is harmful to SSDs. Simply not true - especially with current generation SSDs which do not suffer write limits of first generation SSDs. But to that, the vast majority of the chkdsk operation is reads, not writes anyway. And reads have no effect on SSD longevity.
Yes, a few people reported problems booting after running chkdsk on a SSD. But we can easily see similar reports for HDs. The truth is, those are one-off exceptions likely caused by some outside force - like a power fluctuation during a critical stage in the checking, for example.
The main reason not run chkdsk on SSDs is because it simply is not needed. This is because SSDs use advanced wear-leveling and controlling techniques that already include error checking functions.
Either way, the error checking program has not changed in many years. Other than to add support for NTFS (in the mid 1980s), and add a few extra switches, it has remained basically the same for the last 40+ years! And this is because hard drive technologies have not changed. You have a R/W head that manipulates magnetic particles on platters (writes), then goes back and senses the orientation of those particles (reads). The rest is in the controller.
BTW, while running chkdsk on a SSD, in theory, is fine, it is often not recommended. But, sadly, for the wrong reasons.
Some incorrectly claim it is harmful to SSDs. Simply not true - especially with current generation SSDs which do not suffer write limits of first generation SSDs. But to that, the vast majority of the chkdsk operation is reads, not writes anyway. And reads have no effect on SSD longevity. Yes, a few people reported problems booting after running chkdsk on a SSD. But we can easily see similar reports for HDs. The truth is, those are one-off exceptions likely caused by some outside force - like a power fluctuation during a critical stage in the checking, for example.
The main reason not run chkdsk on SSDs is because it simply is not needed. This is because SSDs use advanced wear-leveling and controlling techniques that already include error checking functions.