CRASH

[TexHorns]

Was continuing my 1792 game using the 1.2.14beta. I am playing in year 1806. During AI turn the game froze and then crashed with the following message:

Microsoft Visual C++ Runtime Library
Assertion Failure
see Visual C++ documentation on asserts
File- c:/Project/PLATO/Header/provmap.h
Line 79
Expression p>0

Hope this helps Eric.

[Naomi]

Reproducing the issue in the section Limited Feedback may catch Erik's eyes sooner.

[ericbabe]

Thanks for the report. Was your game started under a version other than 1.2.14? There might be some save game incompatibility at work here.

[TexHorns]

Yes, Eric I believe you are right it was.

[hammersinger]

I just bought this game, loaded the same patch and have the same bug. I get it after one or two turns.

[garoco]

I probe the patch 1.2.17 and this doesn´t occurs until now, playing 8 hours of game continue against Grand Armee

[hammersinger]

I went through a number of "crash to POST" errors with this. The Microsoft tool said it was a RAM problem. That probably meant that there was a memory leak in the code. That looked bad. Then I thought to uninstall everything and do a clean install on my C: drive. I had been trying to run it on my RAID array which is way faster than the C: drive. When on the C: drive it runs completely stable, as far as I can tell, in its initial install and with either patch.
My conclusion is that there are some calls in the code that tell it to look on C: somewhere for something. It cannot find that something and then "instability happens!" This is not good code btw. Lots of people nowadays have multiple drives, RAID, SCSI etc. I try to keep anything like games or Office or anything like that on the RAID because the C: is always the target of malware. I have lost total C: drive contents due to needed reformatting several times following infections. You get a malware attack every four minutes online now (some authorities say). Broadband is always on so any minute your computer is turned on it is getting malware insertion attempts. The less I need to reinstall the better. best, hammersinger

[hammersinger]

I have again encountered a crash problem. After getting seven or eight turns into a game running the beta patch I get a crash to POST. The Microsoft error tool again says this is either a device driver or RAM problem. My device driver profile is fine and no other programs encounter this sort of error. My question is: Does COG contain any device drivers? Possibly for the sound functions? also: Is anyone else encountering crash to POST errors? thanks

[ericbabe]

ORIGINAL: hammersinger

I went through a number of "crash to POST" errors with this. The Microsoft tool said it was a RAM problem. That probably meant that there was a memory leak in the code. That looked bad. Then I thought to uninstall everything and do a clean install on my C: drive. I had been trying to run it on my RAID array which is way faster than the C: drive. When on the C: drive it runs completely stable, as far as I can tell, in its initial install and with either patch.
My conclusion is that there are some calls in the code that tell it to look on C: somewhere for something. It cannot find that something and then "instability happens!" This is not good code btw. Lots of people nowadays have multiple drives, RAID, SCSI etc. I try to keep anything like games or Office or anything like that on the RAID because the C: is always the target of malware. I have lost total C: drive contents due to needed reformatting several times following infections. You get a malware attack every four minutes online now (some authorities say). Broadband is always on so any minute your computer is turned on it is getting malware insertion attempts. The less I need to reinstall the better. best, hammersinger

All the directory names are path names relative to the install location of CrownOfGlory -- there is no C: hardwired into any of the directory names. But, reading your next message, it seems you're still getting this error.

The only similar errors to the one you're describing we've experienced in-house comes from having out-of-date sound drivers. But in this case, the crash occurred as soon as the first sound was attempted to be played. (The system reported that the sound device was working fine, but the problem was fixed by going to SoundBlaster and downloading the newest set of drivers, so a report by Windows that the drivers are OK doesn't necessarily mean that they are.)