 |
Can you try to enable crashdumps for all applications? https://www.meziantou.net/tip-automatically-create-a-crash-dump-file-on-error.htm This should always create a dump when DR is crashing. It might be possible that the crash is AMD related, since I've been getting reports on the forums about two AMD users not being able to run 3.2.0 |
|
|
As for beta testing, there's no real test run anymore, and I'm considering not continuing these at all. These beta tests have been exhausting and time-consuming. If you want to help test DR development, the closest thing is to just grab the latest snapshot from the Github pages when I push something to the master branch. It might have some glitches here and there, but I don't plan on push any breaking changes where things are broken for weeks and months. |
 |
Am currently trying to get WER to work via the above link, as atm its not creating dump files. And to make matters worse now 3.10 is CTD'ing for no aparent reason, where is was stable and solid. I am begining to wonder if a recent windows updates that were installed on the 14/09/22 might to blame - - KB5017022 - Services stack 10.0.19041.1940 - KB5017308 |
|
|
On the 3.10 CTD's, checking event viewer I am seeing 2 distinct errors - "A TDR has been detected. The application must close. Error code: 7 (pid=7196 tid=4604 darkradiant.exe 64bit) Visit http://nvidia.custhelp.com/app/answers/detail/a_id/3633 for more information." and "Faulting application name: DarkRadiant.exe, version: 3.0.0.0, time stamp: 0x6301eb00 Faulting module name: DarkRadiant.exe, version: 3.0.0.0, time stamp: 0x6301eb00 Exception code: 0xc0000005 Fault offset: 0x00000000000237e3 Faulting process ID: 0x12f4 Faulting application start time: 0x01d8ccc655761aa4 Faulting application path: C:\Program Files\DarkRadiant\DarkRadiant.exe Faulting module path: C:\Program Files\DarkRadiant\DarkRadiant.exe Report ID: 915ae6fe-37d3-4ab5-a494-704b69bd8431 Faulting package full name: Faulting package-relative application ID: " Regarding the first error, the nvidia support article is saying that windows "Increase the timeout value to allow more time to complete more intensive rendering." I have no idea WTF the second error means. I will now install DR 3.2.0 and see if I am seeing the same above errors. dr310ver.jpg (90,603 bytes) |
|
|
Updated the nvidia driver to 516.94 and installed DR 3.2.0, same openGL TDR error, going to the nvidia support link to see what reg entry I need to tweak to see if it stops the CTD's. tdr_error.jpg (195,081 bytes) |
|
|
Still happening so dug down into the following thread - - https://answers.microsoft.com/en-us/windows/forum/all/increase-time-out-limit/e979e2ad-e15f-450b-9818-a148cbf01078 Which then pointed me to - - https://www.nvidia.com/en-us/geforce/forums/discover/149264/opengl-driver-lost-connection-error-7-/ I then remembered I am running a custom voltage curve via Msi Afterburner, so have disabled that to see if that was what was causing the OpenGL TDR error. |
|
|
With the custom voltage curve removed DR 3.2.0 was once again stable, I was able to map for a few hours with no crashing. So I would say that this tracker can be closed. |
- Anonymous
