Bug in Windows 7 RTM

Also, I thought rck01 was the Kennedy person for whom so many of you possess disdain. As far the referenced Kennedy goes, I have only read two web pieces written by him. Both were lucid and cogent. And something about no pants.

Back OT - I am pursuing this anomoly for a single reason: there is nothing on the interweb regarding it's cause or solution. An unsourced citation regarding something someone said is irrelevant and amateur. To this point, MD's treatment remains the singular attempt at professional analysis that I have seen. The treatment, however, remains speculative, to a degree, and does not address the discrepancy between dllhost, explorer and chkdsk memory consumption. The discrepancies are prima facie evidence that the analysis may not be on target.

I do not know of what value it would be, other than for pride - imagine that SevenForums were able to identify the specific cause and proposed solution before the hotfix is released.

Mr GRiM said:

Disk Check on all 3 drives and no problems on Build 7600.16384 x64...

Can you show the processes page? How much mem was allocated to the task?

Do you have an "updated" chipset driver?

Mr GRiM said:

I'm using Nvidia Nforce Win 7 chipset Drivers...

I am not asking which chipset driver you are using, rather which version. There is an unsubstantiated report that legacy (pre-RTM) mfgr's chipset drivers are at fault for the observed phenomenon. Is your chipset driver dated after the release date of your OS install?

Also, the reported issue does not seem to affect the sysvol. What is the file count on your G and external drives? Low file counts are consistent with (relatively) low mem usage in other reports.

what's happened to ant's and grim's avatars???

Mr GRiM said:

Drivers were pre-RTM Win 7 drivers, version 15.35 signed 8th of May.

Interesting. Now I am curious and will do some Googling - are AMD systems affected? Are nVidia chipsets affected? What is the commonality?

Also, I still do not have enough data to fully grasp what is different about your result. a) I do not have enough non-RAID drives to run multiple instances of chkdsk (et al) to duplicate your 3 drive test. I do not have 2 drives that I can unmount (you can bet that I will revisit my drive configuration though). This is important only because you seem to be running multiple instances of chkdsk in your posted result.

I am not willing to run chkdsk /r on my RAID volumes. Please advise, anyone, if I am reticent without reason.

In order to corelate file count to mem usage per drives, I need to know the mem usage per instance of chkdsk.

Forward: chkdsk will now mean chkdsk.exe, dllhost.exe or explorer.exe unless otherwise noted.