Guild Wars 2

Beredol.3705:

Got 100% skill points, elite specialization is unlock, but cannot select or use…..

Try the bottom slot with the fancy border.

OOM crashes are not as frequent and now largely limited to HoT maps, but still happening. Usually can go 1 hr, 30 mins about before it happens.

OGDeadHead.8326:

Kylden Ar.3724:

While I will have a new 64-bit rig around late December probably, not everyone in that boat can do that.

If your game is capable of running GW2, it should also be able to go 64 bit, considering the minimum requirements of the game when it comes to the cpu are all able to run 64 bit:

Intel® Core 2 Duo 2.0 GHz, Core i3 OR AMD Athlon 64 X2, or better

Please also note: “Due to potential changes, system requirements may change over time and you may be required to upgrade your current system (or obtain a new system) to continue to play the game.”

I love how all these armchair IT ‘experts’ assume I didn’t already try all this stuff, and also apparently don’t read all the words —

Kylden Ar.3724:

While the processor is 64-bit able, and I could take an ISO and use the original 32-bit license key on this to make the Win 10 I currently have 64-bit, in theory, it doesn’t work. Tried. I assume as it’s the only original part left that matters the limitation is the motherboard.

So, you tell me how I’m supposed to install a 64-bit Windows when it keeps telling me the hardware is not compatible?

Johan Skold.4708:

Feniks.6842:

Question: is this FAQ the official response to people crashing with OoM errors?
More specifically: is Anet’s response to the OoM crashes “it’s your client + os”, or is Anet admitting that something changed significantly with HoT with regards to memory-usage?

This is the initial solution (though it’s been in the works for quite some time). Something did indeed change with HoT memory-wise though: Mainly, the new features require more of it, to the point where the extra usage causes a lot of pressure that wasn’t there before. It’s getting increasingly difficult to stay within the limited address space (not necessarily memory constraints) of 32-bit processes.

That said, we’re still dedicated to supporting the 32-bit client for as long as necessary. Necessary fixes for it will take a bit longer to develop however.

That’s good to know. I only recently entered middle class income and am still hesitant to spend more than $20 on anything not my house. While I will have a new 64-bit rig around late December probably, not everyone in that boat can do that.

Do we have any idea on a time-frame, or is the testing/debugging still too early for that?

At least you can try the 64-bit client. Those of us waiting on bonus and/or taxes to upgrade to a 64-bit system are pretty much boned.

autopsie.6159:

Are the people running 32 bit client just screwed?

Is Anet planning actually fix the 32 bit client or do they intend to drop any and all support for it? (as it seems they dont support it now from the response i got from the support team)

In short, yes. Of course, they prevented these errors in beta by limiting it, so that we would not see in the pre-purchase and not return it and demand a refund.

I will never buy another Gem or Pre-purchase again from ANet.

And the PCMasterRacists won’t help.

And people wonder why consoles even have a market… Crap like this is why.

Kylden Ar.3724:

Not sure why/if it was related, but since Halloween ended, I only get OOM Crashes in the new HoT maps and much less occasionally in the Borderlands.

Idea – I noticed that I can last longer in a HoT map if I reset the Field of View and camera options to default, then bring field of view in a bit tighter. The new maps are huge and layered. Maybe a checkbox to further limit draw distance (cheat and use the old Silent Hill fog idea) will give more stability to lower end machines? It’s a jungle. It can be misty, right?

Spoke too soon. Had a crash switching between two characters in core maps.

Aneko.2534:

Daralii.8940:

Aneko.2534:

Hello,
I’m not sure if it’s just me or if others are experiencing this. But I’m noticing on my asura revenant that when I dodge/evade an attack, my character occasionally drops a bomb. Also, my revenant seems to be missing the racial abilities that my other asuran characters have. I don’t really use them much(took me this long to realize I didn’t have them) but I hadn’t heard anyone else mention it so I thought I would bring it up.

Revenants not having racial skills is intended.

Thank you for clearing that up. So then am I the only one whose character drops bombs whenever I dodge an attack or get stunned?

What runes are you using? Maybe Superior Rune of the Citadel?

Not sure why/if it was related, but since Halloween ended, I only get OOM Crashes in the new HoT maps and much less occasionally in the Borderlands.

Idea – I noticed that I can last longer in a HoT map if I reset the Field of View and camera options to default, then bring field of view in a bit tighter. The new maps are huge and layered. Maybe a checkbox to further limit draw distance (cheat and use the old Silent Hill fog idea) will give more stability to lower end machines? It’s a jungle. It can be misty, right?

As expected, still getting OOM errors on 32-bit. Could hope that there was help.

Colin posted on a reddit thread that a x64 client beta is coming today. Won’t help those of us on budget PC’s (stupid mortgage and feeding kids) but those with 64-bit machines should be happy…

Still crashing, but got +10 FPS and the crashes to take 40-60 mins before happening last night by sliding FOV, horizintal postion near and far all the way to the left.

The world looks small and cloister phobic that way, and it looks like I move so slow. Please fix OOM or give official revisions to minimum specs soon.

Still crashing, but got +10 FPS and the crashes to take 40-60 mins before happening last night by sliding FOV, horizintal postion near and far all the way to the left.

The world looks small and cloister phobic that way, and it looks like I move so slow. Please fix OOM or give official revisions to minimum specs soon.

Celtic Lady.3729:

Vayne.8563:

The public has a short, short memory.

Depends on the subject matter. Sometimes the public has a long memory. They don’t like it when that happens, either.

I still remember the manifesto.

Will we get a batch of bug and client fixes with this change?

Bosco.2680:

1. Constant crashes during large events, namely Octovine and Mouth of Mordremoth. You put a two hour event into an unstable expansion, and when you crash (and you will), there’s no way to get back in. You miss out on loot and two hours of work.

2. Missing world completion rewards. You put these pretty neat new maps in, make them difficult to explore (in a good way) and then don’t reward players when they go through the trouble to 100% them.

3. Verdant Brink hero point still bugged. I go there daily, hoping it’d be fixed. But then I remind myself: what’s the point? It’s not like I get anything for completing the map.

Add to these three your inability to communicate yourselves out of a paper bag and we’ve got one of the worst expansion launches in memory. And then, with a straight face, you pretend it’s all right.

You don’t deserve my money. You deserve a host of debilitating diseases.

While I disagree with the anger and tone, I agree with the content.

It’s time they tell us if and when they will fix these issues. If they are not, we might as well uninstall and move on.

Sheobix.8796:

Azumi.9572:

Crashing like crazy in Auric Basin. Every Meta Event, spending hours building it up and then – boom – crash right at the climax. Game built around staying logged in for Map Progression and increased rewards – and you release it in this state?

I’m not even laughing. I’m legitimately angry.

If you have 32 bit Windows, this can be an issue.

Wrong. False. Misleading.

In these 51 pages there are many cases of crashes with 64-bit machines.

Thank you, come again.

Well, this will put to rest the suspecion I have that bad mapping of Halloween assets from old LA to New LA is contributing to the oom leaks.

FYI folks, I tested last night, a real tight field of view gives 10 fps and seems to stop the oom crash, at least thru one whole Tarir defense.

Just for HoTs and giggles, I took out the added video card, and used the original onboard ATI Radeon HD 3200 as one last test with Win10.

As expected, CRASH! and an official FPS of ‘Tuber’.

Kylden Ar.3724:

And still crashing after Windows 10 update…

So, I basically don’t get to play till after the new year when I use taxes or bonus to get a new 64-bit rig… except OOM is hitting 64-bit machines as well. Golden.

So, I tried Supports ‘idea’ of removing a GB of RAM. Still crashed. Was stable for almost an hour though, as opposed to 5-15 minutes.

So, yeah. I’m gonna go put my RAM back in.

And still crashing after Windows 10 update…

So, I basically don’t get to play till after the new year when I use taxes or bonus to get a new 64-bit rig… except OOM is hiting 64-bit machines as well. Golden.

Per Lauren’s request, I opened a ticket and got the same response as many. Below is my response. Emphasis added to some parts.

Sent: Saturday, October 31, 2015 12:55 PM
To: ‘Guild Wars 2 Support’
Subject: RE: [Guild Wars 2 Support] Re: Constant OOM Crashes

Hello Shiro (I use that legend a lot when it’s not crashing on me)—

Few points I’d like to address.

1) I never had this problem before Heart of Thorns, and I did Teaquatl and WvW almost daily.
2) Simple Math. 3 GB is 3072, from the crash report (and knowing my hardware) the GeFroce 210 is “VidMem = 1024 MB” which means 4096 total, the max addressable in a 32-bit system. And if you read the entire log file, you will see that I tried a few times in MSConfig to lower my usable RAM to 2GB, and still had the crashes.
3) This is the same ‘try a 64-bit system’ scripted result ANet has given numerous people on the forums. https://forum-en.gw2archive.eu/forum/support/support/Client-Crashing-constantly-1/page/2#post5665628 But even just this morning another person with a 64-bit system has reported this same issue. https://forum-en.gw2archive.eu/forum/support/bugs/Issue-Reports-Heart-of-Thorns-Merged/page/46#post5696192 He is not the only. We have many with 64-bit systems having the problem. https://forum-en.gw2archive.eu/forum/support/support/Client-Crashing-constantly-1/page/5#post5697356
If it was JUST happening to 32-bit systems, I’d believe this. And if I had not already tried lowering the effective memory to 2 GB via MSConfig.

I know it’s not your fault, and I know that ANet did not on purpose block what could be as much as 10% of their players (if you assume the numbers on the forum and reddit are a percent of the folks having the issue bothering to report it) out of the game with this expansion, but people are getting hot (pardon the pun) about this. We understand that this might take a while to fix on your end, and you are trying to give us workarounds in the meantime, but we have tried them all, and it’s not helping. Until the core code is fixed, we’re hot out of luck.

Per Lauren Kamieniecki, the OOM issue is being worked on (https://forum-en.gw2archive.eu/forum/support/bugs/Issue-Reports-Heart-of-Thorns-Merged/page/33#post5665191 ) we just have no ETA. And that fine and understandable. I plan, code and test business apps for a living. It takes a long time to get some things working ‘perfect’ and we have by comparison a lot less ‘moving parts’.

All we’re asking is that someone officially tell us if and when they will bother to address this issue, and that we will be told specifically when a fix is in place. It is disHEARTening to see ‘Fixed a client crash’ in the update notes, log in hoping that it’s over and we can finally experience this fine game you have given us, only to have another OOM crash THORN in our side in 10-30 minutes.

Please, for the love of the Six and kittens, communicate to us about this. Don’t spoonfeed us scripted support anymore, this is past that.

Thank you and regards,
Player of Kylden Ar.3724

From: Guild Wars 2 Support [mailto:support@guildwars2.com]
Sent: Saturday, October 31, 2015 4:45 AM
To: [Redacted]
Subject: [Guild Wars 2 Support] Re: Constant OOM Crashes

1. Please type your reply above this line -##
   Your request (1911920:Constant OOM Crashes) has been updated. To add information to your request, simply reply to this email. If you no longer need assistance, just reply with “I no longer need help” in the body of your email.
   GM Shiro (Guild Wars 2 Support)
   Oct 31, 01:44
   Hello [Redacted],
   Thanks for contacting The Guild Wars 2 Technical Support Team.
   The issue you are having is known as an Out Of Memory Error, as you mention on your email. While we do have some suggestions for helping players work around this issue, ultimately we need you to understand that this is a limitation of 32-bit Operating Systems and not actually of Guild Wars 2 itself. *{writers note- except all the 64-bit people having this same problem…}* The main issue here is simply memory limitations inherent in 32-bit Operating Systems, which you can actually see below in your Game Advisor report:
   — Memory: 3072 MB RAM
   — Available OS Memory: 3072 MB RAM
   According to our report, you have upwards of 3GB of RAM and your system appears to be using the entire 3GB. The problem comes in the form of the additional video memory your graphics card has:
   — Display Memory: 2258 MB
   — Dedicated Memory: 978 MB
   — Shared Memory: 1279 MB
   This is where it gets a little complicated, 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 a 64-bit operating system. Others simply have 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 learned regarding these issues. You can read more about this issue from Microsoft here: http://support.microsoft.com/kb/929605. 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.”
   Please let us know if you have any questions.
   Regards,
   GM Shiro
   Guild Wars 2 Support Team
   http://help.guildwars2.com/

[Redacted]
Oct 30, 14:11
Requested files attached, plus a more recent individual crash.

[Redacted]
Oct 30, 13:46
So, as seen in This Thread there are a lot of OOM issues going on. It affects both 32-bit and 64-bit systems. It seems to be focused on NVIDA cards, but we have seen error reports with other cards. I pre-purchased this expansion. I played in BW3 fine with no errors or crashing (just the usual FPS drop I expect for high activity areas like the Silverwastes). There was no indication during the beta that I would not be able to play on release.
Now I get OOM crashes, all the time. My record uptime is 1 hr, 44 mins, but that took me literally sitting idle for 1 hour and 30 minutes.
I have already tried all the advice about lowering settings, limiting to 1 pre-rendered frame, clean boots, and limiting the RAM to prevent overlap thru MSConfig.
This is getting old. There are a lot of us with this issue. It did NOT happen before HOT, so it is something in the new HOT code that broke it for many low to mid and even a few high end systems based on the megathread.
Fix it. Please. Tell us what you are trying to do to fix it. Or start offering refunds.

This email is a service from Guild Wars 2 Support.
Message-Id:NYV59Y607N_56347f86727

I got the Windows 10 upgrade overnight (still 32-bit) so I will see if I have any better luck today with Win10’s better RAM and Virtual Memory management. But I expect I will be back shortly with a new crash log…

Valiant.8016:

I have to say, as a Mac user I’m pleased to hear that the crashes no longer seem to be isolated to Macs anymore. That’s not meant to be malicious, as when I heard the Mac subforum was done away with, maybe A.Net decided to give Mac users the finger. But if this is bleeding out to all users with the same preemptive problem(maps with large amounts of players), then I’m still holding out that maybe if and when these issues are fixed, it might improve the lot of Mac players, even if that isn’t what the devs intended.

I can’t blame you. I would not try to game on a mac, but that’s just because I work in IT and all my work stuff is also PC.

And. another crash. New record up-time, but most of it was in personal instances or old areas.

DrMORO.4627:

DrMORO.4627:

Reaper Greatsword, becomes ‘Unequipped’ after jumping from WP to WP, back in my Inventory, and leaving one of the Weapon slots empty. Really weird…
This only happens when traveling in the non-HoT world WPs, I think, as it never happened in the HoT area. Not sure if this is a HoT bug, but definitely has been newly introduced with the HoT Expansion, with the Reaper Elite Profession has been added to the Necromancer.
I did report this using the in-game Bug Reporter, attached with screenshot.
Hoping for a HoT (overused pun… :P) fix.

Okay, I think I’ve self-solved this issue.
But, before saying anything, I’d like to ask a question:
Is the Reaper Greatsword NOT averrable in WvW?

Well, I just noticed that my Reapers’s Greatsword was again ‘Unequipped’ & lying in my Inventory now. This was just after I have clicked the WvW & entered the area, to jump quickly get back to Lion’s Arch.

Could this be the very reason my Reaper Greatsword becomes ‘Unequipped’?

Yes. WvW build is now different from PvE, so if you have not equipped elite spec in WvW the weapon hits inventory.

I shudder to think if they didn’t account for full bags in this kind of case and going to WvW makes you lose your weapon… I have made a suggestion that weather or not you equip the spec, having it unlocked lets you equip the weapon, but no real response on that.

As for the ongoing OOM crashes, I don’t know if it was last patch, or the fact that I was mostly in personal instances, but new record up-time of 1 hr, 25 minutes. I also reset the field of view to original default settings.

Report sent in and attached.

Request #1911920 “Constant OOM Crashes” created

Request #1911920 “Constant OOM Crashes” created

Diefzix.5468:

How many of us are there suffering unplayable games and persistent crashes?
I’ve contributed my own reports a few times (OOM 10 seconds – 2 mins, lowest possible settings, updated Nvidia & 32-bit W7), but for each ever-lengthening thread, not so much as a peep out of Anet.

Look, Guild Wars 2 is still my top favourite MMO (I miss playing like burning and it especially hurts that I’m missing out on Halloween!), however dev responses have left a lot to be desired. The situation has been summed up numerous times by other players (32-bit & 64-bit both affected, Nvidia and other cards) and it’s clear that the surge of problems started last Friday at the Halloween/HoT update.

It has been a full week and we’ve waited patiently, please someone respond and tell us what the issue is and whether it is even being looked into.

Thank you.

Hear hear!

It would be a little easier to take if we knew they were working on it and would specify when it’s fixed. I keep hoping every time I see a ‘Fixed a client crash’ only to have my hopes shattered in 10 minutes….

So, as seen in This Very Thread there are a lot of OOM issues going on. It affects both 32-bit and 64-bit systems. It seems to be focused on NVIDA cards, but we have seen error reports with other cards. I pre-purchased this expansion. I played in BW3 fine with no errors or crashing (just the usual FPS drop I expect for high activity areas like the Silverwastes). There was no indication during the beta that I would not be able to play on release.

Now I get OOM crashes, all the time. My record uptime is 1 hr, 44 mins, but that took me literally sitting idle for 1 hour and 30 minutes.

This is getting old. There are a lot of us with this issue. It did NOT happen before HOT, so it is something in the new HOT code that broke it for many low to mid and even a few high end systems based on the megathread.

Fix it. Please. Tell us what you are trying to do to fix it. Or start offering refunds.

Sephalo.5407:

Just to stay on topic:
This is about the constant crashes and has nothing to do with the server being down. I hope the people that had issues with the server can play again. But there are still a lot of people that can’t properly play GW2 even when the servers act normal again.
Those OOM crashes keep appearing minutes after logging in, and it would be really great to see ArenaNet replying to this post.

I created a second post about this issue, and today ArenaNet merged that post with this one (without saying anything to me). So I know that it’s being read, but why is nobody from the company communicating with us. A small ‘sorry, we’re looking into it’ would be so great already.

Yesterday I was on the edge of buying a new (64bit) OS, but now I have doubts again if this will actually solve anything… I’m full with doubts, and I need an expert, PREFERABLY from ArenaNet to come with a REAL solution.

Do not get a 64-bit OS just to help this. It will not.

So, as seen in This Thread there are a lot of OOM issues going on. It affects both 32-bit and 64-bit systems. It seems to be focused on NVIDA cards, but we have seen error reports with other cards. I pre-purchased this expansion. I played in BW3 fine with no errors or crashing (just the usual FPS drop I expect for high activity areas like the Silverwastes). There was no indication during the beta that I would not be able to play on release.

Now I get OOM crashes, all the time. My record uptime is 1 hr, 44 mins, but that took me literally sitting idle for 1 hour and 30 minutes.

This is getting old. There are a lot of us with this issue. It did NOT happen before HOT, so it is something in the new HOT code that broke it for many low to mid and even a few high end systems based on the megathread.

Fix it ANet. Tell us what you are trying to do to fix it. Or start offering refunds.

So, as seen in This Thread there are a lot of OOM issues going on. It affects both 32-bit and 64-bit systems. It seems to be focused on NVIDA cards, but we have seen error reports with other cards. I pre-purchased this expansion. I played in BW3 fine with no errors or crashing (just the usual FPS drop I expect for high activity areas like the Silverwastes). There was no indication during the beta that I would not be able to play on release.

Now I get OOM crashes, all the time. My record uptime is 1 hr, 44 mins, but that took me literally sitting idle for 1 hour and 30 minutes.

This is getting old. There are a lot of us with this issue. It did NOT happen before HOT, so it is something in the new HOT code that broke it for many low to mid and even a few high end systems based on the megathread.

Fix it. Tell us what you are trying to do to fix it. Or start offering refunds.

Xinchro.2605:

Game is continually crashing, at least once an hour, no matter what I’m doing.

This seems to be an issue with the GTX 970, as this person is having similar issues.

Crash report

hide spoiler

—> Crash <—
Exception: c0000005
Memory at address 00000000 could not be written
App: Gw2.exe
Pid: 180136
Cmdline:
BaseAddr: 00EB0000
ProgramId: 101
Build: 54738
Module: CoherentUI.dll
When: 2015-10-30T16:26:22Z
Uptime: 0 days 0:14:02
Flags: 0

—> System <—
Name: CELCIUX
IpAddr: 192.168.1.7
Processors: 8 [GenuineIntel:6:12:3]
OSVersion: Windows 6.1 (64 bit)

—> System Memory <—
Physical: 5320MB/16313MB 32%
Paged: 15150MB/32625MB 46%
Virtual: 179MB/ 4095MB 4%
Load: 67%
CommitTotal: 17474MB
CommitLimit: 32625MB
CommitPeak: 26412MB
SystemCache: 5837MB
HandleCount: 105300
ProcessCount: 129
ThreadCount: 2145

—> Process Memory <—
Private: 3242MB
WorkingSet: 3031MB
PeakWorkingSet: 3038MB
PageFaults: 6423206

—> Memory Category Usage (Inclusive) <—
[Category] [Size(MB)] [Count]
VRAM 1074.72 32326
Root 922.70 1263577
Art Assets 430.44 9254
Programmer Data 368.75 351457
VRAM – Character Geo 325.34 996
Anim Import Models 235.24 677
Anim Import Packfile 235.24 677
VRAM – Composite Tex 155.99 174
Game 142.70 116851
Engine 142.61 180839
Character Models 136.16 2527
VRAM – Effect Geo 124.49 552
Content 96.50 37301
Uncategorized 95.37 881020
Gr 92.53 119604
VRAM – Prop Tex 89.59 653
Composite Models 88.94 1561
VRAM – Gr Postproc 79.39 20
Collections 56.56 9734
Dictionary 53.40 1550
Composite Packfile 50.35 1329
VRAM – Gr Geometry 43.63 1152
Character Packfile 42.74 363
VRAM – DDI Shader 42.00 27262

—> Memory Category Usage (Exclusive) <—
[Category] [Size(MB)] [Count]
VRAM – Character Geo 325.34 996
Anim Import Packfile 235.24 677
VRAM – Composite Tex 155.99 174
VRAM – Effect Geo 124.49 552
Content 96.50 37301
Uncategorized 95.37 881020
VRAM – Prop Tex 89.59 653
VRAM – Gr Postproc 79.39 20
Dictionary 53.40 1550
Composite Packfile 50.35 1329
Gr 44.51 4004
VRAM – Gr Geometry 43.63 1152
Character Packfile 42.74 363
VRAM – DDI Shader 42.00 27262
VRAM – Terrain Tex 39.23 71
Composite Tex Pool 38.51 78
Text 33.75 5494
VRAM – UI Textures 30.97 931
Prop Packfile 28.56 363
VRAM – Gr Cloud 27.00 105
VRAM – Prop Geo 19.52 104
Effect Packfile 19.45 212
Audio 17.40 1288
VRAM – Terrain PgdImg 14.00 56

—> Game Context <—
MapId: 28
Flags: 0×241
ElapsedTime: 00:05:03

—> World State <—
<WorldState BufferCapacity=“83506016” BufferUsed=“76227180” DrawCalls=“2708” Fps=“32” EffectLights=“0” Lights=“24” Materials=“1012” Particles=“3267” Submodels=“2811” TextureLoadsPending=“0” TextureMemory=“-605085268” Triangles=“1849659” VerticesSoftwareTransformed=“0” VideoMemoryTotal=“486570304” CameraPos=“15037.3, 13406.4, -3185.96” CameraFwd=“0.723669, 0.0604255, 0.687497” MapName=“wZY+N.r5jOv” MapNamespace=“7bzex” MapSector=“IJwR+.i8PF5” MapType=“Public” MapFloor=“1” MapId=“28” MapGuid=“AF4C92BD-C9A9-48EE-A2FD-BB487BCFCA51” MapTimeOfDay=“0.263333” PlayerFacing=“-0.996532, -0.0832107, 0” PlayerPos=“15280.5, 13466.7, -2835.75” PlayerVelocity=“0, 0, -0” />

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

—> Thread 0×2cc8c <—

—> Trace <—
Pc:5ae8e9bc Fr:06e4fc54 Rt:5ae678e7 Arg:00000000 ead20000 001f6768 efa6789d
Pc:5ae678e7 Fr:06e4fcb4 Rt:5ae53b40 Arg:00000000 0a4749b0 0a47fd20 0a4749a0
Pc:5ae53b40 Fr:06e4fce4 Rt:5ae567d6 Arg:00000005 00000000 00004b5c efa67931
Pc:5ae567d6 Fr:06e4fd18 Rt:5ae4b3fd Arg:00000000 019c5d68 04d86c10 4cbf9794
Pc:5ae4b3fd Fr:06e4fd30 Rt:014fd5af Arg:014f6842 06e4fdbc 0786dab8 04d87854
Pc:014fd5af Fr:06e4fd60 Rt:014f8c5f Arg:3cf03282 0136c733 04d87810 04d87c60
Pc:014f8c5f Fr:06e4fe08 Rt:0136a6be Arg:04d87810 00000002 00000002 00000010
Pc:0136a6be Fr:06e4fe84 Rt:0136b8c2 Arg:b6f1780b 01d1132f 928e0810 00000001
Pc:0136b8c2 Fr:06e4fec4 Rt:01369e91 Arg:04bf3d30 00880638 011bef78 00000000
Pc:01369e91 Fr:06e4fee4 Rt:01310660 Arg:04bf3d30 928e09c8 00000000 00880638
Pc:01310660 Fr:06e4ff1c Rt:01310788 Arg:00000000 06e4ff34 76fe337a 00880638
Pc:01310788 Fr:06e4ff28 Rt:76fe337a Arg:00880638 06e4ff74 775392e2 00880638
Pc:76fe337a Fr:06e4ff34 Rt:775392e2 Arg:00880638 0d0106e1 00000000 00000000
Pc:775392e2 Fr:06e4ff74 Rt:775392b5 Arg:0131070c 00880638 00000000 00000000
Pc:775392b5 Fr:06e4ff8c Rt:00000000 Arg:0131070c 00880638 00000000 00000000

—> Thread registers <—
eax=00000000 ebx=0a474a58 ecx=00000068 edx=00003ece esi=ead20000 edi=00000000
eip=5ae8e9bc esp=06e4fc48 ebp=06e4fc54
cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00210203

ebx-32 0A474A38 00000000 00000000 00000000 00000000
ebx-16 0A474A48 00000000 00000000 00000000 00000000
ebx 0 0A474A58 ead20000 00000000 00000000 00000000
ebx16 0A474A68 0e338010 0e33beb8 00000008 00000000
ebx+32 0A474A78 00000000 00000000 0e340630 00000000
ebx+48 0A474A88 00000000 00000000 0000003a 0000003f
esi-32 EAD1FFE0 00000000 00000000 00000000 00000000
esi-16 EAD1FFF0 00000000 00000000 00000000 00000000
esi 0 EAD20000 99000000 99000000 99000000 99000000
esi16 EAD20010 99000000 99000000 99000000 99000000
esi+32 EAD20020 99000000 99000000 99000000 99000000
esi+48 EAD20030 99000000 99000000 99000000 99000000

—> Code <—
5AE8E99C c1ea0774 65eb068d 9b000000 00660f6f …te……..f.o
5AE8E9AC 06660f6f 4e10660f 6f562066 0f6f5e30 .f.oN.f.oV f.o^0
5AE8E9BC 660f7f07 660f7f4f 10660f7f 5720660f f…f..O.f..W f.
5AE8E9CC 7f5f3066 0f6f6640 660f6f6e 50660f6f ._0f.of@f.onPf.o
5AE8E9DC 7660660f 6f7e7066 0f7f6740 660f7f6f v`f.o~pf..g@f..o
5AE8E9EC 50660f7f 7760660f 7f7f708d b6800000 Pf..w`f…p…..

—> Stack <—
06E4FC48 00000000 001f6768 0a4749b0 06e4fcb4 ….hg…IG…..
06E4FC58 5ae678e7 00000000 ead20000 001f6768 .×.Z……..hg..
06E4FC68 efa6789d 00000000 0a4749b0 0a47fe6c .×.......IG.l.G.
06E4FC78 5ae7d655 00000000 3f600000 00000000 U..Z……`?….
06E4FC88 3f500000 00000000 06e4fcac 76fe41f0 ..P?………A.v
06E4FC98 00000002 fffde000 00000000 efa6789d …..........×..
06E4FCA8 06e4fd0c 5aec8630 ffffffff 06e4fce4 ….0..Z……..
06E4FCB8 5ae53b40 00000000 0a4749b0 0a47fd20 ;.Z.....IG. .G. 06E4FCC8 0a4749a0 00000000 06e4fce3 0a4749b0 .IG..........IG. 06E4FCD8 0a47fd20 06e4fcf4 00e764a2 06e4fd18 .G......d...... 06E4FCE8 5ae567d6 00000005 00000000 00004b5c .g.Z........\K.. 06E4FCF8 efa67931 0785b410 00000022 00000022 1y......"..."... 06E4FD08 0a47fed4 06e4feb4 5aec6e28 00000000 ..G.....(n.Z.... 06E4FD18 06e4fd30 5ae4b3fd 00000000 019c5d68 0......Z....h].. 06E4FD28 04d86c10 4cbf9794 06e4fd60 014fd5af .l.....L`.....O. 06E4FD38 014f6842 06e4fdbc 0786dab8 04d87854 BhO.........Tx.. 06E4FD48 3d0b4396 3cf03282 3cf03282 3cf03282 .C.=.2.<.2.<.2.< 06E4FD58 3d0b4396 3d0b4396 06e4fe08 014f8c5f .C.=.C.=...._.O. 06E4FD68 3cf03282 0136c733 04d87810 04d87c60 .2.<3.6..x..`|.. 06E4FD78 00000001 00000002 00000002 00000010 ................ 06E4FD88 06e4fda0 06e4fda8 04d87c60 00000002 ........`|...... 06E4FD98 06e4fe70 0000000c 00000000 0786dac8 p............... 06E4FDA8 00000000 04d87854 00000001 04d87810 ....Tx.......x.. 06E4FDB8 06e4fdf8 0786dac4 04d8784d 0132ae97 ........Mx....2. 06E4FDC8 04d87b8c 0136ca93 04d87810 00000000 .{....6..x...... 06E4FDD8 00000000 06e4fe08 06e4fe20 0136ad5f ........ ..._.6. 06E4FDE8 04d87810 7c92b479 00000001 04d87b58 .x..y..|....X{.. 06E4FDF8 00000000 06e4fdfc 06e4fdfd 928e08dc ................ 06E4FE08 06e4fe84 0136a6be 04d87810 00000002 ......6..x...... 06E4FE18 00000002 00000010 06e4fe70 04d87c60 ........p...`|.. 06E4FE28 00880638 00000001 7c92b479 1965a2d5 8.......y..|..e. 06E4FE38 0000076c 00000000 7751fddd 76763bdb l.........Qw.;vv 06E4FE48 00000000 76763c07 ee4fed3e 00000001 .....<vv>.O..... 06E4FE58 0000000a 00880638 00000024 00000001 ....8...$....... 06E4FE68 00000000 00000000 b6f1780b 01d1132f .........x../... 06E4FE78 7c92b479 00000022 928e0850 06e4fec4 y..|"...P....... 06E4FE88 0136b8c2 b6f1780b 01d1132f 928e0810 ..6..x../....... 06E4FE98 00000001 7c92b479 00880638 00000001 ....y..|8....... 06E4FEA8 c0000005 06e4fe94 06e4f690 06e4ff0c ................ 06E4FEB8 013109a0 964b92b4 00000000 06e4fee4 ..1...K......... 06E4FEC8 01369e91 04bf3d30 00880638 011bef78 ..6.0=..8...x... 06E4FED8 00000000 00880638 00000000 06e4ff1c ....8........... 06E4FEE8 01310660 04bf3d30 928e09c8 00000000 `.1.0=.......... 06E4FEF8 00880638 00880638 00880638 06e4fef0 8...8...8....... 06E4FF08 01315683 06e4ff64 013109a0 964ba68c .V1.d.....1...K. 06E4FF18 00000000 06e4ff28 01310788 00000000 ....(.....1..... 06E4FF28 06e4ff34 76fe337a 00880638 06e4ff74 4...z3.v8...t... 06E4FF38 775392e2 00880638 0d0106e1 00000000 ..Sw8........... 06E4FF48 00000000 00880638 00000000 00000000 ....8........... 06E4FF58 00000000 06e4ff40 00000000 ffffffff ....………..
06E4FF68 77571a05 7cb73c05 00000000 06e4ff8c ..Ww.<.|……..
06E4FF78 775392b5 0131070c 00880638 00000000 ..Sw..1.8…….
06E4FF88 00000000 00000000 00000000 0131070c …………..1.
06E4FF98 00880638 00000000 00000000 00000000 8……………
06E4FFA8 00000000 00000000 00000000 00000000 …………….
06E4FFB8 00000000 00000000 00000000 00000000 …………….
06E4FFC8 00000000 00000000 00000000 00000000 …………….
06E4FFD8 00000000 00000000 00000000 00000000 …………….
06E4FFE8 00000000 00000000 00000000 00000000 …………….
06E4FFF8 00000000 00000000 00000000 00000000 …………….
06E50008 00000000 00000000 00000000 00000000 …………….
06E50018 00000000 00000000 00000000 00000000 …………….
06E50028 00000000 00000000 00000000 000002c7 …………….
06E50038 00000040 06e50000 8b55770f 505756ec @……..wU..VWP

—> Error Logs <—
le to map memory on buffer 0
Coherent Assert: Unable to map memory on buffer
Coherent AssertFailure: Assert failure: Unable to map memory on buffer 0
Coherent Assert: Unable to map memory on buffer
Coherent AssertFailure: Assert failure: Unable to map memory on buffer 0
Coherent Assert: Unable to map memory on buffer
Coherent AssertFailure: Assert failure: Unable to map memory on buffer 0
Coherent Assert: Unable to map memory on buffer
Coherent AssertFailure: Assert failure: Unable to map memory on buffer 0
Coherent Assert: Unable to map memory on buffer
Coherent AssertFailure: Assert failure: Unable to map memory on buffer 0
Coherent Assert: Unable to map memory on buffer
Coherent AssertFailure: Assert failure: Unable to map memory on buffer 0
Coherent Assert: Unable to map memory on buffer
Coherent AssertFailure: Assert failure: Unable to map memory on buffer 0
Coherent Assert: Unable to map memory on buffer
Coherent AssertFailure: Assert failure: Unable to map memory on buffer 0
Coherent Assert: Unable to map memory on buffer
Coherent AssertFailure: Assert failure: Unable to map memory on buffer 0
Coherent Assert: Unable to map memory on buffer
Coherent AssertFailure: Assert failure: Unable to map memory on buffer 0
Coherent Assert: Unable to map memory on buffer
Coherent AssertFailure: Assert failure: Unable to map memory on buffer 0
Coherent Assert: Unable to map memory on buffer
Coherent AssertFailure: Assert failure: Unable to map memory on buffer 0
Coherent Assert: Unable to map memory on buffer
Coherent AssertFailure: Assert failure: Unable to map memory on buffer 0
Coherent Assert: Unable to map memory on buffer
Coherent AssertFailure: Assert failure: Unable to map memory on buffer 0
Coherent Assert: Unable to map memory on buffer
Coherent AssertFailure: Assert failure: Unable to map memory on buffer 0
Coherent Assert: Unable to map memory on buffer
Coherent AssertFailure: Assert failure: Unable to map memory on buffer 0
Coherent Assert: Unable to map memory on buffer

—> DirectX Device Info <—
VendorId = 0×10de
DeviceId = 0×13c2
Version = 9.18.0013.4788
Description = NVIDIA GeForce GTX 970
Compat = 0×00100800
VidMem = 4095 MB

Not just that card, seems to be NVIDA cards in general, across both 32-bit and 64-bit clients.

Still here too. Nice to know I prepurchased a game I can’t effectively play.

Verificus.4320:

VERY IMPORTANT: Revenant Runes are currently unavailable outside of using upgrade extractors on gear. Without these runes Herald runes CANNOT be crafted. Please fix this ASAP because right now Herald is the ONLY specialization that DOES NOT have access to their elite specialization rune set. Please make this a PRIORITY. Doesn’t take long to quickly add a recipe to Armorsmith (Also has Rune of Warrior and Guardian). Requiring 1 Mordrem/Evergreen Lodestone, 1 Orichalcum Ingot and 1 Bolt of Gossamer (in line with all the other base profession runes).

I’m sorry, but I think the people that can’t even get thru their prologue and the constant OOM crashes take priority over a rune set… you know you’re going to use Traveler’s or Strength anyway.

I feel for the folks still stuck in Prologue, but by the Six I am so far behind in the XPac because events (and thus the most Mastery XP) is essentially denied me due to all the OOM crashes.

Getodacul.9634:

Client keeps crashing all the time. A couple of minutes ago i went to Southsun to kill Karka quenn for achievement and lining item required for my revenant and game crashed in the middle of the fight,same in Auric Basin at Octovines and pretty much everywhere i go.I almost never had these problems before the launch of HoT but since then it is harder and harder for me to keep playing even if i absolutely love the expansion.Please fix game crashes as soon as possible; which you probably are working at.

There is a lot of OOM crashes, on both 32-bit and 64-bit systems. Most are with NVIDA cards, but we are seeing posted a few others scattered here. You can go thru the pages and see them all. We have been told they are ‘aware’ and working on it, but no one has said anything on if and when it will be fixed.

If you can avoid people it usually lasts longer before the crash, but I just tested this morning being idle in a quiet corner of the Basin, and I still crashed after 1 hr, 44 minutes.

Yes. See the big thread.

The giant 44 page error thread is about half the OOM issue. It is not just a few…

Dredrum.2563:

Let us know when we can play the game we payed for again. I had a number of serious crash errors that I would have to do system restores on reboot just to boot my comp back up, that I haven’t logged back in for a week. I just keep checking this thread to see when the crash problems have been resolved, which as I read everyday still hasn’t been solved even though every patch says they fixed client crash. How many are there to fix 1000’s?

They really need to at least give a general type of client or server crash they are fixing in these patches.

The OOMs for NVIDA cards continues—-

Kylden Ar.3724:

autopsie.6159:

NEVER had a problem with this game until HoT…. Getting crashes every 5-10 minutes like everyone else is… OBVIOUSLY a problem with the game… not my PC, so i emailed support and here is the reply…

THEY TOLD ME TO REMOVE MEMORY FROM MY PC and it was a WINDOWS 32 BIT problem… Not the game.. WTF..

my husband can run this on his laptop with intel UMA with only 32M of video memory and shared 1gig system memory.

THIS IS A PROBLEM WITH NVIDA cards and the game client, not our pc’s, and needs to be fixed ASAP.

Please get this fixed or refund me the money i paid for a game i can no longer play because of bad coding…

Hello —-—-,

Thanks for getting back to us.

The issue you are having is known as an Out Of Memory Error. While we do have some suggestions for helping players work around this issue, ultimately we need you to understand that this is a limitation of 32-bit Operating Systems and not actually of Guild Wars 2 itself. The main issue here is simply memory limitations inherent in 32-bit Operating Systems.

The problem comes in the form of the additional video memory your graphics card has:

— Display Memory: 2257 MB
— Dedicated Memory: 978 MB
— Shared Memory: 1279 MB

This is where it gets a little complicated, 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 a 64-bit operating system. Others simply have 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 learned regarding these issues. You can read more about this issue from Microsoft here: http://support.microsoft.com/kb/929605. 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:

Right-click on your desktop and select “Nvidia Control Panel.”
Select "Manage 3D Settings.”
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.

Regards,

GM Skull Knight
Guild Wars 2 Support Team
http://help.guildwars2.com/

I will try this, but not hopeful.

It made the crash time before forst crash 40 mins as opposed to 10, but still did not fix the OOM issue.

Chris Cleary.8017:

We are currently aware of this issue and are working to resolve it.

By the Six let the answer also fix the issue with OOM crashes for both 32-bit and 64-bit machines with NVIDA cards…

autopsie.6159:

NEVER had a problem with this game until HoT…. Getting crashes every 5-10 minutes like everyone else is… OBVIOUSLY a problem with the game… not my PC, so i emailed support and here is the reply…

THEY TOLD ME TO REMOVE MEMORY FROM MY PC and it was a WINDOWS 32 BIT problem… Not the game.. WTF..

my husband can run this on his laptop with intel UMA with only 32M of video memory and shared 1gig system memory.

THIS IS A PROBLEM WITH NVIDA cards and the game client, not our pc’s, and needs to be fixed ASAP.

Please get this fixed or refund me the money i paid for a game i can no longer play because of bad coding…

Hello —-—-,

Thanks for getting back to us.

The issue you are having is known as an Out Of Memory Error. While we do have some suggestions for helping players work around this issue, ultimately we need you to understand that this is a limitation of 32-bit Operating Systems and not actually of Guild Wars 2 itself. The main issue here is simply memory limitations inherent in 32-bit Operating Systems.

The problem comes in the form of the additional video memory your graphics card has:

— Display Memory: 2257 MB
— Dedicated Memory: 978 MB
— Shared Memory: 1279 MB

This is where it gets a little complicated, 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 a 64-bit operating system. Others simply have 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 learned regarding these issues. You can read more about this issue from Microsoft here: http://support.microsoft.com/kb/929605. 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:

Right-click on your desktop and select “Nvidia Control Panel.”
Select "Manage 3D Settings.”
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.

Regards,

GM Skull Knight
Guild Wars 2 Support Team
http://help.guildwars2.com/

I will try this, but not hopeful.

This issue still persists.

Something is very wrong with all these 64-bit systems crashing too…

Still ongoing…

And…. even post the ‘big update’ still getting these….

*--> Crash <--*
OOM: Heap, bytes=1362892, 
App: Gw2.exe 
Pid: 4008
Cmdline: 
BaseAddr: 012B0000
ProgramId: 101
Build: 54646
When: 2015-10-28T01:56:36Z 2015-10-27T21:56:36-04:00
Uptime:   0 days  0:10:00
Flags: 0

*--> System <--*
Name: OPSCON1-PC
IpAddr: 192.168.1.4
Processors: 2 [AuthenticAMD:15:11:2]
OSVersion: Windows 6.1 (32 bit)

*--> System Memory <--*
Physical:   804MB/ 3071MB  26%
Paged:     3104MB/ 6140MB  50%
Virtual:    138MB/ 2047MB  6%
Load: 73%
CommitTotal:   3036MB
CommitLimit:   6140MB
CommitPeak:    3124MB
SystemCache:    954MB
HandleCount:  18753
ProcessCount:    43
ThreadCount:    652

*--> Process Memory <--*
Private:         1472MB
WorkingSet:      1349MB
PeakWorkingSet:  1349MB
PageFaults:   1685134

*--> Memory Category Usage (Inclusive) <--*
[Category]                 [Size(MB)]  [Count]     
Root                       812.14      1207347     
Programmer Data            359.44      417614      
Art Assets                 335.81      12171       
VRAM                       296.59      21213       
Engine                     143.64      247776      
Game                       136.89      114506      
Anim Import Packfile       127.81      294         
Anim Import Models         127.81      294         
Map Assets                 104.65      9312        
Content                    96.49       37301       
Prop Models                95.23       5401        
Prop Packfile              91.29       581         
Gr                         90.67       152736      
Character Models           86.05       1114        
Uncategorized              80.88       729175      
VRAM - Gr Postproc         64.85       18          
Collections                56.30       9764        
Dictionary                 53.99       1984        
Character Packfile         42.96       197         
Composite Models           42.57       275         
Composite Tex Pool         38.80       144         
Composite Tex              38.80       144         
Collide                    36.01       48387       
VRAM - DirectX Geo Buffers 30.56       1520        

*--> Memory Category Usage (Exclusive) <--*
[Category]                 [Size(MB)]  [Count]     
Anim Import Packfile       127.81      294         
Content                    96.49       37301       
Prop Packfile              91.29       581         
Uncategorized              80.88       729175      
VRAM - Gr Postproc         64.85       18          
Dictionary                 53.99       1984        
Character Packfile         42.96       197         
Gr                         38.92       7506        
Composite Tex Pool         38.80       144         
VRAM - DirectX Geo Buffers 30.56       1520        
VRAM - Prop Tex            28.81       1198        
Text                       28.05       4164        
VRAM - UI Textures         25.87       475         
VRAM - DDI Shader          23.47       15910       
VRAM - Gr Geometry         23.37       189         
Collide Havok              16.85       38489       
Effect Packfile            15.22       165         
Model Granny               14.47       17558       
VRAM - Prop Geo            14.25       396         
Gr Cloud                   13.00       23012       
Collide                    12.84       9136        
Audio FMOD                 12.42       9102        
Gr Umbra                   11.28       1435        
Archive                    11.21       65          

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

*--> ClientContextThreadProc Thread 0xf60 <--*

*--> Trace <--*
Pc:015bd92f Fr:05e4f884 Rt:01ebed30 Arg:00000000 00000000 024670d4 000004b3 
Pc:01ebed30 Fr:05e4fac4 Rt:01ebfa97 Arg:00000000 04187410 00000080 00000080 
Pc:01ebfa97 Fr:05e4fafc Rt:01eb70e8 Arg:00000000 015bee49 0000087c 015fce80 
Pc:01eb70e8 Fr:05e4fb4c Rt:018f60bb Arg:3e03126f 3e038fa8 05e4fbdc 0afffab8 
Pc:018f60bb Fr:05e4fb80 Rt:018f896f Arg:3e038fa8 0176c393 0434d010 0434d460 
Pc:018f896f Fr:05e4fc28 Rt:0176a2de Arg:0434d010 00000002 00000002 00000010 
Pc:0176a2de Fr:05e4fca4 Rt:0176b4e2 Arg:e0fde6c7 01d11123 c389cc17 00000001 
Pc:0176b4e2 Fr:05e4fce4 Rt:01769ab1 Arg:03ff2d30 00468360 015befc8 00000000 
Pc:01769ab1 Fr:05e4fd04 Rt:017104f0 Arg:03ff2d30 c389cdcf 00000000 00468360 
Pc:017104f0 Fr:05e4fd3c Rt:01710618 Arg:00000000 05e4fd54 7708ee6c 00468360 
Pc:01710618 Fr:05e4fd48 Rt:7708ee6c Arg:00468360 05e4fd94 76f33ab3 00468360 
Pc:7708ee6c Fr:05e4fd54 Rt:76f33ab3 Arg:00468360 721a259b 00000000 00000000 
Pc:76f33ab3 Fr:05e4fd94 Rt:76f33a86 Arg:0171059c 00468360 00000000 00000000 
Pc:76f33a86 Fr:05e4fdac Rt:00000000 Arg:0171059c 00468360 00000000 00000000 

*--> Thread registers <--*
eax=05e4f3f8 ebx=05e4f840 ecx=024670d4 edx=05e4f840 esi=7707f26a edi=00000000
eip=015bd92f esp=05e4f81c ebp=05e4f884
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000246

eax-32 05E4F3D8  00000000 00000004 fffffd34 000002e4 
eax-16 05E4F3E8  fffffd34 000002cc 00000018 00000000 
eax +0 05E4F3F8  80000003 00000000 00000000 7514812f 
eax+16 05E4F408  00000000 41ea9a9c c4166c01 44d24cab 
eax+32 05E4F418  262027d3 433d0000 03828a48 3e40462c 
eax+48 05E4F428  01738c34 05e4f480 03828a64 3e404624 
ebx-32 05E4F820  024670d4 000004b3 00000000 4b068a10 
ebx-16 05E4F830  05e4f8b8 4b068a50 00000000 00000006 
ebx +0 05E4F840  70616548 7962202c 3d736574 32363331 
ebx+16 05E4F850  00323938 00000000 00006e07 00006e07 
ebx+32 05E4F860  05e4f888 016c4305 00000000 05e4f8b4 
ebx+48 05E4F870  05e4f884 05e4f8b8 05e4f8b4 00000000 
ecx-32 024670B4  65646f4d 7270206c 616f6c65 656c2064 
ecx-16 024670C4  20736b61 65746564 64657463 0000002e 
ecx +0 024670D4  2e5c2e2e 2e2e5c2e 676e455c 5c656e69 
ecx+16 024670E4  65646f4d 6f4d5c6c 466c6564 2e656c69 
ecx+32 024670F4  00707063 006f004d 00650064 0020006c 
ecx+48 02467104  00690066 0065006c 00250020 00200073 
edx-32 05E4F820  024670d4 000004b3 00000000 4b068a10 
edx-16 05E4F830  05e4f8b8 4b068a50 00000000 00000006 
edx +0 05E4F840  70616548 7962202c 3d736574 32363331 
edx+16 05E4F850  00323938 00000000 00006e07 00006e07 
edx+32 05E4F860  05e4f888 016c4305 00000000 05e4f8b4 
edx+48 05E4F870  05e4f884 05e4f8b8 05e4f8b4 00000000 
esi-32 7707F248  90909090 9825ff90 9077041d 90909090 
esi-16 7707F258  909005eb ff909090 041c0c25 90909077 
esi +0 7707F268  ff8b9090 5dec8b55 909005eb ff909090 
esi+16 7707F278  041db025 90909077 186a9090 07f32068 
esi+32 7707F288  da7ae877 4d830000 35ffffe4 77106010 
esi+48 7707F298  13a015ff f6337704 33fc7589 7d8947ff 

*--> Code <--*
015BD90F  806a2102 8d45bc6a 4050e852 68ffff83 .j!..E.j@P.Rh...
015BD91F  c4108d55 bcb90500 00006a00 ff751453 ...U......j..u.S
015BD92F  e8ac9400 008b55b4 8b45b88d 5a178b75 ......U..E..Z..u
015BD93F  1883e3f0 8bcb8843 fa8ac32a c2668973 .......C...*.f.s
015BD94F  f88843fb 0fb6c02b c8897bfc 3bca7414 ..C....+..{.;.t.
015BD95F  68e50300 00bafc69 2102b990 6a2102e8 h......i!...j!..

*--> Stack <--*
05E4F81C  015bd934 024670d4 000004b3 00000000 4.[..pF.........
05E4F82C  4b068a10 05e4f8b8 4b068a50 00000000 ...K....P..K....
05E4F83C  00000006 70616548 7962202c 3d736574 ....Heap, bytes=
05E4F84C  32363331 00323938 00000000 00006e07 1362892......n..
05E4F85C  00006e07 05e4f888 016c4305 00000000 .n.......Cl.....
05E4F86C  05e4f8b4 05e4f884 05e4f8b8 05e4f8b4 ................
05E4F87C  00000000 c389c877 05e4fac4 01ebed30 ....w.......0...
05E4F88C  00000000 00000000 024670d4 000004b3 .........pF.....
05E4F89C  00000068 00000001 00000000 e0fe34e7 h............4..
05E4F8AC  4b068a10 03828a48 0014cbcc 01006f06 ...KH........o..
05E4F8BC  01730000 03828a48 00000000 070160b0 ..s.H........`..
05E4F8CC  00000006 00000001 00000000 00000001 ................
05E4F8DC  2f7f1a40 05e4f900 0173c05a 038284c0 @../....Z.s.....
05E4F8EC  070160b0 00000006 00000000 00000000 .`..............
05E4F8FC  070160b0 2f7f1a40 0172d997 2f7f1a40 .`..@../..r.@../
05E4F90C  00000000 00000060 00000060 042b5188 ....`...`....Q+.
05E4F91C  0226ac84 00000060 05e4f940 0172d3bf ..&.`...@.....r.
05E4F92C  07016000 00000060 00000001 05e4f98c .`..`...........
05E4F93C  042b5188 05e4f970 0172cefa 042b5188 .Q+.p.....r..Q+.
05E4F94C  00000000 00000060 00000001 00000001 ....`...........
05E4F95C  00000048 042b5188 00000000 05e4f901 H....Q+.........
05E4F96C  00000000 05e4f990 0172d72c 042b5188 ........,.r..Q+.
05E4F97C  00000060 00000001 05e4f98c 00000001 `...............
05E4F98C  00000060 05e4f9fc 015c275c 00000060 `.......\'\.`...
05E4F99C  00000040 015bd9b3 067e84b0 00000000 @.....[...~.....
05E4F9AC  015bd9c2 2f7f1a40 00000001 00000000 ..[.@../........
05E4F9BC  00000000 02213bcc 00000295 00000008 .....;!.........
05E4F9CC  067e84e8 00000008 00000080 00000008 ..~.............
05E4F9DC  067e84e8 067e84d4 58fa6000 05e4fa68 ..~...~..`.Xh...
05E4F9EC  0164af32 0246d208 067e84d4 067e84b0 2.d...F...~...~.
05E4F9FC  7e1de010 00000001 76f1569c 751478a6 ...~.....V.v.x.u
05E4FA0C  05e4fa54 001f0003 00000000 02790270 T...........p.y.
05E4FA1C  05e4fa68 05e4fa60 016edeb0 03c2c178 h...`.....n.x...
05E4FA2C  00013e1d 03c2c208 00013e1e 4cf1be54 .>.......>..T..L
05E4FA3C  4cf1be54 03c2c208 00000001 03c2c178 T..L........x...
05E4FA4C  00013e1d 03c2c208 76f1646c 75147513 .>......ld.v.u.u
05E4FA5C  000000f4 00000001 00000000 05e4fa90 ................
05E4FA6C  015bbf77 000000f4 00000001 00000000 w.[.............
05E4FA7C  05e4fa8c 016ee551 7e1de010 79aad090 ....Q.n....~...y
05E4FA8C  042af814 05e4faa0 01ec2913 79aad090 ..*......).....y
05E4FA9C  4a5dc9b0 05e4fac4 01ebee43 00000000 ..]J....C.......
05E4FAAC  7e1de010 0001b364 05e4fac8 015bb8cf ...~d.........[.
05E4FABC  05e4fac0 c389ca37 05e4fafc 01ebfa97 ....7...........
05E4FACC  00000000 04187410 00000080 00000080 .....t..........
05E4FADC  2d3b5990 01d11123 e0fe34e7 624243d0 .Y;-#....4...CBb
05E4FAEC  00000000 00002710 00000000 0703b690 .....'..........
05E4FAFC  05e4fb4c 01eb70e8 00000000 015bee49 L....p......I.[.
05E4FB0C  0000087c 015fce80 06543f10 00000028 |....._..?T.(...
05E4FB1C  2dbc1c90 05e4fb54 015fb6f1 2dbc1c90 ...-T....._....-
05E4FB2C  00000028 022d0e6c 00000080 015ccd5a (...l.-.....Z.\.
05E4FB3C  00000010 015f121f 04187410 00000008 ......_..t......
05E4FB4C  05e4fb80 018f60bb 3e03126f 3e038fa8 .....`..o..>...>
05E4FB5C  05e4fbdc 0afffab8 0434d054 3e03126f ........T.4.o..>
05E4FB6C  3e038fa8 3e038fa8 3e038fa8 3e03126f ...>...>...>o..>
05E4FB7C  3e03126f 05e4fc28 018f896f 3e038fa8 o..>(...o......>
05E4FB8C  0176c393 0434d010 0434d460 00000001 ..v...4.`.4.....
05E4FB9C  00000002 00000002 00000010 05e4fbc0 ................
05E4FBAC  05e4fbc8 0434d460 00000002 05e4fc90 ....`.4.........
05E4FBBC  0000000c 00000000 0afffac8 00000000 ................
05E4FBCC  0434d054 00000001 0434d010 05e4fc18 T.4.......4.....
05E4FBDC  0afffac4 0434d04d 0172ac97 0434d38c ....M.4...r...4.
05E4FBEC  0176c6f3 0434d010 00000000 00000000 ..v...4.........
05E4FBFC  05e4fc28 05e4fc40 0176a97f 0434d010 (...@.....v...4.
05E4FC0C  010d826c 00000001 0434d358 00000000 l.......X.4.....

*--> Error Logs <--*
Debug token '0x266fa': Lightning ran out of space for new bolts.
Model '0x082245': Failed to resolve AimIK bone indices.
Material '0x034fc5' is missing textures.
Material '0x034fc5' is missing textures.
Material '0x034fc5' is missing textures.
Material '0x034fc5' is missing textures.
Content is referencing a propID that doesn't exist propId='1907337256732033536'
Content is referencing a propID that doesn't exist propId='1907337037688701442'
Content is referencing a propID that doesn't exist propId='1907337699113665028'
Texture missing mip chain: 0x1346ff
Texture missing mip chain: 0x1346fe
Debug token '0xf1059': Lightning ran out of space for new bolts.
Map load hang on STATE_MODELS_STREAM detected: MapId: 1052, Position: (-19769.900391, -10905.200195, -20101.500000), Completion: 0.000000
Couldn't find projectile effect for skill 'KIWQR.F77q2'
Map load hang on STATE_MODELS_STREAM detected: MapId: 1052, Position: (-19769.900391, -10905.200195, -20101.500000), Completion: 0.000000
Couldn't find projectile effect for skill 'Y6s+P.8WKlD'
Couldn't find projectile effect for skill 'Aw3PF.xcnwE'
Map load hang on STATE_MODELS_STREAM detected: MapId: 1052, Position: (5321.759766, -994.742004, -16930.500000), Completion: 0.000000
Couldn't find missile launch point for gadget '0xdd22'.
Coherent AssertFailure: Assert failure: Dispatching a message to a non-active view  7 at UISystemImpl.cpp : 1856
Coherent Assert: Dispatching a message to a non-active view 
Texture missing mip chain: 0x010140
Texture missing mip chain: 0x118f71
Couldn't find projectile effect for skill 'KIWQR.F77q2'
Couldn't find projectile effect for skill 'Aw3PF.xcnwE'

*--> DirectX Device Info <--*
VendorId    = 0x10de
DeviceId    = 0x0a65
Version     = 9.18.0013.4144
Description = NVIDIA GeForce 210 
Compat      = 0x00100800
VidMem      = 1024 MB

Just a reminder and follow up —

Still getting OOMs. And we have seen people on 64-bit machines in this thread with the same kind of error.

I have noticed that all of my OOMs don’t show near max memory either. What is trying to load suddenly that takes over 25% of my available RAM, Video, and Virtual RAM all at the same time?

Tzozef.9841:

When is this going live?

Sounded like tonight, but who knows for sure?

Argon.1563:

JOKe.3597:

No way to pass the 14 step of the personal story there are some CLUES or kittenS that you have to interact with ALL the time some of them is not working started from beginning more then 10 times.. peace of * if this is nice gaming experience …

Im having this issue as well. Its an absolute joke. You can tell this wasn’t play-tested, for a game-breaking bug to occur in the main storyline.

Also, why has this not been fixed yet? The expansion has been out for 5 DAYS. Some people paid £80 for this expansion pack, myself included. Im not expecting it to be bug free, but I at least expect the main questline to be playable.

At least you can get that far. I got as far as chapter three before the constant crashes made me give up playing new content.

Some poor folks can’t even get thru the prelude into Verdant Brink after 5 days.