screen freeze

[ax0lotl]

While playing, my screen freezed. Sound was still OK. Then I alt-tabbed to see if there was an error message in an underlying screen, there was not. I alt-tabbed back, and the screen was black, with an FA cursor, that did change (to assist-icon etc.) when apparently moving over stuff (i could move the cursor).
I have had this once before, 2 days ago. Then I could open chat and type stuff (in the blind), which, I later saw in the replay, was there and seen by my opponent. This time I may have pressed Enter twice, did not know if I was in chat window, so no chat this time.
I played 8 games in between without any problem.

Nothing special to see in the event viewer.

Windows 8.1 64 bits
Core i5 3350P
AMD/ATI Radeon HD 7850
Graphics driver version 13.251.0.0

The graphics driver was updated on 19/1. I'm afraid that that is the culprit. It is the latest version available.
First screen freeze at 21/1.
I deleted C:\ProgramData\FAForever afterwards at 21/1, so fresh automatic install in that directory.
After that played 8 games without problem.
Second screen freeze today at 23/1.

Replay numbers of problematic games (replays don't replicate problem):
1784234 - Waters of ISIS R001
1777464 - Fields of Thunder V2

game.log: http://pastebin.com/wzyzHL6D
forever.log: http://pastebin.com/dvBrssJE

Is the display driver indeed the problem?
I have done a rollback of the display driver to the previous version now, 13.152.1.8000. Let's hope that that solves it...

[Ze_PilOt]

Is the display driver indeed the problem?
I have done a rollback of the display driver to the previous version now, 13.152.1.8000. Let's hope that that solves it...

Check your log, it's filled with DirectX drawing errors, most likely a driver problem.

[ax0lotl]

Aha. I assume you're referring to
[warning: c:\work\rts\main\code\src\libs\gpggal\DeviceD3D9.cpp(937) Invalid call]

c:\work is a directory I don't have, I assume that that path is a default value.

I now, so with the older driver, did a test with the same map in sandbox, and this time in the game.log those warnings were not there. Looks good.
Thanks for your help.

[Ze_PilOt]

It's a debug message. The path is the path of the guy who compiled FA. But it's still related to a directX error.