The usual path would be to shut down or uninstall any other programs that might be causing issues, and see if that improves it.
In your case, I would start by setting an exclude in you Antivirus from active/realtime scanning/protection on InnerSpace.exe and eqgame.exe. This is not the same as excluding from scanning altogether.
You might even want/need to uninstall your antivirus. This
article from MS, while long, explains some stuff about filter drivers and then in a small bit of text explains....
KB816071 wrote:Most antivirus software uses filter drivers that work together with a service to scan for viruses. These filter drivers are still loaded after the service is deactivated. These filter drivers scan files as they are opened and closed on a hard disk. For troubleshooting purposes, temporarily remove the antivirus software
Second would be to monitor your computer and see if there are any spikes, whether on the GPU/CPU/Memory/IO (disk/network), at the time of the failure. There is a basic process
here, but you will need to get further in depth for looking at IO if it comes to it. If you know how to use and understand the output of PerfMon and or ProcessMon that would help as these are the tools you may end up needing.
You might also consider removing anything you don't specifically need to play from the running active processes. Like UTorrent, GForceExperience, etc.
If this is a Windows 10 upgrade, did you update the Intel drivers too, including the chipset and storage items. These should be checked out.
Do you get crash reports? These should provide some kind of insight as to the failure point.
If not, you could use
Procdump to capture one if the game is not generating one (some games do hide them too).
- Code:
x:\folder\procdump -accepteula -e -t -ma -l -f "" -w "eqgame.exe" > x:\folder\procdump.log
You can run this at an Admin command prompt and it will wait for a crash of the named process and then it will write out logs and a memory dump.
The log file may provide some useful info. Otherwise the memory dump of the crash can be analysed with WinDbg or similar to see if you can get a stack trace out of it. Failing that, you can upload it to
http://www.osronline.com/page.cfm?name=analyze and it might give you an indication (although the feedback there is not always the best).
If your dump is too big to be analysed online, you can try the -mp switch instead of -ma, or remove the -ma switch completely. This switch is to dump the complete memory of the crashing process, so is not really needed for a basic stack trace
Sun Sep 20, 2015 6:24 am 
