[PoF] Game crashing straight to desktop. No error code, just a prompt to send a report to ANet.

MrWubzy.3587 · September 24, 2017

Hi. I've been playing in the first Path of Fire map for the last couple of days, and at odd times my game will crash straight to desktop with no error code. It will only give me a prompt to send an error report to ArenaNet, and each time this has happened I've done so. I've tried to recreate it on each occasion but it seems to happen at random. The only constant is that I'll be either in or near Amnoon Oasis when it happens, and the one odd time that I had just finished one of the hearts in the north-eastern corner of the map. It crashes like this frequently, probably once every couple of hours. No rollbacks or anything occurred when these crashes happened, and there are no malicious log-in attempts according to my account overview page.

I've also done extensive scans with both Malwarebytes and avast! and they've both come up with nothing malicious on my computer. I will note, though, that these hard crashes occurred during the first Path of Fire demo weekend for the same reason. Can anyone shed some light on this?

Thanks,

Wubzy

Inculpatus cedo.9234 · September 24, 2017

Is the 'prompt' a window that has the option to 'Show Details'? If so, you can click that and post the very first part.

Also, are you using the 64-bit client?

Good luck.

slowhands.3705 · September 25, 2017

> @MrWubzy.3587 said:

> Hi. I've been playing in the first Path of Fire map for the last couple of days, and at odd times my game will crash straight to desktop with no error code. It will only give me a prompt to send an error report to ArenaNet, and each time this has happened I've done so. I've tried to recreate it on each occasion but it seems to happen at random. The only constant is that I'll be either in or near Amnoon Oasis when it happens, and the one odd time that I had just finished one of the hearts in the north-eastern corner of the map. It crashes like this frequently, probably once every couple of hours. No rollbacks or anything occurred when these crashes happened, and there are no malicious log-in attempts according to my account overview page.

>

> I've also done extensive scans with both Malwarebytes and avast! and they've both come up with nothing malicious on my computer. I will note, though, that these hard crashes occurred during the first Path of Fire demo weekend for the same reason. Can anyone shed some light on this?

>

> Thanks,

> Wubzy

I have the same problem on my Mac Book Pro late 2017

nykur.2154 · September 26, 2017

Having the same issue with my game since PoF came out, even in old zones - just crashed twice and got a BSOD on the 3rd crash in Silverwastes.

Never once crashed before PoF came out, now its every day, multiple times a day. I'm about to just stop playing this game because this is the only game I am having issues with.

MrWubzy.3587 · September 26, 2017

> @"Inculpatus cedo.9234" said:

> Is the 'prompt' a window that has the option to 'Show Details'? If so, you can click that and post the very first part.

> Also, are you using the 64-bit client?

>

> Good luck.

Yes, it has that prompt. The next time it happens I'll update the post with the details. Also yes I am using the 64-bit client.

Nephalem.1458 · September 27, 2017

I've had similar random crashing issues (e.g. Memory at address 00000000`00000060 could not be read) for the past 4-6 months and I've been playing on the same system since 2012 when the game was released. I tried memcheck, Prime95 to stress the CPU, Furmark to stress the GPU, repaired the client multiple times, reinstalled the game, reinstalled Windows 10, tried about 10 different versions of GeForce drivers, including some from last year when I was playing without crashing, tried an old graphics card from a secondary machine, and nothing worked.

Then, when PoF was released, the problem disappeared. I played for hours and hours on end for many days in all types of situations, old and new content, and the game never crashed once. I thought the problem had been resolved and that the countless bug reports I sent to Anet finally did the trick. And there was much rejoicing!

But now, unfortunately, one of the updates in the past 2-3 days (there have been many) has reintroduced the issue and I'm crashing with the same or similar memory issues again. 3 times in the past hour, in fact. :(

Anet! Whatever you "fixed" with the memory addressing in the past few days, un-fix it please!

Inculpatus cedo.9234 · September 27, 2017

I had a similar experience. Path of Fire release worked really well, compared to the Demos, but a recent patch brought all the issues back. Sigh.

Jon Olson.8439 · September 27, 2017

Post the `*--> Crash <--*` sections from your ArenaNet.log @"Nephalem.8921" / @"Inculpatus cedo.9234" / @"MrWubzy.3587"

On Windows it's located here: `%appdata%\Guild Wars 2\ArenaNet.log`

**Note** there could be multiple crash logs in the file. Posting the last one is likely the ones you are currently dealing with.

Inculpatus cedo.9234 · September 27, 2017

Oh, I didn't have crashes. I have heating issues, again, since the latest patch(es). Sorry for the confusion.

Nephalem.1458 · September 27, 2017

@"Jon Olson.8439" - I have an open support ticket as well. My crash log is very large, but please see a few of my most recent excerpts below:

*--> Crash <--*

Exception: c000001d

App: Gw2-64.exe

Pid: 18520

Cmdline:

BaseAddr: 00007FF649D30000

ProgramId: 101

Build: 82548

When: 2017-09-27T01:30:06Z 2017-09-26T21:30:06-04:00

Uptime: 0 days 0:10:35

Flags: 0

*--> Crash <--*

Exception: c0000005

Memory at address 00000000`00000060 could not be read

App: Gw2-64.exe

Pid: 21732

Cmdline:

BaseAddr: 00007FF649D30000

ProgramId: 101

Build: 82548

When: 2017-09-27T02:37:25Z 2017-09-26T22:37:25-04:00

Uptime: 0 days 0:37:24

Flags: 0

*--> Crash <--*

Exception: c0000005

Memory at address 00000000`00000060 could not be read

App: Gw2-64.exe

Pid: 20596

Cmdline:

BaseAddr: 00007FF649D30000

ProgramId: 101

Build: 82548

When: 2017-09-27T14:37:43Z 2017-09-27T10:37:43-04:00

Uptime: 0 days 1:02:16

Flags: 0

*--> Crash <--*

Exception: c0000005

Memory at address 00000000`00000052 could not be read

App: Gw2-64.exe

Pid: 12184

Cmdline:

BaseAddr: 00007FF649D30000

ProgramId: 101

Build: 82548

When: 2017-09-27T15:05:14Z 2017-09-27T11:05:14-04:00

Uptime: 0 days 0:25:06

Flags: 0

*--> Crash <--*

Exception: c0000005

Memory at address 00000000`7f80001d could not be read

App: Gw2-64.exe

Pid: 1720

Cmdline:

BaseAddr: 00007FF649D30000

ProgramId: 101

Build: 82548

When: 2017-09-27T16:25:03Z 2017-09-27T12:25:03-04:00

Uptime: 0 days 1:19:44

Flags: 0

MrWubzy.3587 · September 28, 2017

@"Jon Olson.8439" Thanks for commenting. The spoilers below contain the most recent crash reports. I will note, though, that after the last couple of patches I haven't been crashing (but then again I haven't been playing on the map in question).

>! *--> Crash <--*

>! Assertion: Model 0x1ab512: Bad bone constraint transform on bone(bone:FlapLMid01[69]), flags(101), animated(true)

>! File: ..\..\..\Engine\Model\ModelBoneConstraints.cpp(623)

>! App: Gw2.exe

>! Pid: 7472

>! Cmdline:

>! BaseAddr: 01260000

>! ProgramId: 101

>! Build: 82488

>! When: 2017-09-25T20:04:40Z 2017-09-25T15:04:40-05:00

>! Uptime: 0 days 0:37:06

>! Flags: 0

>!

>! *--> Crash <--*

>! Assertion: timePercent >= 0.0f

>! File: ..\..\..\Game\AnimationBlendTree\AbtBlendOps.cpp(394)

>! App: Gw2.exe

>! Pid: 2524

>! Cmdline:

>! BaseAddr: 01260000

>! ProgramId: 101

>! Build: 82488

>! When: 2017-09-25T19:27:14Z 2017-09-25T14:27:14-05:00

>! Uptime: 0 days 0:06:10

>! Flags: 0

>! *--> Crash <--*

>! Exception: c0000005

>! Memory at address 6a651352 could not be written

>! App: Gw2.exe

>! Pid: 4672

>! Cmdline:

>! BaseAddr: 00FA0000

>! ProgramId: 101

>! Build: 82488

>! When: 2017-09-25T14:32:34Z 2017-09-25T09:32:34-05:00

>! Uptime: 0 days 1:10:30

>! Flags: 0

MrWubzy.3587 · September 28, 2017

A slight update. I was in the second map (I believe it's the Desert Highlands) and experienced another crash. I just did the hero point in the northwest corner if the map in the ruins with all the destroyers, and shortly after that I crashed whilst fighting a Veteran Destroyer. Details in spoiler below.

>! *--> Crash <--*

>! Assertion: (m_sphereRadius + TOLERANCE >= m_boxExtent.x) || (m_sphereRadius + TOLERANCE >= m_boxExtent.y) || (m_sphereRadius + TOLERANCE >= m_boxExtent.z)

>! File: ..\..\..\Engine\Gr\GrBound.cpp(94)

>! App: Gw2.exe

>! Pid: 8092

>! Cmdline:

>! BaseAddr: 01350000

>! ProgramId: 101

>! Build: 82594

>! When: 2017-09-28T08:19:27Z 2017-09-28T03:19:27-05:00

>! Uptime: 0 days 3:34:06

>! Flags: 0

Kwitzak.6529 · September 28, 2017

I had it while waiting for fire elemental to spawn..

Xen Blutschatten.3415 · September 29, 2017

I have the same issue starting with today. I played the first PoF-Map without any issue. I played a good while yesterday on the second one as well, but now my game crashes within minutes. I noticed that it is worse if I start playing directly after the loading screen. It seems way better if i wait for a moment.

The memory adress in the crash part of the log looks pretty off, if you ask me. I tried the repair option, but it didn't help.

>!

>! *--> Error Logs <--*

>! /i>

>! CtlText::Markup() ERROR: Invalid tag name detected. Tag: "

>! Model '0x1ad337': Failed to resolve AimIK bone indices.

>! Model '0x082239': Failed to resolve AimIK bone indices.

>! Model '0x005704': Permutation 'default' not found, auto selecting permutation

>! Model '0x082239': Failed to resolve AimIK bone indices.

>! Model '0x005704': Permutation 'default' not found, auto selecting permutation

>! Model '0x1ad5c8': Failed to resolve AimIK bone indices.

>! Model '0x1ad5c7': Failed to resolve AimIK bone indices.

>! Model '0x1ad5c8': Failed to resolve AimIK bone indices.

>! Model '0x1ad5c7': Failed to resolve AimIK bone indices.

>! Model '0x1ad5c8': Failed to resolve AimIK bone indices.

>! Model '0x1ab2f4': Failed to resolve AimIK bone indices.

>! Model '0x1ab301': Failed to resolve AimIK bone indices.

>! Model '0x082239': Failed to resolve AimIK bone indices.

>! Model '0x08223a': Failed to resolve AimIK bone indices.

>! Model '0x082239': Failed to resolve AimIK bone indices.

>!

>! *--> DirectX Device Info <--*

>! VendorId = 0x10de

>! DeviceId = 0x1b80

>! Version = 22.21.0013.8541

>! Description = NVIDIA GeForce GTX 1080

>! Compat = 0x00100000

>! VidMem = 0 MB

>!

>! *--> Crash <--*

>! Exception: c0000005

>! Memory at address ffffffff`ffffffff could not be read

>! App: Gw2-64.exe

>! Pid: 9164

>! Cmdline:

>! BaseAddr: 00007FF677D10000

>! ProgramId: 101

>! Build: 82640

>! When: 2017-09-29T17:10:24Z 2017-09-29T19:10:24+02:00

>! Uptime: 0 days 0:02:20

>! Flags: 0

zolcor.2601 · September 29, 2017

I can no longer play the Tequatl event without crashing during waiting or when in the middle of battle. I don't know what's happening with my GW2 game. Sometimes I crash at Tequatl almost instantly. Is anyone able to help me?

Nephalem.1458 · October 2, 2017

@"Jon Olson.8439" - this memory error crash is still happening and it's about 50/50 now if it will write something to the error log. If it doesn't write to the log it's because a Windows error box has popped up and said "GuildWars 2 has stopped responding." The error log is full of messages similar to "Model '0x1aac89': Failed to resolve AimIK bone indices." Any thoughts?

MrWubzy.3587 · October 3, 2017

@"Nephalem.1458" I've had similar problems where the crash report wouldn't write itself into the document, even after sending an error report to ANet through the prompt. I can't post the crash reports here, but during guild missions last night I had frequent crashes just before fighting a bounty (Brekkabek), doing a guild race (the chicken one in Diessa Plateau) and just before a node was triggered during a Trek (easy one). The only constants were these: either _I_ was mounted, my guild mates were mounted en mass near me, or I was transformed (a la guild races). The only exception was that I crashed just before the guild trek node was triggered and nobody was mounted.

I would like to note that I've only had two or three hard crashes before PoF, and those were because of patches rolling out with game-breaking bugs. With the release of the new expansion it seems that I'm getting a crash prompt every few hours or so.

DeWolfe.2174 · October 3, 2017

Here's 3 of the last errors in the logs. Be mindful, the game crashes with far higher frequency without creating a log because it blue screens hard almost every time.

Noticing "Display driver nvlddmkm stopped responding and has successfully recovered." in the windows event viewer.

Exception: c0000005

Memory at address ffffffff`ffffffff could not be read

App: Gw2-64.exe

Pid: 21804

Cmdline:

BaseAddr: 00007FF7EBDF0000

ProgramId: 101

Build: 81328

When: 2017-08-25T02:35:21Z 2017-08-24T22:35:21-04:00

Uptime: 0 days 0:35:38

Flags: 0

Assertion: Launcher: Browser crashed

File: ..\..\..\Game\Launcher\LauncherCoherent.cpp(2354)

App: Gw2-64.exe

Pid: 24484

Cmdline:

BaseAddr: 00007FF727D00000

ProgramId: 101

Build: 81328

When: 2017-08-26T03:20:24Z 2017-08-25T23:20:24-04:00

Uptime: 0 days 0:01:26

Flags: 0

Assertion: Launcher: Browser crashed

File: ..\..\..\Game\Launcher\LauncherCoherent.cpp(2351)

App: Gw2-64.exe

Pid: 10816

Cmdline:

BaseAddr: 00007FF6C4AA0000

ProgramId: 101

Build: 82488

When: 2017-09-25T08:19:06Z 2017-09-25T04:19:06-04:00

Uptime: 0 days 6:43:11

Flags: 0

DeWolfe.2174 · October 3, 2017

Tried playing for 5 minutes-10 minutes and the system utterly died and restarted. Played for another 5 minutes and the system utterly died again! Don't even get BSOD, just a screen flash to a grey or blue'ish color screen with a buzzing sound, then restart.

Nokomis.5076 · October 5, 2017

It sounds like your RAM might be damaged. As soon as a certain amount of RAM is allocated, it might hit a Bit (or some more) which are damaged leading to a total crash.

You can try testing your RAM. I don't know it MemTest+ is still working on computers these days. I think, Windows 10 has an option to test memory as well.

Ashamir.9574 · October 5, 2017

For me the client is basically doing the same thing it did when HoT launched: it's using more and more memory until at same point the game crashes. It seems to be a problem associated mainly with the PoF maps (the same as it was with HoT). If you spent too much time in the new maps the game will kill itself from maxing out RAM.

Personally, I'm experiencing the problem with the 32 bit client, as I had the exact same problem peramanently on the 64 bit client in HoT. Switching to 32 for some reason solved the problem for me then. Guess I'll try switching to 64 bit again and hoping that helps.

DeWolfe.2174 · October 6, 2017

I've tested the ram before and let Memtest do another two passes this afternoon. The only issue my system has is with GW2. The crashing occurs in a none reproducible manner.

Nokomis.5076 · October 6, 2017

Do you use any special driver configurations for GW2? Something like GeForce Experience or alike? If yes, maybe you could try running Gw2 just in standard settings.

Ever tried a -repair just out of testing purpose? Could take a moment, but maybe it's just a file damaged and when it tries to read from it, it does something awfully wrong.

When it says, browser crashed and pointing to coherent, this is usually the "browser" acting in the background for the gemshop and trading post.

Eventually try to delete the bin (or bin64) folder within your Guild Wars 2 installation. When you start the gw2.exe, it should download it anew.

vampirem.2065 · October 6, 2017

*--> Crash <--*

Exception: c0000005

Memory at address 00000008 could not be read

App: Gw2.exe

Pid: 5100

Cmdline:

BaseAddr: 00400000

ProgramId: 101

Build: 14215

When: 2012-05-15T01:01:22Z 2012-05-15T03:01:22+02:00

Uptime: 0 days 1:00:04

Flags: 0

MrWubzy.3587 · October 7, 2017

> @Nokomis.5076 said:

> Do you use any special driver configurations for GW2? Something like GeForce Experience or alike? If yes, maybe you could try running Gw2 just in standard settings.

>

> Ever tried a -repair just out of testing purpose? Could take a moment, but maybe it's just a file damaged and when it tries to read from it, it does something awfully wrong.

>

> When it says, browser crashed and pointing to coherent, this is usually the "browser" acting in the background for the gemshop and trading post.

> Eventually try to delete the bin (or bin64) folder within your Guild Wars 2 installation. When you start the gw2.exe, it should download it anew.

I did a repair of the client last night and so far, no crashes have occurred. If all else fails I'll try getting rid of the .bin.

[PoF] Game crashing straight to desktop. No error code, just a prompt to send a report to ANet.

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Create an account or sign in to comment

Create an account

Sign in