Chkdsk bug in Windows 7 RTM Build 7600.16385/16399

[majortom1981]

hmm this is why i wait till the exact version that will ship in stores. You never know what last minute fixes would be thrown in at the last second.

[JOHW]

I'm not sure if this is a bug. But CHKDSK does use a lot of ram. It has stablized to about ?10MB of ram from shown image.

I have 4GB of ram on a HP EliteBook 6930p on 16385

No antivirus running..

UPDATE: The chkdsk has finished. It closed properly and released all the ram immediately.

The verdict is still out whether this is a memory leak, or a by-design..

I've never really used chkdsk in vista..so I'm not sure..

I believe it's probably a bug, but definitely not a real show stopper.

Edited August 4, 2009 by JOHW

[Dilligaf2008]

Yup, happens on mine too (16385). Got to more than 1GB ram usage in less than 10 seconds. :o

Hopefully MS releases a patch for this soon.

[Subject Delta]

First, both of you post exact hardware specs. Lets see if we can find something in common.

Second, I dont believe this bug at all. I think it has to do with certain HW/SW configs. Note that the first guy (with screenshots) gets a BSOD and the second does not.

http://www.infobyte.org/newsimg/

(My opinion)

Also happens on my Laptop (screenshot attatched is laptop, previous was desktop, I don't think this is config related, I think it is just a bug. Spec anyway:

Desktop

• Q6600 @ 2.9 GHZ (Water cooling, Overclocked)
  
• 8GB Corsair XMS2 PC6400 DDRII - 800 MHZ
  
• 512MB HiS ATI 4850HD, Catalyst 9.7
  
• Realtek ALC890 onboard Audio (5.1 surround mode, R2.29)
  
• nVidia nForce 650i SLi Chipset, nForce 16.25
  
• Windows 7 X64 Edition obviously (Ultimate)
  
• Boot drive: 250GB Western Digital WD2500JB IDE Hard Drive
  
• Drive test was performed on: 750GB Samsung Spinpoint HD753LJ (SATAII, running on default SATA drivers, not nVidia drivers)
  
• 570W PSU, never had problems with lack of PSU power before
  

Laptop

• AMD QL-62 Dual Core CPU, 2GHZ, 1MB L2 Cache
  
• 3GB DDRII 667 Memory
  
• 250GB Sata Hard Disk, test was performed on a partition
  
• ATI Chipset (can't remember revision)
  
• ATI 3200 Mobile Graphics (256MB shared memory)
  

Both machines running MSE for AntiVirus

[Jimmy422]

It's using quite a bit of memory. Up to 1GB now.

[AltecXP]

I get it, goes up to 1.7GB

[jwil1]

Confirmed on 7100.

Specs:

Dell Studio 1555

3GB RAM

Intel P8600 processor

ATI Mobility Radeon HD 4570

Scandisk used 1.6GB at it's peak, when I killed it, memory usage immediately dropped back down to 1GB.

[sanctified Veteran]

It's really strange for me to see people deny such bugs or flaws because they use or like certain apps or operative systems. No OS is perfect, why the need to defend something you didn't create?

[firey]

Not sure how this is show stopping? Does everyone do chkdsk every hour of every day? Is there some sort of leet crazy hack I am not aware of?

[Subject Delta]

Not sure how this is show stopping? Does everyone do chkdsk every hour of every day? Is there some sort of leet crazy hack I am not aware of?

Its show stopping because it can eat up your available memory and cause a BSOD very quickly, when something as simple as chkdsk causes such a severe memory leak.

Its just lucky for Microsoft that this has been discovered before general release, they could really do without the negative publicity

[Pharos]

RTM code is RTM code. It's finished. Done. They will patch that through Windows Update. And that's that. Showstopper? Just because it's RTM, doesn't mean it doesn't have undiscovered bugs. Otherwise we wouldn't have service packs and hotfixes.

Edit. Sorry for jumping the gun too quickly. HOLY @#*(&(*#& @**(@&*(#@

Yeah. It's serious. :woot:

Edited August 4, 2009 by Pharos

[firey]

Its show stopping because it can eat up your available memory and cause a BSOD very quickly, when something as simple as chkdsk causes such a severe memory leak.

Its just lucky for Microsoft that this has been discovered before general release, they could really do without the negative publicity

Hmm, fair enough I would have thought "Critical Show Stopper" as being something that any person would do day to day such as Rename a file, or copy a file, or something that would make the system unusable for a standard every day thing.

[mike.r.olson]

Since I'm running a tech shop with my XPS and I need to be running chkdsk's on hard drives before I back them up, I'd consider it a pretty big issue.

[Subject Delta]

Its not a critical show stopper but it is a bug that has no place being in RTM code, its a pretty serious flaw

[Chris123NT]

Confirmed. And yes this should be considered a showstopper. chkdsk killing a machine is not cool as there are real world uses for that tool.

[Panda X]

Repo'd.

[Subject Delta]

Confirmed. And yes this should be considered a showstopper. chkdsk killing a machine is not cool as there are real world uses for that tool.

Precisely. Whilst this is not so likely to be a problem for home users, enterprise users could have some serious problems from this

[Raa]

Since I'm running a tech shop with my XPS

That's probably not a wise idea.

Even so, it's still a pretty big bug. I'm sure it'll be squashed very quickly. ;)

[spy beef]

Holy crap this happens on mine too! How did M$ miss this show stopping bug after such a long beta?

[RushHour2k5]

Confirmed. And yes this should be considered a showstopper. chkdsk killing a machine is not cool as there are real world uses for that tool.

I definantly 2nd that Chris123NT. Also, if "chkdsk" can crash a computer by BSODing it during a fix that "chkdsk" might be performing it can perminantly delete or render data unusable on the drive it is running on. This is 100% a Critical Show Stopper bug that IMO needs to have the RTM recalled and recompiled before the TechNet/MSDN copies go live and at least a Hotfix for the OEMs to impliment in System Recovery.

[Owen W Veteran]

Confirmed. And yes this should be considered a showstopper. chkdsk killing a machine is not cool as there are real world uses for that tool.

Okay, Okay, well, everyone should stop complaining here, and send it to Microsoft - they won't listen unless alot of people submit it...

[Stetson]

Yep, good catch. MS will now have to recall all the disks they sent out and remotely wipe RTM downloads from everyone's machines. They will then have to re-open full Windows 7 development to fix the issue and go through another round of voting before signing off on yet another RTM build, pushing to release back to sometime in 2011.

Or they could just issue a patch :p

[powerade01]

I see ATI and WD as common factors.

Again please post your entire system specs including brands and models.

[Subject Delta]

I definantly 2nd that Chris123NT. Also, if "chkdsk" can crash a computer by BSODing it during a fix that "chkdsk" might be performing it can perminantly delete or render data unusable on the drive it is running on. This is 100% a Critical Show Stopper bug that IMO needs to have the RTM recalled and recompiled before the TechNet/MSDN copies go live and at least a Hotfix for the OEMs to impliment in System Recovery.

They will just release a hotfix, they are won't recall code once it has been RTMed

I see ATI and WD as common factors.

Again please post your entire system specs including brands and models.

Try again before jumping to conclusions. The drive that I performed the scan on was a Samsung Spinpoint, not a WD. The WD is my boot drive, and I don't have any WD drives in my Laptop.

[RushHour2k5]

Yep, good catch. MS will now have to recall all the disks they sent out and remotely wipe RTM downloads from everyone's machines. They will then have to re-open full Windows 7 development to fix the issue and go through another round of voting before signing off on yet another RTM build, pushing to release back to sometime in 2011.

Or they could just issue a patch :p

I know ur joking about this but no need to be a wise a$$. :p