Crash during Tequatl fight

#1 - Sept. 24, 2013, 12:22 a.m.
Blizzard Post

I seem to be getting a lot of crashes during the Tequatl fight. At least once a day. It is getting really annoying since it is already very hard to get in to my main server, only to to have the game crash after putting a lot of effort in and not getting the reward I earned.

Below is the copy and paste of the latest crash, the log has additional info on previous crashes, but it seems they are similar.

—> Crash <—
Exception: c0000005
Memory at address 00000008 could not be read
App: Gw2.exe
Pid: 8120
Cmdline:
BaseAddr: 00400000
ProgramId: 101
Build: 14215
When: 2012-05-15T01:01:34Z 2012-05-14T18:01:34-07:00
Uptime: 0 days 1:33:04
Flags: 0

—> System <—
Name: SECUND3R-SCOUT
IpAddr: 192.168.0.199 192.168.56.1
Processors: 8 [GenuineIntel:6:10:7]
OSVersion: Windows 6.1 (64 bit)

—> System Memory <—
Physical: 10225MB/16360MB 62%
Paged: 10212MB/17359MB 58%
Virtual: 2371MB/ 4095MB 57%
Load: 37%
CommitTotal: 7146MB
CommitLimit: 17359MB
CommitPeak: 8687MB
SystemCache: 9803MB
HandleCount: 38987
ProcessCount: 99
ThreadCount: 1444

—> Process Memory <—
Private: 1295MB
WorkingSet: 1186MB
PeakWorkingSet: 1397MB
PageFaults: 4896020

—> Game Context <—
MapId: 171
Flags: 0×241
ElapsedTime: 00:00:56

—> Error Logs <—
d ‘0×00ce57’ from parent bone ‘aura’, there’s no bone with that name.
Model ‘0×0062f2’: Can’t link child ‘0×00ce57’ to parent bone ‘aura’, there’s no bone with that name. Linking to root instead
Model ‘0×0062f2’: Can’t unlink child ‘0×00ce57’ from parent bone ‘aura’, there’s no bone with that name.
Model ‘0×0071f7’: Missing anim or fallbacks: ggtalrtrunf
Model ‘0×006645’: Missing anim or fallbacks: ugmturn r
Mem Arena ‘Environment’ capacity exceeded. Attempted alloc category: ‘Prop Packfile’ Size: 172612
Texture missing mip chain: 0×011f2e
Texture missing mip chain: 0×011f30
Model ‘0×013892’: Missing anim or fallbacks: zeropose
Model ‘0×013a11’: Missing anim or fallbacks: zeropose
Model ‘0×01397b’: Missing anim or fallbacks: zeropose
Model ‘0×0139a3’: Missing anim or fallbacks: zeropose
Model ‘0×00e54f’: Missing anim or fallbacks: zeropose
Model ‘0×013e54’: Missing anim or fallbacks: zeropose
Model ‘0×013de4’: Missing anim or fallbacks: zeropose
Model ‘0×006645’: Missing anim or fallbacks: ugtrunfidl
File ‘0×7209’: Shader constant 0×30463360 (“fxclr”) has not been set.
Model ‘0×007209’: Missing anim or fallbacks: wgtidlerunr
Model ‘0×00f894’: UnlinkModel called on CModel without LinkComponent
Model ‘0×00f0fd’: Can’t link child ‘0×00df68’ to parent bone ‘root’, there’s no bone with that name. Linking to root instead
Model ‘0×007209’: Missing anim or fallbacks: xgtalrtrunf
Model ‘0×00f0fd’: Can’t unlink child ‘0×00df68’ from parent bone ‘root’, there’s no bone with that name.
Model ‘0×0071f7’: Missing anim or fallbacks: ggtalrtrunf
Model ‘0×007209’: Missing anim or fallbacks: xgtrunfalt l
Model ‘0×007209’: Missing anim or fallbacks: hgtrunfalt l
Model ‘0×00f0fd’: Can’t link child ‘0×00df9a’ to parent bone ‘root’, there’s no bone with that name. Linking to root instead
Model ‘0×00f0fd’: Can’t unlink child ‘0×00df9a’ from parent bone ‘root’, there’s no bone with that name.
Model ‘0×0071f7’: Missing anim or fallbacks: ggtalrtrunl
Model ‘0×0071f7’: Missing anim or fallbacks: ggtalrtrunf

—> DirectX Device Info <—
VendorId = 0×1002
DeviceId = 0×6718
Version = 8.17.0010.1124
Description = AMD Radeon HD 6900 Series
Compat = 0×00000000
VidMem = 1755 MB

#2 - Sept. 24, 2013, 2:54 p.m.
Blizzard Post

Hi Baal – It looks like you’re getting Out of Memory crashes. The short version of this is that you’ve got more memory on your system (GPU + RAM combined) than the 3.5ish limit that 32-bit operating systems allow.

And to copy and paste what I told another player earlier: "This is where it gets a little complex but the short version is that the additional memory can push your total available memory into negative numbers resulting in crashes or simply, “out of memory errors.” Some players have resolved this by upgrading to 64-bit operating systems and others have simply removed physical RAM from the system to bring the memory totals closer to values intended for that revision of Windows (32-bit). Obviously removing RAM from your PC is not an ideal solution but I wanted to give you all the information we have found regarding these issues. You can read more about this issue from Microsoft here: http://support.microsoft.com/kb/929605 but the important part is listed below:
“For example, if you have a video card that has 256 MB of onboard memory, that memory must be mapped within the first 4 GB of address space. If 4 GB of system memory is already installed, part of that address space must be reserved by the graphics memory mapping. Graphics memory mapping overwrites a part of the system memory. These conditions reduce the total amount of system memory that is available to the operating system.”
One solution presented by players being affected by this is to change the “Maximum pre-rendered frames” in the Nvidia control panel. To do this:
1. Right-click on your desktop and select “Nvidia Control Panel.”
2. Select “Manage 3D Settings.
3. Scroll down until you find “Maximum pre-rendered frames” and change it from “Use the 3D application settings” to “1.”
Once completed, click “Apply” to save your changes and try Guild Wars 2 again.”

Hope this helps. I can’t tell you to upgrade to a 64-bit operating system, and I know other players in the forums have some workarounds, though I personally would recommend upgrading if this is something that you’re able to do.

EDIT: If you do NOT have a 32-bit operating system, please send us a support ticket. I’m trying to track this issue and so the more information we can gather from players experiencing this issue with 64-bit operating systems the better.

#4 - Sept. 24, 2013, 3:15 p.m.
Blizzard Post

Silly, yes. However, this is not an issue specific to Guild Wars 2. It’s a limit of 32-bit operating systems which can happen on a number of different newer games.

And as I mentioned in the edit, if you have a 64-bit operating system please submit a support ticket so that we can further assist you.

#8 - Sept. 24, 2013, 4 p.m.
Blizzard Post

The most recent crash errors are toward the bottom, not the top. Again, the the original response was edited. If the original poster or anything else is experiencing “Out of Memory” crashes but has a 64-bit operating system creating a support ticket is the way to go so we can collect more data in regards to this issue and narrow down the cause and in turn hope to get it resolved for everyone.