The source of this news item-
A critical show stopper bug has been found in the Final Windows 7 RTM 7600.16385 and in the updated 7600.16399 builds! Thanks to mikerolsonw7c of Windows7Center for informing us of the critical bug. The issue is related to the "chkdsk /r" command on a drive other than the system drive. For example if you have drive C: and drive D: with C: being Windows 7. If you open "cmd" and run "chkdsk /r D:" on "Stage 4" of chkdsk it will have a very critical memory leak and max out the system memory then BSOD due to lack of memory available. This issue is present on non-Patched 7600.16385 and Patched 7600.16399 RTM builds. This is a very critical bug that Microsoft should have caught before sending 7600.16385 to OEMs. Sadly, now Microsoft will have to fix this and then re-distribute RTM code to OEMs or patch it. I would not doubt myself when Microsoft gets word of this Show Stopper bug if the TechNet/MSDN releases on Thursday the 6th get pushed back to re-implement new code into the RTM build.
The bug has been confirmed on many different hardware setups --it's been verified to occur on everything from a Intel Atom-based netbook running the 32-bit version, to a Intel Core 2 Duo notebook running the 64-bit version, and a VMware Workstation 6.5.2 virtual machine running the 32-bit version.
No point delaying. The issue is only on the 64-bit version of Windows 7 and it's not a true memory leak.
The version of chkdsk.exe is the same on both 32-bit and 64-bit installations of Windows 7, but doesn't seem to be compiled for 64-bit use or being run through the 32-bit emulator properly. So, when memory is addressed it goes into a loop and never stops incrementally allocating a memory block. The issue doesn't happen when using the 32-bit version of command prompt ("C:\Windows\SysWow64\CMD.exe").
Easy solution, push out a 64-bit version of chkdsk.exe to 64-bit installations via Windows Update. It's less than 100 kbtyes in size, taking a few seconds to download and install.
Big freaking WHOOP. Stop the dramatics, Mick.
Non of AMD 64 Cpu product react to this bug yet , if you really go for extreme performance gaming and system operating and 64bit application suggest you use it on "amd 64" series for full compatibility