Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a Win 7 32-bit Pro machine joined to a domain on a 10/100 ethernet connection. At times this machine runs all sorts of slow. For example, it took it 20 seconds for a command prompt to pull up, not to mention the other 15 seconds for the start bar to recognize that I clicked on it. There are a few times where it took almost 10 minutes for the machine to even prompt for a password after powering it on. There are various other situations in which the computer exhibits it's "slowness".

Inspecting task manager does not reveal anything obvious. All other processes combined consumes < 1% in an idle state, and physical memory sits around 30%-40% consumed. On the other hand, the System Event View reveals that several process are reporting X service entered the stopped state and X service entered the start state at various times. Some other errors in the event viewer that reveals symptoms of the

Event ID: 7011

A timeout (30000 milliseconds) was reached while waiting for a transaction response from the X service.

There were several of these errors where the X serice was SmcService, IAStorDataMgrSvc, Microsoft .Net Framework NGEN v4.0.30319_X86, a few others. I don't think that these services are causing the problem. Rather there's something thats causing this services to time out. What on earth is going on?

share|improve this question
I/O / Interrupts most likely, you can figure out which through performance analysis. – Tom Wijsman Jul 13 '12 at 19:27

The two things have nothing to do with each other. Idle is talking about CPU usage, not memory. It seems that you have identified the issue though, there is something wrong with these services (or a common dependency).

I would try to disable them one by one, and see if that changes anything. Additionally, I would try leaving the domain, booting in safe mode, and booting without network access.

share|improve this answer
up vote 0 down vote accepted

Turns out that Symantec Endpoint Protection is the culprit. Unintsalling the program and rebooting made it seem like a new computer again (as it should being only 6 months old).

Still, I am unable to find the cause for it to slow down. There are no other virus scans on the computer, not even Microsft's Security Essentials. This is all I have for now.

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .