GcasServe and GcasDtServe Lock up my computer

  • Thread starter Thread starter Mikell
  • Start date Start date
M

Mikell

They run multiple instances of their processes and take
over 100% of CPU process. I shut down each GCAS process and
the next GCAS process in the list takes over 100% of CPU
cyles.
Finally over came after shutting down 4 instances of the
GCAS processes. When I tried to Uninstall the software it
did not complete. Gave me an error message 1905 Module -
indicated it could not unregister gccollection.dll -
suggested I contact support personnel.

Any suggestions?? Anyone else having this problem?
 
I have this problem too. I have to kill the gcasDtServ.exe process because
it runs all the time using 100% of my CPU, causing my computer to run at a
temperature of about 70 degrees, which is not good.

It seemed to just start happening after it "updated the software" to the
slightly newer version released last week or so. Should I uninstall and then
downgrade?

Any help would be appreciated,

pr0gram the pr0grammer
 
-----Original Message-----
I have this problem too. I have to kill the
gcasDtServ.exe process because it runs all the time
Click to expand...
using 100% of my CPU, causing my computer to run at a
temperature of about 70 degrees, which is not good.

It seemed to just start happening after it "updated the
software" to theslightly newer version released last
week or so. Should I uninstall and then
downgrade?

Any help would be appreciated,
Click to expand...

-Can you see something within your error.log. Program
files - MSAS.

- Remove all temporarily junk. User/Local settings
(hidden)

- Scan a deep scan in safe mode with MSAS.

- Scan with other tool as Adaware or Spybot.

MSAS must be "working" with something beacuse of your CPU
load and perhaps it needs a little help from other tools
to clear it out.
 
Would you be up for creating an intentional crash dump to help analyze this
bug? Microsoft says they could use several such dumps. I didn't get clear
whether they need a full memory dump or just a mini dump, so I suppose full
would be better.

Send me email by removing the last two terms from my address, and I'll send
you a KB reference that shows how to set up a keystroke to crash the machine
and create the dump.

I don't know what level of risk to your data is involved in such a crash. I
sure wouldn't have other apps open. I have done it on my own system with no
noticeable ill effect.

It does require that you have a ps/2 style keyboard--i.e. round plug, vs USB
flat plug.
 
i am having the same problem-i have installed the anti-spyware on to a
windows 2000 terminal server-with 10 users-so there is 10 instances of it
running at once-in the last 10 days i have had the server grind to a
hault-when i look at the processes its maybe just 2 or 3 of the antispyware
processes are running flat out....i was wondering is the system terminal
server compliant....obviously the same problem is on other users machines
too
 
The current beta is not recommended for production machines, and any testing
done in a Terminal Services environment is likely to have been very
informal.

I've got it running on some servers which use Administrative terminal
services sessions, and haven't had significant problems, but one of those
installs had a log file which grew out of control.

In your environment, I would recommend using it for cleaning on a one-shot
basis and then taking it off or disabling real-time protection via the
workaround paragraph in this KB article:

http://support.microsoft.com/kb/892375 End users may be prompted to allow or
block administrative actions that originate from a central management tool
after they install Windows AntiSpyware (Beta) on a computer that is managed
by Systems Management Server 2003
 
Back
Top