Hi Biel,
thanks for your report. I assume when you say "3.7.9" you mean "3.7.1"?
Do you have all the updates available for Windows 8 installed?
What exactly do you mean by "crash"? Do network games fail with an error message produced by the game, or do you only get a Windows message box saying something along the lines of "this application has run into an error and has been closed"?
Is a DMP file created in %ApplicationData%\megaglest\ (and is it current - if not, delete the one you have and reproduce the problem)?
Is an error.log files created in the same directory (and is it current - if not, delete the one you have and reproduce the problem)?
Does this happen in single player, too, or only in network games?
You say it happens quite randomly. The developers will need either a meaningful (often a problem is that the ones the application generates are not pointing to the actual problem - since this is not really always possible to get right) backtrace or a way to reliably (and as quickly as possible) reproduce a problem. If you can work towards providing either this would be quite helpful.
The error.log file may already contain a backtrace. The DMP file, if you have one, may allow for creating a backtrace. If you run the game from a cmd.exe command line you may receive more output which may help getting a better idea of what is going wrong (see the advanced section on the FAQ for details).
Finally, it would be good if you could also test the latest windows test / development build (no need to download the game data, it should be the same as that of 3.8.0 beta1), since those are actually built on the Windows 8.1 preview, which should not, but might make a difference.