Memory "bug" won't delay Windows 7
Wow! I decided to take the morning off and when I came back to the office I found my inbox is stuffed with emails from readers concerned that a Windows 7 bug that was uncovered yesterday might cause Windows 7 to be delayed. Sorry to disappoint, but this is one time when you shouldn't believe everything you read on the internet!
The bug is an interesting one. Basically, you run the Chkdsk command using the /r switch and sit back and watch Explorer.exe consume most of your system memory. According to initial reports, this might also lock up your system completely.
While I can reproduce the high memory usage, I've net yet managed to crash a system. The idea that this is some sort of "catastrophic" or "show-stopping" bug is ridiculous. The idea that people could crash their workstations by running this command is also just as ridiculous. In fact, comments made by Steven Sinofsky, president of Windows division, suggest that the memory consumption is not a bug but "by design". This leaves a few random crashes to fix. Oh wow, Windows crashes ... film at 11 ...
Hardly "catastrophic" or "show-stopping" news.
I've heard rumors that this issue is down to chipset drivers. Personally I'm not too sure of this as it seems to affect too many different systems. I certainly wouldn't start ripping apart the system to fix this minor issue.
Bottom line, this will be fixed before the GA (general availability) date.