Bug in Windows 7 RTM

Mark · 05 Aug 2009

LFB said:

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...

I think it's without CHKDSK <C:> /r

LFB · 05 Aug 2009

Mr GRiM said:

I think it's without CHKDSK <C:> /r

All right just show this:

D:\>CHKDSK D: /r
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Chkdsk may run if this volume is dismounted first.
ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID.
Would you like to force a dismount on this volume? (Y/N)

Is this safe? should I type Yes?

Mark · 05 Aug 2009

LFB said:

All right just show this:

Is this safe? should I type Yes?

As long as you are not using the drive then you can press yes, as it will become inaccessible during the process.

Antman · 05 Aug 2009

LFB said:

Is this safe? should I type Yes?

If you are not calling anything on the drive, it is safe. It is what I have been doing all along.

I tried to do it on a drive that I knew it was not safe, and 7 refused. Just ignored me, no error dialog.

Mark · 05 Aug 2009

And the conclusion, NO BSOD and memory usage remained at the posted screen shot until completion and then went back to normal, not much of a "show stopper" IMO.

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

Zidane24 · 05 Aug 2009

Mr GRiM said:

And the conclusion, NO BSOD and memory usage remained at the posted screen shot until completion and then went back to normal, not much of a "show stopper" IMO.

I think the name of the thread should be changed...if it is actually a showstopper than it is only for a certain group of people

Mark · 05 Aug 2009

Zidane24 said:

I think the name of the thread should be changed...if it is actually a showstopper than it is only for a certain group of people

Done.

Zidane24 · 05 Aug 2009

Mr GRiM said:

Done.

thanks Mark...I think the thread name was giving people a rather un-educated insight on what was really going on here

Antman · 05 Aug 2009

Mr GRiM said:

And the conclusion, NO BSOD and memory usage remained at the posted screen shot until completion and then went back to normal, not much of a "show stopper" IMO.

I do not see the issue as a showstopper. No forum member has reported a BSOD as a result and MD is spot on regarding when chkdsk is run. I wonder what would happen if I ran my mobo with 1GB RAM, or even two. Would chkdsk start paging? And what if the drive I'm testing is my page volume?

Interesting that your test released the memory while other tests, from drive/tools, did not.

Cool that this process resulted in the correction of previously undetected errors on your drive.

Muad Dib · 05 Aug 2009

Maybe the only bug is that "Cancel" does not cancel?

I did another test run from the disk Properties>Tools>Error-Checking option.

The Explorer process started and all memory was promptly used, page faulting began, etc. as in other tests.

I clicked the "Cancel" button (twice maybe?), and the dialog box closed. However, the Explorer process continued on. This time I let it run to completion and monitored it rather than abort it manually. When it completed the memory was freed, system performance returned to normal and a successful CHKDSK event was entered in the Application event log.

If this glitch still exists in the v7600 RTM (I'm still on 7232) then "Cancel" not canceling could be a source for confusion and irritation but hardly a showstopper.

I also tested a small 10GB partition and the Working Set of the Explorer process remained very low.

Nice work folks. Any chance we can bury this dead horse and give MS permission to release the Retail ISO on Technet tomorrow?

P.S. Antman my Doctor won't even let me play with her stethoscope. And believe me I would like to check her heartbeat! :)