Curse

Missy E · Apr 25, 2006, 09:40 AM // 09:40

Hi!
I have a very annoying problem that I wanna speak about.
As I have read alot on the forums I know that im not alone. Although I feel that my problem is a little bit of unique.

U see, as many other my GW often closes down with the "Send in report to Anet". What is so freaking, it ONLY happens when Im in HA, either waiting for the team to finish up, but also when Im "in-fight".
When in HA sometimes it takes 5 minutes, sometimes 20. But it almost always happens in half an hour.
Well, then I went into it RA instead. Here i can play for as long as 2 hours, still no shutdown. I've done this several times the last week when the problem started.

My spec:
Acer Aspire 5024

AMD Turion ML-34 (1,8 GHz, ATI Mobility RADEON® XPRESS 200 series chipset)
1024 MB Ram PC2700 (Hyundai Electronics)
ATI X700 128MB

This how the log starts (last time it went down):
*--> Crash <--*
Exception: c0000005
Memory at address 00000008 could not be written
App: Gw.exe
ProgramId: 1
Build: 16943
When: 4/25/2006 00:30:10
Flags: 0

*--> System <--*
Name: ACER5024
IpAddr: 192.168.0.5
Processors: 1 [AuthenticAMD:15:4:2]
OSVersion: 5.1

*--> Thread 0xfffffffe <--*
eax=00000008 ebx=00000000 ecx=00000008 edx=00000009 esi=16923c94 edi=00000002
eip=00592009 esp=012dfb44 ebp=012dfbb4
cs=210202 ss=001b ds=0023 es=0023 fs=0023 gs=003b efl=00000000

esi-32 16923C74 c221af39 10000104 140914e4 3bb1b04e
esi-16 16923C84 bfdc5ae9 c27abe0f 00000004 14092a44
esi +0 16923C94 bbac2dcb bf11227a c28400f9 00000000
esi+16 16923CA4 1409bbae bd90bf7f 361fe91f c28c10d6
esi+32 16923CB4 10000100 140a5c86 3f09864c 3f86f913
esi+48 16923CC4 c2718668 00000003 140a5c92 4109e344

*--> Code <--*
00591FE9 8100e890 00e7ffa1 d0478300 2bc3a3d0 .........G..+...
00591FF9 4783008b 14855847 83008915 545b8300 G.....XG....T[..
00592009 5f5bc390 90909055 8bec83ec 1853568b _[.....U.....SV.
00592019 f15783fe 058bfa7c 1468a205 0000bae0 .W.....|.h......
00592029 9e7f00b9 885c8300 e84a00e7 ff85ff0f .....\...J......
00592039 85a40000 008d04b6 c1e00a05 58e38200 ............X...

The only thing I get out from it is:
Memory at address 00000008 could not be written <-- Does this mean that my RAM is ****ed up and I should get a new one?

If you want more please just tell me.

Anyways, yesterday it went so frustrating i just decided to reformat the hdd and do a clean install of Windows Xp Pro SP 2.
Did it solve the problem??? NO

The problem for is that it only happens in HA. Therefor i dont know how to act. I dont know here to start the search for the problem. Any help is greatly appreciated.

Just ask away if there are any questions...

MuRRe

Divinus Stella · Apr 25, 2006, 10:29 AM // 10:29

I'd guess its the mesmers, try pre-veiling and call for the odd SB when poss.

Pupu · Apr 25, 2006, 10:57 AM // 10:57

Quote:

Originally Posted by Divinus Stella

I'd guess its the mesmers, try pre-veiling and call for the odd SB when poss.

<--------------wtf at that mesmer comment?

anyways to your question to your error, i would do a repair data -repair in shortcut or do a quick reinstall., if you installed from cd try the client from gw webbysite, if that dont work...then your probaly having same issues as me try some of the solutions posted in my error thread, good luck ----> http://www.guildwarsguru.com/forum/s....php?t=3016355

Missy E · Apr 25, 2006, 01:36 PM // 13:36

BTW, im sitting at school with my lappy. It hasnt hanged yet. So strange. Have been playng HA for about 2 hours now. Mb it has to do with my internet at home.
Have Netgear Router

audioaxes · Apr 25, 2006, 04:22 PM // 16:22

id say a memory error (RAM)
im one of the many that have the same problem with gw, crashes to desktop due to memory error
if your memory is to sticks try putting one stick of ram in at a time and see if it crashes

Narada · Apr 25, 2006, 05:07 PM // 17:07

Quote:

Originally Posted by audioaxes

id say a memory error (RAM)
im one of the many that have the same problem with gw, crashes to desktop due to memory error
if your memory is to sticks try putting one stick of ram in at a time and see if it crashes

memtest86 is also a great way to check your memory for errors. http://www.memtest86.com/