LukeV1

Um, unfortunately disabling GLSL and/or setting everything to minimum/maximum/custom doesn't help (if sometimes GLSL is causing crashes, why does the tooltip recommend using it?). 0 A. D. seriously do not like that hardware. So I'll have to dive into debugging. Since the PC isn't actually mine but from a friend of mine, I'll have to convince him to install VS13 - this will probably take a few days the numa.h crash just seems to be the first sign of the underlying problem (game crash at loading a game) - and it has to do with memory size/allocation. I'll probably check if the numa-thing is connected with the strange output in the system_info.txt regarding RAM properties... Yeah, I will do this - but first I want a running 0 A. D. version. Maybe the problem isn't actually caused by this lines but by something in a lower layer (i. e. memory allocation) Right now I'm really focused on that memory thing without knowing that much about it - but to me it seems to be the most probable reason...

Pyrogenesis survived startup now! I've deleted all three "numa_"-lines (313-315) and 0 A. D. is starting now (first couple of times it crashed while loading fonts and textures, but then it worked). It also created a nice system_info.txt - where I noticed that HWdedect seems to have a problem with DDR4 RAM - i've got only 1 8GB module but it lists four (see appendix). For testing purposes I've skipped RunHardwareDetection() completely then (by adding a return statement as suggested) and 0 A. D. is behaving completely same. What means that those three lines are causing that error. Now I'm very interested in what this numa_-thing should actually do (starting with the question what numa should mean). Any idea? Unfortunately 0 A. D. still crashes if I try to start a game. It shows the map select menu but as soon as I hit play everything freezes after a second with a half-loaded map loading screen and windows displays it's obligatory "this program has stopped working" message. Sadly no crashlog file gets generated and the mainlog shows 0 errors (last entries are loading messages of simulation scripts). Thats pobably what you meant with Where can I change that (I guess its some kind of textfile)? Thanks, Luke system_info.txt

Did so, recompiled everything and - it still crashes. Now at the next line in HWDetect (which has become line 313 since I deleted the orignal one). I've appended the crashlog. BTW: you may update the wiki links for downloading VS 2013. The second link is totally broken and the first one points to the VS17 site. You may consider inserting this link: http://download.microsoft.com/download/7/2/E/72E0F986-D247-4289-B9DC-C4FB07374894/wdexpress_full.exe (taken from here) I'll probably try disabling the hardware detection completely, but at least to me this doesn't sound like a real solution crashlog.txt

Wow! Thanks for your fast response! I haven't thought that I would get an reply that fast. Tested r19876 and r18915 (Release of Alpha 21), both crashed as well - but quite differently to the actual version Both old versions created slightly differrent log outputs (not counting different adresses), see attachments... (Now you've got the machine name :D) Anything else I should test / upload?? crashlog_r18915.txt crashlog_r19876.txt

First of all: I'm new to this forum so I am probably posting things in the wrong forum or whatever. Apologize for any mistake Originally I wanted to create a ticket on trac, but unfortunately I never recieved a trac account activation email so I am not able to do so... Concerning my orignial problem: 0 A. D., Release 22 and the (currently) newest svn version 20096 crashes on startup. It displays a black screen and then a window of the error handler. I appended the generated crashlog of the svn version, the Release 22 crash is almost identical (can upload this as well if needed). The "interesting log" file is empty and the "mainlog" file shows just the configuration settings (maybe this is intended?). I guess the error is caused by faulty hardware detection, but I am no expert. You may be interested in my hardware (created with dxdiag): Hope you may help crashlog.txt