Windows 7: Checkdisk Bug in Windows 7 - Bloggers overreact

Oh boy! It appears that Microsoft’s glowing track record with Windows 7 is about to come to an abrupt and unceremonious end. According to various Web sources [1], the RTM build 7600.16385 includes a potentially fatal bug that, once triggered, could bring down the entire OS in a matter of seconds.
The bug in question -- a massive memory leak involving the chkdsk.exe utility -- appears when you attempt to run the program against a secondary (that is, not the boot partition) hard disk using the "/r" (read and verify all file data) parameter. The problem affects both 32- and 64-bit versions of Windows 7 and is classified as a "showstopper" in that it can cause the OS to crash (Blue Screen of Death) as it runs out of physical memory.

Read the story at: Critical Windows 7 bug risks derailing product launch

Isn't this the same bug being discussed here? Bug in Windows 7 RTM

Ken

I cant see any show stopper, what I do see is another crap article by Kennedy

I don't run the chkdsk.exe = no problem for me and also posting Kennedy links can be dangerous to your health from what I read in another thread little bit ago.

It is the same "bug". But, the author of your Ex_Brit's link does not seem to be held in high regard at SF. I do not know why.

He's a hack.

This is an isolated problem with a few users only...

Personally I've ran chkdsk and nothing happened...

He is also a member here (unfortunately) and he posted in the original thread regarding this Bug...hint hint.

I do agree that it is a crap article, though. His analysis is no better than mine and I am absolutely not qualified to divine the cause or cure.

The author references the NTFS driver stack as if he understands it, but provides no example of a possible connection.

"According to some sources, Microsoft is passing the buck..." is drawn from an unqualified and unsourced posting on another forum.

This is neither science nor journalism. The thread here at SF is decidedly more professional.

That would explain the almost identical part from a users post here
"explorer.exe failed to release the RAM when I canceled the disk check and grew even more despite the fact that the check was now aborted"