Tech Support Forum - View Single Post

zero9046 · 04-15-2008, 10:57 AM

well, long story short i ended up upgrading my processor (from AMD dual core 4000, to 4800) and that still didn't fix the problem, but now I have a faster processor (marginally speaking)!

still irked by the problem, I spent 2 hours checking each addon in the game individually and found out that it was the recount damage meter. now I just need to find a new damage meter i like. but at least the hiccups are gone!

Now my system specs are as follows:

AMD Athlon 64 x2 4800 (2.5ghz with 1mb cache)
BFG 650W PSU
MoBo: Asus NARRA2
4G RAM (PC5300)
EVGA 8600GTS w/ 256MB DDR3 (overclocked with rivatuner)

I'm pretty happy with the setup now considering how little it has cost me (relatively).

BTW, I just upgraded to SP1 for Vista, and in the past, even with 4GB of memory, it only registered 3. Now when I logon and the welcome screen pops up, it is registering 4GB. Don't know if that was SP1 fix but I just thought I'd mention it.

04-15-2008, 10:57 AM	#15 (permalink)
zero9046 Registered User Join Date: Mar 2008 Location: North Texas Posts: 30 OS: Vista Home Premium	Re: WoW fps issues well, long story short i ended up upgrading my processor (from AMD dual core 4000, to 4800) and that still didn't fix the problem, but now I have a faster processor (marginally speaking)! still irked by the problem, I spent 2 hours checking each addon in the game individually and found out that it was the recount damage meter. now I just need to find a new damage meter i like. but at least the hiccups are gone! Now my system specs are as follows: AMD Athlon 64 x2 4800 (2.5ghz with 1mb cache) BFG 650W PSU MoBo: Asus NARRA2 4G RAM (PC5300) EVGA 8600GTS w/ 256MB DDR3 (overclocked with rivatuner) I'm pretty happy with the setup now considering how little it has cost me (relatively). BTW, I just upgraded to SP1 for Vista, and in the past, even with 4GB of memory, it only registered 3. Now when I logon and the welcome screen pops up, it is registering 4GB. Don't know if that was SP1 fix but I just thought I'd mention it.