Crash to Desktop on 2.2.1 Release

[Buginator]

Had my first crash on Alpha 1 with 2.2.1 after updating my vid driver this morning, specifically after taking out the third scavenger base and scrolling back up to view said area.

It is still crashing in the video driver.

[Kamikazee]

.es and .gam aren't supported here. So i can't upload them...
So: http://www.megaupload.com/?d=Z4UW1KNZ That is the .es file
And this is the .gam file: http://www.megaupload.com/?d=7E58EQM2


Here is the savedgamename directory: http://www.megaupload.com/?d=VS0TLFT0

[Thyranim]

you can zip the files and upload the zip-file here

[Kamikazee]

Yeah, woulda been a smarter thing to do, just takes me a while you know?

[Jonas]

It is still crashing in the video driver.

Huh, and that's with theJune 18th 2009 release of it as found Here. Is there anything else I can try that might help?

[vsk]

Hi!

I post in this thread, because I got similar problems. Game ends without any message. In the RPT-file I found

"D:\Warzone 2100\warzone2100.exe caused an Access Violation at location 0040506c in module D:\Warzone 2100\warzone2100.exe Reading from location 00000000."

I monitored the game the second time with processmonitor:

Code: Select all

18:03:37,5019681	warzone2100.exe	2668	RegQueryValue	HKLM\System\CurrentControlSet\Services\TSDDD\Device0\Attach.PrimaryDevice	NAME NOT FOUND	Length: 130
18:03:37,5019767	warzone2100.exe	2668	RegQueryValue	HKLM\System\CurrentControlSet\Services\TSDDD\Device0\Attach.ToDesktop	NAME NOT FOUND	Length: 130
18:03:37,5019882	warzone2100.exe	2668	RegCloseKey	HKLM\System\CurrentControlSet\Services\TSDDD\Device0	SUCCESS	
18:03:37,6422530	warzone2100.exe	2668	Process Exit		SUCCESS	Exit Status: -1073741819, User Time: 159.8437500, Kernel Time: 136.0312500, Private Bytes: 73.732.096, Peak Private Bytes: 73.793.536, Working Set: 64.393.216, Peak Working Set: 64.491.520
18:03:37,6422963	warzone2100.exe	2668	CloseFile	D:\Warzone 2100	SUCCESS	
18:03:37,6423857	warzone2100.exe	2668	CloseFile	D:\Warzone 2100\stdout.txt	SUCCESS	
18:03:37,6425055	warzone2100.exe	2668	CloseFile	D:\Warzone 2100\stderr.txt	SUCCESS	
18:03:37,6426024	warzone2100.exe	2668	CloseFile	C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.5512_x-ww_35d4ce83	SUCCESS	
18:03:37,6426840	warzone2100.exe	2668	CloseFile	D:\user\Warzone 2100 2.2\netplay.log	SUCCESS	
18:03:37,6429083	warzone2100.exe	2668	CloseFile	D:\Warzone 2100\warzone2100.RPT	SUCCESS	
18:03:37,6441982	warzone2100.exe	2668	CloseFile	D:\Warzone 2100\warzone2100.exe	SUCCESS	
18:03:37,6448008	warzone2100.exe	2668	CloseFile	D:\Warzone 2100\music\track2.ogg	SUCCESS	
18:03:37,6448681	warzone2100.exe	2668	CloseFile	D:\Warzone 2100\fonts\DejaVuSans.ttf	SUCCESS	
18:03:37,6449413	warzone2100.exe	2668	CloseFile	D:\Warzone 2100\fonts\DejaVuSans-Bold.ttf	SUCCESS	

Computer Hardware, OS `n Stuff

• Windows XP SP3
  Intel C2D E6850
  XFX Ge7900 GTX
  2 GB RAM
  Comodo Internet Security

[CaptainSteveP]

I have the same Problem. Game was running for 2 hour than it terminates itself and go back to desktop. Errorlog is on the end.

warzone2100.RPT

[Daywalker]

Same problem here, also custom maps are slowing down up to unplayable (tested various drivers - all the same), campaign is working fine not yet through (22) but crashing from time to time and often crashes when using the research information (where the newly researched features and the campaign tasks are explained).

[Per]

Research information - true, this part of the code is extremely poorly tested. I guess us developers never use it.

Unfortunately, the RPT file posted above does not contain debug information. So it tells us nothing.

[EHThripshaw]

Hey there,

Just started playing after stumbling upon you guys in a reddit article. Which is ironic since me and my friend were just sitting in an ice cream shop discussing how awesome this game was when we used to LAN it in retail haha.

But anyhoooo we just all got it last night and started downloading it and played it. I was keeping my fingers crossed that the game would run in Vista 64 and sure enough it performs beautifully.

Although I did get an instant crash to desktop IF I ran a skirmish with 7 AI comps and the game goes to a white screen and becomes unresponsive. I just clicked around a few times and started building my command center. So I thought maybe I had too many AI opponents and it just crashed on AI calculations or something.

So we started a multiplayer and were playing against 3 AI opponents with 3 humans and got into a very prolonged game (about 2 hours) and we were winning then at the ~2 hour mark I got the crash again to a white screen with the *not responding* vista dialogue. This time however I chose to wait and see if it kept responding. I was on ventrillo and both my mates said I was still in game and I did not do the self destruct when a player leaves. So I went to brush my teeth and after about 3 minutes it FINALLY completely crashed and lo and behold

"Your Nvidia display driver has encountered a problem with OPENGL and was forced to close" and a bubble had popped up saying the display driver had crashed and recovered.

So I was wondering if this was the same crash as if I do click and do the generic this is not responding it seems to be a crash with no error output. It will not tell you the display driver has crashed UNLESS you let it stand and finish crashing.

So I think this may be some more evidence that it is perhaps a driver issue.

Comp

Vista 64 home premium
8 GB RAM
E8600
EVGA 9500GT

I have the latest driver from Nvidia got it as soon as it was released.

Perhaps we are experiencing the same crash yet Vista is reporting it differently? As I show no error messages in the RPT either. The only feedback I got was when I let it stew for a bit and it finally pronounced that the OPENGL driver had crashed. Maybe XP has no indication of a crashed display driver recovery?