Quieting Windows 7 down....

JimLewandowski said:

I've looked into this and got a "not all disc activity is bad" from the morons over at aumha.net. Research and find out where they're going (which I did AND posted).

Sure, these I/Os are not "bad" or "wrong" but is does beg the question:

why have a disc spin-down time for the C: drive (sure it works on my 2nd IDE drive) when even at idle it won't stop

I feel for those with SSDs as I would think this would really kill the life of the drive

I don't have any of the old sysinternals tools that do I/O trace so I could see what Cyl, Head, Sector is being written and possibly coming from what storage location.

I rather suspect sysinternals etc aren't going to be of much help here... it may not even be something we can turn off, even if we do find it.

So far I've:

systematically disabled and renabled services
disabled and re-enabled windows search (that makes a difference)
disabled and renabled scheduled tasks
tinkered with 3rd party drivers even when the Win7 ones worked fine
messed with CD autorun and Shell hardware detection
disabled and renabled entire subsystems (Windows audio etc.)
even tried uninstalling my disk drives (boy did it complain about that!)

I don't necessarily expect the thing to sit totally dormant when not in sleep mode, but the amount of activity is worrisome... Some have suggested it would calm down after a couple of days... 2 weeks later it's still as busy as it was the first hour.

The Aspire concerns me for the effect on battery life. I used to get about 90 minutes out of the 2200mah battery pack and about 4 hours from the 7200... now it's down to something like 60 minutes and 3 hours.

But it's the ASRock that worries me the most. It's on 24/7 as a music/movie server that is used throughout the house. It's busy all hours of day and night as one of the kids is on shift work... It's also used for most of our downloading since we can send files there to be shared with the whole family.... It's not so easy to turn off. The only grace in that situation is that the drive LED isn't very bright. (The entire room lights up with the LED from the desktop.)

I don't know if this is harmful or not but I can definately hear the HTPC's 500g drive doing long steps once a second... and that's abnormal even when playing movie files.

I dunno... maybe it's much ado about nothing, I like Win 7 in other respects, but this one is just stuck in the old craw....

antharr said:

I Windows 7 64x on a Toshiba laptop with an AMD Turion Dual Core and 4GB of memory and have little to no HDD activity at idle.

I would be very interested to know if the behavior is different when on power than when on batteries... The Aspire One beahves more or less "normally" on batteries but when plugged in it just keeps blinking away.... I'm wondering if this is something we can go after with power settings...

My write activity is no different now than it was when I first installed W7.

Search/index doesn't make sense to be doing anything when it says "indexing complete" on the applet for Indexing Options.

My question: what could it POSSIBLY be doing to do virtually ALL writes. What's the point? I rarely see reads when the disc is chugging with nothing going on in the foreground.

I've also had my second IDE awakened occasionally and I can't figure out what for as I'm not accessing it in any way.

I think I/O trace by sysinternals would give us a clue regarding access patterns.

JimLewandowski said:

My question: what could it POSSIBLY be doing to do virtually ALL writes. What's the point? I rarely see reads when the disc is chugging with nothing going on in the foreground.

Here's 30 seconds from Disk Monitor (SysInternals)....

Code:

5:16:29 AM 0.00032425 0 Write 6324568 8 
5:16:29 AM 0.00032425 0 Write 6235232 8 
5:16:29 AM 0.00032425 0 Write 1278880 8 
5:16:29 AM 0.00032425 0 Write 6324576 16 
5:16:29 AM 0.00032425 0 Write 6235224 8 
5:16:29 AM 0.00032425 0 Write 6235208 8 
5:16:34 AM 0.00032425 0 Write 6527240 8 
5:16:39 AM 0.00032425 0 Write 6324592 8 
5:16:39 AM 0.00032425 0 Write 6235232 8 
5:16:39 AM 0.00032425 0 Write 6235216 8 
5:16:44 AM 0.00032425 0 Write 6498296 8 
5:16:49 AM 0.00032425 0 Write 6324600 16 
5:16:49 AM 0.00032425 0 Write 6235224 8 
5:16:49 AM 0.00032425 0 Write 6235208 8 
5:16:54 AM 0.00032425 0 Write 6570968 8 
5:16:56 AM 0.00032425 0 Write 6503112 8 
5:16:56 AM 0.00000954 0 Write 562136 5 
5:16:58 AM 0.00000000 0 Write 495944 1 
5:17:00 AM 0.00000954 0 Write 6324616 8 
5:17:00 AM 0.00000954 0 Write 6235232 8 
5:17:00 AM 0.00000954 0 Write 6235216 8

I left this running for an hour while I had breakfast... there were literally tens of thousands of these.... always less than 20 bytes written....

I have to join your quandry.... what could it possibly be doing?

CommonTater said:

Code:

5:16:29 AM 0.00032425 0 Write 6324568 8 
5:16:29 AM 0.00032425 0 Write 6235232 8 
5:16:29 AM 0.00032425 0 Write 1278880 8 
5:16:29 AM 0.00032425 0 Write 6324576 16 
5:16:29 AM 0.00032425 0 Write 6235224 8 
5:16:29 AM 0.00032425 0 Write 6235208 8 
5:16:34 AM 0.00032425 0 Write 6527240 8 
5:16:39 AM 0.00032425 0 Write 6324592 8 
5:16:39 AM 0.00032425 0 Write 6235232 8 
5:16:39 AM 0.00032425 0 Write 6235216 8 
5:16:44 AM 0.00032425 0 Write 6498296 8 
5:16:49 AM 0.00032425 0 Write 6324600 16 
5:16:49 AM 0.00032425 0 Write 6235224 8 
5:16:49 AM 0.00032425 0 Write 6235208 8 
5:16:54 AM 0.00032425 0 Write 6570968 8 
5:16:56 AM 0.00032425 0 Write 6503112 8 
5:16:56 AM 0.00000954 0 Write 562136 5 
5:16:58 AM 0.00000000 0 Write 495944 1 
5:17:00 AM 0.00000954 0 Write 6324616 8 
5:17:00 AM 0.00000954 0 Write 6235232 8 
5:17:00 AM 0.00000954 0 Write 6235216 8

what could it possibly be doing?

Based on that data its obviously writing some data to your drive duh!

Disk Monitor aint going to be very useful unless you know the process and file being modified, grab Process Monitor and leave it running for awhile: Process Monitor

Note, Having anything running or using your machine while its running will generate 100's of events and is not advisable.

You mentioned one machine is acting as a media server, what software are you using to share the media? WMP, Nero...?

Steven

dmex said:

Based on that data its obviously writing some data to your drive duh!

Very funny... But it's also keeping my drives spun up and preventing my systems from going into standby.

Disk Monitor aint going to be very useful unless you know the process and file being modified, grab Process Monitor and leave it running for awhile: Process Monitor

Just went out and got it, will give it a look...

Actually Resource Monitor is turning out to be the most informative so far... It's actually showing me filenames and amounts read and written... The activity seems to be mostly tied to a couple of files named "LastAlive.da0" and ".da1"... I'm currently thinking it comes from the Reliability testing.... but that cursed led is still flashing...

Note, Having anything running or using your machine while its running will generate 100's of events and is not advisable.

Oh, believe me I'm quite aware of that...

You mentioned one machine is acting as a media server, what software are you using to share the media? WMP, Nero...?

Windows. Really, it's all done through standard windows file sharing and windows file associations... wanna hear a song or see a movie that's on the server? Just click on it in windows explorer and let your media player do it's thing... I use Media Player Classic, Home Cinema Version on the receiving end... FWIW.

I took WMP and Media center completely off my system (under XP) after it managed to completely chew up the Tags in over 5000 MP3 files I've collected... Seems it knows better than I what constitutes a playlist, imported everything into it's library and then proceeded to reorganize it all into albums... changing the tags as it went and getting about half of it wrong in the process. So it's toast.

Windows 7 was "VLited" so the Speech Recognition, Media Center, WMPlayer and a couple of other minor annoyances never even made it to my hard disks. The actual install is less than 1.4gb and uses about 3.5gb on disk.

I'm from the mainframe (IBM) world so, it mystifies me to see a write with a data-length of 8 (or 20) bytes. I assume this is an 8-20 byte update of SOME 4096-byte disc sector. IOW, in the mainframe world, you write whole BLOCKS of data, not bytes.

It's like it's writing timestamps or something. On my system, all these background writes are PID 4 (System).

JimLewandowski said:

I'm from the mainframe (IBM) world so, it mystifies me to see a write with a data-length of 8 (or 20) bytes. I assume this is an 8-20 byte update of SOME 4096-byte disc sector. IOW, in the mainframe world, you write whole BLOCKS of data, not bytes.

It's like it's writing timestamps or something. On my system, all these background writes are PID 4 (System).

It is writing timestamps to two files... Lastalive.da0 and LastAlive.da1, which explains the constant frive stepping, unless they are right together.

I tried something that seems to have it stopped...

HKEY_LOCAL_MACHINE\software\microsoft\reliabilityanalysis\wmi\WMIEnable = 0

Thing is I've done so much to this poor thing I don't know if that's all of it or not. It would be nice to see if it works for someone else.

DiskMon says no more writes and I don't hear drive stepping ... but curiously the drive light is still flashing????

Has Task Manager -> Process Monitor show disc I/Os still??

WMI Is Windows Management Instrumentation?? or something.???

https://www.sevenforums.com/tutorials...y-monitor.html

Reliability Monitor - Reset

JimLewandowski said:

Has Task Manager -> Process Monitor show disc I/Os still??

WMI Is Windows Management Instrumentation?? or something.???

https://www.sevenforums.com/tutorials...y-monitor.html

Reliability Monitor - Reset

Not like before... it will go quiescent for most of an hour then a little burst then quiet again... there's still some activity but not 20 events every 30 seconds.

WMI is part of reliability and performance testing... unless you're benchmarking servers it can safely be turned off.