Curse

samba · Jul 21, 2008, 03:24 PM // 15:24

Hiya.

So, I bought a new computer, builded it myself from the parts i ordered.

Comp was workin fine, untill I got Gw on it from my old computer. Didn't install it from a CD.

Started playin, played a while and my computer froze, everything just sopped and I had to boot from the reset button. This has happened about 10 times already,always then GW is on, once the comp froze about 5 seconds after I opened GW.

Here's some information bout my comp:
club3d 8500gt 512MB DDR2
AMD 5000+ X2 64
2gb ram
Avira Antivirus Personal Free
Comodo Pro Firewall

So, do any of you have a clue what's going on?

Btw, i have checked the temperatures of my graphics controller etc, they are just fine, also I have checked all the wires inside the computer.

Thanks.

Etta · Jul 21, 2008, 03:33 PM // 15:33

So many suggestion.....must pick...only one. or two.

1. Check that all of your drivers, graphic card, motherboard etc has been install and are up to date. 2. Keep the old gw dat file (the 3gb+ one) on the side, reinstall the game as it intend, then swap the dat file and see if that work.

More detail like window, dx and driver version help as well. Also is Gw the only game that playing up?

Snograt · Jul 21, 2008, 03:36 PM // 15:36

Check in your Guild Wars folder for an ArenaNet.txt - that will possibly give us an insight into what's going on.

You say you've checked your GPU temps, but how about the CPU?

Vista or XP?

Etta · Jul 21, 2008, 03:40 PM // 15:40

Oh yeah you have the X2, get the Dual-Core Optimizer from AMD as well. Also try to play GW on 1 core.

samba · Jul 21, 2008, 03:52 PM // 15:52

Okay, here's some answers and more questions:

-All my computers temps are fine, somewhere near 30-50C.
-No ArenaNet.txt found
-All drivers installed.
-I have Windows XP SP2
-Other games like GTA vice city, Neverwinter nights 2 are running just fine.
-DXDiag log here: http://pastebin.org/54862

-How am I going to get from 2 core to 1?
-Dual-Core Optimizer from AMD???? :S
-Cant unistall/install GW, I dont have the original CD enymore??? :S

Alexandra-Sweet · Jul 21, 2008, 03:55 PM // 15:55

Quote:

Originally Posted by samba93

-Dual-Core Optimizer from AMD???? :S

Download it from http://www.amd.com/us-en/Processors/..._13118,00.html and install it.

Quote:

Originally Posted by samba93

-Cant unistall/install GW, I dont have the original CD enymore??? :S

Delete the Guild Wars .dat file, then restart Guild Wars.

jiggles · Jul 21, 2008, 03:55 PM // 15:55

http://guildwars.com/support/downloadclient/default.php

or do as alexandra says ^^

samba · Jul 21, 2008, 04:00 PM // 16:00

Okay now, downloaded the optimizer, deleted .dat file and now installing it again. I'll let you know how it goes.

samba · Jul 21, 2008, 04:31 PM // 16:31

FFS, I went eating and when I came back, there was the login screen to GW, and my computer was frozen. !"()#)"¤/("#)#!&(/!!!!!

E: Tried to open it again, the same thing happened in the same spot, couldn't even login

And another issue popped up, but lets try to fix this first.

Alexandra-Sweet · Jul 21, 2008, 04:38 PM // 16:38

Run Guild Wars
Then go to Task Manager

Hit CTRL + Alt + Del

OR

Right click the Task Bar and click "Task Manager"

Once you've opened the Task Manager go to the tab "Processes"

From that tab search for Gw.exe

Right click on Gw.exe and click Set Affinity, then make sure only one box is
checked (doesn't matter which one)

Hit the Ok button and see if Guild Wars freezes again.

samba · Jul 21, 2008, 04:50 PM // 16:50

How am I supposed to do that, because after deleting the .dat file and installing a new one, I cant even log into GW because it freezes after 5 seconds when I open it...

E: I deleted the .dat file and started installing it again, now I could set the affinity. Only one box is checked now. Lets see if it works.

samba · Jul 21, 2008, 05:04 PM // 17:04

Oh wait LOL. I cant do anything else but laugh atm. Froze again, suprise suprise.

Any other ideas? :ASd

Alexandra-Sweet · Jul 21, 2008, 05:06 PM // 17:06

Create a Shortcut of Guild Wars > Right click it and click Properties > Where it says Target put -diag at the end of the line.

Example:

"..\Guild Wars\Gw.exe"

Changes to

"..\Guild Wars\Gw.exe" -diag

Then run Guild Wars through the shortcut and wait for Guild Wars to finish the diagnostic, if it passes the DirectX diagnostic we'll need to go back to troubleshooting.

samba · Jul 21, 2008, 05:21 PM // 17:21

All of them said 'Complete' and it gave a logfile, NetworkDiag.

Snograt · Jul 21, 2008, 06:00 PM // 18:00

Just a thought - I had to disable Defense+ on the Comodo firewall to allow Guild Wars to run. Apparently the basic functonality of Comodo is fine without the Defense+ fripperies. Give that a try?

samba · Jul 21, 2008, 06:17 PM // 18:17

I already disabled Defence+ when I installed Comodo.

Any other ideas?

Kattar · Jul 21, 2008, 06:21 PM // 18:21

Hehe, Snog said fripperies.

The -diag switch should have caused a little window, like the GW "connecting to Anet" window, to pop up showing you what it was testing. It should have put a file in your GW folder called "ArenaNet.txt" or something similar.

Do you see this file anywhere?

Snograt · Jul 21, 2008, 06:27 PM // 18:27

Crashes generate the ArenaNet.txt whereas -diag generates the NetworkDiag.txt. Could post the contents here, but it's likely to be irrelevant.

Heck, post it anyway.

samba · Jul 21, 2008, 06:29 PM // 18:29

It created a that logfile called NetworkDiag.. No Arenanet or similiar in GW folder. I also tried to search it with windows search, no result.

The logfile is here: http://pastebin.org/55000

Kattar · Jul 21, 2008, 06:30 PM // 18:30

Oh, thanks Sno, I knew it was something like that. But yeah sure, post the contents of both, if they exist. Give us something else to look at anyway.

EDIT: *looks at logfile* BorkBorkBork.

Code:

192.168.1.35:1366      67.192.11.81:80        TIME_WAIT
  TCP    192.168.1.35:1367      67.192.11.81:80        TIME_WAIT
  TCP    192.168.1.35:1368      67.192.11.81:80        TIME_WAIT
  TCP    192.168.1.35:1369      67.192.11.81:80        TIME_WAIT
  TCP    192.168.1.35:1370      67.192.11.81:80        TIME_WAIT
  TCP    192.168.1.35:1371      67.192.11.81:80        TIME_WAIT
  TCP    192.168.1.35:1372      67.192.11.81:80        TIME_WAIT
  TCP    192.168.1.35:1373      67.192.11.81:80        TIME_WAIT
  TCP    192.168.1.35:1374      67.192.11.81:80        TIME_WAIT
  TCP    192.168.1.35:1375      67.192.11.81:80        TIME_WAIT
  TCP    192.168.1.35:1376      67.192.11.81:80        TIME_WAIT
  TCP    192.168.1.35:1377      67.192.11.81:80        TIME_WAIT
  TCP    192.168.1.35:1378      67.192.11.81:80        TIME_WAIT
  TCP    192.168.1.35:1379      67.192.11.81:80        TIME_WAIT
  TCP    192.168.1.35:1381      67.192.11.81:80        TIME_WAIT
  TCP    192.168.1.35:1382      67.192.11.81:80        TIME_WAIT
  TCP    192.168.1.35:1383      67.192.11.80:80        TIME_WAIT

See all those TIME_WAIT? Those are not right. Could be a network issue. For comparison, mine looks like this:

Code:

  160.36.239.105:1391    160.36.75.134:443      ESTABLISHED
  TCP    160.36.239.105:1392    160.36.75.134:443      ESTABLISHED
  TCP    160.36.239.105:1393    160.36.75.134:443      ESTABLISHED
  TCP    160.36.239.105:1394    160.36.75.134:443      ESTABLISHED
  TCP    160.36.239.105:1395    160.36.75.134:443      ESTABLISHED
  TCP    160.36.239.105:1396    160.36.75.134:443      ESTABLISHED
  TCP    160.36.239.105:1397    160.36.75.134:443      ESTABLISHED
  TCP    160.36.239.105:1398    160.36.75.134:443      ESTABLISHED
  TCP    160.36.239.105:1399    160.36.75.134:443      ESTABLISHED
  TCP    160.36.239.105:1400    160.36.75.134:443      ESTABLISHED
  TCP    160.36.239.105:1401    160.36.75.134:443      ESTABLISHED
  TCP    160.36.239.105:1402    160.36.75.134:443      ESTABLISHED

BUT, after reading back through the post, that doesn't really have much to do with your problem. Sorry, I get confused as to what thread I'm in sometimes.