Bug in Windows 7 RTM

zigzag3143 · 05 Aug 2009

Tews said:

It seems that Antman has morphed into a monkey named MoJo and Grim is doing his happy dance!

Maybe its just rule 15 and the admins having some fun

btw they got mine too

K

Zidane24 · 05 Aug 2009

Antman said:

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.

Nice new avatar Antman...MooooJoooo-JoJo

Zidane24 · 05 Aug 2009

zigzag3143 said:

Maybe its just rule 15 and the admins having some fun

btw they got mine too

K

Ken snip the post above....2222 posts

Antman · 05 Aug 2009

mickey megabyte said:

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

DJG revealed my secret identity in the x86 versus x64 fight. Cloaking momentarily offline. I need Petrossa's flux capacitor to reset the timeline. My cockroachbots are on recon.

Mark · 05 Aug 2009

I just ran it again and checked the process Tab and explorer went from 123MB to 954MB and it was constant in it's ascent so I guess if there were fore files then it may have gone considerably higher, also you will notice in the first screen I posted of the performance Tab, the memory usage did go back to normal immediately after completion of each test.

Antman · 05 Aug 2009

Mr GRiM said:

...it was constant in it's ascent so I guess if there were fore files then it may have gone considerably higher

...also you will notice in the first screen I posted of the performance Tab, the memory usage did go back to normal immediately after completion of each test.

I misinterpreted your screenshot.

But, I do notice that you are not duplicating the test. Both check boxes should be selected to emulate chkdsk /r.

Apples and oranges. Can you test again?

Mark · 05 Aug 2009

This is taking a bit longer to complete now, 30 minutes in and....

Bug in Windows 7 RTM-2009-08-06_035156.jpg

Bug in Windows 7 RTM-2009-08-06_035214.jpg

Bug in Windows 7 RTM-2009-08-06_035615.jpg

Bug in Windows 7 RTM-2009-08-06_041804.jpg

Antman · 05 Aug 2009

Now you have seen what the buzz is about. Interesting that you get ~1GB, ~2GB and ~3GB results. I have not cross-referenced these to your file counts, I am assuming they corelate. If they do, your results are consistent with the MD's initial analysis.

I am glad that I did not bother with the Google re: AMD/nVidia.

While in the Resource Monitor-Memory tab I right clicked the hung Explorer process (after cancelling the repair) and selected "Analyze Wait States". It reported that one of the threads in the process was waiting for a Network I/O to complete....(?)

Muad Dib, MD, will always be "The Doctor" in my mind as a result of this examination. Once I get an acronym in my head, I can't shake it out.

Muad Dib · 05 Aug 2009

I duplicated my original test to confirm that CHKDSK /R executed from a command window does relenquish its memory usage when aborted by closing the command window or via the Task Manager - Process Window.

LFB · 05 Aug 2009

Access is denied...

Can't run here... what are the commands? CHKDSK <C:> /r

I have two HDs let's see if this crash my system...