Guild Wars 2

Jarid.4952:

Tried 12.9 a week ago, didn’t changed anything. I think Arenanet muss configure this ingame, lets hope they notice this Bug & will take care of it!

I think you mean 12.8 since that’s the newest version? And the beta is even older than that…

…but yeah, major gfx issues with 12.8 I think, at least on the newer cards.

I couldn’t care less about more performance, not at least until they get all these graphical glitches sorted out. I had no issues with 4890, now with my brand new 7870 I have strange black lines on the ground, terrain/geometry flashing, etc. and it’s driving me NUTS.

Vanth.4583:

For me the problem goes away entirely if I use a wired mouse. It has to be wired though – I tried another wireless one (also a different make – not Logitech like my usual mouse) and the problem is still there. I would rather not use my crappy wired mouse though…

This sounds like it could be an interference issue; only affecting wireless eh?

Jim.1829:

Having the same issue. Shocked that this post hasn’t been answered yet.

I believe it has been, numerous times in the Tech Support forum. Disable Ambient Occlusion in the NVidia display settings.

tekwiz.8635:

At some point, AMD stated that obsolete hardware will have no support in new driver versions.

That is not what they said.

AMD/ATI stated that older series cards (4xxx and prior) will only receive periodic legacy updates, meaning every 6 months. Those updates will contain bug-fixes only, as they claim that the older series have already been optimized to their full potential.

“AMD has moved to the AMD Radeon™ HD 4000, AMD Radeon HD 3000, and AMD Radeon HD 2000 Series new driver support model. These updates will focus on resolving application specific issues and critical updates. The reason for the shift in support policy is largely due to the fact that the AMD Radeon HD 4000, AMD Radeon HD 3000, and AMD Radeon HD 2000 Series have been optimized to their maximum potential from a performance and feature perspective.”

This does not mean you cannot run with the newest drivers on the “older hardware,” it just means that you shouldn’t expect improved performance with them.

Overlays (Mumble, TeamSpeak, MSI AB, etc.) can cause CTDs as well, and not just in GW2 but many games – this is pretty well documented. Also the reason my post instructs to disable the OSD from within AB.

I was getting CTDs with the overlay disabled (I wouldn’t exactly call them “constant,” more like “random” – could be 5 mins, 2 hours, and occasionally I could play without it occurring at all), so I knew it had to be something else. Turns out it has something to do with AB’s kernel address space and GW2 trying to access hardware-mapped memory ranges. Again, I’m fairly certain GW2 or any game should not be trying to access this memory space in the first place, hence the MSI AB tooltip regarding “Badly designed applications” (and the option for ‘kernel mode’)…haha!

Rav.9354:

Update. I plugged in a different mouse. The problem disappeared entirely.

What happens when you reattach the old mouse? Does the issue return, or does it remain gone?

If the issue returns, the next step would be to try the affected mouse on a separate PC. If there is no issue on a separate PC, I would tend to blame the original systems mouse or USB drivers. If the issue persists on the other PC, more than likely your RMB has worn out. This does happen, guys – I just replaced a mouse due to this. It was my Logitech G700 after only 1 year of use (has 3 year warranty). The RMB developed issues with registering clicks (sometimes it wouldn’t register at all, other times it would double click when I single’d, etc.). This is why testing with a different mouse and/or PC is important. The Logitech mouse I had before my first G700 (Revolution VX), wore out the LMB after a couple years, which they also replaced under warranty, and is the main reason I buy Logitech mice (and other products – their Customer Support is amazing).

mthomas.2763:

Tried both. Doesn’t matter. It’s clearly a game issue since every other application and game I use has absolutely no issues.

That’s what I was looking for, thanks. I have seen a few more posts popping up about this issue on the forum. I would hope A.Net is fully aware of this issue (submit bug reports ASAP if you haven’t) as it seems more people are starting to be affected by this. Either that or you guys played too much Diablo 3 and all wore out your mouse buttons. :P

Let us know what happens. Flashing isn’t hard, just make sure you don’t accidently power off the PC while it’s flashing or you may end up with a bricked comp (specifically, a bricked motherboard). Just FYI

Now running 12.8 cap 3 and the issue persists…

Can we get a community rep to respond on this? We were told it was being worked on, but have not heard a peep in over 2 weeks.

That’s definitely relevant concerning the BIOS clock.

Check for BIOS updates first, there may be an update to correct this issue.

Do you know how to flash your BIOS, if so?

XeuQinu.6019:

If I am, then please share your thoughts and tell me why one of the best AMD CPUs paired with the best Nvidia GPU can’t seem to crunch/render this “revolutionary game” that seems to be taxing the hell out of a large number of high end systems, but then runs smooth as silk on lower end pc’s/laptops. If you can explain that, then I’ll shell out and buy the equipment below.
<snip>

I’ll try. More than likely, and even though GW2 spawns multiple working threads, there is a main thread that the engine relies on, and if this thread slows or stalls for any reason, the other threads that rely on it also slow and stall. Since AMD CPUs are, by nature of hardware design, not as efficient per core as newer Intel CPUs, and the main thread of GW2 only occupies one core, you will see less performance (even with more cores) on a similiar AMD setup vs. an Intel setup. This is why the BullDozer (8 core AMD CPU) performs so much worse than even quad core Intel CPUs in this game. It’s not always about the number of cores, it’s about the efficiency of them, especially in games and apps that heavily rely on one main thread for most of it’s operations (you may be surprised how many games do). As far as the top-end Nvidia card goes, well I can almost guarantee that it’s being bottlenecked by the CPU, for the aforementioned reasons. You could probably run with a 5-series and see nearly identical FPS in-game.

The only way you’ll see improvements with the AMD system vs. buying a new Intel rig outright, is when and if A.Net optimizes the game to make more use of the GPU, offloading certain CPU tasks to the GPU, etc. No telling when/if that will ever happen, but a lot of us are hoping it will. This also pertains for other games; as I mentioned there are plenty out there that, even though the developer may claim multi-core support, still rely on one main thread to run the engine. It sucks, but I hear it’s easier to develop that way. Still, with all of the multi-core CPUs these days, and especially with these kinds of games being heavily CPU-dependent, devs should be looking for more efficient ways to spread the load evenly amongst all cores in a CPU. It just hasn’t really happened yet.

Hope that helps.

PS – I’m not telling you to run out and drop thousands on a new rig, that’s all you! Haha.

There really is no issue here. The CPU is waiting on the GPU to finish rendering (meaning the GPU is bottlenecking the CPU) before continuing operations, and in the meantime is in an idle-to-low-activity state. This is normal.

About all you can do (and should) is turn Shadows down (Ultra does kill your FPS, and High looks 90% as good anyways), and Reflections to Sky/Terrain. I would also disable depth blur simply because I opt to have distant objects actually clear instead of blurry, but this is personal preference and may or may not increase your FPS a bit.

Other than that, you are looking at a vid card upgrade to get any more frames/sec. If and when you decide to upgrade your GPU, you will see your CPU usage rise as well (and most likely your GPU usage will drop if you get a high end card).

garethh.3518:

Yeah that was one of the first sites I found ><

I tried it multiple times to no avail…

(thnks for the response though)

What happened when you tried it? Errors, codes, etc. may be relevant.

Swordbreaker.2581:

Try this. http://www.intrepid.com.au/computer-clock-running-too-fast-or-too-slow/

That’s a good find and I’d definitely start there. However, one would think that the service would correct itself when you restart the OS…then again, I don’t work at MS. Lol.

Hmm why can I no longer edit my post. It was available just a minute ago and now all I see is “permalink.”

Anyways, Module: nvd3dum.dll was from Insanitys post. Insanity I’m not sure what that file is, but that’s most likely the cause of your issue. Nvidia driver(s) perhaps? Not sure. Run a windows search for the file, identify the application or driver using it, and update/uninstall/block as necessary. Try that and report back.

Module: d3d9.dll (first crash report)
Module: nvd3dum.dll (second)

^ These are related your problem. Looks like the display driver you are using has issues, or it could be DirectX. I recommend a complete uninstall and clean install of the latest driver (or if attempting to use the latest, try the previous version, etc.), or the latest version of DX.

Let us know how it goes.

EDIT: Ashley beat me to it, and I think she’s right. :P

So, I got an infraction (and post deletion) by posting “Lol” as my only response text. Seriously Mods? That’s…sad. I didn’t realize a subject such as this required contribution, but hey let me get right on that.

Ok, here’s my contribution.

“Please share this fix in the Low FPS thread because I’m sure nobody has thought of this and it sounds like a safe and easy fix, other than all of the people that are unable to overclock due to the lack of BIOS options or hardware warranties in effect.”

I think I picked up a little sarcasm in the OP so I figured I’d return some, not trying to troll or anything.

mthomas.2763:

Exact same issues using a Logitech mx518.
<snip>

…and are you using the Logitech Setpoint software (installed from CD/downloaded), or the built-in mouse drivers by Microsoft (you installed nothing with the mouse)? These things are important…

rinzler.4908:

Targeting and camera controls in this game are currently pretty terrible.

What’s sad is that a F2P game like Sevencore has better targeting and camera controls.

How exactly is the targeting terrible? Sounds like user error, tbh.

There are bindable keys for Closest Enemy, Next Enemy, Previous Enemy, Next Friendly, Previous Friendly, Self, Mark Target, Acquire Target, and more. It is very similar if not exactly the same as GW1, which has worked just fine for 7+ years. Other MMOs are the same or have less options.

There are more options than just “TAB,” ya know. Helps to check the control settings.

(Oh, and the camera is controlled in 3D by the mouse…how much more control do you need? 4 dimensions? Lol.)

My only other suggestion would be to disable/uninstall your 3rd party mouse drivers (Logitech Setpoint, Razer Synapse, etc.) and try running on the built-in MS mouse driver. This could be a [new?] issue regarding driver compatibility with the game; just a shot in the dark here.

Seeing a whole lot of Razer issues in this thread. Others are not listing their mice or which driver they are using. You guys need to list your hardware and software.

+1 needs fixing

I do not have a solution for those receiving this type of error that are not users of MSI AfterBurner or other programs based on RivaTuner/Statistics Server. Sorry.

Though it may be a related issue – I mean, after all it does say that “Badly designed applications” can sometimes reference hardware-mapped memory ranges, resulting in system instability. One can only wonder exactly what GW2 is trying to access, but from what I can gather, I’m fairly certain it shouldn’t be trying in the first place…

I posted a new thread regarding my potential fix for this issue.

It can be located here: https://forum-en.gw2archive.eu/forum/support/tech/Fix-for-c0000005-errors

I posted a new thread regarding my potential fix for this issue.

It can be located here: https://forum-en.gw2archive.eu/forum/support/tech/Fix-for-c0000005-errors

I posted a new thread regarding my potential fix for this issue.

It can be located here: https://forum-en.gw2archive.eu/forum/support/tech/Fix-for-c0000005-errors

Well lo and behold…I have now gone several days, with upwards of 7+ hours continuous uptime in-game, with zero crashes. While I will not claim this to be the end-all, be-all fix for the related memory CTDs (feedback required), I think we have found our culprit – or at least one of them.

////////////// SEE ATTACHED IMAGE //////////////
If you suffer these memory CTDs and are using MSI AfterBurner:

1. Change the ‘Low level hardware access interface’ setting from ‘User mode’ to ‘Kernel mode.’ Restart AfterBurner. If you are not using the automatic profiler option, this should be the only option needing to be changed, as the OSD server .exe should not be running in the background. This can be verified by checking Task Manager for RTSS.exe; it should not be there. If it is running, proceed to step 2.

2. If you’re using the automatic profiler to detect 3D apps and change profiles on-the-fly, attempting to use other features of the OSD server (not recommended in GW2), etc., I would recommend the following steps:

2a. Open the OSD server (the other icon in the system tray). Change the following options to: Show On-Screen Display – OFF, Application detection level – LOW, Stealth mode – ON, On-Screen Display support – OFF.

2b. Click the wrench (options) icon in the OSD server. Ensure ‘Enable compatibility with modified Direct3D libraries’ is disabled – unchecked. Click OK to accept. This is not pictured in the attached screenshot (forgot, sorry!) but should still be verified.

3. Minimize the OSD server back to the system tray and restart AfterBurner.
////////////// SEE ATTACHED IMAGE //////////////

That should do the trick – at least it did wonderful, magical things for my gaming experience. No longer do I suffer memory CTDs at random intervals. What a beautiful thing.

Before you continue reading, you should know that this fix only pertains to those users who receive (quite often randomly) a CTD with the error…

“Exception: c0000005
Memory at address XXXXXXX cannot be read/written”

…and are users of programs such as MSI AfterBurner, EVGA Precision X, or any other video card overclocking utility that relies on the RivaTuner core program/statistics server. These programs are written by the same author of the once-popular RivaTuner, so they are very similar/based upon the same code as far as I know.

The following blurbs reference my use of ATI cards while diagnosing this issue, however should be relevant to NVidia users as well.

Since I dislike using Catalyst Control Center for my ATI video card, I opt to use MSI AfterBurner instead, as it gives me complete control of clock speeds, fan speeds, and voltages, offers performance monitoring, an in-game OSD, and many other advantages.

After suffering through these “memory CTDs” for a couple weeks, and watching the game get updated almost nightly but in no way fixing my CTDs, I went into fix-it mode. I tried nearly everything – forcing Catalyst A.I. completely off (requires registry editing for newer cards such as 7xxx series), raising voltages in the system (GPU, CPU, CPU PLL, FSB, NB, RAM), clean driver re-installation, getting the new CAP for the 12.8 driver, updating Windows 7, uninstalling .NET 4.0, etc. I was nearly stumped.

Then it occurred to me – since I recently upgraded to the 7870 GHz Edition up from an aging 4890 (which I had BIOS flashed to overclock, meaning I didn’t use CCC -or- AfterBurner), I had started receiving these memory CTDs in GW2. I didn’t have those with the old 4890. So I asked myself: what did I change? Besides the actual hardware upgrade, I installed the latest version of MSI AfterBurner, in order to make separate 2D and 3D profiles – not only for overclocking, but for fan speed control.

So the other day, I really sat down with AfterBurner and went over ALL the settings available. Now, I had used AfterBurner before in the early days of my 4890, long before I flashed it’s BIOS. I figured that -maybe- I ought to re-review all of the individual settings, as perhaps something had changed or I overlooked something important. It should be noted that I have AfterBurner set up to use it’s Automatic Profiles Management system, simply meaning it will detect (through the use of the RTSS server that runs in the background) application calls to the Direct3D and OpenGL runtime libraries, and automatically change profiles to what you have selected for 2D and 3D. In essence, when it detects application calls to D3D or OpenGL, AfterBurner automatically loads my custom 3D profile – upon exiting the application/game, will automically re-load my 2D profile. This is convenient for those that do not want to use hotkeys and the like for changing profiles.

So, upon perusing the many options in the AfterBurner settings page, I came back to one single thing that caught my eye. There is a setting called ‘Enable low-level hardware access interface’ in the main tab of the settings page, with the options of ‘User mode’ (this is the default setting) or ‘Kernel mode.’ The tooltip is lengthy, but basically states that ‘User mode’ gives the best monitoring performance and doesn’t consume kernel address space, while ‘Kernel mode’ can protect hardware-mapped memory ranges from unauthorized access by badly-designed applications* and in this way can protect the system from instability. That got me thinking – I had been receiving, seemingly at random (could be 2 minutes or 2 hours), these memory CTDs in GW2 and apparently the default setting of ‘User mode’ does not provide protected kernel address mapping for AfterBurner/RTSS. I decided to change that setting to ‘Kernel mode’ and hoped for the best, as I could not find any other setting that may cause system instability that I had not already changed…

(continued in post #2)

gosu.8153:

Idolicious.6091:

Those with gaming mice should turn up the USB polling rate (you can actually do this for a standard mouse too, if you know how) to see if that alleviates the issue.

That isn’t a fix really, but may help until A.Net can figure out what’s going on with some peoples mice.

Default Windows USB polling rate: 125hz

Ya’ll should try: 250hz, 333hz, 500hz, and 1000hz.

Stop wasting your time.
The problem isn’t with mice. It’s the game.
If you haven’t experienced the problem, it’s due to the class/profession you play or your playstyle.

I never experienced this while leveling.
It only happens when I am trying to do like 20 things at the same time in PVP.

I realize that it probably isn’t all these guys’ mice acting up, however increasing the polling rate forces the system to capture USB data at 2-8x the normal rate, and might alleviate (not fix) the issue while they wait for a real fix.

Haha, those IPs are routing to the NCSoft Datacenter in Austin, TX. I live in Austin, and I was there when I tested an early build of GW2 in early 2011.

EU clients should be routing to the EU Datacenter, for sure, if one actually does exist…lol.

No prob, please take a screenshot of all normal running background processes (CTRL+SHIFT+ESC, make sure “Show processes from all users” is checked at the bottom left). Upload it to this thread and we’ll take a look. Also, screenshot your msconfig (start→run→type ‘msconfig’→press enter→click Startup tab) and upload that here as well.

FYI to those questioning .NET 4.0:

I’ve had 4.0 cause system instability before – not even talking games, but overall stability. Freezes on Windows start (randomly), etc. Seems 4.0 has issues with certain PC configurations.

I would HIGHLY suggest completely uninstalling .NET 4.0 (3.5 works fine, and only a handful of apps require 4.0) if you are at all questioning it/looking for more stability/trying to increase performance. Just my 02c.

Deathstar: Are you using MSI AfterBurner (or EVGA Precision X, etc.)?

I have a possible incoming fix for this issue. Going to do extensive testing tonight before I post it on the forums, though.

Those with gaming mice should turn up the USB polling rate (you can actually do this for a standard mouse too, if you know how) to see if that alleviates the issue.

That isn’t a fix really, but may help until A.Net can figure out what’s going on with some peoples mice.

Default Windows USB polling rate: 125hz

Ya’ll should try: 250hz, 333hz, 500hz, and 1000hz.

I think I’ve found a potential fix for this issue – going to do extensive testing tonight before I post it on the forums though. Things are looking up though.

I’m pretty happy to report that I think I’ve solved the “memory cannot be read/written” issue. I believe have found a way to have the best of both worlds – able to use AfterBurner AND play GW2 without crashing. Going to test for several more hours tonight (had an uptime of 7+ hours in-game yesterday with NONE of those crashes), before I report back. Keep your eyes peeled…

This is not due to peoples PC having lackluster performance; getting tired of people with no clue what they are talking about chime in on peoples threads saying “oh it’s gotta be your PC cuz I don’t have that issue!” well guess what you do actually, you just don’t notice it or don’t care.

The game uses mouse smoothing/interpolation. End of story. This should be an option that the user can disable/enable as it does not cause an advantage having it set off.

Laggy mouse is laggy.

Well, the point of running ShieldsUP directly connected to the modem (eliminating the router as a cause of port-related issues/blocking) is to see if there is any software on your PC causing port and connection-related issues. If you have no firewall software installed, Windows firewall is disabled, and you are bypassing the router, they should read OPEN under normal circumstances. This is just a troubleshooting step to ID the actual problem, as you definitely don’t want a bunch of open ports under normal circumstances.

Sounds like a typical overheating scenario…have you checked your CPU and GPU temps, fan speeds (are they still spinning as they should), etc.? Check the components for dust build up, too.

majestic.8129:

As ArenaNet has already stated, this is a known issue so either you suck it up and run on low settings until a fix is implemented or perhaps, you could actually use all the hardware you purchased efficiently by installing 64-bit for free.

Sorry to say, but this IS the answer you are looking for, OP.

I’m still waiting on this vid to be uploaded but I will say that if you unlocked MSI AB oc limits then it’s a very simple process to revert it. Remove files and/or re-install AB. That said I have not increased the oc limit of AB (no need), but also am unsure that what I’m seeing is what these other guys are referring to. Please upload vid =P

xyzzy.8970:

As long as the DLLs are loaded (check in processes and services in Task Man.), EVGA Precision and MSI Afterburner can cause c0..5 (access violation) errors, as can overlay programs (raptr, Steam, Mumble, maybe Xfire etc too).

This is a possibility and why I asked the question. It also helps to run AB in Stealth Mode (this is an OSD server option from AB) and at Low Application Detection, if using the auto profile feature.

Have you directly connected to the modem, bypassing the router? Set your IP to automatic (if it’s manually assigned) and directly connect. If that still doesn’t work there’s some software on the PC either blocking ports, incoming connections, etc. I’ve had issues with firewall software leaving my ports blocked after it was UNinstalled. Try running a port checker online (again, directly connect first) to check. I suggest using ShieldsUP: https://www.grc.com/x/ne.dll?bh0bkyd2

^ This is the main reason I recommend using MSI AfterBurner vs. messing with the CCC .xml files. Seperate 2d/3d clocks, seperate fan speed profiles, seperate voltage settings, usage/clocks/temps/fan/voltage monitoring, etc. etc. It really is worth the time to set up MSI AB properly. I used to play the “hack the xmls” game but have given that up for more usability and features of AB. Just my 2c.

Did you get that flicker vid uploaded?

Question:

Are you running MSI Afterburner/Sapphire Trixx/EVGA Precision/etc.?

Please upload your entire crash log at the next occurrence so that we can take a look.

I assume you guys have tried different mice in order to replicate the problem…? Ya’ll are positive that you aren’t clicking/dragging on something in the UI that is preventing mouse-look, yeah?

If so, next step would be to submit bug reports. Strange that neither I nor anyone I know have this issue, though. But sometimes that’s how it goes.

note.5817:

What I still believe to be the reason is that the GPU drivers are somewhat buggy and might get fixed within next WHQL driver release.

I agree with you on that. Both ATI and NV seem to be definitely having issues with this game (could of course be due to buggy GW2 programming).

Post linking seems glitchy, I’d suggest just reading the whole thing, it’s not that long.