Ed covers some 64-bit Vista questions related to memory use, and VPNs. Keep reading →

Consider the following scenario:

• You have a Windows Server 2008-based print server.
• This print server has many Windows Vista-based printer clients.

In this scenario, the memory usage of the Print Spooler service increases over time. For example, assume that you have several thousand printer clients that connect to the print server. Eventually, the print server becomes unresponsive, and you must restart the server to recover from this problem.

You installed AutoCAD 2009 on a workstation with Windows Vista 64-bit. You want to know how to change the Memory Limit setting in the “Advanced Render Settings” dialog box.

For more information on this issue, including potential causes, workarounds, and resolutions, see: AutoDesk KB Article TS1084828.

When you use Microsoft System Center Operations Manager 2007 to monitor system performance on Windows Server 2008-based computers, a memory leak occurs. Specifically, this memory leak occurs in the performance counters that are used by System Center Operations Manager 2007.

Note: Any applications that use performance counters in Windows Server 2008 may also experience this problem.

Consider the following scenario:

• On a computer that is running Windows Server 2008 or Windows Vista, you have more than 4 gigabytes (GB) of physical memory installed.
• The system is configured to generate a full memory dump file.
• The DedicatedDumpFile and DumpFileSize registry values are created. The value of the DumpFileSize parameter is larger than 4096.

In this scenario, the generated dump file is unexpectedly truncated to 4 GB.

Note: To deploy, troubleshoot, and service large memory platforms, OEM partners and customers may have to create large dump files.

When you run an application that calls the MessageBeep function on a Windows Vista-based computer, several system page table entries (PTEs) are leaked. Under most circumstances, this minor leak is not noticeable. However, if the MessageBeep function is frequently or repeatedly called, this leak may cause the computer to stop responding (hang).

Note: You can view the system PTE usage in Performance Monitor. To do this, add the Free System Page Table Entries counter to Performance Monitor.

A great explaination of why you probably can’t use 4GB of RAM on your PC, even if Vista SP1 says you are. Keep reading →

• 4sysops - Why Windows Vista only sees 3GB memory in a PC with 4GB RAM and how Vista SP1 fools its users
  A great explaination of why you probably can’t use 4GB of RAM on your PC, even if Vista SP1 says you are.
  (tags: RAM Memory SP1 )
• Detection and deployment guidance for the April 8, 2008 security release
  All the different ways of getting those new updates out to your users.
  (tags: Updates Deployment )

Keep reading →

On a Windows Vista-based computer, when you run an application that uses the Refresh method of the IWbemRefresher interface, the application may result in a memory leak.

After the application runs for several days, the computer may become unresponsive. In this case, you have to restart the computer.

Additionally, if you use system performance monitor tool (perfmon.exe) to monitor the Private Bytes counter of the application, you may notice that the private bytes increase quickly.

Consider the following scenario:

• You have a computer that is running Windows XP or Windows Server 2003.
• You run a WebBrowser control application for a long time.

In this scenario, you may notice that system performance drops significantly. Additionally, if you use a performance monitor tool to monitor the system’s performance, you find evidence of a memory leak in the Msctf.dll component.

This issue occurs if the following conditions are true:

• Under Regional and Language Options in Control Panel, you click to clear the Turn off advanced text services check box.
• The value of the LoadIMM registry entry is set to 1 in hexadecimal format.
  Note: This registry entry is located under the following subkey:

  HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\CurrentVersion\IMM

You may also encounter this problem on a computer that is running Windows Vista.