I've been experiencing some fairly awful latency and lack of bandwidth during peak hours(6:00-11:00) in the past few weeks, but I think that's attributed toward poor routing/heavy stress on my ISP's end.

I've made a shortcut for "wow.exe -nosound" , it does improve fps a tiny bit, but the disconnects are still occuring.

Downloading : FileForum | Download Spybot Search and Destroy
To search for some spy/adware.

Would it be possible to limit wow to 70-80% cpu time? it's nearly impossible to use other windows while wow is running.

Zurgat,I don't know if this helps but you can set priorities on your task manager (ctrl alt del that is).Just go to second tab to the left and set priority a bit higher to wow.I'm working "real time" for my proxy server and "high" for my wow.exe and works fine 90% of the time.Of course stability is an issue when you are on a vpn or a proxy.

I just put wow.exe on "below normal" and that seems to work quite well so far.
Wow just gets choppy for a few seconds so n then, nothing you really notice.
Only really works if you're not using any other applications obviously, but wow was eating 99% cpu time when in the foreground.
And you have to re-set it each time you lauch wow.

It'd be better if you could set a CPU limit of 80% or so, but at least its finally possible to startup teamspeak, skype or ie7 without having to wait 5 minutes, or having to minimize wow for it to get enough cpu time to load.

Try 'start wow.exe /BELOWNORMAL' as a shortcut.

Blizzard applied a hotfix for the brewfest (and possibly other things) on friday, i haven't disconnected a single time on sunday.
Quite odd.

Target = "C:\Games\World of Warcraft\WoW.exe" -nosound /belownormal
Does not give the desired result.

I had (or have) a similar problem. I only seem to DC suring hyjal trash specifically though, and never outside a raid definitely. I can't begin to count how many 'fixes' i've tried. No sound, -opengl mode etc, even though this all cut down on the dc rate, i'm playing at a significantly lower level (in terms of what i can see etc) than i know my pc can handle, and its a bit frustrating.
The problem does occur significantly less now that i cut back on my addons and so on, but its still there. Everything on my screen just pretty much stops, and i get booted to the login screen after 5-10 seconds. I've found it a real pain to troubleshoot. I assumed it might be addon traffic, but while that might have added to the issue i still had the problem once in a while even with 0 addons.

Bigwigs. (ace2)

Start is a command (and a program I think).

/BELOWNORMAL is a parameter for the Start command.

So, what you (could) do is to create a batch file (startwow.bat) in your wow directory containing the following on one single line: The @ is there to prevent the batch file from showing the line.

Wouldn't it be possible to modify a shortcut. (Seems a bit cleaner than a bat file)

I used to have a problem identical to this while I was on vacation over the summer. Using the Titan Performance panel on a fresh login during Hyjal trash to monitor network flow(it's best to relog or type /reloadui, since the mod takes an average from the duration you've been logged in), I saw that even without a single mod - aside from Titan of course - my network flow ingame was at 12-14kb/s in during trash, which led me to believe that there was way too much data coming in from the sheer number of NPCs and mobs running around. I'd always promptly disconnect as the trash pull began to heat up, and the disconnects came faster with every increasing wave.

Since my connection at the time could barely sustain ventrilo and a 25man raid under normal circumstances, this overloaded it terribly and I had the same problem without fail, only on Hyjal trash.

The best I could do was leave the raid channel on Vent, and the bandwidth was usually a bit less overloaded during bosses that I rarely disconnected during those.

2.2.3 Mac client crashes when an addon tries to play a custom sound; we had five crashes on the first Ground Slam on Gruul. Everyone turned off BigWigs sounds, and we've had no disconnects since.

I'm running the 2.2.3 Mac client and have custom sounds on with no issues. Admittedly, I missed tonight's raid due to work, so it may be a combo of being in a group and custom sounds that causes the crashes and not just custom sounds alone.

Could you install AddonSpamFu, and see if perhaps players in your raid are doing a lot of broadcasting as well?

From the Mac tech forums for the WoW site:

Many users are having issues with crashing since 2.2.3 has gone live. In particular with crashes that say something similar to one of these two messages:

Error: signo: 11, Fault address: 0x2a8f7000, code(1): Address not mapped to object.
Error: signo: 10, Fault address: 0x00000009, code(2): Nonexistent physical address.

This error is caused by a problem with the lua function PlaySoundFile(). The Blizzard built in UI does not use this function however many 3rd party addons do especially popular addons like FuBar_QuestsFu, Omen, BigWigs, CT_RABossMods, DeadlyBossMods, etc...

Q. When is Blizzard going to fix this?
A. We don't know. They're looking into the issue, they're aware it's causing problems for a lot of users and have said that they will fix it. No timetable for it has been given but it will take a patch.

Q. Can I just update my addons to fix this?
A. No. It's a bug in the client. However you can disable the addons that are using the function.

Q. How do I know which addons can cause the problem?
A. You can open the Terminal applications and run this command:
grep -lr --include \*.lua PlaySoundFile /Applications/World\ of\ Warcraft/Interface/AddOns/

Every file returned by that has the possibility of causing this problem.

Q. Now that I know which addons are doing it what are my options?
A. You can do one of the following:
* If the addon supports it find the option within it to disable the sound that it will play.
* Disable the addon entirely by clicking on the Addons button on the character selection screen and unchecking the box for the addon.
* Disable Sound by pressing Escape, Clicking on Sound (or Sound & Voice) and unchecking Enable Sound.

Q. I'm getting an Assertion error is this the same problem?
A. No, Assertion problems are caused by either addons or corrupt installations. See other threads for more details.

Q. I'm still having the problem, I'm pretty sure I've turned off sound for all the addons is there anything I can do? I really can't play without my addons!?!?
A. Yes, Type these three commands. Note you'll have to re-enter them everytime you start wow.
/script PlayMusic = function() return nil; end;

/script PlaySound = function() return nil; end;

/script PlaySoundFile = function() return nil; end;



Addon Instructions
Below is a set of instructions for disabling the problematic sound with a variety of addons. If you have instructions for an addon not listed here please post below.

BigWigs
Type
/bw Plugins Sounds toggle

If it says it is set to Off you're set, if not type it again.

CT_BuffMod
Type /ct to bring up the CT Configuration window.
Choose CT_BuffMod from the list.
Make sure Play Expiration Sound is unchecked.
Close the window.

FuBar_MailFu
Right click on the icon/text for Mailfu, Uncheck Use Sound

FuBar_QuestsFu
Right click on the icon/text for QeustsFu, go to the Sound on complete and Sound on Progress and uncheck Enabled for both.

Omen
Type:
/omen warnings warningSound None


ORA2
Type:
/ora ready sound

If it says Off you're set if it says on type it again.

Prat
Type:
/prat enable sounds

If it says Off you're set if it says On type it again.

As with every patch, Blizzard sends a "kill cache" command to the client. Your local client item and generic cache is being wiped due to this. This causes people with bad network cards/settings/connections to disconnect a lot. And this happens more or less every single time a new patch comes. When the cache is wiped, there is additional data that is constantly being transferred and this is then too much for the affected and they get disconnected, especially in raids where lots of sync messages and other spam is being sent and received.

I bet the same people that serial disconnect often have random red question marks instead of items or it takes ages for them until NPCs in major cities spawn in, too, after each patch.

Workaround fix: Whenever a new patch comes, don't go direct login->raid. Login at least an hour before any raid, preferably not in a major city. Log in, stay there and don't do anything at all. Let the char stay for 30 min, then logout. Exit game. Login again go to a major city or scan the AH. Logout. Afterwards your client should have its cache populated and not serial disconnect anymore.

Permanent fix: Fix your network connection. Probably your network card or setup has some problem and when lots of data is being moved, things go bad. There's a FAQ on Blizzards Techforum somewhere but I don't have a link handy. Go through that, if nothing helps there, start replacing your network card/hubs/switches to eliminate the culprit.