Curse

skie88 · Oct 17, 2007, 05:19 PM // 17:19

Hi,

I haven't encounter any problems with the game until yesterday, i was doing the final mission of EoTN when the game crash whe im attacking the final boss, with crash, i mean my screen blurred and hang. When i restarted my laptop and relogged, i was brought to the return to outpost screen and got the same blurred/hang screen, that i have to restart again. In the third restart, im getting the blurred/hang screen in the logon page, and i haven't een able to run/log to gw eversince..

So far ive only tried running msconfig and going to selective startup. I tried to defrag my notebook using contig and ive been getting the same problem as with the game, the blurred/hang screen.

my videocard is NVIDIA GeForce Go 6600 and i still have about 30+ Gig in free space.. I plan on reinstalling gw and updating drivers this weekends.. also do you think it would be wise to update to directx10? Any advise/help will be very much appreciated..

regards,
Skie

tijo · Oct 17, 2007, 05:37 PM // 17:37

dx10 is totally useless, your video card isn't dx10 compatible. Have you checked your fans to see if they're full of dust. (i know is't a laptop and that you can't open it to clean the fans, but still if your fan is covered with dust, it might caus esome overheating). As for updating the drivers, you may have to get your drivers from your laptop's manufacturer's website. I had o do that for my toshiba's GeForce 6600 since the driver is made for that specific type of laptop.

Snograt · Oct 17, 2007, 09:01 PM // 21:01

The fact that the game has been running fine up until this incident would tend to rule out driver problems. Is this only a problem with GW or do any other (especially graphics-intensive) programs hang too?

If it is only GW that is affected, it may have been a one-off, unrelated crash that has corrupted your gw.dat

gtteam7 · Oct 18, 2007, 02:20 AM // 02:20

I have the same problem as the first post. Before it was fine, then the update. Once GW start up, see the login screen then crash.

*--> Crash <--*
Exception: c0000005
Memory at address 98c0a6de could not be read
App: Gw.exe
ProgramId: 1
Build: 23986
When: 10/17/2007 22:11:54
Flags: 0

System spec: Desktop
dual core 3800+ AMD
3 GB RAM
alot of free space in HD
Windows Vista
6600gt pro from evga

Try solution but didn't help:

Try new nvidia driver + the beta
Delete GW and start fresh (not copy the dat again but stream fresh from server)
Send so many msg to anet about the crash through gw game with same crash msg.
Try most of the command line from here: http://wiki.guildwars.com/wiki/Command_line still no go.

skie88 · Oct 18, 2007, 06:18 AM // 06:18

Quote:

Originally Posted by Snograt

If it is only GW that is affected, it may have been a one-off, unrelated crash that has corrupted your gw.dat

I guess ill have to reinstall, its happens before the update as well like the poster above.

gtteam7 · Oct 25, 2007, 09:32 PM // 21:32

Ok, I found the problem was Eamonn. After GW update and Eamonn update, it was Eamonn that cause GW to crash.
I found this after I turn off all the programs that was running and start GW and found that GW run and then start Eamonn and it crash GW. For those that use Eamonn, do not update unless Eamonn fix the problem. Or use old version of Eamonn.

For now I uninstall Eamonn and GW start fine and no crash.

Quote:

Originally Posted by gtteam7

I have the same problem as the first post. Before it was fine, then the update. Once GW start up, see the login screen then crash.

*--> Crash <--*
Exception: c0000005
Memory at address 98c0a6de could not be read
App: Gw.exe
ProgramId: 1
Build: 23986
When: 10/17/2007 22:11:54
Flags: 0

System spec: Desktop
dual core 3800+ AMD
3 GB RAM
alot of free space in HD
Windows Vista
6600gt pro from evga

Try solution but didn't help:

Try new nvidia driver + the beta
Delete GW and start fresh (not copy the dat again but stream fresh from server)
Send so many msg to anet about the crash through gw game with same crash msg.
Try most of the command line from here: http://wiki.guildwars.com/wiki/Command_line still no go.