Hm, the repeated 'Debug Message: Popup Manager Update: Updating window with ID=34' seems a bit odd but that doesn't strike me as ample cause for a crash on its own.
For your CTDs, please install 'SmartException' from the free stuff section in Stardock Central. Make sure that SE is running and start your game as normal. If the game crashes it will generate an exception report that can be emailed to gc2bugs@stardock.com.
Include with the email a description of what you were doing at the time, how to reproduce the crash if possible, a zipped save if applicable when you send an SE log to gc2bugs, and the appropriate debug.err file for DL or DA. The devs cannot help if you do not provide these details!If SE does not automatically pop up and prompt you to send the report when the game crashes, you can find it at C:\Program Files\Stardock\SmartException (it will be the newest file with a .CRA extension).
A spontaneous reboot often means your computer is tossing a Blue Screen of Death but is set to not display it. BSODs are generally caused by hardware or driver problems, and the error message it shows can help pin down exactly what the issue is.
To have your computer display BSODs instead of rebooting immediately, go to Control Panel->System Properties->Advanced Tab->Startup and Recovery Settings and uncheck 'automatically restart'.
The next time it crashes, you may get a BSOD similar to the one below (not all highlighted parts may be present):
Write down the information in the highlighted areas before turning your computer off. The information there can then be researched online to see if others have experienced similar problems, and what the cause was. You may also get a 'windows has recovered from a serious error' message when you turn your computer back on--if you do this, you should agree to send the report to microsoft. You'll then be forwarded to information about that error on Microsoft's knowledgebase, if they have any.
