ATTN: Dentarg (US) - Weekly ICC Server Lag

#0 - Jan. 30, 2010, 12:20 a.m.
Blizzard Post
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Ever since the release of the new raid content, Icecrown Citadel, numerous players and guilds have reported a strange issue of lag when it came to this new instance. I speak on behalf of the guild I participate in, <imho>, and for the rest of the server when I say that this issue is something we've never seen before. Multiple guilds have been having trouble with this including <Darker Sanctum>, <Calamitous Intent>, and <From The Internet>. Here is how the situation has been since early December:

Our weekly raid times are from 8-12 PM server time. Before this time, lag is nearly nonexistent (for me personally, completely not a problem, no issues). My guildmates and I understand that there is a difference between the realm server and the instance servers. However, during these raids in ICC, we experience the problem. Lag hits whenever combat is initiated but not in the sense you would expect: latency lag, lag spikes, etcetera). This type of lag even causes trash mobs and bosses to delay their own mechanics (for instance, Lord Marrowgar would not cast flames or bone spikes for the 30-45 sec or so of "lag" we encounter, nobody would take damage, and no actions would take place). Now, in a normal lag situation, if it had occurred for a 30 second interval, it would most likely be a wipe. BUT, like I said, nobody takes damage including the boss. Mind you, this lag happens 90% of the time for the majority of the fight, so as a guild we are being delayed in progression because of this.

I have taken the extreme measures to make sure that I have concluded any obscurities on my side of the mirror. I have run DxDiags, I have done the Tracert, and I have reported my computer specs, all of which proved to be normal according to the 2 tech support operators. Myself as well as my guild mates have updated our video, sound, motherboard, network, and other drivers that MIGHT have been of any suspicion, to no effect.

To reiterate, this is not a case of an individual. For weeks, it has been such a consistent problem, the talk of making server-wide raid times has come up. This is on the Dentarg-US (PvP) realm which currently, according to http://www.WarcraftRealms.com updated on 1-28-10, we have a total population of 5407 characters above level 10 with an Alliance:Horde ratio of 1:17.3. In other words, we are a very low pop server seeing all the negatives of a high pop during raid hours.

We (myself and my guildmates) have submitted numerous tickets in-game and have used the "Report Lag" feature continuously to no avail for over a month. We haven't heard from any contact other than the usual ticket closure email and in-game mails telling us to use the forums. So, here I am...

Below are all the things I could think of to help assist any GM in making this easier for them.

Thank you.

- Kathakubal, desperate customer

-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Computer Specs:

CPU - Intel Q6600
GFX - EVGA 9800 GX2
RAM - Corsair 4GB DDR2
PSU - Ultra 550W X2
AUD - Asus D2 Audio Card
MOBO - Asus P5K-E WiFi Edition

Internet Speed - T1 direct connect University line
In-Game Latency during problem - 82-150ms




Tracert:

Tracing route to us.logon.worldofwarcraft.com [12.129.232.111]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms gw-gorham-int.unet.maine.edu [141.114.174.1]
2 51 ms 1 ms <1 ms GW-P-Science-int.unet.maine.edu [130.111.0.41]
3 <1 ms <1 ms <1 ms gi3-3.gw-portland.net.maine.edu [130.111.0.69]
4 <1 ms <1 ms <1 ms te2-2.gw-portland2.net.maine.edu [130.111.0.19]
5 5 ms 5 ms 5 ms te4-4.ccr01.bos05.atlas.cogentco.com [38.104.187.145]
6 5 ms 5 ms 5 ms te3-3.ccr02.bos01.atlas.cogentco.com [154.54.25.249]
7 11 ms 11 ms 11 ms te3-1.ccr02.jfk02.atlas.cogentco.com [154.54.5.241]
8 17 ms 17 ms 17 ms te4-1.ccr01.dca01.atlas.cogentco.com [66.28.4.126]
9 29 ms 29 ms 29 ms te8-1.ccr01.atl01.atlas.cogentco.com [154.54.2.45]
10 44 ms 44 ms 44 ms te2-1.ccr01.iah01.atlas.cogentco.com [154.54.29.2]
11 79 ms 79 ms 79 ms te9-1.ccr01.lax01.atlas.cogentco.com [154.54.0.233]
12 * 80 ms 80 ms te3-4.ccr02.lax05.atlas.cogentco.com [154.54.3.10]
13 * 80 ms 80 ms 192.205.35.5
14 81 ms 81 ms 81 ms cr1.la2ca.ip.att.net [12.122.84.202]
15 81 ms 80 ms 81 ms cr83.la2ca.ip.att.net [12.123.30.109]
16 80 ms 80 ms 80 ms gar5.la2ca.ip.att.net [12.122.129.25]
17 81 ms 81 ms 81 ms 12.122.255.74
18 81 ms 81 ms 81 ms 12.129.193.242
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.




DxDiag 64-bit:

------------------
System Information
------------------
Time of this report: 1/29/2010, 13:09:37
Machine name: JESSE-PC
Operating System: Windows 7 Professional 64-bit (6.1, Build 7600) (7600.win7_rtm.090713-1255)
Language: English (Regional Setting: English)
System Manufacturer: System manufacturer
System Model: P5K-E
BIOS: BIOS Date: 10/31/07 18:19:46 Ver: 08.00.12
Processor: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz (4 CPUs), ~2.1GHz
Memory: 4096MB RAM
Available OS Memory: 4096MB RAM
Page File: 1842MB used, 6345MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7600.16385 64bit Unicode

------------
DxDiag Notes
------------
Display Tab 1: No problems found.
Sound Tab 1: The file cmudaxp.sys is not digitally signed, which means that it has not been tested by Microsoft's Windows Hardware Quality Labs (WHQL). You may be able to get a WHQL logo'd driver from the hardware manufacturer.
Sound Tab 2: No problems found.
Sound Tab 3: The file cmudaxp.sys is not digitally signed, which means that it has not been tested by Microsoft's Windows Hardware Quality Labs (WHQL). You may be able to get a WHQL logo'd driver from the hardware manufacturer.
Sound Tab 4: The file cmudaxp.sys is not digitally signed, which means that it has not been tested by Microsoft's Windows Hardware Quality Labs (WHQL). You may be able to get a WHQL logo'd driver from the hardware manufacturer.
Input Tab: No problems found.

--------------------
DirectX Debug Levels
--------------------
Direct3D: 0/4 (retail)
DirectDraw: 0/4 (retail)
DirectInput: 0/5 (retail)
DirectMusic: 0/5 (retail)
DirectPlay: 0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow: 0/6 (retail)

---------------
Display Devices
---------------
Card name: NVIDIA GeForce 9800 GX2
Manufacturer: NVIDIA
Chip type: GeForce 9800 GX2
DAC type: Integrated RAMDAC
Device Key: Enum\PCI\VEN_10DE&DEV_0604&SUBSYS_050410DE&REV_A2
Display Memory: 2287 MB
Dedicated Memory: 495 MB
Shared Memory: 1791 MB
Current Mode: 1680 x 1050 (32 bit) (59Hz)
Monitor Name: Dell 2209WA(Digital)
Monitor Model: DELL 2209WA
Monitor Id: DELF011
Native Mode: 1680 x 1050(p) (59.954Hz)
Output Type: DVI
Driver Name: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
Driver File Version: 8.17.0011.9562 (English)
Driver Version: 8.17.11.9562
DDI Version: 10
Driver Model: WDDM 1.1
Driver Attributes: Final Retail
Driver Date/Size: 11/20/2009 21:34:54, 11775080 bytes
WHQL Logo'd: Yes
WHQL Date Stamp:
Device Identifier: {D7B71E3E-4544-11CF-3456-0F251CC2C535}
Vendor ID: 0x10DE
Device ID: 0x0604
SubSys ID: 0x050410DE
Revision ID: 0x00A2
Driver Strong Name: oem6.inf:NVIDIA_SetA_Devices.NTamd64.6.1:Section003:8.17.11.9562:pci\ven_10de&dev_0604
Rank Of Driver: 00E62001
Video Accel: ModeMPEG2_A ModeMPEG2_C ModeVC1_C ModeWMV9_C
Deinterlace Caps: {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoPr
#44 - Feb. 1, 2010, 2:35 a.m.
Blizzard Post
If you are experiencing a large amount of latency I would suggest using the newly introduced Report Lag Feature. This feature may be located by clicking on the Help Request option. This option is located in the small navigation tray near the bottom of your screen and symbolized by a red question mark icon.

This will bring up the In-Game Knowledge Base window, a database full of support articles for your reference. Four options will also appear towards the bottom of the window:
    • Talk to a GM
    • Report Issue
    • Report Lag
    • Character Stuck

Selecting the Report Lag button will open up a new intractable window in which you will be asked to specify what type of latency you are experiencing. You will be able to select from the following options:

    • Loot
    • Auction House
    • Mail
    • Chat
    • Movement
    • Spells and Abilities

After you click on one of these options, your report will be issued immediately and the selection will result in a confirmation window which will be displayed for your acknowledgement. If more than one form of latency is being experienced, a report can be issued in each appropriate category. These reports will not be accompanied by a Game Master interaction, but instead will utilized as a diagnostic tool by our Realm Technicians to help potentially identify underlying causes of latency so that they may be addressed.

We understand the frustration that these types of issues may cause and also understand that the Lag Report feature does not provide feedback regarding your reports. Please rest assured that these reports are taken seriously and are investigated appropriately.

If we, those of us who moderate the CS forum, are able to provide additional information we will though it is important to note that this is not information we are normally provided. Most available updates regarding a specific realm or Battlegroup will be provided in the Service Status forum.

http://forums.worldofwarcraft.com/board.html?sid=1&forumId=11113