If you are referring to me, I WANT to use all my RAM. I just don't a bug to ruin any of my prized hardware or software.
Also Muad Dib, Thanks for the info. I read the whole thread. It appears there is no real solution. I have up-to-date drivers for my chipset. I will have to run it sooner of later but don't want to waste 2 hours and get a BSOD. I am getting write errors on my external drive trying to create a disk image so I have a feeling I need to run it.
You will run it sooner or later, directly or indirectly. It does not hurt to run it periodically as a maintenance check. I usually run it after an image backup(s).
I like to keep all my bits new and shiny. The used ones I save in a bit bucket and put in a yard sale. :)
Again, here we go, it turns out to be DRIVERS for certain Chipsets.
It is not the OS. I have ran chkdsk /f on all 8 of my HDDS, and nothing has happened BAD. it just keep on chugging.
The issue is with /r not /f.
The intermittent BSODs reported may be related to the non-standard lack of a page file on systems where chkdsk /r is executed.
The BSODs reported may also be another example of unsourced citations.
Please provide a source for "it turns out to be DRIVERS for certain Chipsets". My challenge of your previous claim remains unanswered. I can source a rebuttal from MS that the claim is unsubstantiated.
[QUOTE]A killer Windows 7 bug? Sorry, no | Ed Bott's Microsoft Report ...
But when you look more carefully, it's arguably a feature, not a bug, and the likelihood that .... Gee, I use chkdsk /f on occasion AnythingButViista | 08/06/09 .... The only show-stopper here is the average consumer... *NEW* vulpine@. ...
blogs.zdnet.com/Bott/?p=1235 [/QUOTE]Seems that most ppl do not have any problems.. with CHKDSKMicrosoft denies CHKDSK bug is 'critical show stopper' Microsoft denies CHKDSK bug is 'critical show stopper' ... Sinofsky went on to say that this is not a big issue but that Microsoft will ...
www.afterdawn.com/news/archive/18762.cfm
PS:
CHKDSK [volume[[path]filename]]] [/F] [/V] [/R] [/X] [/I] [/C] [/L[:size]] [/B]
volume Specifies the drive letter (followed by a colon),
mount point, or volume name.
filename FAT/FAT32 only: Specifies the files to check for fragmentatio
.
/F Fixes errors on the disk.
/V On FAT/FAT32: Displays the full path and name of every file
on the disk.
On NTFS: Displays cleanup messages if any.
/R Locates bad sectors and recovers readable information
(implies /F).
last but not least:Ryan Price's Blog » Major chkdsk Bug in Windows 7 RTM
Aug 3, 2009 ... Simply update the chipset drivers, including your controller drivers and your chkdsk /r will complete without BSOD's or system slowdowns. ...
www.bluescreenofdeath.org/?p=94
In the ZDNet article, the author quotes Sinofsky from the interview where Sinofsky rebuffed the chipset driver claim. The same applies to the AfterDawn article. The PC World article does not cite source - but you can be certain it is, however far removed, extracted from the Sinofsky interview.
Sinofsky rebuffed the chipset driver claim.
There is no MS report, no MS announcment, no MS statement, no MS publication claiming an issue with chipset drivers.
Also /f is not inclusive of /r. /r is inclusive of /f
/F Fixes errors on the disk.
Means - Reads files only
/R Locates bad sectors and recovers readable information (implies /F).
Means - Reads every sector including those with and without files.
With the possible exception of those machines without a page file, there is no bug.
Yes, all in all it really would be rather hard for MS to make a 100% comment on a OS's that is not officially released to the General Public.
The chats with and or about such a problem are actually NULL and Void.
but still nice to chat/speculate about.
True. I really got on to this story earlier in the week, just before the big buzz. No question, this forum has the most exhaustive examination that I could find. Much credit or Muad Dib for an anlysis that provided the light bulb.
Chipset drivers as a cause has been logically disproven anyway.
just tried this myself, and the problem is present on my 7264 x64 build as well... has this been resolved yet through a patch or something?
here is a screeny:
As you can see, it is taking over 800MB of memory as soon as it starts, which isthe available free memory.. this is terrible...
Quote