Memory Address "ffffffff" at "fffffffff" could not be read

[trueanimus.4085]

Any ETA on the memory leak bug affecting the new Domain of Istan map?

 

I get this from time to time with a "serious error has occured" pop up report.

 

It usually says memory address "FFFFFFFF to FFFFFFFF" could not be read and asks me to send a report... done that about 20x in the last few days and nothing.. People are crashing from it in all maps but seems to be the worst in the new map during or right after you call your griffin mount (for me anyway)

[trueanimus.4085]

*--> Crash <--*

Exception: c0000005

Memory at address ffffffff`ffffffff could not be read

App: Gw2-64.exe

Pid: 8288

Cmdline:

BaseAddr: 00007FF7D5210000

ProgramId: 101

Build: 84555

When: 2017-12-04T19:12:45Z 2017-12-04T14:12:45-05:00

Uptime: 0 days 0:42:05

Flags: 0

[PatriotArrow.6320]

I've got the same thing going on once or twice a day depending on how much I play. It just happened in Lion's Arch too.

[Juclesia Elcritian.8410]

Getting the same crash error. Several times a day. It's getting really annoying.

[trueanimus.4085]

yeah im getting it sometimes just as i log in, sometimes it takes a hour or so.. happened in silverwastes as well once and in wvw a few times

 

[trueanimus.4085]

9 mins this morning then poof

 

 

 

*--> Crash <--*

Exception: c0000005

Memory at address ffffffff`ffffffff could not be read

App: Gw2-64.exe

Pid: 8400

Cmdline:

BaseAddr: 00007FF6F5450000

ProgramId: 101

Build: 84555

When: 2017-12-05T14:43:48Z 2017-12-05T09:43:48-05:00

Uptime: 0 days 0:09:43

Flags: 0

 

*--> System <--*

Name: DESKTOP-VT9F79M

IpAddr: 192.168.1.66

Processors: 8 [GenuineIntel:6:14:9]

OSVersion: Windows 10.0 (64 bit)

 

*--> System Memory <--*

Physical: 10981MB/16316MB 67%

Paged: 13342MB/18748MB 71%

Virtual: 134213761MB/134217727MB 3%

Load: 32%

CommitTotal: 5405MB

CommitLimit: 18748MB

CommitPeak: 9645MB

SystemCache: 3799MB

HandleCount: 32423

ProcessCount: 59

ThreadCount: 1122

 

*--> Process Memory <--*

Private: 3597MB

WorkingSet: 3072MB

PeakWorkingSet: 3072MB

PageFaults: 4730897

 

*--> Memory Category Usage (Inclusive) <--*

[Category] [size(MB)] [Count]

Root 1413.84 1240672

VRAM 961.39 19763

Programmer Data 887.95 434391

Engine 479.32 235467

Uncategorized 363.97 734652

Model-Programmer 350.30 63857

VRAM - Prop Tex 325.63 1284

Game 259.97 143031

Content 183.19 50443

VRAM - Character Tex 131.35 458

Collections 105.42 5868

VRAM - Gr Postproc 104.39 22

Dictionary 103.58 2147

Art Assets 97.87 22224

Gr 94.05 135878

Character Models 72.43 3074

Composite Models 69.77 1525

Collide 64.05 49405

Text 62.01 6191

VRAM - Composite Tex 58.31 139

VRAM - Effect Texture 48.94 259

Gr Umbra 47.04 2687

Composite Tex 47.01 96

Composite Tex Pool 46.51 90

 

*--> Memory Category Usage (Exclusive) <--*

[Category] [size(MB)] [Count]

Uncategorized 363.97 734652

Model-Programmer 341.54 39771

VRAM - Prop Tex 325.63 1284

Content 183.19 50443

VRAM - Character Tex 131.35 458

VRAM - Gr Postproc 104.39 22

Dictionary 103.58 2147

Text 62.01 6191

VRAM - Composite Tex 58.31 139

VRAM - Effect Texture 48.94 259

Gr Umbra 47.04 2687

Composite Tex Pool 46.51 90

VRAM - Terrain Tex 43.42 37

VRAM - Prop Geo 38.73 127

VRAM - UI Textures 35.40 1147

Collide 34.51 2014

VRAM - Composite Geo 29.66 97

VRAM - DirectX Geo Buffers 27.17 802

Archive 23.12 106

Composite Packfile 22.63 371

Collide Havok 21.04 46428

VRAM - DDI Shader 20.93 14944

Gr Model 20.32 45757

VRAM - Zone Tex 15.07 63

 

*--> DllList <--*

C:\Guild Wars 2\Gw2-64.exe

C:\Windows\SYSTEM32\ntdll.dll

C:\Windows\System32\KERNEL32.DLL

C:\Windows\System32\KERNELBASE.dll

C:\Windows\System32\USER32.dll

C:\Windows\System32\win32u.dll

C:\Windows\System32\GDI32.dll

C:\Windows\System32\gdi32full.dll

C:\Windows\System32\ADVAPI32.dll

C:\Windows\System32\msvcrt.dll

C:\Windows\System32\sechost.dll

C:\Windows\System32\RPCRT4.dll

C:\Windows\System32\WS2_32.dll

C:\Windows\System32\WINTRUST.dll

C:\Windows\System32\MSASN1.dll

C:\Windows\SYSTEM32\VERSION.dll

C:\Windows\System32\CRYPT32.dll

C:\Windows\SYSTEM32\WTSAPI32.dll

C:\Windows\SYSTEM32\WINMM.dll

C:\Windows\System32\ucrtbase.dll

C:\Windows\System32\PSAPI.DLL

C:\Windows\System32\ole32.dll

C:\Windows\SYSTEM32\WINMMBASE.dll

C:\Windows\System32\combase.dll

C:\Windows\System32\bcryptPrimitives.dll

C:\Windows\System32\OLEAUT32.dll

C:\Windows\System32\msvcp_win.dll

C:\Windows\System32\SHELL32.dll

C:\Windows\System32\cfgmgr32.dll

C:\Windows\System32\windows.storage.dll

C:\Windows\System32\powrprof.dll

C:\Windows\System32\shlwapi.dll

C:\Windows\System32\kernel.appcore.dll

C:\Windows\System32\shcore.dll

C:\Windows\System32\profapi.dll

C:\Windows\SYSTEM32\MSACM32.dll

C:\Windows\WinSxS\amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.14393.1715_none_aec701fbddd850fa\gdiplus.dll

C:\Windows\SYSTEM32\MSIMG32.dll

C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_5.82.14393.447_none_0d5aa7fbb6d35646\COMCTL32.dll

C:\Windows\SYSTEM32\USP10.dll

C:\Windows\SYSTEM32\Secur32.dll

C:\Windows\SYSTEM32\CRYPTBASE.DLL

C:\Windows\SYSTEM32\SSPICLI.DLL

C:\Windows\System32\IMM32.DLL

C:\Windows\SYSTEM32\dbghelp.dll

C:\Windows\system32\uxtheme.dll

C:\Windows\System32\imagehlp.dll

C:\Windows\SYSTEM32\CRYPTSP.dll

C:\Windows\system32\rsaenh.dll

C:\Windows\SYSTEM32\bcrypt.dll

C:\Windows\system32\nvspcap64.dll

C:\Windows\SYSTEM32\ntmarta.dll

C:\Windows\System32\clbcatq.dll

C:\Windows\System32\MSCTF.dll

C:\Windows\system32\dwmapi.dll

C:\Windows\system32\napinsp.dll

C:\Windows\system32\pnrpnsp.dll

C:\Windows\system32\NLAapi.dll

C:\Windows\System32\mswsock.dll

C:\Windows\SYSTEM32\DNSAPI.dll

C:\Windows\System32\NSI.dll

C:\Windows\SYSTEM32\IPHLPAPI.DLL

C:\Windows\System32\winrnr.dll

C:\Windows\System32\fwpuclnt.dll

C:\Windows\System32\rasadhlp.dll

C:\Windows\SYSTEM32\WindowsCodecs.dll

C:\Guild Wars 2\bin64\CoherentUI64.dll

C:\Windows\SYSTEM32\d3d9.dll

C:\Windows\SYSTEM32\gpapi.dll

C:\Windows\System32\cryptnet.dll

C:\Windows\SYSTEM32\WINNSI.DLL

C:\Windows\SYSTEM32\DPAPI.dll

C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_2d65b7647eff8c45\nvldumdx.dll

C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_2d65b7647eff8c45\nvd3dumx.dll

C:\Windows\SYSTEM32\nvapi64.dll

C:\Windows\System32\SETUPAPI.dll

C:\Windows\SYSTEM32\dxgi.dll

C:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvStereoApiI64.dll

C:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvSCPAPI64.dll

C:\Windows\SYSTEM32\DEVOBJ.dll

C:\Windows\SYSTEM32\WINSTA.dll

C:\Windows\System32\MMDevApi.dll

C:\Windows\System32\PROPSYS.dll

C:\Windows\SYSTEM32\wdmaud.drv

C:\Windows\SYSTEM32\ksuser.dll

C:\Windows\SYSTEM32\AVRT.dll

C:\Windows\SYSTEM32\AUDIOSES.DLL

C:\Windows\SYSTEM32\wintypes.dll

C:\Windows\SYSTEM32\msacm32.drv

C:\Windows\SYSTEM32\midimap.dll

C:\Windows\SYSTEM32\mscms.dll

C:\Windows\SYSTEM32\USERENV.dll

C:\Windows\SYSTEM32\icm32.dll

 

[DbgHelp.dll is C:\Windows\SYSTEM32\dbghelp.dll]

[DbgHelp.dll version 10.0.14321.1024 (64/32-bit compatible)]

 

*--> Thread 0x1384 <--*

 

*--> Trace <--*

Pc Rt : Args

00007ff6`f56561be 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000

00007ff6`f565642f 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000

00007ff6`f56a36cf 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000

00007ff6`f56543cf 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000

00007ff6`f565330d 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000

00007ff6`f565555b 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000

00007ff6`f560b531 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000

00007ff6`f5799c09 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000

00007ffd`2b1e8364 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000

00007ffd`2bbb7091 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000

 

*--> Thread registers <--*

rax=0000000000000000 rbx=0000027fa932e3a0 rcx=3dd0e5603dd0e560

rdx=000000846c6ffa08 rsi=000000846c6ffc10 rdi=0000027fa93306f8

rip=00007ff6f56561be rsp=000000846c6ffa10 rbp=000000846c6ffb29

r8=0000000000000001 r9=0000000000000000 r10=000000846c6ff840

r11=000002800ed38e40 r12=0000000000000000 r13=0000000000000000

r14=0000027fa932e3a0 r15=0000000000000000

cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010206

 

rbx-32 0000027FA932E380 00000000`00016280 089fed15`ded757a8 0000027f`a98e4080 00330110`9cc3c260

rbx +0 0000027FA932E3A0 00000000`00000000 00000000`00000000 00100000`00000000 7f9dffd7`00000001

rbx+32 0000027FA932E3C0 00170015`000d228b 000010de`00001c02 00000100`00000008 00000000`00001000

rdx-32 000000846C6FF9E8 00007ffd`15bf802b 0000027f`a98c91e8 0000027f`a98c91e0 00000084`6c6ffc10

rdx +0 000000846C6FFA08 00000001`0000003e 00000001`00000015 ffffffff`fffffffe 0000027f`a98c91e8

rdx+32 000000846C6FFA28 00000438`00000000 00000000`00000001 00007ff6`f565642f 0000027f`a932e3a0

 

*--> Code <--*

00007ff6`f565619e 833f0075 18488b89 98000000 4c8bc7ba .?.u.H......L...

00007ff6`f56561ae 01000000 488b01ff 90d80100 00488b0f ....H........H..

00007ff6`f56561be 488b01ff 5020488d 0d15ccb1 01e8e033 H...P H........3

00007ff6`f56561ce e0ff488b 05f1cbb1 01a80175 4348895c ..H........uCH.\

00007ff6`f56561de 2430488b 1de1cbb1 014885db 742d0f1f $0H......H..t-..

00007ff6`f56561ee 4000488b 43204885 c0740648 8b4b10ff @.H.C H..t.H.K..

 

*--> Stack <--*

00000084`6c6ffa10 00000001`00000015 ffffffff`fffffffe 0000027f`a98c91e8 00000438`00000000 ............................8...

00000084`6c6ffa30 00000000`00000001 00007ff6`f565642f 0000027f`a932e3a0 00000000`00000001 ......../de.......2.............

00000084`6c6ffa50 00000000`00000000 00000438`00000780 00000000`00000000 00007ff6`f56a36cf ............8............6j.....

00000084`6c6ffa70 0000027f`9d9790fc 00000438`00000780 00008109`fdf1c893 00007ffd`15bf80ea ............8...................

00000084`6c6ffa90 00000000`00000000 00000000`00000000 0000027f`a98c91e8 00007ffd`15bb50e0 .........................P......

00000084`6c6ffab0 00000280`0353cea0 00000000`00000000 0000027f`a932e3a0 0000027f`9d979088 ..S...............2.............

00000084`6c6ffad0 00000000`00000000 00007ff6`f565694b 0000027f`a932e3a0 00000000`00000000 ........Kie.......2.............

00000084`6c6ffaf0 0000027f`9d979088 00000000`00002a00 00000000`00000000 00000084`00000000 .........*......................

00000084`6c6ffb10 00000084`6c6ffb28 0000027f`e7db8a10 00000003`00000003 00000000`00000000 (.ol............................

00000084`6c6ffb30 00000000`00000000 00000438`00000780 00000438`00000780 00000000`00000000 ............8.......8...........

00000084`6c6ffb50 00000000`00000000 00007ff6`f56ae322 00000000`00000000 0000ad86`c58e0ba7 ........".j.....................

00000084`6c6ffb70 00000000`00000000 0000027f`9d9790fc 00000000`00000000 00007ff6`f56543cf .........................Ce.....

00000084`6c6ffb90 00000000`00000000 00007ff6`f68eaae8 00007ff6`f5654395 00000000`00000000 .................Ce.............

00000084`6c6ffbb0 00000364`ffba8e70 00000000`00000000 00000000`00000000 0000027f`9cbb4a68 p...d...................hJ......

00000084`6c6ffbd0 0000027f`9d9790fc 00007ff6`f565330d 0000027f`9cbb6690 00000000`000001fc .........3e......f..............

00000084`6c6ffbf0 00000000`00000000 00000000`00000000 00000000`00000002 00007ff6`f565555b ........................[ue.....

00000084`6c6ffc10 0000027f`000001fc 0000027f`9cbb6690 0000027f`9cbb4a68 00000084`6c6ffc10 .........f......hJ........ol....

00000084`6c6ffc30 0000027f`9cbb4a60 00007ff6`f560b531 00000000`000001fc 00000000`00000001 `J......1.`.....................

00000084`6c6ffc50 00000000`00000000 00000000`00000005 00007ff6`f560b4c0 00007ff6`f5799c09 ..................`.......y.....

00000084`6c6ffc70 0000027f`00000000 0000027f`9cbb4a60 00000000`00000000 00000000`00000000 ........`J......................

00000084`6c6ffc90 00000000`00000000 00007ffd`2b1e8364 00000000`00000000 00000000`00000000 ........d..+....................

00000084`6c6ffcb0 00000000`00000000 00000000`00000000 00000000`00000000 00007ffd`2bbb7091 .........................p.+....

00000084`6c6ffcd0 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 ................................

00000084`6c6ffcf0 00000000`00000000 00007ffd`28aa4e20 00000084`6c6feb10 00000084`6c6feb10 ........ N.(......ol......ol....

00000084`6c6ffd10 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 ................................

00000084`6c6ffd30 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 ................................

00000084`6c6ffd50 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 ................................

00000084`6c6ffd70 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 ................................

00000084`6c6ffd90 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 ................................

00000084`6c6ffdb0 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 ................................

00000084`6c6ffdd0 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 ................................

00000084`6c6ffdf0 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 ................................

 

*--> Error Logs <--*

effect for skill 'wR9sL.ed+kg'

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

Model '0x080b24': Failed to resolve AimIK bone indices.

Texture missing mip chain: 0x1af5db

Texture '0x03539b' dimensions too small

Loading '0x03539b' texture failed

Model '0x082241': Failed to resolve AimIK bone indices.

Model '0x1ab532': Failed to resolve AimIK bone indices.

Model '0x1ab532': Failed to resolve AimIK bone indices.

Model '0x1ab532': Failed to resolve AimIK bone indices.

Model '0x1ab532': Failed to resolve AimIK bone indices.

Model '0x1ab532': Failed to resolve AimIK bone indices.

Model '0x08223f': Failed to resolve AimIK bone indices.

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

Model '0x1ab532': Failed to resolve AimIK bone indices.

Model '0x080b24': Failed to resolve AimIK bone indices.

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

Model '0x1ab532': Failed to resolve AimIK bone indices.

Model '0x080b24': Failed to resolve AimIK bone indices.

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

Model '0x1ab532': Failed to resolve AimIK bone indices.

Model '0x1ab532': Failed to resolve AimIK bone indices.

Model '0x1ab532': Failed to resolve AimIK bone indices.

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

Model '0x1ab532': Failed to resolve AimIK bone indices.

Model '0x1ab532': Failed to resolve AimIK bone indices.

Model '0x1ab532': Failed to resolve AimIK bone indices.

Model '0x1ab532': Failed to resolve AimIK bone indices.

Model '0x1ab532': Failed to resolve AimIK bone indices.

Model '0x1ab532': Failed to resolve AimIK bone indices.

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

Model '0x08223f': Failed to resolve AimIK bone indices.

Model '0x080b24': Failed to resolve AimIK bone indices.

Model '0x1ab532': Failed to resolve AimIK bone indices.

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

Debug token '0x00000000000266FA': Lightning ran out of space for new bolts.

Model '0x080b24': Failed to resolve AimIK bone indices.

 

*--> DirectX Device Info <--*

VendorId = 0x10de

DeviceId = 0x1c02

Version = 23.21.0013.8843

Description = NVIDIA GeForce GTX 1060 3GB

Compat = 0x00100000

VidMem = 3072 MB

 

 

 

[trueanimus.4085]

guessing they are on vacation... no fix yet and no reply

[MariaGuess.4103]

same problem here, the game crash and the error message "Memory at address ffffffff`ffffffff could not be read" appear. For the moment for me its at Istan mostly during the Paladawan meta

[Vulpes Cohort.4823]

Besides the upmentioned error, since i came back with the PoF expansion, gw2 gave me a lot of freezes in highly populated areas. I never had any problems with gw2 before.

[trueanimus.4085]

> @"Vulpes Cohort.4823" said:

> Besides the upmentioned error, since i came back with the PoF expansion, gw2 gave me a lot of freezes in highly populated areas. I never had any problems with gw2 before.

 

Yeah .. i have to admit since the last patch, i have been getting a lot of FPS lag sometimes, even though i am on a brand new high end i7700 system.

 

It will start fps skipping while im moving or running, then if i stop for a second and stand still.. it goes away. My ping usually isnt effected and it only seems to temporarily effect my fps.. however with the crash we are getting, im wondering if its just side effects from that crash sitting in memory.

[Trall.4150]

This issue started occuring for me after halloween update came. Happens daily and regardless of what I do I am unable to fix it. It happens in Lion's Arch and Verdant Brink (atleast from the maps I have noticed so far). I have contacted the support but that wasn't exactly helpfull.

[Ethan Warner.1829]

I've been having the same issue. Is it just a memory leak in the new map? I used to get a similar crash in the Silverwastes a few months back as well.

[linamaria.1830]

In my opinion, this post in other thread, has a solid clue about what is happening:

 

> @"darksome.1697" said:

> Add me to the list of people suffering this freezing and crashing issue since after Halloween. Played the game flawlessly for a year before that on the same system i7 6700K, 32GB, Win10 Home, nVidia GTX 1080.

>

> - I've crashed just like others have described, where the whole game freezes and there's nothing to do but to ctrl-alt-del and sign out to make W10 kill the game.

> - I've also experienced it mostly in heavily populated areas, and usually where a lot of people are mounting up (tequatl, karka queen, ls4 zone etc).

> - It started with just a few crashes a week initially, growing worse with time, and today I had three crashes in less than two hours.

>

> **I'm also suspecting the new mount skins, the more people getting these "hollow star filled" birds everyone is after (can't remember the name) and the other "special" ones, the more crashes. If you've been playing Gw2 for some time, you may remember a skin added to the gem store a few years ago that made everyone crash if they looked at it. Along with the bone errors and the game trying to read memory at ffff ffff, it sure does look like something that's Gw2-related, not Windows 10 / nvidia driver related.**

>

> Any chance we can get a response from Anet on this?

> It's been going on for a fair while now and like someone said, it's disheartening to logon when you know you're going to crash.

 

For me it does make sense, because this "Memory at address ffffffff`ffffffff could not be read" crash started about at the same time when the new mounts skins were released. That time not so many people had the bugged skin(s), so the crash was happening only for a few people, mostly when in high populated events (Silverwastes, HoT metas, Teq, etc.). With time, more people probably got the affected mount skin, so it is logic that more people will start to have that crash regardless the map. Basically where there are many people concentrated with mounts = higher the chance of that crash.

 

Anyways, even if a new mount is not the cause of the crashes, more people are complaining about the same crash log error, so hopefully Anet will check it sooner and comes with a fix.

 

[darksome.1697]

Thanks for reposting @"linamaria.1830". And yeah we have a thread going in the technical bug forum about the same thing over there:

https://en-forum.guildwars2.com/discussion/15804/extremely-frustrating-freezes-and-crashing

 

[atheria.2837]

> @"trueanimus.4085" said:

> Any ETA on the memory leak bug affecting the new Domain of Istan map?

>

> I get this from time to time with a "serious error has occured" pop up report.

>

> It usually says memory address "FFFFFFFF to FFFFFFFF" could not be read and asks me to send a report... done that about 20x in the last few days and nothing.. People are crashing from it in all maps but seems to be the worst in the new map during or right after you call your griffin mount (for me anyway)

 

The memory leak is insane.

 

I can watch it after I start the game and it never ends until I crash.

 

Why the memory leak???

 

Anet???

[trueanimus.4085]

Was just looking at the crash log i posted... this should tell them everything they need to know to fix it... BUT... no dev reply yet at all on any of the threads

 

 

-> Error Logs <--

effect for skill 'wR9sL.ed+kg'

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

Model '0x080b24': Failed to resolve AimIK bone indices.

Texture missing mip chain: 0x1af5db

Texture '0x03539b' dimensions too small

Loading '0x03539b' texture failed

Model '0x082241': Failed to resolve AimIK bone indices.

Model '0x1ab532': Failed to resolve AimIK bone indices.

Model '0x1ab532': Failed to resolve AimIK bone indices.

Model '0x1ab532': Failed to resolve AimIK bone indices.

Model '0x1ab532': Failed to resolve AimIK bone indices.

Model '0x1ab532': Failed to resolve AimIK bone indices.

Model '0x08223f': Failed to resolve AimIK bone indices.

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

Model '0x1ab532': Failed to resolve AimIK bone indices.

Model '0x080b24': Failed to resolve AimIK bone indices.

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

Model '0x1ab532': Failed to resolve AimIK bone indices.

Model '0x080b24': Failed to resolve AimIK bone indices.

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

Model '0x1ab532': Failed to resolve AimIK bone indices.

Model '0x1ab532': Failed to resolve AimIK bone indices.

Model '0x1ab532': Failed to resolve AimIK bone indices.

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

Model '0x1ab532': Failed to resolve AimIK bone indices.

Model '0x1ab532': Failed to resolve AimIK bone indices.

Model '0x1ab532': Failed to resolve AimIK bone indices.

Model '0x1ab532': Failed to resolve AimIK bone indices.

Model '0x1ab532': Failed to resolve AimIK bone indices.

Model '0x1ab532': Failed to resolve AimIK bone indices.

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

Model '0x08223f': Failed to resolve AimIK bone indices.

Model '0x080b24': Failed to resolve AimIK bone indices.

Model '0x1ab532': Failed to resolve AimIK bone indices.

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

Debug token '0x00000000000266FA': Lightning ran out of space for new bolts.

Model '0x080b24': Failed to resolve AimIK bone indices.

 

--> DirectX Device Info <--

VendorId = 0x10de

DeviceId = 0x1c02

Version = 23.21.0013.8843

Description = NVIDIA GeForce GTX 1060 3GB

Compat = 0x00100000

VidMem = 3072 MB

[trueanimus.4085]

im a necro so im guessing that the Debug token '0x00000000000266FA': Lightning ran out of space for new bolts. is a model light issue that causing the crash??

[Inculpatus cedo.9234]

For an individualized response, you can contact the Tech CS Team via the 'Support' link above/below.

 

Good luck.

[linamaria.1830]

Try to set Character Model Limit: Lowest.

 

Every time i'm going to run a meta event or just stand in high populated zones, i do it. So far it is working.

 

I know it is not convenient and kinda annoying to limit our game based on a not our's fault problem. But yeah, we are all in Anet's hands...

[RoughDraft.9514]

I've been having the same problem in the silverwastes and istan since the 28th. I've tried -repair to no avail.

[Greyling.4768]

I've been having this same issue a few times per week since Halloween. I haven't noticed that it is linked to multiple mount skins or players in my vicinity, though. It just happened again about 10 minutes ago and I was not on a mount and was not anywhere near a populated area. I set Player Model Limit to Lowest last week in an attempt to slow the crashes, but it hasn't had any impact on frequency.

[Undertow.2389]

I don't think it (this specific Exception: c0000005 crash that started right after Halloween) necessarily depends on memory leaks or mount model counts. I had the crash today in the middle of Fields of Ruin, with relatively no one around, after ~14 minutes of game play. Old world core Tyria, using only ~2.4 GB of ram at the time. My last crash was in Snowden Drifts with relatively no one around. And yet I've done about a few dozen Auric basin, tangled depths, and dragon stand metas now without a crash. This is with model count limit set to "Low" and model quality set to "Medium"

 

*--> Crash <--*

Exception: c0000005

Memory at address ffffffff`ffffffff could not be read

App: Gw2-64.exe

Pid: 2096

Cmdline:

BaseAddr: 000000013F400000

ProgramId: 101

Build: 84555

When: 2017-12-11T21:01:57Z 2017-12-11T13:01:57-08:00

Uptime: 0 days 0:14:41

Flags: 0

 

*--> System <--*

Name: PC-2013

IpAddr: 192.168.0.3

Processors: 4 [GenuineIntel:6:12:3]

OSVersion: Windows 6.1 (64 bit)

 

*--> System Memory <--*

Physical: 3298MB/ 8143MB 40%

Paged: 11382MB/16285MB 69%

Virtual: 8385664MB/8388607MB 99%

Load: 59%

CommitTotal: 4902MB

CommitLimit: 16285MB

CommitPeak: 7186MB

SystemCache: 4046MB

HandleCount: 19154

ProcessCount: 54

ThreadCount: 779

 

*--> Process Memory <--*

Private: 2505MB

WorkingSet: 2443MB

PeakWorkingSet: 2674MB

PageFaults: 5082729

 

*--> Error Logs <--*

mIK bone indices.

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

Texture missing mip chain: 0x014655

Texture missing mip chain: 0x014657

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

Content is referencing a propID that doesn't exist propId='1182152709399184385'

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

Map load hang on STATE_MODELS_STREAM detected: MapId: 18, Position: (3167.820068, -1375.329956, -5410.100098), Completion: 0.000000

Model '0x080b24': Failed to resolve AimIK bone indices.

Texture '0x191b0e' dimensions too small

Loading '0x191b0e' texture failed

Texture '0x191b0f' dimensions too small

Loading '0x191b0f' texture failed

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

Texture missing mip chain: 0x014655

Texture missing mip chain: 0x014657

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

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

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

Texture missing mip chain: 0x093493

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

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

Model '0x080b24': Failed to resolve AimIK bone indices.

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

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

Content is referencing a propID that doesn't exist propId='1260912513885734329'

Content is referencing a propID that doesn't exist propId='1316091261102392334'

Content is referencing a propID that doesn't exist propId='1316086798631371785'

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

Model '0x080b24': Failed to resolve AimIK bone indices.

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

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

Debug token '0x00000000000266FA': Lightning ran out of space for new bolts.

Texture missing mip chain: 0x011f2e

Texture missing mip chain: 0x011f30

Model '0x080b24': Failed to resolve AimIK bone indices.

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

[atheria.2837]

I have had three major crashes that look amazingly like the above.

[Undertow.2389]

Also, I first started getting this crash (and had zero crashes for the 3-4 weeks I played before) right after a build update on Friday, November 3rd. It was memorable because GW2 had never been unstable before. The new mount skins weren't released until Tuesday, November 7th.

[Ray Koopa.2354]

@trueanimus.4085 Are you running in Windowed Fullscreen and on Windows 10 Fall Creators Update? the fps drops you randomly get are related to the most recent win10 update. run in real fullscreen to fix those or downgrade to the previous win10 version while you still can.

 

the error log just shows typical bugged resource stuff, I don't remember something like that not being there, lol