

- #Crucial storage executive not starting full
- #Crucial storage executive not starting software
- #Crucial storage executive not starting Pc
- #Crucial storage executive not starting windows
#Crucial storage executive not starting Pc
(In a few hours I'll check again, when I log my "official" daily values.) Possibly the 11 was a fluke, or perhaps a short term benefit of briefly turning off the pc (resetting the ssd). unforunately it's gone up considerably during the approximately 21 hours since then, to about 30. Regarding the "good" news I reported yesterday about the daily WAF shrinking to 11. in the future you might want to resize the Crystal window when you screencapture, so we will be able to see all of the SMART data.) (The limited portion that we can see, that is.
#Crucial storage executive not starting windows
(It should be straight-forward to create a Windows symlink so that Comodo will uncompress to a hard drive, if I learn which ssd folder is the normal destination for What did you mean, earlier in this thread, when you said it's been "triggering" and CrystalDiskInfo "alerts" about it? Your image of CrystalDiskInfo doesn't show a yellow alert it's all blue. to a hard disk, for example, or perhaps to ram. I assume Comodo needs to uncompress archives in order to scan their contents, but if Comodo were smarter it would give the user a choice of where to uncompress.

#Crucial storage executive not starting full
On my pc, Comodo's weekly full virus scan wrote a lot of temporary files (once a week) to the ssd until I decided to disable scanning of compressed archives. That wouldn't explain the ssd's large WAF, but it's possible that Bitdefender could have been reconfigured not to write the temporary files to the ssd. On the other hand, Bitdefender apparently wrote a lot of temporary files to the user's ssd. It's possible the problem actually went away due to the pc restart that was presumably one of the uninstall steps, in which case Bitdefender may have been completely innocent with regard to the ssd's large WAF. However, the thread didn't indicate the experiment was properly completed in other words the user didn't verify Bitdefender actually was the problem by reinstalling it to see if the problem would recur. Several people in that thread concurred that Bitdefender was the culprit, because the ssd started writing much less to NAND after the user uninstalled Bitdefender. My interpretation of the thread linked in a post above, about the antivirus program, is that one user of Bitdefender reported about 4 years ago that it appeared to be a major contributor to his ssd's high amount of writing. In a few days I'll resume running CrystalDiskInfo or HWiNFO to learn whether they're related to the 50-ish WAF. I'll continue to log the MX500's daily WAF. (The pc had been powered for many weeks, with occasional restarts but no shutdowns, so I theorized that the ssd might need to be reset by a power off/on, similar to how Windows must be restarted every few weeks to prevent Windows from misbehaving or stop it from misbehaving.) Perhaps the WAF improvement was caused by one the following actions yesterday: That's still poor, but much better than its 50-ish average during the previous 3 days (when I began recording the ssd's "daily WAF," calculated using the daily increases of the F7 & F8 S.M.A.R.T. I have some "good" news to report: My Crucial MX500's Write Amplification Factor is down to about 11 during the last 24 hours. The spreadsheet at the left of the image shows the recent rapid acceleration of the decrease of Remaining Life.

My pc has Comodo antivirus suite, and perhaps I'll see what happens if I disable it.Īnother problem I've had is that Momentum Cache wouldn't activate.Ĭrucial/Micron tech support have been unable to figure out either problem.īelow is a screencapture that I made after the Remaining Life reached 93%.

#Crucial storage executive not starting software
In the thread at linked above, some people several years ago blamed BitDefender for a WAF that was approximately 25 (assuming I calculated correctly) in a Crucial M4 256 GB ssd, but in my opinion a huge WAF should always be blamed on the ssd, not on software running on the pc. I've used the F7 and F8 SMART attributes to calculate its Write Amplification Factor (WAF = "1 + ΔF8/ΔF7" where the Δ refers to the increase of the attribute over a period of time) over recent days, and WAF has averaged approximately 50 over the last three days. Previously it dropped from 95% to 94% after writing 390 GB, almost as terrible. For example, it dropped from 94% to 93% after the pc wrote only 138 GB. I too have a Crucial MX500 500GB ssd (SATA) and I'm alarmed by its accelerating decrease of Remaining Life.
