Need some help

[Bob]

As you noticed, I started getting DCed under tonight's raid.

It first started when we were running back from the Fankriss whipe - just prior to zoning in, my computer froze.  I didn't think too much of it, as it has happened a couple of times before (nothing regulary, very seldom to be honest), so I just did a hard-reset and restarted WoW.

When I started again, it all seemed to work fine, so I just kept on going, but after 5 minutes or so (was halfway through the tunnell after Fankriss) it all froze again.  Now I got a bit more suspicious, cause two freezes like this haven't happened before, so after this restart I tried to start only WoW and TS (had had both browser, torrent download, and some other stuff running earlier).
Even though I did this, I almost instantly crashed again as soon as I had loaded into AQ.

I did one more restart, and this time I started only WoW, but this time I froze just as I had typed in my password on the logon screen...  Now things are really starting to look strange.

Looking in my Errors folder under WoW, I found the most recent error to be:

Code Select Expand

This application has encountered a critical error:

ERROR #132 (0x85100084) Fatal Exception
Program:    C:\Program Files\World of Warcraft\WoW.exe
Exception:    0xC0000005 (ACCESS_VIOLATION) at 001B:004014C5

The instruction at "0x004014C5" referenced memory at "0x00000004".
The memory could not be "read".With this info, I found this site on the blizzard support web.
I've now tried to use the blizzard repair utility (didn't find any errors), without any success.
I've tried running the Windows Memory Diagnostic tool (didn't find any errors), without any success.
I've tried to remove all temporary files and addons (***, WDB and Interfance folder), without any success.
I've tried to update my graphic card driver, without any success.
I've tried running the game with the parameters -opengl -windowed -nosound, without any success.
I've checked the harddisk for errors (didn't find any errors), without any success.
I've tried to do a rollback to earlier today, without any success.

The only thing left to try now, if to do a full re-install of the game.  I'd rather avoid this (bloody tedious installing the whole game, with all the patched and everything <_<), so before I start doing that sometime tomorrow, I was hoping that some of you folks might have some hints to what I could try.


The thing I find really strange about this whole thing, is that I can't see any reason what so ever that this should happen.  The things I've done on my computer since last raid (Thursday), is installing BF2 (with a couple of patches) and Azureus, but none of these should in any way affect WoW afaik.
And it's also strange that this started to happen mid-raid, when I had already played for 2 to 3 hours...  I've also been online a bit earlier today, without noticing anything strage.

:helpsmilie2::help2::please:

[Asheera]

maybe the new patch corrupted on WOW file, try to delete the folders *** and WDB and move your add on folder away then download the last version of the add-ons last time worked for me

[Marduk]

Maybe its just blizzards way of saying you play to much and you should cut back a little..
 
All things in moderation ( even world of warcraft)

[Soulbringerx]

Looking at the record seems to me itsa problem with your memory but i could be wrong here.

[Zabard]

I had similar problems before. The screen blacked out from time to time, first only in SG. Then it started happening all over the place, and at last even sometimes at character selection. Bought a new screen card, and everything was fixed. Now, I'm not suggesting buying a new one just yet, as they are damn expensive, but do u have the possibility to borrow one from somewhere just to test it?

[Bob]

@Asheera: Have already tried that, didn't work.  And it's also a bit strange if it should be the last patch, cause I played all fine on Thursday.

@Soulbringerx: Yes, this might be the case.  I did run that MS Memory Diagnostic tool, but I only ran the fast test.  I'll give it one more try this afternoon running the thorough version of the test.

@Zabard: Might be, but it's a bit hard to check, since I'm playing on my laptop.  But I'll keep it in mind after I've tried everything else - the computer is still withing it's warranty period, so if this should be the case it shouldn't at least cost me too much to get it fixed - other than being without a computer for some weeks <_<


But thanks for the advice folks :smile:
I'll try a new memory test this afternoon, and if that doesn't work I'll try a full reinstall of WoW.  If that also fails, I'll have to try a full format of my laptop, but really hope it doesn't get to that :sad:


Edit:
@Marduk: bah, that's all just bullshit :devil:

[Umbra]

Hmm, bf2 or this azureus (no idea) may have installed newer shared dlls (updated directX?) WoW might be using, The exception is a general one such as happens if an app tries to delete/free memory that it shouldn't.

Try clearing the relatively temp WoW files. or see if those apps did alter any shared files, shouldn't affect it but well...

[Akall]

I've searched around the internet and you are not the only one with this problem the strange thing is that the most of the players having this Error are players who hacked WoW, maybe you should save your addon and configuration folders and just reinstall the game, you might have some corrupted file in there (it seems your WoW can't use his memory slots)... don't trust blizzard repair utility too much.
 
ATM searching on official forums If I'll find something useful I'll post it right away.
 
EDIT:In the official forums there are many complaining of this error after patch 1.12.1 but no Blizz poster answered yet.

[Umbra]

It might be a problem accessing high areas of memory, which is why it didn't show up immediately, try running wow with no other apps open, or swapping memory sticks round (if you have 2) to confirm. Personally I think i'd reinstall while you have a day off raiding , but we need you for tuesday

[Padding]

I would go directly to reinstall. Sure takes a while, but you have all the patches lying in your wow directory as files, so just copy them out before installing, and you are up'n'running within 1 hour

[saori]

Well, it can be a problem involving memory, corrupted WoW file and hardware troubleshoot, specially HEAT since you are playing in a laptop.
 
WoW engine is a lot of CPU and GPU consuming software, the graphic cards tend to overheat when they are used to extreme. The symptom will be that suddently the screen goes "black" althoug you can keep hearing wow sounds, windows sounds, etc. Thats because of the graphic card reaching the heat threshold and switching it off to prevent overburn!!! In a laptop things goes tigher due to space inside the mother board, so they tend to overheat a lot!!!
 
What i will suggest is to erase the addons and wtb folder in your WOW install directory. Download the repair tool from WoW and the latest content patch (about 350 MB to patch all).
 
Also make sure you dont have any firewall running that can be blocking TCP and UDP packages used by WoW. Update Windows with the latest security patches (only security ones, since others can crash things, and only update if your windows is original, if its "pirate" you will have to deail with legacy check control and im not going to explain how to patch windows to avoid that authenticate check, buy original software! :biggrin: )
 
Also you can check the BSoD of winxp to see which error is reporting (yes, windows xp also has blue screens of death, but they are hided). And of course check your EVENT log under "control panel/administrative tools/event viewer". If there is an application error or a hardware troubleshoot it will be listed there.
 
And a good technique while playing with laptops is to leave some space between the laptop base and the desk where is placed, that way it will disipate heat in a more effective way!
 
hope this helps, friend! see you!:byebye:

[Neff]

Tell me, do you get an error with Kernel32.dll? if so, try "restoring" your windows:)Shelf restored my windows, ran a virus scan and it worked with me.
 
(findmeanother word for restore!)

[Shadowsong]

The error-discription is usualy the same. I even had those in Warcraft III.
Memory modules (RAM) is still fine though, so don't think you have to worry about that too much.
You can check it with Memtest86, but if you do, do a full test (not standart run) and let it test it for a night (depending on memory size and speed, it usualy takes a couple of hours to test it good enough to make sure your mem is ok or not).
 
Freezes can be caused by heat, or software errors (in drivers for example). My brothers PC freezes a lot too (Burningsteppes and stuff) because of an error in the drivers (ATI graphics card) and his (pray to play) audigy causes lots of crashes too.

[Umbra]

graphics problems due to overheating usually causes graphical corruption or glitches first.

yep, winxp does have a BSoD but it culminates in a reset.

that error is a programming problem, to do with memory accessing, i fix a load each day at work it's usually bad code (dereferencing a pointer when you've deleted the object) .  or stack corruption because some other object has written past it's allocated area into the stack area and so the call stack turns to $hit. reinstall wow and revert dlls

[Bob]

Seems like the **** has really hit the fan
I was writing a post about the latest news, but I got a crash just before I finished the post :huh:

Can't write a long post about it now, cause I'm writing this from my PDA while taking an emergancy backup in safe-mode...
You can check out [post=153664]this post[/post] which I managed to post a bit before I crashed.

It doesn't look too good at all. When the backup is done, I'm gonna try to swap out the memory chips to see if the error might be there, but i fear that it's the gfx card that is bye gone