4

I'm trying to deal with a zombie problem. Every process I load in Windows 8 sticks around as a zombie.

A couple notes: a restart works, but takes a while. It's a solution, but not my favorite. Zombie processes in my case fill up 16k in the page table and 4k in private memory. All the information I've managed to collect come from Rammap, a system utility.

In Rammap I see a variety of processes:

wuauclt.exe
wsqmcons.exe
WSHost.exe
WOTLauncher.exe
WorldOfTanks.exe
WmiPrvSE.exe
WLMerger.exe
wemgr.exe
...

Big problems are PING.EXE and conhost.exe

This problem forces me to restart my computer once a day to play games at all, and it's quite aggravating. (the games are spawning many PINGs and conhosts)

How can I find out what process(es) to kill in order to get rid of the zombie processes?

Doktoro Reichard
  • 5,390
  • 5
  • 35
  • 42
Zeus Kabob
  • 41
  • 1
  • 1
  • 2
  • 2
    Can you see them in Task Manager and/or [Process Explorer](http://technet.microsoft.com/en-au/sysinternals/bb896653.aspx)? – Bob May 12 '14 at 10:20
  • 1
    You start by Googling for the executable names and making an inventary of what these processe **are**. Some of the examples you give are perfectly normal and persistent. Note that when Googling executable names, the top results are often to fake pages that do not give much actual information; they are just adverts for (fake) cleanup tools. You may have to go through several search results to get at useful info. – Jan Doggen May 12 '14 at 10:30
  • Also, just semantics, but a child process without a parent is an *orphan process*, not a *zombie process*. I'm unclear on the usage on the **zombie** tag, though. – Raystafarian May 12 '14 at 11:05
  • Thanks for the comments. I can only find them in Rammap. The executables are all perfectly ordinary processes that I run. The problem is when there are hundreds of dead (or orphan) processes using 20kb of memory apiece. – Zeus Kabob May 12 '14 at 15:56
  • 2
    @Raystafarian - the term **zombie** as used here refers to any process (child or not) that hanged, is not responding, and may be difficult to kill. – Jesse Chisholm Jun 07 '15 at 16:11

1 Answers1

3

In Windows a zombie process is often the result of a buggy driver - and that would be my first suspect, especially with so many unrelated processes remaining. Check out Cannot end Windows 7 Process, even tried pskill and Why do some process stay in Task Manager after they've been killed? for additional information.

Check for driver updates. I would pay particular attention to graphics and networking drivers. You might be able to remove those drivers and see if it helps.

Especially if this is a recent issue, you can try reverting anything that has changed. System Restore tends to work reasonably well for undoing driver installations.

Community
  • 1
Bob
  • 60,938
  • 25
  • 191
  • 216
  • I have no idea how long this issue has persisted, but I've had problems with "unaccounted for" memory for a while. I'll try updating my drivers, and I'll get back to you on how it works. – Zeus Kabob May 12 '14 at 15:57
  • I updated all drivers that I could; turned out only to be a webcam driver, Intel HD 4000 driver update, and a bluetooth driver. I also installed some non-vital windows updates. After the updates and a full system restart, the issue persists (tested by running ping 350 times. All instances remain in the page table). – Zeus Kabob May 13 '14 at 06:50