- Joined
- Jul 16, 2009
- Messages
- 134
Sick of seeing topics about lag or poor performance? Me too! So here is something to fix it.
This article is taken directly from Valve concerning the operation of Steam, however it applies to everything.
I will edit comments and protips in as the become available.
Any applications running in the background may negatively affect gameplay and video performance. Certain applications can lead on to more serious issues such as limited connectivity and game crashes. It is highly recommended that you close all background applications before launching Steam to ensure the best performance and stability. After you are done playing, feel free to re-enable these applications.
The applications listed below have been known to generate connection errors and/or crashes while using the Steam application:
HIDDEN PROCESSES
Certain applications may load when Windows starts and are not obviously indicated. For example, they do not appear in the Windows task bar but they may be among some of your active processes, using your system's resources. These programs may cause crashes and other difficulties using Steam and playing games.
Please see the How to Disable Background Applications article if you would like instructions to disable non-essential background programs and prevent background applications from silently loading when Windows starts.
SOFTWARE TO LOOK OUT FOR
The following applications have been known to cause issues with Steam and playing games:
Anti-Virus Applications - Any incorrectly configured Anti-Virus program could potentially block Steam and Steam game access. Please make sure that Steam and all Steam games are listed as exceptions in these programs. If the issue persists, please try disabling or uninstalling the program to test the issue.
DETAILS
Issues related to any of the programs listed below may be resolved by exiting and/or disabling the program and then exiting and restarting Steam. For certain applications, a system reboot may be required after you have shut down or disabled them.
Antivirus Software
Incorrectly configured antivirus software may prevent proper operation of Steam and Steam games.
VIGuard anti-virus software has been found to conflict with Steam games - an error message stating "Failed to duplicate pipe handle" will be generated when attempting to load the game. Add the contents of your Steam installation folder to VIGuard's authorized folder exceptions list to correct this issue.
AVG 7.5, Norton/Symantec and Nod 32 software has been known to cause game crashes. AVG 7.5 must be fully removed from your system in order to prevent these crashes.
Spyware Detection Software
Aggressive spyware detection software may block the normal operation of Steam. We have received reports that Spycatcher Express, Webroot Spy Sweeper and CA Pest Patrol (bundled with AOL's Security Center) may prevent Steam client application updates and connecting to game servers.
Peer-to-Peer (P2P) Clients
P2P programs such as Kazaa, LimeWire, BitTorrent, E-mule, and Exeem can consume a large portion of your bandwidth, which may prevent Steam from connecting. Do not run file sharing applications while you are using Steam.
FTP and Web Server Applications
As with P2P programs, these programs are generally very bandwidth-intensive and may generate errors in Steam. Examples include IIS services for Windows, Apache web server and MySQL servers.
IP Filtering Programs
Peer Guardian, CYBERsitter, and Netlimiter have been found to cause Steam connection issues. These programs are not compatible with Steam and must be disabled or permanently removed from the computer in order to avoid conflicts.
IP Masking Programs
Programs designed to mask your IP (GhostSurf 2007, Anonymizer, etc) will impact Steam's ability to send and receive data.
Download "Accelerator" and Download Manager Programs
These programs may interfere with installing and/or downloading updates through Steam. Download accelerator programs should be disabled while using Steam.
Additionally, Internet Download Manager has been found to cause crashes when the Steam Storefront is loaded.
Windows Theme Editors
Tuneup WinStyler Theme Service has been found to cause a crash with the Steam client application and WindowBlinds may cause crashes with Source games.
Virtual Private Network (VPN) Software
VPN software will prevent the Steam client application from accessing the Steam network.
Other Applications
Look'n'Stop has been reported to cause issues with Steam when its "Unknown UDP Packet" filter is enabled.
PowerStrip custom display modes software may cause issues with load time and crashing in games - it is recommended that you select the "Restore to default" setting in PowerStrip before playing (you may resume using PowerStrip normally once you are done).
The nVidia Network Access Manager has been found to cause problems as described in the Nothing appears on the Storefront screen in Steam topic.
IN-GAME OVERLAY APPLICATION INCOMPATIBILITY LIST
X-Fire
The in-game overlay may not function if X-Fire is running and also trying to draw its in-game chat interface on the game you have launched.
Workaround:
Close X-Fire, or set it to not attempt to run its in-game portion on games not launched via X-Fire.
Windows Blinds
Reported as possibly preventing the in-game overlay from functioning in some games.
Workaround:
We are currently investigating a solution to this issue. In the mean time, please do not use Window Blinds with Steam.
Ventrilo
Reported that the in-game hot-key bindings for Ventrilo may stop working with the overlay.
Workaround:
This has been reported to be a Vista issue and making the involved apps Run as Administrator solved the problem.
This article is taken directly from Valve concerning the operation of Steam, however it applies to everything.
I will edit comments and protips in as the become available.
Any applications running in the background may negatively affect gameplay and video performance. Certain applications can lead on to more serious issues such as limited connectivity and game crashes. It is highly recommended that you close all background applications before launching Steam to ensure the best performance and stability. After you are done playing, feel free to re-enable these applications.
The applications listed below have been known to generate connection errors and/or crashes while using the Steam application:
HIDDEN PROCESSES
Certain applications may load when Windows starts and are not obviously indicated. For example, they do not appear in the Windows task bar but they may be among some of your active processes, using your system's resources. These programs may cause crashes and other difficulties using Steam and playing games.
Please see the How to Disable Background Applications article if you would like instructions to disable non-essential background programs and prevent background applications from silently loading when Windows starts.
SOFTWARE TO LOOK OUT FOR
The following applications have been known to cause issues with Steam and playing games:
Anti-Virus Applications - Any incorrectly configured Anti-Virus program could potentially block Steam and Steam game access. Please make sure that Steam and all Steam games are listed as exceptions in these programs. If the issue persists, please try disabling or uninstalling the program to test the issue.
- Avast!
- AVG Anti-virus *
- Kaspersky Anti-virus
- McAfee Anti-virus
- Nod32 Anti-virus *
- Norton/Symantec Anti-virus
- Threatfire
- Trend Micro
- VIGuard Anti-virus
- Anti-Spyware Applications
- Ad Aware
- CA Pest Patrol
- Spycatcher Express
- Webroot Spy Sweeper *
- Firewall/Security Applications
- Comodo
- CYBERsitter
- ESET Smart Security
- Netlimiter
- McAfee Personal Firewall
- Nvidia Network Access Manager/Firewall *
- Nvidia ForceWare Intelligent Application Manager
- Peer Guardian
- Tiny Personal Firewall
- Verizon Internet Security Suite
- Zone Alarm
- Other Applications
- Alcohol 120%
- ATI Hotkey Poller
- BitTorrent/UTorrent (all clients)
- Catalyst AI
- Daemon Tools
- Download Accelerators (all clients)
- GhostSurf 2007
- Google Toolbar, Google Updater
- K-Lite Codec Pack
- LimeWire, BearShare or other Peer 2 Peer applications
- nProtect GameGuard *
- Skype
- Slysoft AnyDVD
- TeamSpeak (can lead to mic issues)
- Total Recorder
- Tuneup WinStyler Theme Service
- UPEK Protector Suite
- Ventrilo (can lead to mic issues)
- VirtuaGirl 2
- WindowBlinds
- Xfire
DETAILS
Issues related to any of the programs listed below may be resolved by exiting and/or disabling the program and then exiting and restarting Steam. For certain applications, a system reboot may be required after you have shut down or disabled them.
Antivirus Software
Incorrectly configured antivirus software may prevent proper operation of Steam and Steam games.
VIGuard anti-virus software has been found to conflict with Steam games - an error message stating "Failed to duplicate pipe handle" will be generated when attempting to load the game. Add the contents of your Steam installation folder to VIGuard's authorized folder exceptions list to correct this issue.
AVG 7.5, Norton/Symantec and Nod 32 software has been known to cause game crashes. AVG 7.5 must be fully removed from your system in order to prevent these crashes.
Spyware Detection Software
Aggressive spyware detection software may block the normal operation of Steam. We have received reports that Spycatcher Express, Webroot Spy Sweeper and CA Pest Patrol (bundled with AOL's Security Center) may prevent Steam client application updates and connecting to game servers.
Peer-to-Peer (P2P) Clients
P2P programs such as Kazaa, LimeWire, BitTorrent, E-mule, and Exeem can consume a large portion of your bandwidth, which may prevent Steam from connecting. Do not run file sharing applications while you are using Steam.
FTP and Web Server Applications
As with P2P programs, these programs are generally very bandwidth-intensive and may generate errors in Steam. Examples include IIS services for Windows, Apache web server and MySQL servers.
IP Filtering Programs
Peer Guardian, CYBERsitter, and Netlimiter have been found to cause Steam connection issues. These programs are not compatible with Steam and must be disabled or permanently removed from the computer in order to avoid conflicts.
IP Masking Programs
Programs designed to mask your IP (GhostSurf 2007, Anonymizer, etc) will impact Steam's ability to send and receive data.
Download "Accelerator" and Download Manager Programs
These programs may interfere with installing and/or downloading updates through Steam. Download accelerator programs should be disabled while using Steam.
Additionally, Internet Download Manager has been found to cause crashes when the Steam Storefront is loaded.
Windows Theme Editors
Tuneup WinStyler Theme Service has been found to cause a crash with the Steam client application and WindowBlinds may cause crashes with Source games.
Virtual Private Network (VPN) Software
VPN software will prevent the Steam client application from accessing the Steam network.
Other Applications
Look'n'Stop has been reported to cause issues with Steam when its "Unknown UDP Packet" filter is enabled.
PowerStrip custom display modes software may cause issues with load time and crashing in games - it is recommended that you select the "Restore to default" setting in PowerStrip before playing (you may resume using PowerStrip normally once you are done).
The nVidia Network Access Manager has been found to cause problems as described in the Nothing appears on the Storefront screen in Steam topic.
IN-GAME OVERLAY APPLICATION INCOMPATIBILITY LIST
X-Fire
The in-game overlay may not function if X-Fire is running and also trying to draw its in-game chat interface on the game you have launched.
Workaround:
Close X-Fire, or set it to not attempt to run its in-game portion on games not launched via X-Fire.
Windows Blinds
Reported as possibly preventing the in-game overlay from functioning in some games.
Workaround:
We are currently investigating a solution to this issue. In the mean time, please do not use Window Blinds with Steam.
Ventrilo
Reported that the in-game hot-key bindings for Ventrilo may stop working with the overlay.
Workaround:
This has been reported to be a Vista issue and making the involved apps Run as Administrator solved the problem.
Last edited:
