Jump to content
  • Sign Up

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


Recommended Posts

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)

Link to comment
Share on other sites

  • Replies 66
  • Created
  • Last Reply

Top Posters In This Topic

9 mins this morning then poof

--> Crash <--Exception: c0000005
Memory at address ffffffff`ffffffff could not be readApp: Gw2-64.exePid: 8400Cmdline:BaseAddr: 00007FF6F5450000ProgramId: 101Build: 84555When: 2017-12-05T14:43:48Z 2017-12-05T09:43:48-05:00Uptime: 0 days 0:09:43Flags: 0

--> System <--Name: DESKTOP-VT9F79MIpAddr: 192.168.1.66Processors: 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: 5405MBCommitLimit: 18748MBCommitPeak: 9645MBSystemCache: 3799MBHandleCount: 32423ProcessCount: 59ThreadCount: 1122

--> Process Memory <--Private: 3597MBWorkingSet: 3072MBPeakWorkingSet: 3072MBPageFaults: 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.exeC:\Windows\SYSTEM32\ntdll.dllC:\Windows\System32\KERNEL32.DLLC:\Windows\System32\KERNELBASE.dllC:\Windows\System32\USER32.dllC:\Windows\System32\win32u.dllC:\Windows\System32\GDI32.dllC:\Windows\System32\gdi32full.dllC:\Windows\System32\ADVAPI32.dllC:\Windows\System32\msvcrt.dllC:\Windows\System32\sechost.dllC:\Windows\System32\RPCRT4.dllC:\Windows\System32\WS2_32.dllC:\Windows\System32\WINTRUST.dllC:\Windows\System32\MSASN1.dllC:\Windows\SYSTEM32\VERSION.dllC:\Windows\System32\CRYPT32.dllC:\Windows\SYSTEM32\WTSAPI32.dllC:\Windows\SYSTEM32\WINMM.dllC:\Windows\System32\ucrtbase.dllC:\Windows\System32\PSAPI.DLLC:\Windows\System32\ole32.dllC:\Windows\SYSTEM32\WINMMBASE.dllC:\Windows\System32\combase.dllC:\Windows\System32\bcryptPrimitives.dllC:\Windows\System32\OLEAUT32.dllC:\Windows\System32\msvcp_win.dllC:\Windows\System32\SHELL32.dllC:\Windows\System32\cfgmgr32.dllC:\Windows\System32\windows.storage.dllC:\Windows\System32\powrprof.dllC:\Windows\System32\shlwapi.dllC:\Windows\System32\kernel.appcore.dllC:\Windows\System32\shcore.dllC:\Windows\System32\profapi.dllC:\Windows\SYSTEM32\MSACM32.dllC:\Windows\WinSxS\amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.14393.1715_none_aec701fbddd850fa\gdiplus.dllC:\Windows\SYSTEM32\MSIMG32.dllC:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_5.82.14393.447_none_0d5aa7fbb6d35646\COMCTL32.dllC:\Windows\SYSTEM32\USP10.dllC:\Windows\SYSTEM32\Secur32.dllC:\Windows\SYSTEM32\CRYPTBASE.DLLC:\Windows\SYSTEM32\SSPICLI.DLLC:\Windows\System32\IMM32.DLLC:\Windows\SYSTEM32\dbghelp.dllC:\Windows\system32\uxtheme.dllC:\Windows\System32\imagehlp.dllC:\Windows\SYSTEM32\CRYPTSP.dllC:\Windows\system32\rsaenh.dllC:\Windows\SYSTEM32\bcrypt.dllC:\Windows\system32\nvspcap64.dllC:\Windows\SYSTEM32\ntmarta.dllC:\Windows\System32\clbcatq.dllC:\Windows\System32\MSCTF.dllC:\Windows\system32\dwmapi.dllC:\Windows\system32\napinsp.dllC:\Windows\system32\pnrpnsp.dllC:\Windows\system32\NLAapi.dllC:\Windows\System32\mswsock.dllC:\Windows\SYSTEM32\DNSAPI.dllC:\Windows\System32\NSI.dllC:\Windows\SYSTEM32\IPHLPAPI.DLLC:\Windows\System32\winrnr.dllC:\Windows\System32\fwpuclnt.dllC:\Windows\System32\rasadhlp.dllC:\Windows\SYSTEM32\WindowsCodecs.dllC:\Guild Wars 2\bin64\CoherentUI64.dllC:\Windows\SYSTEM32\d3d9.dllC:\Windows\SYSTEM32\gpapi.dllC:\Windows\System32\cryptnet.dllC:\Windows\SYSTEM32\WINNSI.DLLC:\Windows\SYSTEM32\DPAPI.dllC:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_2d65b7647eff8c45\nvldumdx.dllC:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_2d65b7647eff8c45\nvd3dumx.dllC:\Windows\SYSTEM32\nvapi64.dllC:\Windows\System32\SETUPAPI.dllC:\Windows\SYSTEM32\dxgi.dllC:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvStereoApiI64.dllC:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvSCPAPI64.dllC:\Windows\SYSTEM32\DEVOBJ.dllC:\Windows\SYSTEM32\WINSTA.dllC:\Windows\System32\MMDevApi.dllC:\Windows\System32\PROPSYS.dllC:\Windows\SYSTEM32\wdmaud.drvC:\Windows\SYSTEM32\ksuser.dllC:\Windows\SYSTEM32\AVRT.dllC:\Windows\SYSTEM32\AUDIOSES.DLLC:\Windows\SYSTEM32\wintypes.dllC:\Windows\SYSTEM32\msacm32.drvC:\Windows\SYSTEM32\midimap.dllC:\Windows\SYSTEM32\mscms.dllC:\Windows\SYSTEM32\USERENV.dllC:\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 : Args00007ff6f56561be 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 000000000000000000007ff6f565642f 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 000000000000000000007ff6f56a36cf 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 000000000000000000007ff6f56543cf 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 000000000000000000007ff6f565330d 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 000000000000000000007ff6f565555b 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 000000000000000000007ff6f560b531 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 000000000000000000007ff6f5799c09 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 000000000000000000007ffd2b1e8364 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 000000000000000000007ffd2bbb7091 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000

--> Thread registers <--rax=0000000000000000 rbx=0000027fa932e3a0 rcx=3dd0e5603dd0e560rdx=000000846c6ffa08 rsi=000000846c6ffc10 rdi=0000027fa93306f8rip=00007ff6f56561be rsp=000000846c6ffa10 rbp=000000846c6ffb29r8=0000000000000001 r9=0000000000000000 r10=000000846c6ff840r11=000002800ed38e40 r12=0000000000000000 r13=0000000000000000r14=0000027fa932e3a0 r15=0000000000000000cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010206

rbx-32 0000027FA932E380 0000000000016280 089fed15ded757a8 0000027fa98e4080 003301109cc3c260rbx +0 0000027FA932E3A0 0000000000000000 0000000000000000 0010000000000000 7f9dffd700000001rbx+32 0000027FA932E3C0 00170015000d228b 000010de00001c02 0000010000000008 0000000000001000rdx-32 000000846C6FF9E8 00007ffd15bf802b 0000027fa98c91e8 0000027fa98c91e0 000000846c6ffc10rdx +0 000000846C6FFA08 000000010000003e 0000000100000015 fffffffffffffffe 0000027fa98c91e8rdx+32 000000846C6FFA28 0000043800000000 0000000000000001 00007ff6f565642f 0000027fa932e3a0

--> Code <--00007ff6f565619e 833f0075 18488b89 98000000 4c8bc7ba .?.u.H......L... 00007ff6f56561ae 01000000 488b01ff 90d80100 00488b0f ....H........H..00007ff6f56561be 488b01ff 5020488d 0d15ccb1 01e8e033 H...P H........3 00007ff6f56561ce e0ff488b 05f1cbb1 01a80175 4348895c ..H........uCH.\00007ff6f56561de 2430488b 1de1cbb1 014885db 742d0f1f $0H......H..t-.. 00007ff6f56561ee 4000488b 43204885 c0740648 8b4b10ff @.H.C H..t.H.K..

--> Stack <--000000846c6ffa10 0000000100000015 fffffffffffffffe 0000027fa98c91e8 0000043800000000 ............................8... 000000846c6ffa30 0000000000000001 00007ff6f565642f 0000027fa932e3a0 0000000000000001 ......../de.......2.............000000846c6ffa50 0000000000000000 0000043800000780 0000000000000000 00007ff6f56a36cf ............8............6j..... 000000846c6ffa70 0000027f9d9790fc 0000043800000780 00008109fdf1c893 00007ffd15bf80ea ............8...................000000846c6ffa90 0000000000000000 0000000000000000 0000027fa98c91e8 00007ffd15bb50e0 .........................P...... 000000846c6ffab0 000002800353cea0 0000000000000000 0000027fa932e3a0 0000027f9d979088 ..S...............2.............000000846c6ffad0 0000000000000000 00007ff6f565694b 0000027fa932e3a0 0000000000000000 ........Kie.......2............. 000000846c6ffaf0 0000027f9d979088 0000000000002a00 0000000000000000 0000008400000000 .........*......................000000846c6ffb10 000000846c6ffb28 0000027fe7db8a10 0000000300000003 0000000000000000 (.ol............................ 000000846c6ffb30 0000000000000000 0000043800000780 0000043800000780 0000000000000000 ............8.......8...........000000846c6ffb50 0000000000000000 00007ff6f56ae322 0000000000000000 0000ad86c58e0ba7 ........".j..................... 000000846c6ffb70 0000000000000000 0000027f9d9790fc 0000000000000000 00007ff6f56543cf .........................Ce.....000000846c6ffb90 0000000000000000 00007ff6f68eaae8 00007ff6f5654395 0000000000000000 .................Ce............. 000000846c6ffbb0 00000364ffba8e70 0000000000000000 0000000000000000 0000027f9cbb4a68 p...d...................hJ......000000846c6ffbd0 0000027f9d9790fc 00007ff6f565330d 0000027f9cbb6690 00000000000001fc .........3e......f.............. 000000846c6ffbf0 0000000000000000 0000000000000000 0000000000000002 00007ff6f565555b ........................[ue.....000000846c6ffc10 0000027f000001fc 0000027f9cbb6690 0000027f9cbb4a68 000000846c6ffc10 .........f......hJ........ol.... 000000846c6ffc30 0000027f9cbb4a60 00007ff6f560b531 00000000000001fc 0000000000000001 J......1......................000000846c6ffc50 0000000000000000 0000000000000005 00007ff6f560b4c0 00007ff6f5799c09 .........................y.....000000846c6ffc70 0000027f00000000 0000027f9cbb4a60 0000000000000000 0000000000000000 ........J......................000000846c6ffc90 0000000000000000 00007ffd2b1e8364 0000000000000000 0000000000000000 ........d..+.................... 000000846c6ffcb0 0000000000000000 0000000000000000 0000000000000000 00007ffd2bbb7091 .........................p.+....000000846c6ffcd0 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................ 000000846c6ffcf0 0000000000000000 00007ffd28aa4e20 000000846c6feb10 000000846c6feb10 ........ N.(......ol......ol....000000846c6ffd10 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................ 000000846c6ffd30 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................000000846c6ffd50 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................ 000000846c6ffd70 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................000000846c6ffd90 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................ 000000846c6ffdb0 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................000000846c6ffdd0 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................ 000000846c6ffdf0 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................

--> 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: 0x1af5dbTexture '0x03539b' dimensions too smallLoading '0x03539b' texture failedModel '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 = 0x10deDeviceId = 0x1c02Version = 23.21.0013.8843Description = NVIDIA GeForce GTX 1060 3GBCompat = 0x00100000VidMem = 3072 MB

Link to comment
Share on other sites

@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.

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

@"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???

Link to comment
Share on other sites

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: 0x1af5dbTexture '0x03539b' dimensions too smallLoading '0x03539b' texture failedModel '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 = 0x10deDeviceId = 0x1c02Version = 23.21.0013.8843Description = NVIDIA GeForce GTX 1060 3GBCompat = 0x00100000VidMem = 3072 MB

Link to comment
Share on other sites

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...

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

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 readApp: Gw2-64.exePid: 2096Cmdline:BaseAddr: 000000013F400000ProgramId: 101Build: 84555When: 2017-12-11T21:01:57Z 2017-12-11T13:01:57-08:00Uptime: 0 days 0:14:41Flags: 0

--> System <--Name: PC-2013IpAddr: 192.168.0.3Processors: 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: 4902MBCommitLimit: 16285MBCommitPeak: 7186MBSystemCache: 4046MBHandleCount: 19154ProcessCount: 54ThreadCount: 779

--> Process Memory <--Private: 2505MBWorkingSet: 2443MBPeakWorkingSet: 2674MBPageFaults: 5082729

--> Error Logs <--mIK bone indices.Model '0x08223a': Failed to resolve AimIK bone indices.Texture missing mip chain: 0x014655Texture missing mip chain: 0x014657Model '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.000000Model '0x080b24': Failed to resolve AimIK bone indices.Texture '0x191b0e' dimensions too smallLoading '0x191b0e' texture failedTexture '0x191b0f' dimensions too smallLoading '0x191b0f' texture failedModel '0x082239': Failed to resolve AimIK bone indices.Texture missing mip chain: 0x014655Texture missing mip chain: 0x014657Model '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: 0x093493Model '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: 0x011f2eTexture missing mip chain: 0x011f30Model '0x080b24': Failed to resolve AimIK bone indices.Model '0x08223a': Failed to resolve AimIK bone indices.

Link to comment
Share on other sites

@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

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...