[d1x/d2x 0.60 beta 2 - Windows] Game won't launch
#21
Thanks for the quick reply. The debug text files, gamelog.txt, stderr.txt, and stdout.txt were all empty but their dates kept getting updated each time I hung the program.

I found a program that triggered a system crash recommended on the nVidia site and used that to generate a complete memory dump while Descent Rebirth hung in the background. I'm uploading the RAR compressed version (as advised) of the memory dump as well as the 8 GB original to google drive. I'll leave it there until I hear back that you've downloaded either version you prefer. I'll post a new reply when it's available.

Thanks again!
Reply
#22
Here's the Memory dump, I figured my laptop would do your bandwidth the least amount of damage. Since my desktops dump would be 32GBs...

Uncompressed: MEMORY.DMP (8GB)
Compressed: MEMORY.RAR (2GB)
Reply
#23
Hello. First of all, THANKS! for all of your work. Me and my friends have also experienced the issue where v60 stops working after windows update 1809. We have copied over the v58 libphysfs.dll, so thanks for that as well. However, I noticed that earlier in this thread, if I understood correctly, you mentioned that the latest version of PhysFS has a fix for this issue. Therefore, I was wondering if you would be so kind as to post an that updated (v3 ?) dll so we can download and use the latest and greatest version of the dll. If that would be possible, it would be much appreciated. And again, thanks for all your work.
Reply
#24
@ChrisHale: indeed, the reduced size is appreciated. While I can work with a full system dump, I was actually hoping for just an application dump, which would be much smaller. It will be a few days before I can spare the bandwidth, even so. Before I fetch it, I should warn you that potentially anything that was in memory on that system since your last reboot might be in the dump. If you did anything sensitive, you might want to purge that dump, boot clean, and produce a new one. (This is the other reason I prefer application dumps: they show me only what you did in the game, so I don't have to worry about stumbling into personal data from other programs.)

@kaiju: I believe the latest physfs source has a fix, yes. I don't post binaries of anything Windows-related. That is all on A Future Pilot. I'm not aware of anything in physfs 3 that you would likely care about though, so if the physfs 2 from 0.58.1 works for you, you can continue using that.
Reply
#25
I can try an application dump but I'm not sure how to set that up. As for security, I don't use the laptop for too many things so that should be fine, but I'll take it down after you've grabbed it just to be sure. =)
Reply
#26
Quick update: I tried the 0.60 release on my work computer since it has an older version of Windows 10 and it's working fine with Version 1709 Build 16299.847.
Reply
#27
The last time I did application dumps on Windows was when Dr. Watson was available. I think that is not available for a few Windows versions now. I'll try to get the dump soon.
Reply
#28
I have the dump locally. I won't be able to look at it for a couple of days yet, but you can make it private or delete it from Google Drive, at your preference.
Reply
#29
I have exactly same problem at 3 of my computes that running latest version of Windows 10.
Can provide you dumps and feedback if you explain me how to dump data or ask questions you want about dxx crash
Reply
#30
ChrisHale: I finally had time to try to work on this. I regret to report that there is nothing I can do, because the debugger refuses to open the dump file and instead reports "The parameter is incorrect." I found reports of this from 2007, but none are clear as to the cause or the solution. Since I can't open it, I can't see what's wrong.

sovietotaku: thank you for the offer. Could you collect a usermode dump (not a kernel dump, as ChrisHale offered) and make it available to me?

During my digging for the debugger problem, I was reminded of ProcDump, which purports to be able to capture the failure at the right time. I haven't used Windows in a long time, so I'm a bit unclear on the state of the art for capturing these problems. I think anyone trying this wants to follow the hung window example:
Code:
Write a mini dump for a process named 'hang.exe' when one of it's Windows is unresponsive for more than 5 seconds:

C:\>procdump -h hang.exe hungwindow.dmp
In our case, procdump -h d2x-rebirth.exe d2xhang.dmp. If the program is crashing instead of hanging, you might try procdump -mp -e d2x-rebirth.exe.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)