There seems to be an issue with the deployment screen - I was able to "produce" as similar effect on my machine - and it surely meets the minimum specs
CPU Typ AMD Athlon 64, 1800 MHz (9 x 200) 3000+
Motherboard VIA K8M800/K8N800, AMD Hammer
Sound VIA AC'97 Enhanced Audio Controller
RAM 1024 MB (PC3200 DDR SDRAM)
NVIDIA GeForce 6600 GT (128 MB)
W2k SP4rollerup
.. and it is rock-stable, normally. Only thing I have to watch out for a high temperatures ...
After "idling" the game for over an hour (sound enabled)with 100% CPU, what turns of the AMD Cool'n'Quiet, I had bought my forces and went into the deployment screen.
~15 minutes later, while re-assigning headquarters and looking at unit info screens, a small (5 pix?) strip of the background map was drawn streched out to the right screen edge, and the game nearly "froze". In fact, it ran extremly slowly (apart from the sound, which was ok IIRC). It took 3-4 minutes for the game to close the unit info screen (obviously, the mouse-click which I did after the "freeze" was properly registered). While the screen was re-drawn, the monitor de-synced for a split second.
For the whole time, the mouse pointer was 100% responding, but despite running in windowed mode I wasn't able to get either the task manager up or the game closed properly via any means - I guess everything
would have worked, if I had waited an hour or so. Did a hard reset.
Simply re-loaded the game, went into the deployment screen and everything was fine.
After a while, though, I noticed single pixel errors in the background of the unit info screens => graphics RAM getting too hot ?
CPU was @47°C, the GPU reached 52°C, what shouldn't be too much, though.
Case temp went to 40°C, due to the CPU running at full 1.8Ghz (instead of 1.0)
Sadly, I have no means to measure the temp of the graphic ram ... .
Edit: Dang! Just noticed I'm in beta-tester mode again, but I'm not a tester for this game at all ... 
Re: winspww2 crash to desktop after 5 mins
Threaded Mode