Started by LoneRanger, December 28, 2017, 08:12:15 AM
Quote from: LoneRanger on December 28, 2017, 08:12:15 AMHi all, First of all thank you very much for what is already a very useful program. I've signed up to ask the question in the title because nobody seems to have a solution for what is going on. To explain:----Normally I can find a solution or workaround for most things by searching the web or trial and error but this has me stumped. The clues as to the culprit are these logs in Event Viewer, which always coincide with the drives spinning up: svchost (3212,G,0) The beta feature EseDiskFlushConsistency is enabled in ESENT due to the beta site mode settings 0x800000. svchost (2884,G,0) The beta feature EseDiskFlushConsistency is enabled in ESENT due to the beta site mode settings 0x800000. taskhostw (5108,G,0) The beta feature EseDiskFlushConsistency is enabled in ESENT due to the beta site mode settings 0x800000.Windows Search is disabled, Indexing disabled (all drives), Write Caching disabled (on mech drives), Superfetch disabled. Mech drives are an exception in Windows Defender as well. Even happens with the mech drives marked offline, which I find barmy.In Power Options I have the hard drives set to turn off after 10 minutes (doesn't matter if 1 minute or 20 or anything) but the event keeps turning them on a few minutes after.Now, the drives aren't unhealthy noisy, but they are a bit noisy. With a quiet fan profile the "hoom.... hoom" is noticeable. I wouldn't mind hearing them when I'm actually writing to or reading from them but not all the time. Aware I could also bungee them to reduce noise, and perhaps will, but I think it would be good/better to find the cause of this as I don't like the idea of the drives unnecessarily being made to work in the first place.----So I was wondering if Process Lassoo could identify what is going on and then help prevent it, and include this as a new feature which would help a lot of people with this issue (if you search for "EseDiskFlushConsistency" and "Win 10 waking up my drives etc").Thank you for reading.
Quote from: LoneRanger on December 31, 2017, 08:58:22 AMHi Ed,1709 version here.The numbers for the Esent events change every startup, and are different on each computer. And I should clarify - they are not error logs, just events in Event Viewer > Windows logs > Application, which coincide with the disks starting up. Also noticed on a few occasions, the disks would start up (without opening File Explorer or anything that should user-manually startup the disks) with no such log created.After using Process Monitor as Jeremy suggested, it seems Defender was accessing the two mech drives all the time. Creating a file, then reading it. I've disabled Defender now. No respect, no stay. I told it to exclude the drives and it didn't respect my choice. Now using Avast. Will update in a few days.