Your screen shots show both the CPU and GPU topping out at 100%. Which would make me think that the issue is occurring when that is happening. I shall await the compatibility diagnostic....
/e ok, it was pointed out you provided one initially and I was too dumb to see it.
Other than the excessive amount of Anti Malware processes running, which might be indicative of something funky going on (and potentially bogging the bejesus out of your computer periodically), not much really shows up.
Last edited by mbox_bob : 09-16-2018 at 11:45 PM Reason: goober here didn't see the initial post.
Originally Posted by mbox_bob
My guess is I was rambling and you simply missed it in the original post =)
I'm trying to have everything that would be relevant so those like yourself who try to help have something to go by other than "it don't work! WAH!"
Re CPU/GPU utilization maxing at 100%: That only happens when I launch teams. After the clients initially load the utilization rarely hits:
RAM: 60%
CPU: 40%
GPU: 30%
As best as I can tell the resources aren't even being maxed when the crashes/freezes occur. In the background the logging still occurs and doesn't show anything unusual. That does give me a thought though. I'm going to reset OHM after I launch the team and see where it is when the issues next occur.
RE antimalware processes. Yeah I noticed that too and have been separately trying to figure out WTH is with it. It doesn't seem to affect anything at all. I'm considering a fresh install of Win 10 and WoW on a spare HDD and see if it shows that after all the updates and such.
/e crashed again, adding resource monitor from right after.
Last edited by WarcraftPundit : 09-17-2018 at 12:17 AM Reason: Added resource monitor from most recent crash.
Thanks so much to all who have replied and helped with this with the great ideas and suggestions!
After several days of testing with the proper power supply I have had only a single crash which was much easier to recover from. Though it acts very similarly with the slowing of the system until the offending WoW client is killed, it is not entirely unusable. I can live with an occasional crash.
The system remains stable with up to 24 hours straight of Prime95 and other stress testing. I've not had any errors so far in any such testing. Using HWinfo I see that the only error during this crash was CPU 0 DTS: Core #2 Power Limit Exceeded Yes. No other core showed this error. Possibly coincidental I have the CPU cores assigned to individual WoW clients in order. The third client is the one which crashed and that was assigned to CPU core 2, the third one.
Unless you are managing all your other background applications and OS functions to make sure they all stick to their cores (network IO / sound / keyboard and mouse input, and anything else that throws interrupts) are using the other cores, I'd suggest against doing that. You are effectively artificially limiting the game, and if the OS grabs your core for something else, your game is SOL and just halts.
As a general rule, you should stick to "All CPUs for All Games" in the CPU strategy wizard of ISBoxer (the last option in the drop down). There are very few reasons these days to limit the cores. This is also the same as just letting Windows, and the smart boffins that wrote the CPU Scheduler manage it (in fact there is another option in the CPU Strategy Wizard of select no CPU's, let windows do it, which is effectively the same as select all CPUs).
Also, it's not clear from what you wrote, but if you select them in order, 1, 2, 3, 4, 5, etc, in the performance tab in ISBoxer, every EVEN number is a hyper thread core, so that game, and the game on the previous odd number are running on the same physical core, but on the two logical cores for that physical. The "rule of thumb" is that a HT logical adds about 30% to the physical, so that would be 1.3 cores for each game. That is a tad limiting, and likely to cause them to run hot when they don't need to.
Posting Rules
Reply With Quote
Connect With Us