Client crashes when turning quests in

[DubbleClick]

(accepting reward)

doesn't happen on all quests and not always

[DubbleClick]

it's probably linked to the quest minimap line stuff

[adituv]

The one I informally reported was on taking the Disruption quest immediately after the Advanced Defense Techniques quest just to pick up skills. There was no quest handin, but I was trying to do speedrun speed so I picked up two quests within maybe 300ms of each other

[Wibblepuppy]

Happening now on Wintersday Quest turn ins at Lions. Not happening/identified at other locations.

[M3d1cZ4pp3r]

Happens to me systematically:

• Didn't occur at all in Pre-Searing
• Occurs regularly in Ascalon area, no correlation with specific outpost
• Might be related to the huge number of quests I have active in post-searing in the same area
• I also could turn in one quest without crash and then immediately another and it crashed
• Occured even with disabled toolbox minimap (quest window is active though)
• After restarting without toolbox I don't have a vanilla quest indicator at all anymore

[M3d1cZ4pp3r]

I checked a bit more. It occurs even when Minimap and Quest Info is not shown.

When I select the quest I want to turn in in the quest log (as active quest) before, it never crashes.

[SMYLOX]

I have the same problem. 90% of the time when I finished a quest and want to get my rewards, the client crashes when I press the button to take my rewards...

I didn't recognize any specific pattern so far...
I even tried different versions of GWToolbox, but 7.0-7.2 all have this problem.

Thankfully Guildwars restarts ultra fast, but it's anoying as hell :/

[DubbleClick]

Have you tried disabling the quest module?

[3vcloud]

Better yet, do you have any crash dumps that you can provide for us?

[SMYLOX]

I think I managed to isolate the "problem". When I disable the "Minimap" function, it doesn't crash anymore.

So I tested different modes to find out which function is responsible for the crash.

After I disabled/unchecked "Draw all quest markers" => no more "Quest-Crashes".

hope that helps

[DubbleClick]

I think I managed to isolate the "problem". When I disable the "Minimap" function, it doesn't crash anymore.

So I tested different modes to find out which function is responsible for the crash.

After I disabled/unchecked "Draw all quest markers" => no more "Quest-Crashes".

I repeat, have you tried disabling the quest module? Does it still crash when you have the minimap option enabled, but the quest module disabled?

Toolbox Settings - Modules - Quest

And please, any crash dumps?

[Nowbob]

I have the same issue, here is a sample error log:

RegGetValueW failed: {status:0x2, KeyName:'asadmin'}
RegGetValueW failed: {status:0x2, KeyName:'noupdate'}

EDIT: Will test some of the suggestions here and report back. First thing I'm going to try is running as admin (as a hunch based on the error log)

[Nowbob]

Alright, I tried running as admin and it had no affect; gwtoolbox and guild wars client both crash upon turning in a quest that isn't currently selected/active in the quest log.

I turned off the quest module in Settings -> Modules and this DID prevent the crashes.

I turned the module back ON, but disabled everything in the "Quest Module" settings: "Double click a quest...", Draw a path to quest marker on "Terrain" and "Minimap" ALL unchecked, and the "Max distance" setting was set to the default of 5000. Crashes would still occur with these settings.

Seems disabling the Quest Module was the only thing that worked.

[3vcloud]

Thanks for the extra info, I’ll take a look. Do you know which quest it was? Might give me a clue as the the state of it I.e did it have an active path at the time

[Nowbob]

As far as I can tell it's every quest.

1. accept more than one quest so that your quest log has multiple entries.
2. complete the objectives of one quest and head to the npc to turn it in, but don't turn it in quite yet
3. open the quest window with L
4. left click the quest you ARE NOT about to turn in so that it is highlighted and the quest module in gwtoolbox will highlight paths etc. for that quest
5. talk to the NPC and attempt to turn the quest in that isn't selected in the quest window
6. clicking the "Accept" button should cause the crash

[3vcloud]

1cb1ff6