Bug in Windows 7 RTM

nate42nd said:

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?

Muad Dib said:

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.

[QUOTE=nate42nd;213775]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.

[quote=Muad Dib;213793]

nate42nd said:

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.

[quote=nate42nd;213802]

Muad Dib said:

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.

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.

nate42nd said:

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.