2.2.3 crash with vista :S

[rowlanm]

hi

ive been playing for ages, and it's been crashhin for a while, and ive never gotten a .rpt file come up, but i did this time when it failed so im submitting the file so u guys can carry on with the great work your doing, and hopefull fix my problem lol

im running on windows vista ultimate 32 bit service pack one, 4GB RAM, intel core 2 cpu 4300 @ 1.80 GHz

hope this helps

thanks

rowlanm


edit: also, something that i found helped to prolong the time between crashes was to save the game very regularily, if that helps

[-Kosh-]

Looks like this is driver related.

[Zarel]

It does? What makes you say it's driver related? I'm seeing a full stack right here...

[topo1948]

ive been playing for ages, and it's been crashhin for a while, and ive never gotten a .rpt file come up, but i did this time when it failed so im submitting the file so u guys can carry on with the great work your doing, and hopefull fix my problem lol

Problems.

Post by -Kosh- » Today, 03:46
Looks like this is driver related.

2.2.3 crash with vista. fixed ?. No way.

i'am,using,Mac.I.play.any.map.the.custom.and.the.ones.I.have.download,from.this.forum(.wd).every,thing.work.perfect. just,for,7minutes.but It crashes.not,justwz.I,mean,the,system.i,have,to,restart.manually.

Problems.

The other thread that you posted about this problem has more information. It does seem like you have a overheating issue.

Warzone can not crash the OS. The problem is with your system (heat / corruptions / bad RAM) or drivers that cause this.

wrote:reinstall newer or older drivers for your graphicscard for example
check temperature of your cpu and gpu
don't know any mac-programs for doing this, sorry

A PPC mac? Yell to apple to fix the drivers or do they tell you to upgrade to OS X 10.6?

2.2.3 crash with Mac Osx. fixed ?. No way.

I find it difficult but I want the above clarification.
If I have some kind of problem or as Rawlanm have now, to enjoy Wz. We ask for help and getting back another problem (Ram, drivers, etc.).. Imagine the feeling of helplessness . I lived.
Main reason to participate in this forum it's to enjoy this beautiful game and most important brings us together around a common theme.
Right or wrong, when I communicate that was my problem. (No experience in forums, language, no idea as a game works. A mere mortal who knows and turn on the computer more or less use it)

This is what I start to read about my problem.

question to the dev's - are the maps / mods being placed in folders the same all across the os's.

The only difference is where the Warzone folder is located, everything inside of that is the same on all systems.

Okay, I haven't been posting since I can't understand topo, but I'm beginning to see that this is a serious issue.

topo, what is your native language? You clearly don't speak English very well, so if you have a language you are more fluent in, can you use that one instead? And describe what's wrong with 2.2.3 as clearly as you can, please.

I will not make the history long.
Please read about, to get the big picture, in [Help] this happened in ver. 2.1 and now happened ver. 2.2.
From that point, just reading those post and following the instructions ( and making mistakes ) actually I'am playing Wz. without any problem, even new maps. I can not ask for more. I can not complain.
Also thanks to the forum and answers I been learning others things.
Peoples are working hard to play Wz.

edit: also, something that i found helped to prolong the time between crashes was to save the game very regularily, if that helps

You are asking for help giving us tips, This it's all about. Share.

It does? What makes you say it's driver related? I'm seeing a full stack right here...

You are in good hands.

[rowlanm]

hi

i dont think it is driver related, all of my drivers are up to date, a friend suggested that with the game crashing and the crashing becoming less frequent if i save. he thought that it might be something to do with the save file. but thats just a n00bs hunch

im not a complete computer N00b tho, i have a little more depth of knowledge in how computers work and i might be doing an MCSE (Microsoft Certified (Systems i think) Engineer for those that dont no, and im confident thats wat it means anyway ) course for my job at some point lol

and yes problems lol i hadnt read the file before i posted it, cause i wanted to get it out lest i should do a runner or something to that effect anyways (thats what was going through my head anyway )

thanks

rowlanm

[-Kosh-]

It does? What makes you say it's driver related? I'm seeing a full stack right here...

Code: Select all

C:\Program Files\Warzone 2100\warzone2100.exe caused an Access Violation at location 77b17dd2 in module C:\Windows\system32\ntdll.dll Writing to location 00000010
Call stack:
77B17DD2  C:\Windows\system32\ntdll.dll:77B17DD2  RtlEnterCriticalSection
1000587E  C:\Windows\system32\OpenAL32.dll:1000587E  alcCaptureOpenDevice
...
77AFA85F  C:\Windows\system32\ntdll.dll:77AFA85F  RtlExitUserProcess
77C73B69  C:\Windows\system32\kernel32.dll:77C73B69  ExitProcess
6993145F  C:\Windows\system32\[b]nvoglv32.dl[/b]l:6993145F  DrvPresentBuffers

That is kernel level. WZ can not cause this, it is driver related.

The other one looks like a corrupt ImageFile pointer.

2.2.3 crash with Mac Osx. fixed ?. No way.

I find it difficult but I want the above clarification.
If I have some kind of problem or as Rawlanm have now, to enjoy Wz. We ask for help and getting back another problem (Ram, drivers, etc.).. Imagine the feeling of helplessness . I lived.
Main reason to participate in this forum it's to enjoy this beautiful game and most important brings us together around a common theme.
Right or wrong, when I communicate that was my problem. (No experience in forums, language, no idea as a game works. A mere mortal who knows and turn on the computer more or less use it)

I do not understand what you want?
From what you posted before you said that your OS crashed. WZ can not do this. It does not have ring 0 or ring 1 access like drivers.
That is why I said that your system is at fault, it could be drivers, RAM, or overheating. I have no way to know, only you can test to find out.

i dont think it is driver related, all of my drivers are up to date, a friend suggested that with the game crashing and the crashing becoming less frequent if i save. he thought that it might be something to do with the save file. but thats just a n00bs hunch

im not a complete computer N00b tho, i have a little more depth of knowledge in how computers work and i might be doing an MCSE (Microsoft Certified (Systems i think) Engineer for those that dont no, and im confident thats wat it means anyway ) course for my job at some point lol

The first crash is driver related.
I do not know how the second crash can happen, it was a corrupted pointer is my guess.
If you want a MCSE... erm... well you need to hit the books! heh
As was posted before having the latest drivers does not mean they are bug free.

[Buginator]

OK Kosh, you're hired.
Sign up

[Zarel]

Code: Select all

C:\Program Files\Warzone 2100\warzone2100.exe caused an Access Violation at location 77b17dd2 in module C:\Windows\system32\ntdll.dll Writing to location 00000010
Call stack:
77B17DD2  C:\Windows\system32\ntdll.dll:77B17DD2  RtlEnterCriticalSection
1000587E  C:\Windows\system32\OpenAL32.dll:1000587E  alcCaptureOpenDevice
...
77AFA85F  C:\Windows\system32\ntdll.dll:77AFA85F  RtlExitUserProcess
77C73B69  C:\Windows\system32\kernel32.dll:77C73B69  ExitProcess
6993145F  C:\Windows\system32\[b]nvoglv32.dl[/b]l:6993145F  DrvPresentBuffers

That is kernel level. WZ can not cause this, it is driver related.

Erm, well, at least we have a stack trace. Does that mean we can work around it?

[Buginator]

Erm, well, at least we have a stack trace. Does that mean we can work around it?

Nope, not enough information.

[-Kosh-]

OK Kosh, you're hired.
Sign up

Thanks
I am thinking about it.

[i-NoD]

Hmm... everyone is sooo concentrated on drivers crash idea. How about both crashes were caused by wz state machine corruption? Look on the savegame name: it has sometrailing spaces that will fail saving routine (on Win at least). Just try to create such a save: it will fail, BUT a .gam fill still exists (can't be removed after the fail). If I try to load this game in front menu it'll fail and return on the main screen, if start structure limiter screen after it'll instantly crash-to-2 without any .RPT dumps Starting a new game will result in a zero power level and probably lead to a similar-to-1 crashes from other non-visible corruptions.
Seems like we need to trim whitespaces during saving games, but there is a problem that we can't override a savegame for now.

[Per]

I doubt the connection, but using user supplied free form text for filenames is a truly stupid idea in the first place, and should be fixed.

[-Kosh-]

Hmm... everyone is sooo concentrated on drivers crash idea. How about both crashes were caused by wz state machine corruption? Look on the savegame name: it has sometrailing spaces that will fail saving routine (on Win at least). Just try to create such a save: it will fail, BUT a .gam fill still exists (can't be removed after the fail). If I try to load this game in front menu it'll fail and return on the main screen, if start structure limiter screen after it'll instantly crash-to-2 without any .RPT dumps Starting a new game will result in a zero power level and probably lead to a similar-to-1 crashes from other non-visible corruptions.
Seems like we need to trim whitespaces during saving games, but there is a problem that we can't override a savegame for now.

I do not follow your logic. How can the state machine cause a kernel violation? The first crash is clearly driver related.

For your next point, I created a savegame called "one two four" and it made the .gam, .es, and all the other files, and it loads up just fine. I then tried "i-nod test " and it does assert out. I am guessing this is a physfs limitation of some kind. I think all spaces should be converted to "_" or whatever. Spaces are evil.

I still can not get it to crash to desktop, and not abort() /exit() out.

error |05:47:07: [openSaveFile] saveFile: savegame/i-nod test /game.map could not be opened: File not found
error |06:06:48: [saveGame] saveGame: writeMapFile("savegame/i-nod test /game.map") failed
error |06:07:03: [gameLoop] Mid Mission: saveGame Failed
error |06:07:03: [gameLoop] Assert in Warzone: ..\src\loop.c:551 (!"saveGame(sRequestResult, GTYPE_SAVE_MIDMISSION) failed"), last script event: 'N/A'
error |06:08:01: [deleteSaveGame] Warning directory[savegame/i-nod test /game] could not be deleted because The system cannot find the path specified.

You got more details?

[i-NoD]

For your next point, I created a savegame called "one two four" and it made the .gam, .es, and all the other files, and it loads up just fine. I then tried "i-nod test " and it does assert out. I am guessing this is a physfs limitation of some kind. I think all spaces should be converted to "_" or whatever. Spaces are evil. I still can not get it to crash to desktop, and not abort() /exit() out.

Just use official 2.2.3 version (will remove asserts).
- Start a new game -> try to save a game with 'savetest ' name -> it will fail -> quit game.
1. Launch game -> try to load a previously failed 'savetest ' game -> it will fail -> load some normal save -> it should load -> try to load 'savetest ' game -> should give you exactly the reported 2-nd crash (attached a similar dump).
2. Launch game -> try to load a previously failed 'savetest ' game -> it will fail -> go to skirmish -> try to enter limiter screen -> a crash without a dump file

I doubt the connection, but using user supplied free form text for filenames is a truly stupid idea in the first place, and should be fixed.

2-nd test case gives a ton of

Code: Select all

resLoadFile: Duplicate file name:

and a crash. I believe that it's possible that after save/load failure something goes wrong in res system resulting in a crash. If only there was a description on actions done...

[-Kosh-]

Just use official 2.2.3 version (will remove asserts).
- Start a new game -> try to save a game with 'savetest ' name -> it will fail -> quit game.
1. Launch game -> try to load a previously failed 'savetest ' game -> it will fail -> load some normal save -> it should load -> try to load 'savetest ' game -> should give you exactly the reported 2-nd crash (attached a similar dump).
2. Launch game -> try to load a previously failed 'savetest ' game -> it will fail -> go to skirmish -> try to enter limiter screen -> a crash without a dump file

The reason why that happens is the state machine voodoo.
It finds the .gam file and it changes whatever based on that file and then it can not load the other files that it needs and nothing gets reset to virgin state.
Most of the stage init routines were called but no shutdown routines are called so nothing gets cleaned up.
Use --debug all and it shows this.