Freezes

[pazgaz]

Hello,

I returned to wow boxing after about 3 years last week.
I'm having MAJOR freeze issues... WoW hangs (all instances) but mouse and sound are still active. After a few seconds mouse is not active either and it takes anywhere between 20 seconds to 2-3 minutes till the PC unfreezes.
5960x with 32gb ddr4 and a 290x. All water cooled so temps are not an issue. Game is installed on a SSD.
Tried:
Changing drivers to beta and to pre-crimson version.
Reducing all instances to low.
Disabling all addons except isboxer.
Updating SSD firmware.
Disabling crossfire.
Reducing wow resolution to 1080p (was 1440p before)
When the game is running I get constant 60 fps on master and 30 on slaves.
Not using monitor swap (all running on the same 4k monitor).
I was able to 5 box in MoP with a 2600k and a 6970 without any issues.


Edit:
Also tried 64bit IS with 64bit wow and 32bit IS with 32bit wow.
I am also able to 4 box diablo without any issues.
I am also able to single box WoW at max details @ 4k without any issues.

[MiRai]

Can you replicate this issue with only one Slot from your Character Set loaded? Or two? Or three?

[pazgaz]

I''ll try. this will take time

[pazgaz]

1 char - smooth
2 chars - smooth
3 chars - smooth
4 chars - smooth
5 chars - small drops almost immediately... playing a bit more with 5 till i get a major (at least 5 seconds) freeze.

[bob]

Have you supplied a diagnostic previously?

[pazgaz]

http://pastebin.com/uxrDMcVd

[bob]

For starters, you are running x86 InnerSpace and x64 WoW. You probably have ticked the "Use 64-bit Inner Space" option in your ISBoxer Profile, but you should really try and load x64 InnerSpace.exe too.
This can be found in "C:\Program Files (x86)\InnerSpace\x64\InnerSpace.exe" You might want to update your desktop shortcut, which by default points to x86 InnerSpace.exe.

You should also try without the following things running

Code:

32. FCDBLog.exe - Process ID: 2652 (C:\Program Files (x86)\Fortinet\FortiClient\FCDBLog.exe) [Admin:NO] [x86] [5.2.4.0650] [Fortinet Inc.] [FortiClient Logging daemon]
33. FCHelper64.exe - Process ID: 5156 (C:\Program Files (x86)\Fortinet\FortiClient\FCHelper64.exe) [Admin:NO] [x64] [5.2.4.0650] [Fortinet Inc.] [FortiClient System Helper]
34. FortiESNAC.exe - Process ID: 2780 (C:\Program Files (x86)\Fortinet\FortiClient\FortiESNAC.exe) [Admin:NO] [x86] [5.2.4.0650] [Fortinet Inc.] [FortiClient Network Access Control]
35. FortiSSLVPNdaemon.exe - Process ID: 2788 (C:\Program Files (x86)\Fortinet\FortiClient\FortiSSLVPNdaemon.exe) [Admin:NO] [x86] [5.2.4.0650] [Fortinet Inc.] [FortiClient SSLVPN daemon]
36. FortiTray.exe - Process ID: 5228 (C:\Program Files (x86)\Fortinet\FortiClient\FortiTray.exe) [Admin:NO] [x86] [5.2.4.0650] [Fortinet Inc.] [FortiClient System Tray Controller]
45. Samsung Magician.exe - Process ID: 7060 (C:\Program Files (x86)\Samsung\Samsung Magician\Samsung Magician.exe) [Admin:YES] [x86] [4.9.0.140] [Samsung Electronics.] [Samsung Magician Application]
71. update_task.exe - Process ID: 3504 (C:\Program Files (x86)\Fortinet\FortiClient\update_task.exe) [Admin:NO] [x86] [5.2.4.0650] [Fortinet Inc.] [update_task]
72. vmnat.exe - Process ID: 2392 (C:\Windows\SysWOW64\vmnat.exe) [Admin:NO] [x86] [12.0.0 build-2985596] [VMware, Inc.] [VMware NAT Service]
73. vmnetdhcp.exe - Process ID: 2400 (C:\Windows\SysWOW64\vmnetdhcp.exe) [Admin:NO] [x86] [12.0.0 build-2985596] [VMware, Inc.] [VMware VMnet DHCP service]
74. vmware-authd.exe - Process ID: 2852 (C:\Program Files (x86)\VMware\VMware Workstation\vmware-authd.exe) [Admin:NO] [x86] [12.0.0 build-2985596] [VMware, Inc.] [VMware Authorization Service]
75. vmware-usbarbitrator64.exe - Process ID: 2868 (C:\Program Files (x86)\Common Files\VMware\USB\vmware-usbarbitrator64.exe) [Admin:NO] [x64] [15. 1.6.2977871] [VMware, Inc.] [VMware USB Arbitration Service]


For Samsung Magician, I suggest uninstalling it. There has been a previous case where this caused all sorts of grief. I think I'd try this out first.

Are you using a wireless network?? If so, try wired.

Is your InnerSpace out of date? I can see your ISBoxer is an older version. The newer InnerSpace may work better with Windows 10. ISBoxer itself wont matter, but InnerSpace will.

Have you disabled your swap file? If so, re-enable it. It doesn't need to be large, but at least 1GB is required (personally I use 1GB fixed on the OS drive and 4GB fixed on the secondary drive).


Other than the above, there is nothing else really that comes to mind, and would probably end up being a case of some deep monitoring using PerfMon. From your description of the freezes, if there is no obvious activity occurring from another process, then it sounds like a driver incompatibility somewhere, which would probably require some mini dumps during a freeze to debug (one of the reasons why above I suggest you remove Samsung Magician).

[pazgaz]

Thanks!
I only installed Samsung magician to update the SSD's firmware. The freezes were there before. Also tried shutting down forticlient but that didn't solve it either, I will prevent it from starting with windows since I got a laptop from work and don't use my PC to remote connect to the office any more.
I did not try shutting down the VMWare processes, will do so now and see if it has any effect.

[pazgaz]

Changed IS to 64bit.
No VMWare, Samsung Magician and FortiClient and still acting up:
http://pastebin.com/FMrpsa4Z
Anything else I should try to shut down?

[bob]

That was pretty much it from what there is listed.

You are now officially in the looking into deeper stuff territory, which usually consists of making sure things are plugged in the correct places in the motherboard, verifying the settings of the UEFI/BIOS (e.g. make sure you aren't doing something silly like running PCIE Gen1 on the GPU port - some MB's have this switching capability), verifying low level drivers are correct, checking for incompatibilities in the hardware, running perf tests/traces to verify that each item is responding under load (disk I/o tests are always great). Unfortunately WoW doesn't come with perf counters, so it is a bit of a black hole.

Most people give up at this point and instead do a clean install of Windows, and end up updating all their drivers at the same time. I tend to do the above so I know what the issue is, but then that comes the day job, where it is necessary to prove the fault to determine whether you have 1 server or 1000 servers to fix.