WoW Crashes

[Gambler1971]

I have 3 accounts, that I run on 2 machines. The second machine runs only one copy of WoW, in full-screen normal mode, and never misses a beat.

The main machine, runs 2 accounts, using 2 monitors, both in Windowed mode, using maximiser (I have a radeon card setup as 1 huge desktop over 2 monitors). Almost everytime I try to fly somewhere, using the Flying Mounts (the ones u buy at 70), both, or at least one account, on this machine, will crash, to a little 'ok' type box, which actually has no writing, but I can push the only button it has and it goes away. Behind this little box is the WoW error, please send to us, window for when WoW crashes.

If only 1 WoW crashes, then the other may sometimes no longer show the mouse movements, but if I can guess where it is, I can still click on say hearth (or any other WoW button I want, open bags etc, just cant see the mouse).

The crash will also happen at other times, even when just simply running. Thankfully it never happened whilst fighting.

It has only started to do it tho, since Keyclone 1.8e. However, I got the new mouse the same day. So I have no idea what is causing it. Any ideas anyone?

My specs:
* 3.0Ghz AMD Athlon X2 Dual Core 6000+
* ASUS motherboard
* 2G Ram (forgot which one for this comp but it was a good brand)
* Radeon HD 2600 Pro
* ASUS 22" monitor (2ms) main - set to 1680x1050
* LG 17" monitor (8ms) secondary - set to 800x600
* Win XP sp2
* Mouse - Logitech G9
* KeyClone v1.8e
* Latest ati & hydravision (as of 13th March 08.)

[keyclone]

i'm thinking its memory.. but you said it crashed every time you jumped on a flying mount.

try this: come in fresh.. don't move.. and jump on the mount. does it crash?
if so... then run your wows... then on keyclone, right-click remove both.. so they are running but not connected.. then try mounting. same problem? then its a blizzard or hardware issue.

let me know how it goes.

g'luck,

Rob

[Gambler1971]

This is a partial of the error code I get from WoW:

================================================== ============================
World of WarCraft (build 7799)

Exe: C:\Program Files\World of Warcraft\Wow.exe
Time: Mar 20, 2008 3:28:36.755 PM
User: removed
Computer: removed
------------------------------------------------------------------------------

This application has encountered a critical error:

Insufficient system resources exist to complete the requested service.

Program: C:\Program Files\World of Warcraft\Wow.exe
File: Data\common.MPQ
================================================== ============================

Being on Windows XP I dont think I can got past 3Gb Ram, currently at 2Gb. I really dont want to buy more ram, unless it is the only solution. Or are the system resources able to be resolved in another manner?

YES. It still does it when removed from KeyClone. However, only one freezes and closes, and it could be either.

[Lorune]

http://memtest86.com/

Download this, and burn it to a CD, reboot your PC and it should start checking your systems memory.

(there is a ISO download on the page)

If a error pops up you know its your memory and should return it.. :)

[Gambler1971]

I had previously done one last Sept. But I downloaded v3.4 and retest my Ram just now. Result:

"Pass Complete, No Errors, Press ESC to Exit".

My ram is KINGSTON (2x)1GB 800MHz DDR2 NON ECC 240pin UNBUFFERED DIMM (KVR800D2N5K2/2G).
My video card has 512Mb onboard.

I have found this out, I have a device that will not load, no matter what I try. It reads:

================================================== ===========
VIA OHCI Compliant IEEE 1394 host controller
---------------------------------------------------------
Device type: IEEE 1394 Bus host controllers
Manufacturer: VIA
Location: PCI bus 3, device 7, function 0

Device Status:
This device cannot find enough free resources that it can use. (Code 12)

If you want to use this device, you will need to disable one of the other devices on this system.

Click Troubleshoot to start the troubleshooter for this device.
================================================== ===========

Im not sure if this would be effecting the game or not. I have no idea what device this even is. I tried removing all my unused resources (parallel port etc) but it still cant find any resources. I am using the Microsoft Driver v5.1.2535.0
As far as I know the only thing I have inserted is the graphics card. But an internet search indicates that the above is related to Firewire devices, so Im probably just hoping it was so simple as fixing that error.

I now have the WoW2 (on the small monitor) on 800x600, with everything at min lvls. I have WoW1 (main) on medium settings.
WoW1 frames is 20-40.
WoW2 frames is 15 (always for some reason).

I have also realised that even tho I think its all one extended desktop, to MAXIMISER, it is 2 separate ones.

Cant think of anything else that maybe relevant.

[keyclone]

another thought would be to trim down your system before you even run wow or keyclone.

personally, when i boot up, my task manager shows about 32 processes and about 350M of memory in use (don't quote me.. i'm at work.. i cannot get the exact numbers). i use hardware firewalls and while i am playing, i turn off my anti-virus and software firewall(s). i also went through and trimmed my services (start/run/services.msc) to only those things i need.

:!: if you don't know what you are doing with services.. please don't noodle with it. if you accidentally 'disable' a vital service and reboot, it's a bear to get back.

anyhow, trimming down your system may give you more room to play. but 2GB should be far more then enough for 2 wows. application crash just seems weird.

good luck

[Gambler1971]

Other than my cpu, sound and video drivers, there is only the mouse driver (i tried turning it off, no difference), and the internet connection notifier (the 2 little blue comps) loaded.

I tried running a mem program in the background. The crashes happen when I still got at minimum 300Mb of Ram left, and a max of 600Mb. It is soo weird. Damm blizz prolly never answer me. I just wish I knew where to look. It does not happen if I open 2 WoW windows, but have one minimised, at worst in this situation, the minimised one might lag behind and stop following me.

Sad, cause I love multi-boxing my 3 accounts. But the errors make it annoying and limit what I can do.

[keyclone]

ok... one more time...

are you able to reproduce the crash every time by having 2 wows running, 1 minimized, and trying to get on a flying mount?

is this accurate?

what is the minimal number of things you need to do in order to reproduce? if you could, can you screen shot your taskmanager (right click system tray/taskmanager) and post it? i'd be interested in the processes and performance tabs (stretch to fit all processes)

[Gambler1971]

How to explain. Umm, ok, if I use non-windowed mode (default mode of WoW), which means I will have to have one WoW minimised in order to play both, then NO, it will not crash, well, it never has for me anyway. But this means alt-tab or using the PiP function to switch between the 2 WoWs.

If, using 2 monitors, I have both WoWs in windowed mode, and use MAXIMISER to stretch them to the full size of each monitor, thus, I will have WoW2 on the small monitor (at 800x600 in windowed mode, low graphics detail), and WoW1 on the main monitor (at 1680x1050 in windowed mode, medium detail), then it will crash. I have been doing some tests. If I hop both WoW1 and WoW2 on their flying mounts in shatt, fly them up say 20 feet, but do nothing other than stopping them from going afk, then they can fly happily for 30 mins plus, and will not crash (not even after the 30 mins). However, if, with both monitors on like this, and in windowed mode, if I put WoW2 into follow mode, and start physically flying around (whether it be in a city, or anywhere), then somewhere between 10secs and 1 min, one, or both of the WoW accounts will crash with the insufficient error. I have noticed it only happens for 2 reasons (well it appears this way), [1] if I change direction of the flight (i.e. I hold down right-mouse and turn in any direction), this one sets it off the most, or, [2] if I hit an area with a lot of players, or NPC's. In either case, my poor hdd sometimes goes nuts, just before it happens, but not always. I am hoping its not cause I run both from the same HDD. {Samsung 320GB HD321KJ HDD - SATA II 7200rpm - split into 2 drives due to Win XP unable to format over a certain size. I have 50Gb left on C drive, and 20Gb on G drive. WoW1 is on C drive, WoW2 on G drive.}

http://img120.imageshack.us/img120/6826/processds2.jpg (http://imageshack.us) http://img180.imageshack.us/img180/4540/performancenp3.jpg (http://imageshack.us)

[keyclone]

checking what you have running,

aawservice.exe Ad-Aware 2007 Service from Lavasoft
PnkBstrA.exe PunkBuster
PnkBstrB.exe PunkBuster
hpzipm12.exe HP printer support

these services you may not need while playing wow. personally, i would remove anything i didn't need, especially if i'm having odd problems.

the other weird processes seem to be related to ATI's graphics drivers.

which brings me to the drivers. are you sure you have:
a. the right drivers for your card?
b. the latest and greatest directly from the ATI support webarea?

at this point, i don't think it's a wow/blizzard issue.. but a graphics card/driver issue.

let me know if you find out anything.

[Gambler1971]

Definately using the correct drivers. I downloaded and re-installed just incase, no change. I also tried matching both desktops at 1024x768, still crapped itself.

I installed SpeedUpMyPC just for the ability to match whats happening. At the point of death, my CPU is between 60-80%, my RAM is 70-90%, and my harddrive is always 95% plus.

When I originally installed Win XP, I used these bios settings for the HDD. "Onboard SATA Controller [Enabled]", and "Onboard SATA Type [IDE Controller]". When I first got my comp it had stability problems which turned out to be the bios setup of the cpu. However, I was told at that time I should not have choosen [IDE Controller], but no one told me which one was the correct one to use so I never reformatted.

What I really dont understand tho, is, if I still have upto 30% of my RAM left, why is my HDD going so crazy. I admit I dont understand paging.

Mind u, my uncle who is a comp engineer for the govt thinks it might be cause my drivers are actually built for Vista, and Im trying to run them on Win XP. Dont really believe that tho, cause there is no other game that even slightly plays up on this comp, not even tf2, half-life 2, lotro (yeah i was dumb enough to play that one), and I run them all at max settings, but never in windowed mode cause I have no need.

I asked for help thru ATI, but the Tech guy just sent me a link to a FAQ which was useless cause I went thru all this when I originally got the computer "https://support.ati.com:443/ics/support/default.asp?deptID=894&task=knowledge&questionID=28022".

My head hurts.

[Gambler1971]

Ok. I have found at least 20 different posts around the internet with the same crash error. Maybe 20% use the same or similar card to me, however, it is happening to nVidia card owners as well. Sometimes it is resolved by any of the following:

..(a) Updating video drivers [latest already]

..(b) Reducing in-game graphics to minimum [tried that]

..(c) Running the repair utility from the WoW directory [tried that]
......- also removing the WTF/Cache/Interface directories

..(d) Running a Scandisk or Defrag [tried that]

..(e) Removing unused windows processes [tried that]
......- I found a post with a link to driverheaven that says exactly what to disable

..(f) Uninstall and entirely delete the WoW directory, then re-install [tried that]

..(g) Test Ram [tried that]

..(h) Set ATI Catalyst Control Centre settings to Application Controlled AA / Introscopic then turn em off in-game [tried that]
......- actually in-game there is no exact AA settings so set multisample to x1 and all detail to min

..(i) Try the omega ATI drivers [tried that]
......- they actually made it worse, but some ppl reported it as a fix for them

..(j) Clean up the HDD and Registry (e.g. DriverCleaner) [tried that]

Unfortunately nothing has worked for me, there is a slightly reduced chance atm that I will crash after doing these things, that is to say, instead of it happening anywhere between 10secs to 30 secs after I mount up and start flying, it now might give me 1 - 2 minutes before it does it. And it almost never does it on a ground mount, except in shatt, and sometimes AV.

Anyway, thanks for your help Keyclone. It helped me cause we were looking in the right areas, as I could tell by the other posts I found on other forums.

Cant afford more Ram, or a new video card, so I just have to hope and pray that ATI or Blizz solve this error.