So I ran CHKDSK with the /f and /r parameters and when I went into task manager to end a unresponsive program, task manager said that CHKDSK was using around 3Gb of RAM... is this normal?

yes, open the 32Bit CMD.exe and run chkdsk here. All users run into this EXCEPT Microsoft:

 

This week a report on a blog described a crashing issue in Windows 7. The steps to reproduce the crash were pretty easy (1) run chkdsk /r on a non-system drive then crash after consuming system memory. Because it was easy to “reproduce”, the reports of this issue spread quickly. Subsequent posts and the comments across the posts indicated that the issue seemed to have been reproduced by others—that is the two characteristics of the report were seen ( a ) consumption of lots of memory and ( b ) crashing.

Like many of you, the first thing I did was try it out. And as you might imagine I did not reproduce both issues

http://blogs.msdn.com/b/e7/archive/2009/08/10/what-we-do-with-a-bug-report.aspx

Jesus, so much arrogance and idiocy... But I am not surprised, it's Microsoft.

it was Sinofsky, Mister arrogance and idiocy. So what have you expected? His arrogance and idiocy lead to the Win8 crap.

so there is no fix for this ?

I see article is from 2009

I doubt this. MS treats Win7 as old an outdated system. You can only use the 32Bit CMD workaround. Here the memory usage is limited to 2GB RAM (32Bit limitation).

Let me remember to file this under "64 bit system advantage".

jaclaz

Would using third party software help in this case, or are they all working off some generic API (like defragmentation does for example), which is bugged?

Edited January 13, 201412 yr by Octopuss

I have no idea. Try the 32Bit CMD Workaround.

I doubt this. MS treats Win7 as old an outdated system.

this is lame, 7 along with vista is BOUND to get major bugfixes

It might be lame, but MS has proven by their actions, or lack of action, that they do not plan to do anything for "older" OS unless they are forced to.

Cheers and Regards

Hi guys!

We seem to be having a dig at Microsoft....lol can I join in....

I would like to see the day when Microsoft actually listen to those that actually buy it....

I get annoyed to think that companies that want to offer alternatives to computers with their crap preinstalled on them...I know there are those that have Ubuntu etc...thinking of the suppliers that have a blank computer so you can decide what you want....

I have seen several go bust because Microsoft just wants us to use their crap...

Don't you just love Microsoft....

bookie32

... 7 along with vista is BOUND to get major bugfixes

Also, just because 7 and Vista are BOUND to get major bugs found, unfortunately this does NOT mean that MS is bound to fix them, again, unless forced.

Cheers and Regards

actually they are bound
but as that article by mvp(?) said, it wasn't reported enough times

and I read few weeks ago article from one of developers from early vista(longhorn), how they do development & bug fixing
and IF certain team didn't report on time the bug, they leave it unfixed even if they are aware of it

they leave it unfixed for next version of winblows

so either they fixed this in w8, and if vista doesn't have this bug then it is limited only to w7 users

which explain above situation

Edited January 14, 201412 yr by vinifera

Would using third party software help in this case, or are they all working off some generic API (like defragmentation does for example), which is bugged?

As a side note, I would be interested in "third party" software that is intended to replace CHKDSK (i.e. that can fix NTFS filesystem errors).

jaclaz