 | game not responding / d3debug.txt timestamp?(1) | Category: Technical SupportJune-27-2013 2:36 PM PDT (9 years ago)  |
| Hi, ever since patch 1.0.7 hit the realms, I've been trouble with my game client freezing/not responding. In the beginning not to often, but still scary since I play hardcore. Adjusted the hardwarelevel to 1 and video options to low (which I didn't have to do when D3 got out initially), but still sometimes crashing. When 1.0.8 went live, the frequency of 'game not responding' got worse and I lost a couple of characters. So I got an usb3 flash drive and migrated D3 to it. Initially it did help, but my game client has gone back to crashing every now and then. The d3 client crashed this time when I used the waypoint to get to the crystal collonade, started to move to the entrance of the next level, some of those shadow creatures spawn when I was near the entrance and then my game client frooze, followed by greying out the D3 window and showing (not responding) in the titlebar. Trying to find out why these crashes are occuring, I opened D3Debug.txt and saw that the logs last lines were <timestamp> Initializing client world a4dun_Garden3_SpireEntrance... <timestamp> Disposing UI for World I had been doing the same run for about 5 times, so I could compare what the log showed for a normal run and the part of the log at the time of the crash. Unfortunately, nothing out of the ordinary was shown (errors etc) and seeing how the file ends, leads me to think that logging stopped on the moment of the crash. The odd thing which I did notice was that the <timestamp> 's are not based on my computers clock, which is set by the system time service and connected to time.windows.com, but were at that point 2 minutes in the future. I'm guessing the timestamps are based on server time? What is even stranger, some 7 or 8 hours later (now), the difference is 20 minutes. The timestamps in my log say 23:53 and my computers time/the clock on my wall say it is still 23;33. (Though strange, I'm not sure if these time differences are related to my game client crashing.) I've reinstalled D3 about 8 times in the last month or so and no logs (d3debug.txt, application log and system log) show anything usefull on this situation and would appreciate any idea on what else I can do to get my game client to function in a normal way (and not crash). | ||
 | game not responding / d3debug.txt timestamp?(4) | June-28-2013 3:56 AM PDT (9 years ago) |
| Hello, Can you try going to your Diablo III folder, then the Data_D3, PC and then MPQs folder, and in here remove the Cache directory then try the game again? I also understand you've been looking into this issue, but we do also require that you check through the steps here: battle.net/support/article/diablo-iii-lockups-and-crash-troubleshooting-windows In addition, can you also reply back with an MSInfo file: battle.net/support/article/obtaining-system-files-301772 It'll be too long to fit on here, but you may be able to spread it across a few different Pastebin logs: http://pastebin.com/ | ||
