Blue wall issue

[Tehtsuo]

Have not seen that kind of thing myself.

You could try to launch each account solo, and go through the Launcher rather than wow.exe and see if they're all patched up.

What software are you boxing with?
What are your computer specs?

Yeah, tried the launcher and it's 100% patched. Boxing with ISBoxer, and I'm running win 7 64 bit with an i7 920, 6 gb ram, Intel SSD and GTX 260.

I'm trying a cache clear and launch solo through launcher to see if that will clear it up.

[thefunk]

I've had that too - I reloaded that window and it fixed it.

No biggie.

[Tehtsuo]

I've had that too - I reloaded that window and it fixed it.

No biggie.

Yeah, the first time I did that and didn't think more of it. However after it happened for the 15th time, my patience had started to wear thin. Completed the cache wipe and let the launcher sit for an hour, then logged in (without innerspace) and did my auctionhouse work for a while this morning. We'll see if that clears it up for good.

[HPAVC]

I would expect their response and yours frankly. You supposed to be better than this if your going to do this hobby.

You gave them no real information other than what you see on the screen superficially and that your boxing. Of course there is no qa process on their end for boxing. Or running multiple launchers, etc. Their solution is pretty simple, the game is working as intended.

I am guessing the download is having a problem locking a file or with a similar semi-static resource, you should do what the other poster said and launch individually (as a test) or run perfmon with an eye for file exceptions.

Since everyone else doesn't have this issue, some discussion on your game disk layout or isboxer config files might be useful.

Perfmon will also show the concurrency against the tcp session to the same endpoint addresses, perhaps they dont allow you to have a large number of sessions against the same streaming server like they do for game play.

[Tehtsuo]

I would expect their response and yours frankly. You supposed to be better than this if your going to do this hobby.

You gave them no real information other than what you see on the screen superficially and that your boxing. Of course there is no qa process on their end for boxing. Or running multiple launchers, etc. Their solution is pretty simple, the game is working as intended.

I am guessing the download is having a problem locking a file or with a similar semi-static resource, you should do what the other poster said and launch individually (as a test) or run perfmon with an eye for file exceptions.

Since everyone else doesn't have this issue, some discussion on your game disk layout or isboxer config files might be useful.

Perfmon will also show the concurrency against the tcp session to the same endpoint addresses, perhaps they dont allow you to have a large number of sessions against the same streaming server like they do for game play.

It was an open-ended support request, not a self service post. I was simply looking for more information about the phenomenon that I was encountering, as I have never witnessed a physical obstruction in the game world before. Remember, I don't have an inside knowledge of the how the game works, that's what Blizzard is there for.

Either way, I've mentioned more than once that my troubleshooting is ongoing and I expect to find a solution for this problem on my own at this point. I am surprised that my post was dismissed like it was, but I never showed any indignation - no need to throw a fit.