Freeze game

[lax]

It doesn't appear you've taken my suggestions to heart.

Your FPS settings are 60 foreground 30 background, and for all we know you've not attempted to lower it. Your CPU Strategy is Round-robin. If you're using the Round-robin CPU strategy and seeing hiccups in the rendering, then you're probably better off with all instances use all cores -- because then if it's an issue where the game is waiting on the CPU, it is possible for another CPU to pick up the slack.

So again my suggestion is to use the CPU Strategy Wizard. Set it to 30 foreground, 30 background, and set the drop-down at the bottom to all instances use all cores. I might even suggest 20 or 25 for both the foreground and background FPS instead of 30 in order to mitigate this issue.

It doesn't appear you've taken my suggestions to heart.

I take, but I didn't play today yet.

I share my current configuration for bob on his request and I'll do all as you wrote before I start play.

I play for a while, and get frozen screen again.

I thing I changed everything as you requested Lax, but I'll share my profile again for sure: http://privatepaste.com/06d908c22d

I also added folder Update1 where I added video and screenshots from process explorer.
I don't see any pick on my cpu/gpu/io images and I also added open hardware monitor screenshot, where I try monitor max value for cpu/gpu.

You can see one pick on io image, but it's from nvidia shadowplay and it's happen 13 seconds after frozen slot1.

[bob]

I'd remove Shadowplay for starters. There are numerous reported issues with Shadowplay and it's interaction with DWM (Aero) causing stuttering. Feel free to read about it on NVidia forums.

As I said earlier, shutting down and removing non-essential programs is a standard part of trying to figure out the cause (after making sure you do what Lax says of course). And by non-essential I mean anything other than Windows, required bare graphics driver, keyboard, mouse, sound, lan, and I guess for you HBA drivers, Innerspace, ISboxer, and your game, and no bloatware features of the prior items (which bit NVidia and AMD seem to be loading up their packages with these days). You can do it one by one, or try and go the whole hog all up front. If in doubt, fresh reinstall (a second drive is handy for this kind of thing), just to prove that it is not the hardware. As a Technical Guy you should be familiar with this normal drudgery of root cause analysis.

I'm back with this topic (after d3 buff ), because I made many tests and still don't know what's wrong.

First what I did:

With old win7 system:
- I optimized it (disabled svc, turn off programs) and the problem still exist
- update all hardware drivers - nothing happen
- update even bios at my motherboards, raid controller and nothing

I installed new win7 (default configuration) with this same hardware setup and:
- newest driver for LAN
- driver only for GPU (only driver, without other stuff like shadowplay)
...and nothing

I optimized this new system (disabled svc, turn off programs) and the problem still exist. (If I well remember I was have any ~30 running processes in memory)

I save crash and freeze file from isboxer, but.. save it at desktop and forgot move it before next reinstall

Ok, next reinstall was with hardware modification.
Remove Dell Raid controller, and use only one SSD drive directly connected to motherboard.
Install, default windows configuration, driver for LAN, GPU, and fail again.
I optimize this installation... and after test again fail.

Next reinstall:
Added second SSD drive and make raid0 with motherboard raid controller.
Win7, driver... test again.. fail.

Next reinstall:
Two SSD, raid0, but this time I try with win8.1
Default configuration - I didn't added any drivers, everything was installed.
Install diablo, isboxer, test and still nothing.. game hungs as before.

I start install many programs and check my system stability.
I play with OCCT, memtest, prime95 and few more.
Run test for many hours to check stability of my PSU, GPU, CPU - all test OK.
I thought make RMA for some elements but which? and what to write as a reason?

Ok, again reinstall with win8.1, raid0.
Newest drive only for GPU with shadowplay, few tips for win8.1 hardening and start play with sysinternals tools and make deeper look into my problem.

I added Update2 folder where you can find:

Slots folders with video where you can see my problem.
D3Debug files for each slot (you can compare times with time when slots are frozen). I don't know how interpret it

What I found interested is info about diablo3 process and registry.
I don't know why, but every time when particular slot stop working diablo3 process made ~1600 reads from registry.
It's happen only when game is frozen.

If you look at this image Process Acivity Summary.png

you can see small peak at registry events (don't look at one the biggest - it's my fault - I change headphone to my speakers)
I play at slot4 mainly in this example and data is from about 2.5h of my gameplay. That why Slot4 (latest d3 process) have largest numbers in File/Network events.

Here is summary activity only for Slot4:

As you can see on mouse cursor, there is a lot regisitry reads.

Now you should check how to looks Process Timeline for each slot - you can see registry read peak where time is exactly the same like on the next img DD_RUNTIME_VERSION.png:


Every time when diablo freeze slots in game it's start registry ready with this HKLM query and many (1681) others like on next image DD_RUNTIME_VERSION_long.png:


I added PML file with dump from my system if you want to look inside : short_logfile.zip - it's 15 sec before and 15 sec after one freeze.

I also added crash/freeze file from isboxer.

If any one can try help me interpret this info?
I don't know if I have problem with my comp or what?