I took a Procmon trace. There are multiple events with “NAME NOT FOUND” and “FILE LOCKED WITH ONLY READERS”, but all the way at the end there is one event “NAME COLLISION” for the path"C:\Users\xxxxxx\Documents\Diablo II\Settings". I am assuming it’s trying to do something with this folder and running into an issue and cannot proceed. I then tried changing the path of my Documents folder to something else in Registry, and D2R is now using the new path but still generating the “NAME COLLISION” event for the new path.
@Blizz - let us know if you need Procmon traces and crash dumps.
Turtlezorg,
Moved you to your own thread to keep the other one more linear while we look into your situation. That’s an interesting crash. Do you have onedrive active for your documents folder? (It’s enabled by default on windows 10.) If so, what happens when you revert your registry changes then disable it?
Hey Drakuloth,
I just created a brand new local user account and still the same issue. This new user account has the default location of the Documents folder. The OneDrive systray icon is showing “Not signed in” - I’m guessing it’s not syncing anything. I think I’m having the same issue as everyone else, I just provided a bit more info.
Let me know if you want me to collect more data for you or join a live Discord/WebEx troubleshooting session.
It’s definitely possible that you’re having the same issue as everybody else, but this information was similar to reports we’ve had with other games in the past so seemed somewhat unique. Can you email your logs to the following place for me?
Edited - this previously requested information, but it’s no longer necessary. Thanks for the reports.
Just sent an email with Procmon trace, DxDiag, and Event Viewer > Application.
Will try installing and launching it on a 3rd desktop where the Beta had not been installed. The 1st and 2nd desktops that are crashing both had the beta installed.
Hey again Turtlezorg,
I checked over your files as well as those from the rest of the thread. For the time being I think you’re right that you’re having the same issue as the rest. Keep an eye on the other thread for more information, and if whatever we post there later doesn’t fix you up please poke me at this thread.
Sounds good.
FYI, just installed it on a 3rd desktop (totally different hardware from my 1str and 2nd), and same issue.
I was able to capture a crash dump of D2R.exe - it’s about 50 MB zipped - let me know if you’d like to upload it somewhere. This could be helpful to the devs. I will try to email it now but afraid the file is too large.
1 Like
I’ll let you know, they’ve got some ideas atm so they’re investigating. Appreciate the help!