Bug in Windows 7 RTM

[Avien]

Nothing a patch wont fix. Hell people shouldn't even be worrying about this since the OS doesnt come out till Oct 22, unless you are technet/msdn which i doubt you will rarely be caring about chkdsk once you get Win 7.


Just read an update.

After emailing back and forth with the VP Sinofsky, it was found that the chkdsk /r tool is not at fault here. It was simply a chipset controller issue. Please update you chipset drivers to the current driver from your motherboard manufacturer. I did mine, and this fixed the issue. Yes it still uses alot of physical memory, because your checking for physical damage, and errors on the Harddrive your testing. I’m currently completed the chkdsk scan with no BSOD’s or computer sluggishness. Feel free to do this and try it for yourselves. Again, there is no Bug.
Thanks all.


This is not an OS bug, but rather a fault in the generic controller driver specifically since MS can’t include all motherboard manufacturers controller drivers on the install disc. Simply update the chipset drivers, including your controller drivers and your chkdsk /r will complete without BSOD’s or system slowdowns. Hopefully, all motherboard manufacturers have the current drivers avaiable on there respective websites.

 

[Antman]

Got this over on another forum...

Just read an update...

Not doubting your input, and I do have an update available for my chipset - but for an issue of this prevalence and web-wide lack of resolve, professionalism demands a source citation.

C'mon give it up - where did you find the reference?

 

[KazeNoKoe23]

Guess this bug doesn't affect me. My 2nd HD is an external that's formatted with FAT32.

 

[blackroseMD1]

Not doubting your input, and I do have an update available for my chipset - but for an issue of this prevalence and web-wide lack of resolve, professionalism demands a source citation.

C'mon give it up - where did you find the reference?

http://www.thehotfix.net/forums/index.php?/topic/25378-critical-show-stopper-bug-in-windows-7-rtm-build-7600-16385-and-patched-7600-16399/page__pid__174483__st__0&#entry174483

 

[Antman]

A more direct link here.

I can only accept this at face value. I can't update my chipset for another hour or so - my beautiful wife is watching the virtual HTPC.

Anyone tested this yet?

 

[rck01]

If the problem is chipset specific, then why is it appearing across multiple, unrelated chipsets? As I mentioned before, I've tested this on two different systems - albeit both Intel based - as well as under VMware. The first two *might* be related, however, the VMware instance most certainly is not. It uses its own, virtualized chipset drivers which, AFAIK, have nothing in common with the one used by the host OS.

Note: I'm not succeeding in generating the blue screen as others have noted. However, I am seeing massive memory consumption - up to 1.7GB on a 2GB VMware session. Given that this same command consumes under 10MB on Vista w/SP2, I'd say it's a pretty big problem, BSOD or not.

Sorry, but I think this is a genuine Microsoft bug and not something they can just pawn off to an OEM as a driver issue.

RCK

 

[mickey megabyte]

it's a problem, but is it a showstopper?

my show is still running along nicely, thank you.

who knows how to spell fud?

 

[SquonkSC]

chkdsk.exe has been a show stopper since the DOS days, rendering so called recovered files totally useless.

I don't understand why this is suddenly an item now. :huh:


I think the Graphics, Audio, Network and Gaming issues I've been seeing lately are of much greater concern.

 

[Mark]

I just ran it on both my drives and they both used the same amount of memory (500MB) and completed normally, using build 7600.16384 x64.

 

[Everlong]

A more direct link here.

I can only accept this at face value. I can't update my chipset for another hour or so - my beautiful wife is watching the virtual HTPC.

Anyone tested this yet?

I have the latest chipset, so maybe that's why mine stopped at 89% and didn't crash.

 

[raj11650]

"showstopper" Definition for a tester
A bug can be considered as "showstopper" when any bug going to break the application or important functionality with respect to business or end user fails is called show stopper.

its not replicable as reported by many users many be specific to some hardware!!!

 

[rck01]

Further testing shows that the problem isn't isolated to chkdsk.exe. If you run the same disk check from the shell (right click on the volume in My Computer and select Tools - Check Now), explorer.exe starts eating RAM like crazy - pushed my test rig up to 98% memory utilization in a matter of seconds. Worse still, it doesn't release the memory when it's done. If you cancel out of the check process, explorer.exe keeps on growing, which is actually even more disturbing than chkdsk.exe, which is terminated when you close its command prompt window. Your only recourse is to logout, reboot or manually kill and restart explorer.exe.

Folks, this is a serious bug. Even if it doesn't cause a BSOD, the fact that this function - which seems to be a file-system-wide, as opposed to program-specific, problem - runs up the memory like this is potentially disastrous in many environments. Think about the R2 server admin who does a proactive check on one more more non-system-boot disks. Having a disk check gobble this much RAM could seriously cripple a high-volume web site or sql server.

Truly scary stuff...

RCK

 

[Antman]

Well, that is odd. Running it from Tools caused dllhost, not Explorer, to consume ~2.26 GB vs ~3.1 GB running in cmd. Still haven't updated chipset.

 

[rck01]

That is weird. The only time I see this running in DLL Host is under Vista. With Windows 7, it always runs as part of Explorer.exe. Maybe it's a permissions thing? Have you cranked-up UAC or something? FWIW, I'm running with the default setting, so...

RCK

 

[Antman]

Mem usage dropped to below 2 vs 3+ yesterday. Dllhost did release. Now I can't find the chipset I downloaded already. Don't see connection to UAC, but I am fairly high at 3 (one down from max setting).

 

[rck01]

Uh-oh! Looks like that crazy Kennedy guy got wind of this one and ran with it:

Link Removed

Man, that guy really steams my clams sometimes...

RCK

 

[Mark]

Uh-oh! Looks like that crazy Kennedy guy got wind of this one and ran with it:

Link removed

Man, that guy really steams my clams sometimes...

RCK

That guy doesn't deserve any acknowledgment or the light of day and we have a unwritten rule about even posting links to his stupid rants, do so again at your own peril, RCK

If I ever seen that guy I would punch him right in the nose.

 

[rck01]

You and me both...the man is a real piece of work.

RCK

 

[Antman]

I guess I missed all the Kennedy stuff?

Anyway - turned off UAC - Disk Checking via Tools is now running as Explorer AND mem usage hit 3.22GB within seconds. File count on the target drive is constant from yesterday.

Cancelled scan and Explorer DID NOT release memory. I was able to close that instance of Explorer with a right click end procees. It closed immediately with no visible affect.

 

[rck01]

Yes, that's exactly what I'm seeing. I didn't disable UAC - just left it in its default configuration, which is how most users will leave it. So the problem is even worse in this case - very troubling.

RCK