Page 1 of 2
1
2
LastLast
  1. #1

    Curse Client, High Latency, and "Unrepairable Damage"?

    Just want to make something clear, I am far from a computer/network expert.

    I had just sent in a ticket to Blizzard about how over the last 24 hours or so I have been noticing high latency (I had went from 50ms for both home and world to random spikes of 300-2700+ms).
    I had troubleshooted and done the typical things that Blizzard asks you to do prior to submitting a ticket (Rebooting router, deleting interface, Cache, WTF fodlers etc). I done al lthis with no success and sent in a ticket. Minutes later, I get the following response:


    I know what the issue is: you have a third party add on called Curse Client operating on your PC. Unfortunately, sooner or later, Curse creates serious technical and security issues. We strongly recommend avoiding any third party programs and are unable to assist with technical issues arising from them. I can tell you this: it won't help if you uninstall it at this point, the damage is done.

    In this case, I recommend you seek a windows certified tech with game installation experience to repair the damage caused by this program. It typically requires a complete wipe and windows reinstall.

    If you still need assistance you can select the “Not Resolved” button below or call us directly. If you would rather speak with someone directly, please contact Account & Technical Services. Our contact information can be found at <http://blizzard.com/support/article/cs>

    Game Master (X)
    Account & Technical Services
    Customer Services
    Blizzard Entertainment
    www.blizzard.com/support
    As I had noted at the top of the thread, I am not computer expert.
    This to me seems kind of extreme. I never heard anything about Curse causing problems to anyone. Could the Curse Client really be the cause of the High latency? If so, is there any way to fix this? I do not want to have to go out, find a computer expert IRL, pay them money, later find out the only option is to restore my computer, then have to get an external hardrive of sort and then transfer my important documents to it.
    If I do need to completely restore my computer, are there any certain (corrupt) files to be wary of transfering? (Such as some folder within world of warcraft).

    Thank you for any help in advance, I appreciate any and all help.

  2. #2
    Deleted
    On a whim, if you play LoL try uninstall Panado media booster.

  3. #3
    I have never tried LoL before and dont have the Panado media booster instaleld.

  4. #4
    Legendary! Seezer's Avatar
    10+ Year Old Account
    Join Date
    Aug 2010
    Location
    DEEEEZ NuUuUuuTssss
    Posts
    6,010
    Quote Originally Posted by Araestira View Post
    Just want to make something clear, I am far from a computer/network expert.

    I had just sent in a ticket to Blizzard about how over the last 24 hours or so I have been noticing high latency (I had went from 50ms for both home and world to random spikes of 300-2700+ms).
    I had troubleshooted and done the typical things that Blizzard asks you to do prior to submitting a ticket (Rebooting router, deleting interface, Cache, WTF fodlers etc). I done al lthis with no success and sent in a ticket. Minutes later, I get the following response:




    As I had noted at the top of the thread, I am not computer expert.
    This to me seems kind of extreme. I never heard anything about Curse causing problems to anyone. Could the Curse Client really be the cause of the High latency? If so, is there any way to fix this? I do not want to have to go out, find a computer expert IRL, pay them money, later find out the only option is to restore my computer, then have to get an external hardrive of sort and then transfer my important documents to it.
    If I do need to completely restore my computer, are there any certain (corrupt) files to be wary of transfering? (Such as some folder within world of warcraft).

    Thank you for any help in advance, I appreciate any and all help.
    No. But do you live on the east coast and have comcast by chance? This has been happening sporadically over the past few months. Does the blizz website take ages to load as well?
    "Do you think man will ever walk on the sun? -Ali G

  5. #5
    Quote Originally Posted by Seezer View Post
    No. But do you live on the east coast and have comcast by chance? This has been happening sporadically over the past few months. Does the blizz website take ages to load as well?

    I do not. Currently living in Alberta, Canada with Telus. The Blizzard website loads fast; Every webpage and other internet service seems to be loading at a normal rate, as far as I can see currently.

  6. #6
    Legendary! Seezer's Avatar
    10+ Year Old Account
    Join Date
    Aug 2010
    Location
    DEEEEZ NuUuUuuTssss
    Posts
    6,010
    Quote Originally Posted by Araestira View Post
    I do not. Currently living in Alberta, Canada with Telus. The Blizzard website loads fast; Every webpage and other internet service seems to be loading at a normal rate, as far as I can see currently.
    While it may be a pain to deal with, I wouldn't worry yourself too much about it. I highly doubt it's the curse client. It often gets blamed for alot of things that it isn't responsible for.
    "Do you think man will ever walk on the sun? -Ali G

  7. #7
    Just wanted to bump this thread, with a small update.
    Its been a day and I still don't have any changes to my latency. Seems to stay stable more around 200-350+ (sometimes staying at around 900). I am trying to run a virus scan incase but it is showing no problems at all.

    Would anyone have any idea how to fix this, in general? As I had put in the OP, My normal latency should be around 30-60. I have tried all the 'basic' things.

  8. #8
    I am Murloc! Cyanotical's Avatar
    10+ Year Old Account
    Join Date
    Feb 2011
    Location
    Colorado
    Posts
    5,553
    it could be a routing issue, the phoenix area of Arizona is SOL atm because a router somewhere is dying

    i would suspect that it is a similar issue for you

    find the IP address of the server you play on and then open a command prompt and type: tracert <server ip>

    then copy and paste the results

  9. #9
    Moderator chazus's Avatar
    10+ Year Old Account
    Join Date
    Nov 2011
    Location
    Las Vegas
    Posts
    17,222
    Try completely uninstalling WoW and reinstalling it. It takes just a few minutes

  10. #10
    Epic! Idrinkwhiterussians's Avatar
    10+ Year Old Account
    Join Date
    Dec 2010
    Location
    In a bar. Somewhere that carries Khalua, cream and Vodka
    Posts
    1,690
    I have been having the same problem, and got a canned response, even while including the info that I had done all of the usual suspect things. I was worried for a bit since I have not seen anything on the forums about it.

    I am trying a fresh install myself, and hopefully that will work.

    As for the trace (as per blizz suggestion also):


    Tracing route to 63.240.161.189 over a maximum of 30 hops

    1 <1 ms <1 ms <1 ms 10.0.1.1
    2 14 ms 14 ms 8 ms 10.41.0.1
    3 12 ms 12 ms 12 ms 72.240.7.25
    4 19 ms 16 ms 17 ms 72.240.0.206
    5 14 ms 13 ms 14 ms core2.buckeyecom.net [72.240.0.205]
    6 36 ms 25 ms 25 ms xe-10-2-0.bar1.Cleveland1.Level3.net [4.53.196.5]
    7 24 ms 23 ms 25 ms ae-6-6.ebr1.Washington1.Level3.net [4.69.136.190]
    8 25 ms 26 ms 26 ms ae-8-8.ebr1.Washington12.Level3.net [4.69.143.218]
    9 25 ms 37 ms 48 ms ae-101-3501.edge1.Washington12.Level3.net [4.69.158.17]
    10 35 ms 40 ms 35 ms att-level3-te.washingtondc12.Level3.net [4.68.62.30]
    11 43 ms 48 ms 47 ms cr2.wswdc.ip.att.net [12.122.134.186]
    12 45 ms 44 ms 44 ms cr1.cgcil.ip.att.net [12.122.18.21]
    13 41 ms 45 ms 40 ms gar2.clboh.ip.att.net [12.122.133.197]
    14 42 ms 43 ms 43 ms 12.122.251.22
    15 41 ms 43 ms 43 ms 63.240.130.210
    16 * * * Request timed out.
    17 * * * Request timed out.
    18 * * * Request timed out.
    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.


    I unfortunately have not taken any of my networking classes yet, so I am not entirely sure what it all means as Blizz mentions: "It wont matter if errors are after our servers, which can include att.net"


    Sorry to kinda jack your thread Araestira, but I thought maybe combining information on the same issue could help us with a common solution.


    Edit: Some relevant info, I have not had issues with anything else, including but not limited to D3.
    Quote Originally Posted by Cyanotical View Post
    anyone want doughnuts? i hear there is a great shop in Vancouver

  11. #11
    I am Murloc! Cyanotical's Avatar
    10+ Year Old Account
    Join Date
    Feb 2011
    Location
    Colorado
    Posts
    5,553
    Quote Originally Posted by Idrinkwhiterussians View Post
    I have been having the same problem....... but I thought maybe combining information on the same issue could help us with a common solution.
    i dont really see anything too high as far as latency goes, so the problem could be either on blizzards end after the firewall, or on your end behind the firewall, try checking to make sure wow is not blocked by either your windows firewall or your router firewall

  12. #12
    I am Murloc! Cyanotical's Avatar
    10+ Year Old Account
    Join Date
    Feb 2011
    Location
    Colorado
    Posts
    5,553
    right click> select all> ctrl+c

  13. #13
    My Results:

    Tracing route to 206.18.149.17 over a maximum of 30 hops

    1 <1 ms <1 ms <1 ms 192.168.1.254
    2 7 ms 6 ms 7 ms 10.235.16.1
    3 9 ms 8 ms 7 ms 209.115.198.217
    4 19 ms 15 ms 7 ms 173.182.206.246
    5 * * * Request timed out.
    6 44 ms 44 ms 43 ms chcgildtgr00.bb.telus.com [154.11.11.34]
    7 44 ms 44 ms 44 ms 173.182.200.2
    8 57 ms 92 ms * 192.205.37.173
    9 * 59 ms 59 ms cr1.cgcil.ip.att.net [12.122.84.54]
    10 58 ms * 177 ms gar2.clboh.ip.att.net [12.122.133.197]
    11 59 ms 73 ms 79 ms 12.122.251.22
    12 59 ms * 59 ms 63.240.130.210
    13 * * * Request timed out.
    14 * * * Request timed out.
    15 * * * Request timed out.
    16 * * * Request timed out.
    17 * * * Request timed out.
    18 * * * Request timed out.
    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.

  14. #14
    I am Murloc! Cyanotical's Avatar
    10+ Year Old Account
    Join Date
    Feb 2011
    Location
    Colorado
    Posts
    5,553
    again, doesn't look like it's anything on the way from you to blizzard, so it could be an issue behind blizzards firewall (63.240.130.210)

    check your firewall settings, otherwise there is not much you can do

  15. #15
    Would saving/copying my addons folder have any affect on uninstalling wow? Dont want to re download everything again heh.

  16. #16
    Moderator chazus's Avatar
    10+ Year Old Account
    Join Date
    Nov 2011
    Location
    Las Vegas
    Posts
    17,222
    Quote Originally Posted by Idrinkwhiterussians View Post
    11 43 ms 48 ms 47 ms cr2.wswdc.ip.att.net [12.122.134.186]
    12 45 ms 44 ms 44 ms cr1.cgcil.ip.att.net [12.122.18.21]
    13 41 ms 45 ms 40 ms gar2.clboh.ip.att.net [12.122.133.197]
    14 42 ms 43 ms 43 ms 12.122.251.22
    15 41 ms 43 ms 43 ms 63.240.130.210
    16 * * * Request timed out.
    Quote Originally Posted by Araestira View Post
    9 * 59 ms 59 ms cr1.cgcil.ip.att.net [12.122.84.54]
    10 58 ms * 177 ms gar2.clboh.ip.att.net [12.122.133.197]
    11 59 ms 73 ms 79 ms 12.122.251.22
    12 59 ms * 59 ms 63.240.130.210
    13 * * * Request timed out..
    I'm seeing you both having problems at those last four hops before the 63.240.x
    Unfortunately, if it is an issue with routing out there, it may or may not be something that can be fixed. I would contact your ISP, and basically tell them "My internet shits out here, how do we fix this?" it may be a case of your ISP contacting someone else to fix their crap.

  17. #17
    Quote Originally Posted by Cyanotical View Post
    again, doesn't look like it's anything on the way from you to blizzard, so it could be an issue behind blizzards firewall (63.240.130.210)

    check your firewall settings, otherwise there is not much you can do
    How/What should I change?

  18. #18
    Moderator chazus's Avatar
    10+ Year Old Account
    Join Date
    Nov 2011
    Location
    Las Vegas
    Posts
    17,222
    Quote Originally Posted by Araestira View Post
    Would saving/copying my addons folder have any affect on uninstalling wow? Dont want to re download everything again heh.
    The purpose of deleting wow entirely, would be to eliminate those things from the problem... So I'd say no. However in light of the trace route, that may not be necessary. I'd contact your ISP first with the traceroute info, confirming other people dropping at that point.

  19. #19
    Quote Originally Posted by chazus View Post
    The purpose of deleting wow entirely, would be to eliminate those things from the problem... So I'd say no. However in light of the trace route, that may not be necessary. I'd contact your ISP first with the traceroute info, confirming other people dropping at that point.
    I see.
    Thank for all the help in this thread. I will phone my ISP tommorow (im guessing they are closed atm).

  20. #20
    I am Murloc! Cyanotical's Avatar
    10+ Year Old Account
    Join Date
    Feb 2011
    Location
    Colorado
    Posts
    5,553
    Quote Originally Posted by chazus View Post
    The purpose of deleting wow entirely, would be to eliminate those things from the problem... So I'd say no. However in light of the trace route, that may not be necessary. I'd contact your ISP first with the traceroute info, confirming other people dropping at that point.
    it's not really a huge problem though, i would expect to see a time of 200+ at a hop if there was a routing issue

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •