elementclient.exe has stopped working

I don't see any glaring issues in the Speccy report, and you have absolutely no AV software enabled at all.

The behavior you describe sounds like a display issue though, and I'd need to see the Dxdiag output to be able to tell if there are issues there. be sure to run the 64-bit version. (Also don't forget to use the CODE tag so that the post isn't a mile long.)​​

Try each of these steps if one after another fails.

1) Have you tried uninstalling and then installing the game again? Verification has been proven by myself to not catch corrupt installs sometimes.
2) Where is the game installed? If in "Program Files" or "Program Files (x86)", install it somewhere else.
3) Do you have ownership over the folder the game is installed in?
4) What is the exact date you started having problems? By any chance was it after getting a Windows Update? If so, rollback that update and see if it works.
5) If none of these suggestions work, I leave it to others to attempt to solve it​​

kittens92 wrote: »

Thanks for such a fast response. I never run any antivirus software (or anything like it) so I knew that wasn't an issue. How would I go about producing the Dxdiag output for you (I've never had to do it before)?

Bottom of this post: http://perfectworld.vanillaforums.com/discussion/comment/4564907/#Comment_4564907

---

As for the other things: The Program Files folder since Vista has had weird folder permissions that can cause very seemingly erratic behavior. This is why you don't want to install it there. You could also take ownership and that should serve the same purpose.

As for reinstalling in 3 hours. Sorry to pry, but may I ask why? Is it bandwidth limitations?​​

Stick the dxdiag output between [code] and [/code] or

For taking ownership, I'd recommend following the blue link in my other post and install the context menu option. Then select the folder PWI is installed in and right click "Take ownership".

---

I'm going to sleep right now because I was already in bed while typing all of this stuff out. Good luck and I'll be back in a handful of hours.​​

kittens92 wrote: »

Putting the output between

and

has it saying that the body is too long to post. The only other thing I can think of is posting each section separately

Oh yay, another way for the Vanilla forums to make things harder on us. use Pastebin and then just give us the link to it.
​​

Out of curiosity, can you see which video device it's trying to use? PWI doesn't use the GPU really, but you'd want it on the 710m instead of the crappy HD4000.

Don't see any DirectX issues offhand, but you might want to try running the DX9 installer from inside the PWI\element folder.

I'm also not seeing any of the audio/video codecs or handlers that are known to cause this type of problem.

So, in short, we've ruled out pretty much 98% of the usual causes for this issue, and if you re-run the DX9 installer, that makes it 99%.

Something else that is strange is that is suddenly occurred out of the blue, and was working just fine previously. the only thing I can really thing of is that the temps are a bit high, but for a laptop, they're still well within what I would consider a normal operating range. The system also isn't really old enough to be having an issue with the crappy heat transfer pads they use in laptops.

It's very rare for this to happen, but I'm currently at a loss.
I'm nearing the end of a 12-hour shift and I ran monthly backups on a bunch of systems with 7 PC's all night though, so I may have missed something that wasn't obvious.​​

Off the top of my head, to play the game with your Nvidia GPU instead of the crappy Intel HD, right-click on the game shortcut, select the "Run with graphics processor" menu, and then select "High-performance NVIDIA processor".

Seems like there's another method, but I cannot think of it right now, and for the life of me I can't get the search feature to find the threads with the answers.​​

kittens92 wrote: »

After nothing would work for me, I thought I'd try restarting my laptop. It's working fine again now!

I forgot the number one rule with troubleshooting. If at a loss for trying things, try resetting.

Anyways, glad it's working again. ​​