Resolved False drive warning while optimizing

Optimizing an SSD hard drive with Auslogics Disk Defrag & Optimizer, the operation goes probably 3-4% then jams. Error message is "Temperature limit exceeded. Current operation paused." Repeat. Repeat. Repeat.

Dell 420 XPS upgraded HD's, Core 2 Quad, power supply, video board, peripherals, etc. OS 10 Home 64 bit Build 19045.4780. No other major flaws.

Error occurred after latest MS update. No other problems. Does not block anything but primary SSD drvie optimization.

Please advice. If remove update, OK. If Auslogic related, recommend work around.

 

You don't need to optimize the SDD. There's nothing to optimize. Use Windows inbuilt Defragmenter or the software with the SDD to trim the SSD.

 

I agree with rsinfo. There is no need to run 3rd party optimizer apps on our drives (HD or SSD). And for the record, the optimizer "Tool" in Windows will NEVER attempt to defragment a SSD. SSDs do not need to be defragmented and should not be defragmented. Because of the way data is stored on SSDs compared to HDs, defragmenting is unnecessary and provides no benefit. The BIOS and OS know the difference between SSDs and HDs, so no worries there either.

If you feel you need to optimize your SSD, do so with your drive Properties > Tools. That said, Windows does this periodically (I think weekly by default) so it really should not be necessary.

 

Thank you, gentlemen.
10-4
I have used computers back to key punch cards and whole floor computers, but no longer update knowledge of OS or programs. Good info to know about current OS and BIOS.
There was a time when HD storage was a major issue and fostered my habit of file and drive maintenance.
Bless you both.

 

I know IBM-80 cards well. And yes, drive maintenance was super important back then. And frankly, it is still today - which is exactly why the Windows OS does it on a scheduled, regular basis for us - so they do not need to depend on us mere, flawed humans to remember to do it manually.

 

I discovered that the SSD cut out temperature was set @ 86 degrees F, when operating temps are from 32 d to 158 d F.
Windows does a lousy job of Defrag & Optimize. This is C, w/OS. Not acceptable.
Reset upper limit to 110d F. Now, I can get decent defrag.

 

Me so frawed

 

Ummm, no it doesn't. It actually does a great job at both.

Remember, SSDs do not get defragged because of the way data is stored on them (see *** below). Defragging a SSD is not only a waste of time, it is ineffective and inefficient and (at least for first generation - "old" SSDs), needlessly uses some of their limited writes capacities.

As for optimizing SSDs, Windows knows (and has for years) how to use SSDs very well and knows how to initiate TRIM and wear leveling features effectively too. Understand, these are NOT complex tasks for any modern OS.

As for defragging hard drives, the defragging utility in Windows is not the most efficient compared to some 3rd party programs but that's because it does not need to be. First, by default, the Windows defragger runs once a week. This ensures the drives never have a chance to become very fragmented in the first place. Second, it is critical to remember (regardless the defragging program used), the minute (within seconds, actually), the drive is used after defragging, fragmentation starts all over again. This happens because every time you (or the OS) open a file, a temporary copy is saved to the drive. And if the original is modified, it is saved to a new location leaving a hole (a chunk of free space) where it used to be. The system will then use that freed space for new files or segments (fragments) of a big new file.

The key to the most efficient SSD optimization and HDD defragmentation is for the user to ensure there is plenty of free disk space on both. What's plenty? 30GB seems to be a good number. Don't go by a certain percentage of the total disk space. With today's monster drives, that will likely result is wasting too much valuable space for no good reason. 30GB is plenty.

Where did you see that? Got a link? What is the model number of the SSD?

86°F is totally unrealistic and MUST be a mistake. 86°F is just 30°C which is a relatively "cool" operating environment inside most PC cases, and very cool inside many laptop cases.

So are you sure it is not 86°C (186.8°F)? The fact it is the C drive or that it is with or with an OS is immaterial.

If it really set to 86°F, then some person changed the default setting (accidently or maliciously), or some how that setting became corrupt. Either way, I assure you, it was not Windows being lousy.

*** You NEVER defrag a SSD. If you look in recent versions of Windows, the program is not even called Disk Defragmenter anymore. It is now "Optimize Drives". When Windows detects a connected SSD, it knows not to defrag it.

The reason you don't defrag a SSD is because of how data is stored on and retrieved from a SSD. A fragmented hard drive is like a drawer in a file cabinet with the pages (file segments) of the documents (files) you need scattered (fragmented) in no particular order from front to back. To retrieve all the pages in the right order, you have to stand in front of the file cabinet and rifle through the drawer sequentially, going back and forth, front to back many times (perhaps 100s!) across the entire drawer (disk platters) to each storage location, picking up the pages in the correct order. This takes a lot of time - especially if page 1 is in the front and page 2 is in the back then page 3 is somewhere near the middle, and so on. And remember, this is a mechanical arm (read: slow) moving back and forth, with friction generating heat and creating wear and tear too.

Defragmenting the drive gathers up (reads) all those scattered pages, and saves (writes) copies of them in the correct order in free disk space. It then verifies the saved file is intact (not corrupt) then it deletes the original scattered pages and moves on to the next file until the entire drive is defragmented.

For a SSD, think of a mail sorting box. You simply stand in front of the box and directly grab each page of the report in the right order. It takes the same amount of time and effort to grab every page, regardless where it is located. It does not matter if the pages (file fragments) are next to each other and in the correct order (not fragmented) or if the pages are scattered all over the place. It takes the exact same amount of time to gather up the whole file in the correct order. And this is not a mechanical arm moving a magnetic Read/Write head back and forth. It is done totally through intelligent electronics (read: very fast).

Also, TRIM is a maintenance tool for SSDs that intentionally (and in the background) moves file segments about for "wear leveling" - a feature to ensure even use of all storage locations across the entire SSD - greatly extending the lifespan of the whole SSD. Actual defragging would simply add pointless wear on a SSD without adding any performance advantages. More importantly, TRIM and wear leveling may actually prevent the defragging program from using some heavily used locations to ensure less used locations are used first (thus, "leveling" the wear). Note wear leveling is the same reason "wipe" programs don't work with SSDs.

I must quickly add the concerns about excess wear decreasing the number of writes a SSD can perform was a problem with first generation SSDs only. Today's generation SSDs still have a limited number, but the numbers are so great, home users need not worry. Only very busy 24/7/365 industrial data centers need to worry about it. That said, even many data centers are moving to SSDs for their most accessed, high priority data.