CO Client uses 50 percent CPU

Hi,

In the last month, my CO client started using 50percent of my CPU power about 5 minutes AFTER I log! My 2 clients now uses 100pct of my CPU, so its laggy i cant play 2 clients even.

Before last month things were fine, my normal CO client uses only 5 to 20pct CPU power. Can anyone help figure out why my CO client uses 50pct of my CPU power now? oh, i have a good PC and graphics card, first assume not my PC problem. and the client was suddenly fine (5 to 20 % CPU) for a couple days before this 5253 patch, after 5253 patch, it uses 50pct to 80pct CPU now! I not using multiclient and any bot.

I need soem help on this, anyone also facing this issue?

Thanks!

In the task manager process list right click Conquer.exe and set the priority to a lower setting, CO may lag a bit more, I'm not totally sure why conquer would all of a sudden start taking up so much of your cpu's power.

If you're using any hacks that inject themselves into Conquer's memory space that could be a problem if they have any memory leaks, it'd cause Conquer.exe to use massive amounts of memory.

on the official forums there is a bug thread about it.

please post there

[Only registered and activated users can see links. Click Here To Register...]
[Only registered and activated users can see links. Click Here To Register...]

It's the new anti-bot system, use Process Explorer and kill the thread that's running tqwea.dll

getting crafty TQ is not.

Got it. Thanks for the link to the bug forum and the solution. I manage to kill the offfending process, though its name is also Conquer.exe instead of tqwea.dll now. I read somewhere tqwea.dll is built into conquer.exe...
Anyway this problem is caused by TQ, happens on fresh client install also.

Quote:

Originally Posted by Coearth Got it. Thanks for the link to the bug forum and the solution. I manage to kill the offfending process, though its name is also Conquer.exe instead of tqwea.dll now. I read somewhere tqwea.dll is built into conquer.exe... Anyway this problem is caused by TQ, happens on fresh client install also.

tqwea.dll's functions were placed into the conquer.exe but it still has it's own thread, that's why gabrola said to kill the thread not the actual application :P

Haven't looked at it though, tqwea hasn't affected me one bit.. haha

Maybe your PC is Sheety :)) sorry for language ... but My clients are use 5% or less ....

Quote:

Originally Posted by killerofthehell Maybe your PC is Sheety :)) sorry for language ... but My clients are use 5% or less ....

Ugh :facepalm: read some posts above