WoW 5 boxing, crashing issue.

[Firebuff]

Greetings,

I recently bought a beef pc to play smooth 5 boxing on 1 pc.
The pc is somewhat like this,

9650 intel2 quad extreme
500 hd -32mb
2x nvidia geforce gtx 280
m/b asus striker 2 extreme ddr3
SB X-fi
and many coolers in the box so heating is not an issue

Note that before i get this pc, i was playing on a total crap pc and was 5 boxing.
Everything was smooth and no crashes, but i was lagging like hell in major towns, or in crowded places.

So the problem is this.. On this new beef machinery, everything is smooth apart the fact i get some of my wow windows crashed every 5 to 30 mins or so..
some times two wow windows crash simultaneously, some rare times even three windows crash simultaneously.
This is annoying inside instances as i had to reload keyclone so i have my party gone broke, as a result any progress goes away and gota redo instance from the beggining.
also annoying when i just grind up, cause i get a wipe fest wherever it happens.
Can somebody help me ? Does anyone else have or had similar issues?
Thank you for any reply, i really can't understand what's wrong. ?( :?:

Edit: I get hell lots of blue screens too..

[Lorune]

First thing to test is your memory i'd say, check out memtest86 on google, burn it on a CD and test the memory.

WoW is very iffy about good memory.

Beyond that, it could be driver issue with the GFX cards. What exactly is the error u get ?

If it is a 132 my bet is on Ram being shabby

[Firebuff]

================================================== ============================
World of WarCraft (build 8606)

Exe: D:\World of Warcraft\Wow.exe
Time: Aug 17, 2008 4:59:55.294 PM
User: Teo
Computer: ENIAC
------------------------------------------------------------------------------

This application has encountered a critical error:

ERROR #134 (0x85100086) Fatal Condition
Program: D:\World of Warcraft\Wow.exe

Failed to read data.



WoWBuild: 8606
------------------------------------------------------------------------------

----------------------------------------
Stack Trace (Manual)
----------------------------------------

Address Frame Logical addr Module

------------------------------------------------------------------------------

================================================== ====================
Hardware/Driver Information:
Processor: 0x0
Page Size: 4096
Min App Address: 0x10000
Max App Address: 0x7ffeffff
Processor Mask: 0xf
Number of Processors: 4
Processor Type: 586
Allocation Granularity: 65536
Processor Level: 6
Processor Revision: 5894

Percent memory used: 36
Total physical memory: 2681864192
Free Memory: 1708163072
Page file: 5593436160
Total virtual memory: 2147352576
================================================== =================

Didn't know how i can make it look like scroll down so it won't get so big.

[Firebuff]

Getting this message some times too..
This time happened to be for ImageReady prog.
Other times happen for wow or other progs..
I think im gona have to paint my pc blue, and throw it deep into the ocean

http://img98.imageshack.us/img98/958/47528232pk3.jpg ('http://imageshack.us')

[Firebuff]

Error uppon crash: ERROR #134 (0x85100086) Fatal Condition

[Thodoros]

got same prob

[Sajuuk]

Try updating your graphics drivers.

[Lorune]

Yeps check the GFX card drivers. see if Older or the latest version work better (newest version first)

[Jayded1]

I got error 134 a bunch until I replaced my RAM. Also make sure each copy of Wow has its own folder

[Thodoros]

I got error 134 a bunch until I replaced my RAM. Also make sure each copy of Wow has its own folder
Dude what do you mean, each copy of wow having its own folder?
Like having 5 sepperate partitions just for ur wow? or have 5 different copys of wow in programme files?
Didn't knew this might help... could it?

[Lorune]

Nah, thats not the case.

However as mentioned before testing your ram is a easy thing to do. and if its flawed it WILL cause you problems when multiboxing

[Thodoros]

so im dling the source code and then write it on a floppy to boot it on a restart? does it work with cd too? i cant make it work tbh..
from windows vista cd i have a similar activity wich i run, and didnt passed the test. memory scans test untill i give the command to terminate them.
hardware problem was the issue. Tomorrow monday im getting the pc with a set of spoon and fork for them to eat it.

[bluekieran]

I've just started 5-boxing (4 on one box) and was getting this lots of crashes with this or a similar error. Proved to be two things:

1. Dodgy RAM. Happened much less frequently after I identified and replaced this.
2. Corrupt game files, possibly caused by copying the installed WoW to other folders with dodgy RAM installed. Fixed this by running the "repair" program within each WoW directory.

Since then, no problems to speak of.

[Firebuff]

Ok today brought the pc back from the hospital, it was the fact i was using 1800 rams on my motherboard wich can handle up to 1333 (or 1600 with overclocking).
Since then, everything is smooth, no blue screens no errors no fatal shits etcetera..
Cool - tnx