Curse

Thorsten · Apr 28, 2008, 12:49 AM // 00:49

I just finished replacing my old Athlon 64 system with a new Core2 Quad setup. As I keep my programs on a second hdd, all I had to do to play GW after installing the OS was reinstall the client and point it to the old .dat file.

Or so I thought.

With (almost) all new equipment, I am having a random problem. Guild Wars is occasionally locking up, repeating the same sounds over and over (a one-second loop driving me insane), and kicking me to the desktop. The GW taskbar items disappears, but the sound loop continues until I kill the process in the Process manager. For a split second, I can see the "GW error submission" box, but it disappears when the taskbar thing does.

The error is completely random. Vanquishing Joko's Domain with my guild last night, it happenned 3 times in 2 hours - thank goodness for the reconnect dialogue! This afternoon, I played for a couple hours and absolutely nothing happenned. Tonight, it took 15 minutes to boot me to the desktop. It's totally random; I can't tell when it will happen.

The system is running at stock and is stable in all other applications; 25C at idle, 45C at maximum load. I have tortured this thing to high heaven (8 hours of ORTHOS, 4 hours of Memtest86) to ensure component stability and nothing has flinched. I've even hard-tested the PSU for rail stability. I can't for the life of me figure out what is going on.

Here is my system, if that will help.
Intel Core 2 Quad Q9300 @ 2.5GHz
Gigabyte P35-DS3R rev 2.1, F3 BIOS
4GB (2x2GB) Corsair DDR2-800
Sapphire x1950xt w/ 8.3 drivers
Hitachi SATA 7K250 hdd
Pioneer SATA DVDRW
Corsair HX620 PSU
Vista64 w/ SP1

Mork from Ork · Apr 28, 2008, 01:02 AM // 01:02

I've been having the same problem since the most recent updates.

I have not had a freeze or crash in something like 8 months but have had 5 crash to desktop/briefly see error submission box since thursday.

Thorsten · Apr 28, 2008, 01:49 AM // 01:49

I just deleted my .dat file and am reinstalling to see if the updates hosed something internally. I'll report back with my findings.

Tarun · Apr 28, 2008, 03:13 AM // 03:13

You may want to set the affinity to 1 core/cpu in your Task Manager.