HS:CT;NetCacheCardValues=1

When I try to open Hearthstone, the game begins to load and then hangs for several minutes and I get one of several different errors, such as “HS:CT;NetCacheCardValues=1”.
Please advise.

1 Like

s0phist,

That’s a generic connection error so it can have a lot of potential causes. What have you already done to try to troubleshoot this, and what type of device/operating system are you playing on?

First I tried employing the “scan and repair” feature. Then I uninstalled and reinstalled. Neither did anything. I’m on a PC with Windows 10 Pro. If I connect with a VPN I can get the game to load.

Sounds like an ISP issue of some sort, since a VPN works around the problem. We can try to find that! If you’re still having this problem, please create a WinMTR test which catches one of these failures to connect. You want to restart the test every 10-15 minutes until you catch one of these problems. Once you’ve caught one red handed, run the test for about 5 more minutes. This will let us look for problems between your house and our servers which may cause this.

If you have problems with posting it due to a link error, go ahead and copy paste this into your next post, and replace “WinMTR goes here” with your test.

~~~~
WinMTR goes here
~~~~
|------------------------------------------------------------------------------------------|

|                                      WinMTR statistics                                   |

|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

|                                  H      -    0 |  387 |  387 |    0 |    0 |   15 |    0 |

|                             192.168.5.1 -    0 |  387 |  387 |    0 |    0 |   15 |    1 |

|             121.sub-66-174-53.myvzw.com -    0 |  387 |  387 |   24 |   36 |   61 |   31 |

|                   No response from host -  100 |   79 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 |   79 |    0 |    0 |    0 |    0 |    0 |

|               83.sub-69-83-81.myvzw.com -    1 |  384 |  383 |   23 |   38 |   57 |   35 |

|                   No response from host -  100 |   79 |    0 |    0 |    0 |    0 |    0 |

|               26.sub-69-83-82.myvzw.com -    2 |  360 |  353 |    0 |   42 |   70 |   31 |

|               26.sub-69-83-82.myvzw.com -    2 |  364 |  358 |   25 |   41 |   61 |   37 |

|              102.sub-69-83-82.myvzw.com -    2 |  368 |  363 |    0 |   39 |   59 |   31 |

|  0.csi1.BLTNMN86-MSE01-BB-SU1.ALTER.NET -    4 |  340 |  328 |    0 |   48 |   80 |   47 |

|                   No response from host -  100 |   79 |    0 |    0 |    0 |    0 |    0 |

|               0.ae3.BR3.CHI13.ALTER.NET -    2 |  364 |  358 |    0 |   48 |   75 |   48 |

|         lag-35.ear6.Chicago2.Level3.net -   11 |  276 |  247 |   34 |   47 |   86 |   43 |

|                   No response from host -  100 |   79 |    0 |    0 |    0 |    0 |    0 |

|    BLIZZARD-EN.ear7.Chicago2.Level3.net -    7 |  305 |  284 |    0 |   50 |  108 |   42 |

|                   No response from host -  100 |   79 |    0 |    0 |    0 |    0 |    0 |

|         et-0-0-3-br02-eqla1.as57976.net -   70 |  103 |   31 |    0 |  113 |  323 |   92 |

|                           137.221.68.91 -   46 |  139 |   76 |    0 |   88 |  142 |   92 |

|        lax-eqla1-ia-bons-03.as57976.net -   46 |  139 |   76 |    0 |   88 |  106 |  100 |

|                           24.105.30.129 -    0 |  387 |  387 |   75 |   87 |  110 |   83 |

|________________________________________________|______|______|______|______|______|______|

   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Hey there,

Thanks for providing the test. It looks like after the data leaves your phone/wireless modem it goes through this myvzw network, where the signal becomes degraded and looses packets.

A VPN or Proxy might work around the issue, but that’s not a fix. This is something that will need to be addressed by the service provider that owns those nodes (Verizon WIreless.)

Thanks for your input. Anything I should do?
As a bit of additional information: Verizon may be doing work or making changes to the tower I connect to. My latency used to be 40-50ms and now it’s consistently ~10ms.
Also, I used to be able to connect with my VPN employing IKEv2 or Wireguard protocols. Those protocols now make the connection prohibitively slow. TCP and UDP protocols still work fine though.
I haven’t made any network changes on my end.

s0phist,

Since we’ve identified the node where the issue is, the best bet for now is reporting the problem to your ISP. Usually if you get in touch with a tier 2 or 3 technician you can get someone to forward it along to whoever has access to that part of the network. As for the VPN issues, that’s beyond the scope of what we can troubleshoot other than suggesting to potentially try a different one. It’s really just a work around until the ISP fixes things anyway. Best of luck with that either way though!

Cool, thanks for the help!

For me helped only a clear dns caches. this is instruction: https://eu.battle.net/support/ru/article/82450

1 Like