One of the slot freeze after new patch

[lax]

At this point I definitely do not need more freeze dumps, they are not providing useful information in resolving or reproducing the issue.

The only diagnostic information I want at the moment is DirectX debugging as detailed in a previous post:

If anyone happens to have the DirectX SDK installed in order to turn on DirectX 9 debugging (yes 9 not 10 or 11, yes even if you're on Windows 7, 8, or 8.1), it's possible that DirectX will provide some useful error information. (This requires both installing the SDK, and having a debugger or DebugView in order to see the error messages)

And of course, I will keep working on reproducing this issue which would go a long way in getting it fixed...

I'll try help you - this freezes are very annoying ;/

I just installed SDK, enabled option "Use Debug Version of Direct3D 9" and run DebugView but nothing capture.
How I should setup this two programs?

I also experiment the "freeze" thing (not very often tho). Oddly enough, when this happen, I can still control the character (with the repeater) meaning he still moves, casts, does what he has to... just when I switch to that window it's frozen (he can't move, cast spell, or pick an item on the ground). I have to kill that window (from task bar) and start it again.

Also I believe it did't happen during the first days of loot 2.0, it began several days after (Blizzard did several hotfixes in the meantime). I guess this doesn't help much, but still

[lax]

Well, it's interesting that only a handful of people are getting this issue. So far I have been unable to reproduce it.

It might be possible to solve by uninstalling/reinstalling drivers, windows updates, or directx updates, or possibly even disabling custom settings in the NVIDIA Control Panel. It definitely seems that something is different on your PCs than mine (or anyone else not getting the issue)...

I also wouldn't be surprised if it would be solved with a clean Windows install, but I'm not expecting all of you to try that. (If someone wants to do it and report back, that would be useful though.)

Well, it's interesting that only a handful of people are getting this issue. So far I have been unable to reproduce it.

It might be possible to solve by uninstalling/reinstalling drivers, windows updates, or directx updates, or possibly even disabling custom settings in the NVIDIA Control Panel. It definitely seems that something is different on your PCs than mine (or anyone else not getting the issue)...

I also wouldn't be surprised if it would be solved with a clean Windows install, but I'm not expecting all of you to try that. (If someone wants to do it and report back, that would be useful though.)

I think it's more a hand full of people that is posting here. I still have the problems and it' slightly getting annoying, but i can live with it. Watching the streamer It'spokey has the same problems and so does his people in hit chat. He multiboxes 4 accounts.

I asked him to post also as he has vid logs and tried alot to sort it for his stream.

Not expecting wonders Lax i have not much time to help atm due to work sorry.

[MiRai]

I've also been trying to help Lax with this issue, but just as him, I can play for hours upon hours w/o a single issue at all. So, to the handful of people who have this issue... You can either deal with it, or you step up and follow his directions in the post above to help out. Here's a quick video I made outlining how to do this:

http://youtu.be/7xUM6y8hi3Q

Relevant Links:

DirectX SDK http://www.microsoft.com/en-us/download ... px?id=6812
DebugView http://technet.microsoft.com/en-us/sysi ... 96647.aspx

You don't need a vast amount of programming knowledge to install these two programs, change two settings, and let a debugger run in the background while you play the game and wait for a freeze. When it freezes, save the log file and send it to Lax.

Well, it's interesting that only a handful of people are getting this issue. So far I have been unable to reproduce it.

It might be possible to solve by uninstalling/reinstalling drivers, windows updates, or directx updates, or possibly even disabling custom settings in the NVIDIA Control Panel. It definitely seems that something is different on your PCs than mine (or anyone else not getting the issue)...

I also wouldn't be surprised if it would be solved with a clean Windows install, but I'm not expecting all of you to try that. (If someone wants to do it and report back, that would be useful though.)

I'm running on a fresh install of W7.

[lax]

Well, it's interesting that only a handful of people are getting this issue. So far I have been unable to reproduce it.

It might be possible to solve by uninstalling/reinstalling drivers, windows updates, or directx updates, or possibly even disabling custom settings in the NVIDIA Control Panel. It definitely seems that something is different on your PCs than mine (or anyone else not getting the issue)...

I also wouldn't be surprised if it would be solved with a clean Windows install, but I'm not expecting all of you to try that. (If someone wants to do it and report back, that would be useful though.)

I'm running on a fresh install of W7.

That helps.

Which version of Windows 7? (Home Premium?)
Do you have Windows 7 Service Pack 1 installed?
Latest windows updates?
Latest video drivers?
What is your video card?
Can you get me "Diagnostics for game crashes" (yes that one) from ISBoxer's Help menu? (http://isboxer.com/wiki/Diagnostics)

All right, steppin' up.

I got the log. Two kinds of errors came up while it was frozen.

Freeze time - 7:57:34
00124786 7:57:35 PM [9376] Direct3D9: (ERROR) :BitBlt or StretchBlt failed in Present
00124787 7:57:35 PM [9376]
00124788 7:57:35 PM [9376] Direct3D9: (ERROR) :BitBlt or StretchBlt failed in Present
...
Then:
00124838 7:57:36 PM [9376] Direct3D9: (ERROR) :Failed to lock driver vertex buffer
00124839 7:57:36 PM [9376]
00124840 7:57:36 PM [9376] Direct3D9: (ERROR) :Vertex buffer in stream 0 must be unlocked during drawing
00124841 7:57:36 PM [9376]
00124842 7:57:36 PM [9376] Direct3D9: (ERROR) rawIndexedPrimitive failed.
00124843 7:57:36 PM [9376]
00124844 7:57:36 PM [9376] Direct3D9: (ERROR) :Vertex buffer in stream 0 must be unlocked during drawing
00124845 7:57:36 PM [9376]
00124846 7:57:36 PM [9376] Direct3D9: (ERROR) rawIndexedPrimitive failed.
...
Ran ISBoxer to get the admin prompt at 7:57:53.
00208772 7:57:53 PM [4436] Direct3D9: (ERROR) :Lost due to display uniqueness change
00208773 7:57:53 PM [4436]
Left for 10 seconds, then clicked "no" to cancel and free up display:
00208774 7:58:03 PM [8892] Direct3D9: (ERROR) :All user created stateblocks must be freed before ResetEx can succeed. ResetEx Fails.
00208775 7:58:03 PM [4436] Direct3D9: (ERROR) :All user created stateblocks must be freed before ResetEx can succeed. ResetEx Fails.
00208776 7:58:03 PM [9376] Direct3D9: (ERROR) :All user created stateblocks must be freed before ResetEx can succeed. ResetEx Fails.
00208777 7:58:03 PM [8892]
00208778 7:58:03 PM [4436]
00208779 7:58:03 PM [9376]
00208780 7:58:03 PM [8892] Direct3D9: (ERROR) :ResetEx failed and ResetEx/TestCooperativeLevel/Release are the only legal APIs to be called subsequently
00208781 7:58:03 PM [4436] Direct3D9: (ERROR) :ResetEx failed and ResetEx/TestCooperativeLevel/Release are the only legal APIs to be called subsequently
00208782 7:58:03 PM [9376] Direct3D9: (ERROR) :ResetEx failed and ResetEx/TestCooperativeLevel/Release are the only legal APIs to be called subsequently
00208783 7:58:03 PM [8892]
00208784 7:58:03 PM [4436]
00208785 7:58:03 PM [9376]
00208786 7:58:03 PM [1336] Direct3D9: (ERROR) :All user created stateblocks must be freed before ResetEx can succeed. ResetEx Fails.
00208787 7:58:03 PM [1336]
00208788 7:58:03 PM [1336] Direct3D9: (ERROR) :ResetEx failed and ResetEx/TestCooperativeLevel/Release are the only legal APIs to be called subsequently
00208789 7:58:03 PM [1336]
00208790 7:58:03 PM [9376] Direct3D9: (INFO) :Using FF to VS converter
00208791 7:58:03 PM [9376]
00208792 7:58:03 PM [9376] Direct3D9: (INFO) :Using FF to PS converter
00208793 7:58:03 PM [9376]
00208794 7:58:03 PM [1336] Direct3D9: (INFO) :Using FF to VS converter
00208795 7:58:03 PM [1336]
00208796 7:58:03 PM [1336] Direct3D9: (INFO) :Using FF to PS converter
00208797 7:58:03 PM [1336]
00208798 7:58:03 PM [8892] Direct3D9: (INFO) :Using FF to VS converter
00208799 7:58:03 PM [8892]
00208800 7:58:03 PM [8892] Direct3D9: (INFO) :Using FF to PS converter
00208801 7:58:03 PM [8892]
00208802 7:58:03 PM [4436] Direct3D9: (INFO) :Using FF to VS converter
00208803 7:58:03 PM [4436]
00208804 7:58:03 PM [4436] Direct3D9: (INFO) :Using FF to PS converter
00208805 7:58:03 PM [4436]
00208806 7:58:17 PM [1336] Direct3D9: (WARN) :Static index buffer locked more than once per frame. Could have severe performance penalty.
...
and it's now back to the usual warnings.

Attached the full log file.

[lax]

That does provide some insight, thank you!

I will see what I can dig up ASAP.