Chkdsk bug in Windows 7 RTM Build 7600.16385/16399


Recommended Posts

you know the thing that bothers me the most is that i noticed this bug back when windows 7 was RC build 7100 and i did send feedback abt it etc. but they didn't fix it. also there is another bug that hasn't been fixed yet despite all my feedback its when u open task scheduler, and try to start a basic task, the cpu consumption greatly increase it froze my pc for a while then it went normal. i am using x86 version of build 7600 now same problem. they don't even listen to feedback once they product is RC. i guess Microsoft feels pressure to release it as soon as possible for maximum sales. bothers me.

Yup this issue is true it happens in RC too this problem went unnoticed the memory usage just increases and the chkdsk doesn't continue well. I too have 8 GB the memory consumption was just increasing like anything went above 6GB it just goes on increasing.

post-189156-1249365857_thumb.jpg

post-189156-1249365912_thumb.jpg

confirmed! but i dont get a BSOD it just use a lot of ram & then returned. i think a hotfix must be on its way..

The original user who found the bug stated to me that he had his unit BSOD. I haven't let my chkdsk run long enough to risk a BSOD and cannot confirm if BSODs are true.

Yup this issue is true it happens in RC too this problem went unnoticed the memory usage just increases and the chkdsk doesn't continue well. I too have 8 GB the memory consumption was just increasing like anything went above 6GB it just goes on increasing.

Damn dude! Your mem usage on Task Manager is funky! You have a comma out of place. It looked like u were using 60GB! "chkdsk.exe Admin 00 60,06,612K Check Disk Utility" LOL It should be like this then 6,006,612K.

It didn't BSOD for me and I finished it, after which all the ram was returned. It stopped increasing in ram usage at 2.7GB on my 4GB machine and maintained till stage 5 was finished.

It might be a feature that it uses as much ram as possible to do the chkdsk (for speed?), and those people with 8GB of ram have chkdsk use up 6+GB because they have that much ram to use.

IMO, it seems like it stops at a certain threshold and shouldn't be a problem.

The original person who experienced a BSOD might have a faulty disk in the 1st place..who knows

Some of us have verified the 'bug', but none of us have had the BSOD yet right?

I don't think it is a bug. Maybe it is by design to speed up the whole checking process. I ran it on my laptop with RTM x86 7600.16385 and left it alone running for about 10 minutes on an external WD 500GB drive. Sure, the RAM usage increased quickly from around 700 MB to 1,701,732 KB in matter of seconds but it stayed there without increasing or decreasing the usage for a few minutes and my computer (again, a laptop) was very responsive.

post-203976-1249372355_thumb.jpg

Specs: Core Duo 1.66 / 4gb RAM / Intel 945GM Graphics

I left the laptop running CHKDSK and tomorrow will see if it BSOD or not. But I'm starting to think that this is not a bug. For the guy that got the BSOD maybe his computer was overclocked or it is a bit unstable...

Will definitively keep an eye on this to see what others say.

Edited by ajua

Just because I don't think anyone has confirmed whether this behaviour is "by design" or not (i.e. was present in Vista too) I'm running a chkdsk /r on a 500GB volume here on a Windows Vista Enterprise x64 SP2 system and memory usage has not gone above 17,204K for the chkdsk process yet.. so it's definitely a fault in Windows 7!

Show stopper?

Is this Tabloid headline season or something.

chkdsk can run automatically if a system was not cleanly rebooted. If you end up where a user is being forced through a chkdsk process, then the system blue screens too then you're potentially into a data loss. The scenario is easy to forsee so I agree when everyone is saying that this is a critical bug which needs fixing and is definitely bordering on being a showstopper.

Just tried it, uses a lot of ram, computer stays responsive, ram is released when chkdsk finished. I'm not sure this is a bug at all to be honest, and even if it is, definitely not a show stopper.

Maybe the OP got a BSOD because he has a bad RAM module which normally isn't used, do a memtest.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Being on GitHub doesn't make something safe. Like any unofficial scripts to do x or y this caters to people with just enough knowledge to be dangerous. If you want to do what this does, and you actually know what you're doing then write your own script (or maybe just add the reg keys yourself) if you don't have the ability to read and understand what a script is doing, and especially don't run it with elevated privileges. Or in this case just use an MSA, sign up the normal route, and stop trying to push water up hill
    • Dude get a clue, LTSC is Enterprise, not even legal for consumers, and ESU is not mainstream support cycle, just an extended security updates period.
    • Nvidia is your issue more so than linux itself. I did used it for a while with an old 1060 3gb, but using propietary drivers was kind of messy.
    • Qmmp 2.3.3 by Razvan Serea Qmmp (Qt-based MultiMedia Player) is a free, open-source audio player that delivers a classic music listening experience with a modern foundation. Inspired by the legendary Winamp, Qmmp features a familiar, customizable interface that supports both Winamp and XMMS skins, making it instantly recognizable to long-time users. It handles a wide variety of audio formats including MP3, OGG Vorbis, FLAC, WAV, AAC, and many others, ensuring smooth playback across diverse music libraries. In addition to basic playback, Qmmp offers advanced features such as a 10-band equalizer, crossfading, gapless playback, and audio visualization plugins. Users can manage playlists efficiently, create and save multiple lists, and even enable streaming from online sources. Plugin support extends the player’s capabilities, allowing integration of features like lyrics display, ReplayGain, and more. Built with the Qt framework, Qmmp runs smoothly and efficiently, making it ideal even for older systems. 10 great QMMP features you might not know: Global Hotkeys Support – Control playback using customizable system-wide keyboard shortcuts. CUE Sheet Support – Automatically detects and plays tracks from CUE files for full album playback. Last.fm Scrobbling – Integrated support for sending playback data to Last.fm. Audio CD Playback – Play music directly from audio CDs. Command Line Interface – Control Qmmp via command-line options for scripting or automation. System Tray Integration – Minimize to and control playback from the system tray. MPRIS Support – Integration with desktop media player controls via the MPRIS (Media Player Remote Interfacing Specification) interface. Spectrum Analyzer and Oscilloscope – Built-in visualizations for real-time audio feedback. Configurable Notifications – Custom pop-ups for track changes and playback status. Multiple Output Backends – Support for ALSA, PulseAudio, JACK, and more, offering flexible audio routing. Qmmp 2.3.3 changelog: fixed build with PipeWire versions less than 0.3.50; fixed settings dialog layout; fixed default CUE encoding; fixed possible null pointer dereference; fixed tracks order when added using drag and drop (2.3.3 only); fixed uninitialized structure usage; improved sid plugin: added libsidplayfp 3.0 support; added feature to build without residfp engine; fixed memory leak; fixed displaying audio information; updated Japanese translation (2.3.3 only). Download: Qmmp 64-bit | 24.0 MB (Open Source) Download: Qmmp 32-bit | 24.1 MB View: Qmmp Homepage | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Rookie
      moog19 went up a rank
      Rookie
    • Mentor
      grik went up a rank
      Mentor
    • Dedicated
      JKR earned a badge
      Dedicated
    • One Year In
      CHUNWEI earned a badge
      One Year In
    • Conversation Starter
      FBSPL earned a badge
      Conversation Starter
  • Popular Contributors

    1. 1
      +primortal
      496
    2. 2
      PsYcHoKiLLa
      270
    3. 3
      Skyfrog
      75
    4. 4
      Steven P.
      68
    5. 5
      FloatingFatMan
      63
  • Tell a friend

    Love Neowin? Tell a friend!