Quad Client (Main Window Problem)

[warwizard]

I have been experiencing an issue since the patch.

My main window will jump to 100% CPU across all cores and FPS will drop to 5fps while the other windows operate normllly.

To get the cpu back under control, i have to kill the client or bring up task manager and preform an administrative task on the client which causes the user control window to pop open. Once Task Manager opens back up the cpu goes back to around 70%. I have disabled everything in the UI but Xperl and my action bars. Graphic settings are down.

Page file stays steady at 3.2gb's


System:
Vista x64
Intel Q6660 @ 2.40ghz (Not Overlocked)
XFX PVT88GYDF4 GeForce 8800GTS
4gb Ram
Seagate Barracuda 7200.10 ST3250410AS 250GB 7200 RPM SATA

Wow folders are Sym linked to the main install, setup has been running fine until this last blasted patch :(

[alcattle]

Did You steal my computer?

SAme specs with 8 gigs of RAM. I have not noticed a thing since the patch, but read there were some graphic changes that might be on by default. Check the WoW Video settings.

[Dominian]

I do assume you have set affinity cores?

If not all clients use core 1 wich should explain the strange behaviour.

[Catamer]

I had a similar problem before this patch..
I used the Vista performance or resource monitor, it displayed CPU/DISK/NETWORK and other feature maybe pagefile.
when I found my PC locked up for several seconds, the disk monitor displayed that it was reading 4G of disk from one of the WoW files all at once.
I think I disabled Super Fetch and the indexing service and some other things ( it was probably just turning the graphics settings down that helped ).

the other itme I had problems it displayed that the page file as being written to a lot, I think I had graphics setting on high then and each copy of wow was using 1.4G of RAM instead of the 600-700M they use now.

[wowphreak]

With 4 gigs of memory I'm betting anytime the wow client goes over 500 megs yer gonna get a ton of lag.

Ideally vista needs 2 gigs of memory for itself to run without paging any thing out that leave 2 gigs free for the game.

[emesis]

I have had similar behavior from my rig pretty much since the beginner, and through multiple upgrades. I 5-box, on a quad-core system with 8 gigs ram and running 64-bit XP pro.

The CPU peg problem can happen any time one of my WoWs is entering the world or an instance. Bringing up the task manager and then closing it, which forces a full window redraw. fixes it.

I have just been living with it, frankly.

[warwizard]

Im going to play around with more settings, if its a gfx related issue maybe a different video driver could be the solution.

[Dominian]

With 4 gigs of memory I'm betting anytime the wow client goes over 500 megs yer gonna get a ton of lag.

Ideally vista needs 2 gigs of memory for itself to run without paging any thing out that leave 2 gigs free for the game.

I got vista 32 with 4gigs of memory(3.2) and the only places i got issues is dalaran and shatrath but ofc i experience long loading screens when i load 4 clients into WG! I even quested about every place as a 5 boxer and done most of the instance and still its only Dalaran and Shatrath that causes issues.