Do not use CHKDSK on Windows 7 (All versions)

mick.fr

Or you can if you want

Run chkdsk as an admin and check the memory...

cpu-dude

mick.fr wrote: »

Or you can if you want

Run chkdsk as an admin and check the memory...

And the reason being:



But just so you know, for this to happen, you have to do this on a non system drive and check with the /R command (for repair).

PS: And the link!

mick.fr

Yep a pretty bad memory leak. I am sure it will be fixed quickly.

Anyway this works on any disk, I did it this afternoon on my C: drive, only have one drive in the laptop, my collleague who has 7 too has the same output.

The /f is an even bigger killer too.

Scarry stuff.

watty

I had heard

chkdsk d: /r /f

is good on Win 7

astrofool

Read Steven Sinofsky's reply on this, it's meant to be working this way, it gives as many resources as possible when chkdsk is being run with /r to speed up the process.

What I'd suspect is happening with the few crashes that happen is the machines are rarely being run at such high memory usage in normal circumstances, and are hitting memory errors once all resources get used up bringing down the machine. nVidia and Via chipsets were notorious for these issues (anyone use nVidia's "IDE" driver?)

mick.fr

astrofool wrote: »

Read Steven Sinofsky's reply on this, it's meant to be working this way, it gives as many resources as possible when chkdsk is being run with /r to speed up the process.

What I'd suspect is happening with the few crashes that happen is the machines are rarely being run at such high memory usage in normal circumstances, and are hitting memory errors once all resources get used up bringing down the machine. nVidia and Via chipsets were notorious for these issues (anyone use nVidia's "IDE" driver?)

Certainly not. This is a memory leak and bad @ss bug.
Nobody in their right mind would develop a hard drive health scanner to behave that way.
Just see for yourself on a Windows 7 machine.

Or check this out here:
http://www.youtube.com/watch?v=ycE0rE3c_Ts

astrofool

mick.fr wrote: »

Certainly not. This is a memory leak and bad @ss bug.
Nobody in their right mind would develop a hard drive health scanner to behave that way.
Just see for yourself on a Windows 7 machine.

Or check this out here:
http://www.youtube.com/watch?v=ycE0rE3c_Ts

If it was a memory leak, it would leak beyond the 95% level that it takes up, and always crash the machine, as it is, the only machines that are crashing are ones with a chipset driver issue, or unstable machines, that don't cope well when resources are constrained.

Did you even read the link that you provided? Particularly the comments?

mick.fr

astrofool wrote: »

If it was a memory leak, it would leak beyond the 95% level that it takes up, and always crash the machine, as it is, the only machines that are crashing are ones with a chipset driver issue, or unstable machines, that don't cope well when resources are constrained.

Did you even read the link that you provided? Particularly the comments?

Ok dude.
Ah ah...

mukki

chkdsk d: /r /f

presume its the same if you right click the d drive and run the scandisk that way


i do that about about once a week on my xp machine (testing hard drives before dumping them)