Iron Edge
Iron Edge => General Discussion => Topic started by: Shannaro on May 17, 2008, 02:20:04 am
-
Yeah so fuck this seriously... ive done everything i can to fix my wow. but still it doesnt work, i keep getting fatal exception.
Removed all the crap, uninstalled wow, installed it again. Yay, failure.
I log on with total no addons, no settings at all and later on i get "Critical Error: Fatal exception"...
Seriously this is anoying the crap out of me, what the fuck is going on...
Anyone really know how to fix this?
-
Maybe a fucked up harddrive/ram? Just spouting ideas here
-
Can you maybe remember what task/thing u last did before that started to happen? Flashback :)
-
Ya, try a system restore.
Otherwise... faulty hardware.
(assuming you've checked the forums for info...)
-
Hope for not damaged hardware, tho we can really only guess. Are you using overclocked comp or something? Any other game/application crashing other then WoW?
-
Does it happen on more than one char or only your mage, try every posible option and then talk to bliz support dudes.
-
before anything drastic. do a scandisk and a ram check.
-
i would guess that the chance for a ram-error is likely.
i was affected by a defect memory once. it started with a wowcrash, just a normal one with "fatal error" or whatever. after that i rebooted and whenever i rightclicked anything i got a windows-error. after that it went downhill. it ended up with me not being able to install certain files from the windows-xp installation. i tried using 6 different windows-xp cds on 5 different harddrives, and getting the exact same error every time, before i even thought the ram could be the culprit. never expected it to be like that when a memory breaks down.
although your problems might not be as drastic, the memory can get alzheimers, and it can play out in different ways. look it up!
-
I used to get that when I had faulty RAM.
Had to take 2 sticks out
-
Thanks for all the tips guys, im thankful.
So yeah...ive reinstalled wow, took away wtf/cache/interface and ive even repaired and it still doesnt work. I did a scandisk and didnt get any errors.
Now im doing a ramcheck with "Prime95". It might be my rams, i dont know...
Anyway the best part! I spoke with another GM today, after waiting 2-3h and they give me crap answers like always.
He basically said. "Reinstall wow, take away wtf/cache/interface" If that doesnt work call tech support -.-. Really, l a m e.
Plus another thing, there's no blue post about Fatal Exception errors on forums, and i asked if they actually read it ...the answer was "unfortunately" lol :p
-
Well it is surely your computer that is the probably and in that case it is quite hard to blame blizzard for it :)
Btw have you tried logging in with all your different toons?
I once had a fatal error that kept coming on only one of my chars when I logged in.
Then I tried logging in from kelrathos computer and it worked perfectly and continued to work :P
-
Yeah i logged in with Shann, kobito, my lvl 1 alts , my priest etc...:S
Its still doing a ramcheck tho...
-
Go download memtest86.
Did you try another computer?
-
hmm...no i havent tried another PC, ill try my brothers tomorrow. It probably works there, cuz hes having no problem playing on his account.
Memtest86, don't i have to like burn that on a cd? :S
-
Yes you have to burn it on to a bootable cd, a bootable usb drive or a floppydisk
-
could you not mount it using daemon tools instead of burning it to disk?
-
nope. the point is to run it before any programs are loaded in to the ram.
-
ahh right during start up? makes sense :p
-
how do i burn memtest86 on a CD? i dont know which file to burn :/
EDIT: Actually, nevermind, burned it already and lets hope for the best now!
-
*WEOWEOWEO* FULL DESKTOP ALERT *WEOWEOWEO*
-
You should leave it running overnight or something, btw.
-
eh, why, does it take like...6h? i thought of running it now coz i cant play wow anyway and got nothing else to do.
-
Ram test can run up to four hours depending on test type and ram speed/capacity. Its best to let it run during night instead of watching into crap application with basic layout doing stuff slowly, its like watching paint dry ::)
-
Memtest86 repeats the same set of tests over and over until you tell it to stop (afaik). The longer you leave it, the greater the chance of finding an error.
It took about 40 minutes for 1 pass on my dad's machine.
-
err i burned the ISO file on a CD, then i put it into my CD rom and restarted..nothing happened :/
Plus, i installed wow again, still crashing, guess my PC is fucked up.
I had some kind of memtest program checking my ram, i had it on for 2h, no errors.
And i tried prime95 or what its called from 21:00-03:00 yesterday and no errors.
Logged on my chars on my brothers PC, it works there.
THIS, SUCKS. Doing a defrag now..worst case i have to formate the PC -.-
http://forums.wow-europe.com/thread.html?topicId=1958407547&sid=1&pageNo=1
not only me.
-
Mine says "press a key to boot off the cd" when i stick one in... did u check what it said when it booted up?
Also, you may need to go into your bios and set it so that it tries to boot off your cd before your hard disk.
-
Yep, you need to set boot sequence in bios, make your CD/DVD rom as primary boot device followed by HDD as secondary. Whenever you have bootable CD in the rom you will get asked to boot from CD, otherwise it will boot from HDD as usual.
-
I really wouldnt format yet.
Do you have 2 ram blocks?
try with only one of them in. then try with the other one.
Good "manual" way to test if its the ram.
If you have done proper tests of the harddisk you could try running wow from an external drive or a generally just another HD.
-
Simon!
I think RAM is a red herring. RAM is used as im sure you are aware frequently for applications that require it when running. If ram was an issue other applications would be affected and also windows as it would be I/O crazy and no doubt reading and writing to the dodgy areas when not in wow anyway. Make sure you bios didnt crazy reset so reflash it anyway new version available or not and Set defaults.
So the question is "why WoW" and whats so special about it? Well these days Math co-processors are not REALLY used that much like they used too. most processing is offloaded to other devices so your looking at co-pro, main pro or video chipset imo. First thing if you havent done it already is whip the side off. run wow and let it do something heavy with alot of graphic effects and stick your hand in the case. Touch each chip and see if they are warm, you should be able to keep your fingers on them (or the corresponding heatseak) and not really feel it's hot that you have to pull your hand off. should be pretty warm but not scolding! If one is hot identify which and why cuz thats most likely the issue. Heat sucks but normally you would get a total lock as its the processor or video (co pro does have a different effect when overheating).
If they are all running fine and the fans are spinning try reseating everything. get the dust all out put your ram and video in a different slot (if possible unless your pci express or agp which dont have too many usually so hope its an sli board)
even get the processor out and give it a good clean with some alchol based agent and add some more computer KY! (any will do but arctic silver pwns)
HDD sector issues im sure you checked for and did all the usual stuff.
Failling all that it could be another application leaking and not clearing up its threading when closed which means you would best format anyway or set up a clean disk just for testing wow with minimal apps. I once had an issue with Google desktop indexing files which caused WoW to crash. I've also had some issues with Vista's new method for tcp tuning which is unrelated but hey.
Failling all that its a hardware replace which sucks trying to isolate it and you will need to swap out bits till you find it. The last time I had freaky crashing that was impossible to find it was the main processor heatsink. Could not work out why as it looked fine but a new one fixed it. possible metal warp creating a bad contact of course by that time most people would have just binned the PC and bought new parts anyway.
I don't know how clued up you are on stuff but if it was me id check heat and also fire up a VMWare ubuntu linux and run wow in that through wine to see if it also crashes in an isolated virtual machine. If you don't know much unix/linux scrap that idea however.
-
in addition have a read here see if any info helps
http://forums.worldofwarcraft.com/thread.html;jsessionid=BE127BEDC397CEC5CD22898C2276C7A7?topicId=74187729&sid=1&pageNo=9
mostly driver updates but might help.
Also im posting the tcp issue for vista cuz if you do have it then it MIGHT be a problem
Open a command prompt as administration and type the following
netsh interface tcp set global autotuninglevel=disabled
when you press enter it should respond with Ok.
it wont hurt adding it as it does stablise alot of other applications if you are usuing vista (and if you ARE usuing vista unplug EVERY usb device you can spare while testing)
Ta
Payu
-
Sweet, will never have to pay for any PC trouble ever again when we have Payu ;D
-
Touch each chip and see if they are warm, you should be able to keep your fingers on them (or the corresponding heatseak) and not really feel it's hot that you have to pull your hand off. should be pretty warm but not scolding!
My northbridge runs at something like 70 degrees. Wouldn't like to hold my finger on that :)
And ram doesn't necessarily have to be a red herring. WoW does use a lot of it, so it's more likely to suffer from ill-effects. Testing for it with memtest86 won't hurt :)
-
since wow doesnt even start but it goes fatal error before even entering the game properly. I would say heat is a red herring.
-
Well, he is able to log in and play for some minutes before it crashes, he was with us in karazhan this weekend and the crashes looked random.
-
Could you post the error messages, Shann?
-
Touch each chip and see if they are warm, you should be able to keep your fingers on them (or the corresponding heatseak) and not really feel it's hot that you have to pull your hand off. should be pretty warm but not scolding!
My northbridge runs at something like 70 degrees. Wouldn't like to hold my finger on that :)
And ram doesn't necessarily have to be a red herring. WoW does use a lot of it, so it's more likely to suffer from ill-effects. Testing for it with memtest86 won't hurt :)
true on ram but i get the impression hes ran it though a few tests and 70C is insanely hot for a northbridge!
-
ah sorry I thought he couldnt get in to the game.
If the crash is after a few minutes, I would say Payu is on to something.
Heat would be a very obvious choice too then.
Have you tried other games with good graphics? Do they crash.
I had a faulty ram stick, I got random errors in games after varying amounts of time, when the actual part of the ram got used for something important.
-
I remember the times of end summer 2006 when we were wiping on Magtheridon. Played on my laptop which couldn't bare with the heat so I had 0.5FPS for 20sec every 180sec. Really sucked, I put a external fan on it and it was fixed though!
Not too long ago my laptop's harddrive crashed, I couldn't right click anything, well I could but it would take 2minutes before the menu popped up. I couldn't install items or remove them. Not too long after my windows wouldn't even start up anymore. Harddrive was pretty broken and won't even be read as a slavedrive anymore.
I usually only blow up monitors, but I might have found a new area!
-
I really wouldnt format yet.
Do you have 2 ram blocks?
try with only one of them in. then try with the other one.
Good "manual" way to test if its the ram.
If you have done proper tests of the harddisk you could try running wow from an external drive or a generally just another HD.
yeah i have 2 ram blocks, and yeah i tested them, nothing wrong with the ram.
I reinstalled wow yesterday, defragged the harddisk and ran wow for about 1.5h, it didnt crash :) (YAY!) hopefully its stable. Yeah...running wow from my extern HDD is pretty smart, coz i have one next to me :D
-
This application has encountered a critical error:
ERROR #132 (0x85100084) Fatal Exception
Program: C:\World of Warcraft\WoW.exe
Exception: 0xC0000005 (ACCESS_VIOLATION) at 001B:082E1944
The instruction at "0x082E1944" referenced memory at "0x00000001".
The memory could not be "written".
WoWBuild: 8278
Realm: Dunemaul [80.239.179.56:3724]
Local Zone: Orgrimmar
Local Player: Shannaro, 000000000034BA7D, (1659.08,-4391.28,23.2954)
Current Object Track: Greda, 00000000013C0AC4, (1658.78,-4399.34,21.3567)
thats not all :> download the text file i uploaded.
-
IF you are talking about the critical 132 error then according to this thread
http://forums.wow-europe.com/thread.html?topicId=4095610014&pageNo=7&sid=1#126 (http://forums.wow-europe.com/thread.html?topicId=4095610014&pageNo=7&sid=1#126)
a solution was found on the french forums which was
there is currently a solution working that was posted on the French forums.
Basically, (this is probably a workaround) just create a new account for your Windows, from this account, WoW will not crash anymore.
"Blues" posted another solution that could also work :
- Start your computer in safe mode
- Press the Windows + R keys at the same time
- Go to "Execute" windows and enter "%temp%
- Just delete everything there, don't worry these are only copies of other files on your computer
- restart the game.
Didn't test that one yet, but the first solution is working
Also just browsing through the forums looking for a solution the american forums have had their tech guys post up a thread of solutions found here.
http://forums.worldofwarcraft.com/thread.html;jsessionid=B13901098035B7E29C035477362CE970.app01_08?topicId=10021053&sid=1 (http://forums.worldofwarcraft.com/thread.html;jsessionid=B13901098035B7E29C035477362CE970.app01_08?topicId=10021053&sid=1)
-
That's what I had in BWL if you can remember Shann, I crashed like every 20 seconds. Can't recall how I fixed it, but as Zakk pointed out there's alot of info for #132 errors.
-
The freakest wow crash I had was naxx and thaddius. dunno if some of you remember but I bombed out everytime he did phase 2. Worked out it was the nvidia drivers screwing up when it was trying to render the lighting bolts. Nothing more frustrating than stuff like that.