• Announcements

    • xper

      MSFN Sponsorship and AdBlockers!   07/10/2016

      Dear members, MSFN is made available via subscriptions, donations and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, become a site sponsor and ads will be disabled automatically and by subscribing you get other sponsor benefits.
Torchizard

Chkdsk and RAM

28 posts in this topic

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?

0

Share this post


Link to post
Share on other sites

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
0

Share this post


Link to post
Share on other sites

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

0

Share this post


Link to post
Share on other sites

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

0

Share this post


Link to post
Share on other sites

so there is no fix for this ?

I see article is from 2009 :blink:

0

Share this post


Link to post
Share on other sites

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).

0

Share this post


Link to post
Share on other sites

Let me remember to file this under "64 bit system advantage". :whistle:;)

jaclaz

0

Share this post


Link to post
Share on other sites

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 by Octopuss
0

Share this post


Link to post
Share on other sites

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

0

Share this post


Link to post
Share on other sites

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

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

0

Share this post


Link to post
Share on other sites

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

0

Share this post


Link to post
Share on other sites

Hi guys!

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

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.... :realmad:

bookie32

0

Share this post


Link to post
Share on other sites

... 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

0

Share this post


Link to post
Share on other sites

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 by vinifera
0

Share this post


Link to post
Share on other sites

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). :unsure:

jaclaz

0

Share this post


Link to post
Share on other sites

maybe if someone ports over Protogon/ReFS :P

0

Share this post


Link to post
Share on other sites

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). :unsure:

jaclaz

There are lots of programs for disk checking out there. Not sure where are you getting the intent part, because I am not aware of anything presented as such :P

P.S. I just remembered Norton Utilities back in Win9x days. Loved those.

0

Share this post


Link to post
Share on other sites

There are lots of programs for disk checking out there.

Good :), can you name any program (please do list all the ones you know) that has the same (or similar features) to CHKDSK (which, JFYI does NOT check the disk, but rather checks the filesystem of a volume and attempts to repair it - again the filesystem, NOT the disk).

Particularly I would be interested in one that can analyze and repair NTFS filesystems.

jaclaz

0

Share this post


Link to post
Share on other sites

actually they are bound :)

In case of Vista the mainstream support ended 2 years ago. MS is only obligated to release security patches. When it comes to pure bug fixes, they may release them but don't have to do it.

0

Share this post


Link to post
Share on other sites

no, you still get hotfixes for Vista because Server 2008 is still in Mainstream support.

Example:

Noncritical disk volumes are included incorrectly in the system state backup image when you use the -allCritical option in Windows Vista SP2 or Windows Server 2008 SP2
http://support.microsoft.com/kb/2895635/en-us

0

Share this post


Link to post
Share on other sites

There are lots of programs for disk checking out there.

Good :), can you name any program (please do list all the ones you know) that has the same (or similar features) to CHKDSK (which, JFYI does NOT check the disk, but rather checks the filesystem of a volume and attempts to repair it - again the filesystem, NOT the disk).

Particularly I would be interested in one that can analyze and repair NTFS filesystems.

jaclaz

Some presumably existent implementation of fsck for ntfs (or maybe even perhaps Tuxera Recovery?)... is there really any such app available at all? dubbio.gif

Then again... :(

No open source NTFS checker is known to have been developed, so there is no point in requesting such a check.

Source: <http://www.tuxera.com/community/ntfs-3g-faq/#ntfsck>

0

Share this post


Link to post
Share on other sites

no, you still get hotfixes for Vista because Server 2008 is still in Mainstream support.

Example:

Noncritical disk volumes are included incorrectly in the system state backup image when you use the -allCritical option in Windows Vista SP2 or Windows Server 2008 SP2

http://support.microsoft.com/kb/2895635/en-us

Extended Support doesn't mean that they absolutely cannot release such bug fixes :P They don't have to do it though.

If you look at the situation of Windows 2000, the last hotfix for it had been released in May 2010 which was just before the system went EOL. However, the vast majority of the other hotfixes were produced between 2000-2005 during the mainstream support phase, and only a small number between 2006-2010 during the extended support period.

0

Share this post


Link to post
Share on other sites

DBbwSzYK.gif

 

 

A solution to cap x64 Se7en's chkdsk /r runaway memory usage:

 

I "FIX" the issue using procgov.exe to limit the memory the process can use

 

https://diagnettoolkit.codeplex.com/releases/view/115170

 

my cmd line: procgov.exe -m 512M chkdsk.exe /r /x X:

 

 

 

(https://social.technet.microsoft.com/Forums/windows/en-US/a3cd974b-4758-44bb-b1c0-289ef813b2e6/windows-7-chkdsk-memory-leak)

 

https://lowleveldesign.wordpress.com/2013/11/21/set-process-memory-limit-with-process-governor/

1

Share this post


Link to post
Share on other sites

in Win8,the issue is fixed. It uses less RAM by default, but here you have a new commandline option to use the win7 way and use all RAM:

 

/perf - Can only be used with a NTFS disk. Must be used with /scan switch. Uses more system resources to complete a scan as a fast as possible. This may have a negative performance impact on other tasks running on your system.

 

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.