Strange, frequent crashes happening recently

#1 - April 26, 2014, 3:02 a.m.
Blizzard Post

Hey guys,

So for the past few weeks my Guild Wars 2 seems to be crashing primarily (but not exclusively) in main cities like Divinity’s Reach, Vigil Keep etc.

Relevant System specs are as follows:

  • Processor: Intel i7k (not overclocked)
  • GPU: GTX670 SLI
  • Power Supply: Seasonic Platinum 1000W
  • 16G Corsair RAM
  • Noctua Heatsink & Fans

If you need anymore details let me know. Crash report is under the spoiler so you can open/close it at will. Due to the world limit in this post, I have included what I think is relevant in the crash, I can provide what isn’t there if you need it.

Cheers,


—> Crash <—
OOM: Heap, bytes=2620852,
App: Gw2.exe
Pid: 3824
Cmdline:
BaseAddr: 00400000
ProgramId: 101
Build: 32998
When: 2014-04-26T07:45:36Z 2014-04-26T17:45:36+10:00
Uptime: 0 days 8:57:38
Flags: 0

—> System <—
Name:
IpAddr:
Processors: 8 [GenuineIntel:6:10:9]
OSVersion: Windows 6.1 (32 bit)

—> System Memory <—
Physical: 178MB/ 3308MB 5%
Paged: 2440MB/ 6614MB 36%
Virtual: 118MB/ 2047MB 5%
Load: 94%
CommitTotal: 4173MB
CommitLimit: 6614MB
CommitPeak: 4249MB
SystemCache: 483MB
HandleCount: 25057
ProcessCount: 64
ThreadCount: 1056

—> Process Memory <—
Private: 1630MB
WorkingSet: 1586MB
PeakWorkingSet: 1614MB
PageFaults: 12900818

[DbgHelp.dll is C:\Windows\system32\dbghelp.dll]
[DbgHelp.dll version 6.1.7601.17514 (64/32-bit compatible)]

—> Error Logs <—
‘1729238864970678820’
Content is referencing a propID that doesn’t exist propId=‘1729238864970678823’
Content is referencing a propID that doesn’t exist propId=‘1741448950136734216’
Content is referencing a propID that doesn’t exist propId=‘1741448950136734219’
Content is referencing a propID that doesn’t exist propId=‘1729238864970678818’
Content is referencing a propID that doesn’t exist propId=‘1741448950136734216’
Content is referencing a propID that doesn’t exist propId=‘1729238864970678829’
Content is referencing a propID that doesn’t exist propId=‘1741448950136734219’
Content is referencing a propID that doesn’t exist propId=‘1741449053215949326’
Content is referencing a propID that doesn’t exist propId=‘1729238864970678818’
Content is referencing a propID that doesn’t exist propId=‘1729238864970678819’
Content is referencing a propID that doesn’t exist propId=‘1741449053215949327’
Content is referencing a propID that doesn’t exist propId=‘1729238864970678824’
Content is referencing a propID that doesn’t exist propId=‘1729238864970678828’
Content is referencing a propID that doesn’t exist propId=‘1729238864970678831’
Content is referencing a propID that doesn’t exist propId=‘1741449272259281420’
Content is referencing a propID that doesn’t exist propId=‘1729238864970678821’
Content is referencing a propID that doesn’t exist propId=‘1729238864970678820’
Content is referencing a propID that doesn’t exist propId=‘1729238864970678823’
Content is referencing a propID that doesn’t exist propId=‘1741448950136734216’
Content is referencing a propID that doesn’t exist propId=‘1741448950136734219’
Content is referencing a propID that doesn’t exist propId=‘1741449053215949327’
Content is referencing a propID that doesn’t exist propId=‘1741449053215949326’
Texture missing mip chain: 0×0374c7
Texture missing mip chain: 0×0374c9
Texture missing mip chain: 0×01350d
Texture missing mip chain: 0×00c1a9
Texture missing mip chain: 0×00c1ab
Model ‘0×082244’: Failed to resolve AimIK bone indices.

—> DirectX Device Info <—
VendorId = 0×10de
DeviceId = 0×1189
Version = 9.18.0013.3523
Description = NVIDIA GeForce GTX 670
Compat = 0×00100800
VidMem = 3388 MB

#8 - April 28, 2014, 12:55 p.m.
Blizzard Post

Hi there,

You say that your system isn’t overclocked, but do you still have the Turbo Boost feature enabled? This has been known to cause crash issues, particularly in areas such as large cities, events, WvW, etc.

#17 - April 30, 2014, 11:48 a.m.
Blizzard Post

Hi Sendai,

I think that’s exactly what’s going on here. I had saw that you were getting OOM crash errors but I mistook someone else’s comment saying “But I’m on a 64-bit OS” and assumed that was you and so I looked past that and considered other variables. But yes, what abomally is saying is entirely correct.