Crash since patch

[bob]

That makes me think that your virtualised config files are not right - this is the second post I've seen about "locked" and "incompatible".

You could try move/deleting the virtualised wtf (and other files) and let them be recreated after you've patched outside of IS.

Although I could be barking mad too

that made me check blizzard forums, i'm not the only one with this issue. I HAD to use the app to repatch my game.... when that's done i'm hoping all systems go

[MiRai]

think so? i'll have try and reboot the modem/router/allinonething. Cause i added the 443 or whatever you had mentioned earlier.. and it let me patch isboxer... but my server list looks like this... cant access either... Locked or Incompatible.

Have you run the launcher since yesterday? Do you have multiple WoW installs?

never ran the launcher... ran the blizzard desktop app and it made me patch again, and now i seem to be fine.

[MiRai]

never ran the launcher... ran the blizzard desktop app and it made me patch again, and now i seem to be fine.

Expect many more (likely small) patches to be pushed over the course of the next 4 weeks which will continue to create this same problem because this is a pre-expansion patch and now millions of people are "testing" it.

I got those errors on my daughters pc. It worked after forcing update in WoW. Not a Multiboxing issue, but a 6.0.2 issue.
I however have been having a problem where one of my clients just drops. This has never happened in the past so I'm assuming that it's a 6.0.2
issue as well.

This is what Windows claims has happened

Problem Event Name: APPCRASH
Application Name: WoW-64.exe
Application Version: 6.0.2.19033
Application Timestamp: 543d7042
Fault Module Name: ntdll.dll
Fault Module Version: 6.1.7601.18247
Fault Module Timestamp: 521eaf24
Exception Code: c00000fd
Exception Offset: 0000000000050e27
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional Information 1: 6896
Additional Information 2: 6896e1e3fca6f943a3cbd5e4592dc0c1
Additional Information 3: 6659
Additional Information 4: 665952a804520a6ae6b213198b2a7627


Anyone getting this?

[MiRai]

This is what Windows claims has happened

<Crash Report>

Anyone getting this?

Are you on the development build of Inner Space? If not, open it up and check the "download development patches." Then shut down and restart Inner Space, and let it patch up.

[bob]

Exception Code: c00000fd

Oooo a Stack Overflow.
If the dev build doesn't fix it, you should check for a compatibility setting in place that shouldn't be there.

You can do a diagnostic for crashes from ISBoxer http://isboxer.com/wiki/Diagnostics and check the registry settings down the bottom for anything related to WOW. You shouldn't have any.

Just patched it I will let you know the outcome, thank you