Bug in Windows 7 RTM

[Antman]

Microsoft has also posted that this MASTER BUG is not a OS problem. it is a CHIPSET Problem...

MS did not post that. Nonetheless, it seems that this is a resolved crisis.

Sinofsky:
Some have reported (as above) that this specific issue repros and then goes away with updated drivers. We haven’t yet confirmed that either but continue to try. We just kicked off overnight stress testing of 40 machines of variants as reported by FireRx. We’ll see.

"As above" refers to this:
FireRx:
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.

FireRX put words in Sinofsky's mouth.

 

[dmex]

I remember one of the biggest problems with an XP network I used to manage was with how nearly every user needed administrative access for running specific application's and how they could use the shutdown command to reboot/shutdown any machine on the network including the server simply because the shutdown command would only check for administrative access on the machine it was executed on and not the server, in comparison this issue or "bug" is not anywhere nearly as bad :sarc:

Since the majority of users will be using the standard chipset drivers that come with Windows 7 and that they are the ones where this "bug" is present, I can only hope Windows 7 is rebuilt with its standard drivers capable of mitigating this resource bug, no one wants to see their machine using 3+gb of memory devoted for a simple disk check

 

[Antman]

...no one wants to see their machine using 3+gb of memory devoted for a simple disk check

To this point, MS is saying that the memory consumed is [total RAM less ~50MB].

This astute observation has been posted: The offending /r switch is not likely to be used during normal usage, rather it is more likely to be used for analysis or recovery purposes.

 

[17mayis]

i think its a fake news just to thread people or scare them to not use pirates windows and forcing people buy the orjinal product specially amator people wich is belive to this kind a news straigh away. this is my opinion.

 

[Antman]

i...this is my opinion.

If you study this site, you will find a thorough examination of the phenomenon and knowledgeable reviews of the analysis. This study is not available elsewhere on the interwebs.

And that is not an opinion.

 

[chuckr]

It's OK as long as she doesn't start playing with your stethoscope. And we know it's not really her heartbeat you want to check out ... :sarc:

Tit for Tat !

 

[KiwiTT]

I just ran this on Windows 7100 RC 32-bit with the latest chipset drivers and can say it exists. But a "showstopper" ... not for me.

I don't run this (chkdsk /r or explorer->tools->check disk and select the "recover option") ever.

 

[Antman]

I don't run this (chkdsk /r or explorer->tools->check disk and select the "recover option") ever.

You should run it at some time. It is a simple tool and task that can prevent a mild defect from bringing down an install.

 

[xan K]

I tried to reproduce this and nothing wrong happened. chkdsk finished checking my external drive just fine. no "eating up all memory" happened. it must only affect some systems.

 

[nate42nd]

I found out the hard way with this bug. IT IS REAL believe me. I have never seen anything like it. 8GB of RAM and I got the your computer is out of memory message. Glad to hear they will deal with it.

There was some talk about it on a thread somewhere but I can't seem to find it. Must have been named something else...

Also, This is the case in build 7229 and the RC both in case this helps anyone.

 

[Muad Dib]

I found out the hard way with this bug. IT IS REAL believe me. I have never seen anything like it. 8GB of RAM and I got the your computer is out of memory message. Glad to hear they will deal with it.

There was some talk about it on a thread somewhere but I can't seem to find it. Must have been named something else...

Also, This is the case in build 7229 and the RC both in case this helps anyone.

How big is your pagefile?

 

[nate42nd]

How big is your pagefile?

I don't have a page file. I know I would not have had the message but still....explorer using 7.5GB of RAM is a bug. I opened resource manager and looked at it before I killed it.

 

[Muad Dib]

I don't have a page file. I know I would not have had the message but still....explorer using 7.5GB of RAM is a bug. I opened resource manager and looked at it before I killed it.[/QUOTE]

First you should read the entire thread....

Did you get an out of memory error or did you kill the Explorer process because you thought you were out of memory?

If you did not get an out of memory error you should run the test again and let it complete. Then check your event log.

If you did get an out of memory error and if you want to run CHKDSK /R with the system booted you should create a pagefile and run the test again.

If you do not want to create a pagefile because you have an SSD you should only schedule CHKDSK /R operations to run at boot time.

 

[nate42nd]

I don't have a page file. I know I would not have had the message but still....explorer using 7.5GB of RAM is a bug. I opened resource manager and looked at it before I killed it.[/QUOTE]

First you should read the entire thread....

Did you get an out of memory error or did you kill the Explorer process because you thought you were out of memory?

If you did not get an out of memory error you should run the test again and let it complete. Then check your event log.

If you did get an out of memory error and if you want to run CHKDSK /R with the system booted you should create a pagefile and run the test again.

If you do not want to create a pagefile because you have an SSD you should only schedule CHKDSK /R operations to run at boot time.

Thanks you Muad Dib. No I didn't read the entire thread. I should have. I did get an out of memory error. Thank you very much for the info. I don't mind creating a page file. I am just testing different configurations. I will try to re-create the issue.

Also this happened running the "error checking" on an external hard drive from the tools inside the menu from "my computer" not from command line. I will try both soon and try to post back the results.

 

[Muad Dib]

Also this happened running the "error checking" on an external hard drive from the tools inside the menu from "my computer" not from command line. I will try both soon and try to post back the results.

I don't have an SSD so I cannot be sure of running the test(s) with or without a pagefile. I have my suspicions but you can run the tests and produce facts.

When the disk repair is run from the Error-Checking option of the Tools menu (with both repair option boxes checked) a CHKDSK event will be recorded in the Event Log (Applications). If it is run from a command window (CHKDSK /R) no event is recorded in the Event Log.

Let us know what you discover. I for one am curious.

 

[nate42nd]

I created a 2GB page file and it ran fine without the "scan for and attempt recovery of bad sectors" checked. That's a change. When I checked the bottom box it happened again. I have it stopped and it's still growing....I killed it at about 6.5 GB used.

 

[Muad Dib]

I created a 2GB page file and it ran fine without the "scan for and attempt recovery of bad sectors" checked. That's a change. When I checked the bottom box it happened again. I have it stopped and it's still growing....I killed it at about 6.5 GB used.

The cancel button does not work. Let the process run to completion. Maybe am hour or so. DON'T KILL IT. Read the thread while it is running.

Edit About 40 mins for 150GB Partition.

 

[Antman]

Let us know what you discover. I for one am curious.

The Doctor (MD) is in the house.

I have continued to watch these reports around the web. Now we have a reasonable indication where the BSODs are coming from.

The only "bug" I see at this point may be the 'no pagefile' environment - and it makes me curious about the [total RAM less ~50MB] claim.

My interest remains even if my input is tabled.

 

[Wii Master 64]

what's so bad about RAM getting used? doesn't it normally always go back down? and i don't see myself using this function when i get windows 7 and i only have one hard drive.

 

[DJG]

what's so bad about RAM getting used? doesn't it normally always go back down? and i don't see myself using this function when i get windows 7 and i only have one hard drive.

Some people like to "collect RAM" but hate to use it, in case it gets worn out and loses its resale value ... :sarc: