If it's some other process or service then you'll have to google for the solution yourself.
I case of launcher leak you can opt to close it when game starts as a temporart solution. If it's indeed Diablo III or Blizzard launcher then I suggest you ask Blizzard support and they'll probably ask you for a DXDiag dump. Once you've confirmed which process is leaking you can start searching for the solution. Process Explorer is a bit better, IMO, as it shows parent-child relations between processes and you don't have to wonder which process spawned that nasty conhost.exe that ate all the memory.
Once your PC starts lagging, at least run Task Manager (or Process Explorer if you prefer it) and confirm which particular process takes all the memory. Not sure what's the root cause, but it seems like you haven't done your initial investigation properly. Last updated at 14:00:17 UTC Weekly Help Desk RAGE Loot Thread Trade Thread
0 kommentar(er)
