Author Topic: MIRC draining the CPU... (Read 231 times)

Leggy Hendrix · « **on:** November 06, 2004, 09:03:35 AM »

anyone have any idea what i can do to stop mirc from draining the cpu so much...its gotten to the point that other things im doing while using mirc are seriously slowed down...

the obvious answer would be to stop using it but any help would be appreciated...

eS El Duque · « **Reply #1 on:** November 06, 2004, 09:17:12 AM »

umm...you got spyware or somthin..i can run loads of shit with mirc running on my old ass 555mhz p3 comp :p

Da WCC Hopar! · « **Reply #2 on:** November 06, 2004, 10:12:44 AM »

wat kind of cpu do u have?

Eddie G. · « **Reply #3 on:** November 06, 2004, 10:20:45 AM »

You probably got an IRC virus, cuz there's no reason for it to take up so much RAM

Leggy Hendrix · « **Reply #4 on:** November 06, 2004, 10:53:40 AM »

ive got 768 mb ddr ram and a 2gig processor...

ive scanned the shit out of my comp and it doesnt come up with any viruses or spyware...dont really know what else to do...

eS El Duque · « **Reply #5 on:** November 06, 2004, 11:52:34 AM »

Quote from: Paradox The Bilateral Metaphor on November 06, 2004, 10:53:40 AM

ive got 768 mb ddr ram and a 2gig processor...

ive scanned the shit out of my comp and it doesnt come up with any viruses or spyware...dont really know what else to do...

and you cant run other shit? you got a prob on your computer lol

Leggy Hendrix · « **Reply #6 on:** November 06, 2004, 11:53:44 AM »

i can run other stuff, but it slows it down quite a bit...

Jome · « **Reply #7 on:** November 06, 2004, 09:23:54 PM »

The more networks you are on, and the worse server you are on, the more CPU mirc will use..
I've set up mirc to join 6 networks, and the CPU-usage is between 30 and 60 RAM, usually never over 50 unless the servers lag or crash..

Try a reinstall if it's too bad, or update to latest version..

Also check your TASK MANAGER, and see what is taking up all the memory..
If you have RealPlayer, Winamp, Quicktime, Kazaa, Emule, etc. running in the background while not in use, that will take up a lot of RAM..