SOLVED ! - CTD on exiting Histwar

[Franciscus]

I do not know exactly when I started getting this, but I think it was sometime along 03A(xxx). The first time I launch the game in a PC session and play, when I exit, I get a CTD. If I load Histwar again in the same session, I get no more CTD when leaving the game.

This also on a super clean new install, 01b -> 02f -> 03A(RC2) -> 03A (RC4)

I have a new internet security (F-secure), but I get the same problem even if I exclude all the Histwar directory from the real time anti-virus...

Any ideas ?
Am I the only one getting this ?

[JMM]

Could you send me the spyboard.txt after the CTD.

JMM

[Franciscus]

I found the cause and I think I found the solution 

It's not Histwar, but my new Internet Security suite, F-Secure Internet Protection (provided by my cable company).

I tried (with cable off) to disable EVERYTHING of this suite, and no CTD. Than I found that it's one of their routines of real-time scanning of processes, called DeepGuard, that caused the crashes. I then added "Serveur.dll" (found in Histwar directory;) to the exceptions list (I had alerady excluded all the Exe files, without sucess), and apparently I have no more CTD.

I am beginning to be sorry to have chosen this program (F-Secure). It seems OK, and light, but I had also problems with another of my games (Scourge of War), caused also by this "DeepGuard" #*?!" feature 

Do you still need the spyboard ?

[JMM]

NO, I don't   

JMM

[Franciscus]

Thank you for your attention and sorry for bringing over a problem that's not caused by Histwar.

I reported this issue in the F-Secure forum.

Best regards.

[Franciscus]

@JMM

F-Secure guys sugested me to submit a "sample file" (I presume the culprit to be the Serveur.dll, but I need more testing), in order for them to update the program and avoid false detections.

Do you want/give me permission to send them this file ?

Regards

[JMM]

@JMM

F-Secure guys sugested me to submit a "sample file" (I presume the culprit to be the Serveur.dll, but I need more testing), in order for them to update the program and avoid false detections.
Do you want/give me permission to send them this file ?
Regards

Why not but I am no sure he can find/use the dll without other program.
Another way :
a) install and check the demo
b) if you get the problem, the best is to send the link to download the demo to F-Secure
c) if the demo runs fine... hummm

JMM

[Franciscus]

(...)
Another way :
a) install and check the demo
b) if you get the problem, the best is to send the link to download the demo to F-Secure
c) if the demo runs fine... hummm

JMM

Is it OK to install the demo and the full game in the same PC (in separate directories, of course) ?. Will not the registry contain entries for both ?

[JMM]

Wait for a special Demo version... probably Sunday.

JMM

[Franciscus]

I am sorry JMM, but I am totally confused  . It's difficult to test this CTD well, because I have to reboot my PC everytime. I THOUGHT yesterday that the problem was caused by the DeepGuard of F-Secure, but today I got again the same CTD on leaving the game (only the first time the game is loaded), even with the file serveur.dll excluded or even with DeepGuard turned OFF. 

So, I really do not know the cause.

I attach here the spyboard file of the latest crash.

Again, sorry for this confusion, but this a difficult issue to test 

[JMM]

I am sorry JMM, but I am totally confused  . It's difficult to test this CTD well, because I have to reboot my PC everytime. I THOUGHT yesterday that the problem was caused by the DeepGuard of F-Secure, but today I got again the same CTD on leaving the game (only the first time the game is loaded), even with the file serveur.dll excluded or even with DeepGuard turned OFF. 

File serveur.dll excluded??? no sure I understand because in the spyboard.txt, the serveur.dll was launched.
You can only launch HW:LG without play a game (so serveur.dll isn't launched). In this case, do you get a crash?
Playing in windowed mode, probably you have not to reboot your PC

So, I really do not know the cause.
I attach here the spyboard file of the latest crash.

No information in the spyboard.txt
Could you re-install DirectX 9c (february 2010 or after)

JMM

[Franciscus]

When I said that I excluded the dll file, I meant excluded from the antivirus "scanning".

As a further note, the CTD only happens if I launch the game via the splash screen (histwar.exe) and then leave the game. If I launch the game via LGDN.exe, no CTD occurs on leaving.

I will try to reinstall the directx.

Many thanks and apologies for disturbing you when you are finishing an important patch...

[JMM]

A bit curious...

To be sure
histwar -> lgdn -> histwar -> out : CTD
histwar -> lgdn -> histwar -> lgdn -> histwar -> out : no problem
lgdn : no problem

I have to take a look at the code which is launching lgdn.
JMM

[Franciscus]

To be sure
histwar -> lgdn -> histwar -> out : CTD
histwar -> lgdn -> histwar -> lgdn -> histwar -> out : no problem
lgdn : no problem

That's not exactly how it happens. It's:

1. histwar -> lgdn -> histwar -> CTD (the splash screen does not even show after I click exit in lgdn, the screen goes black, and CTD, I never get a chance to click exit on histwar)

2. The second is impossible, because I can not get back to histwar, it crashes when I leave lgdn as stated above

3. lgdn alone: no problem

BUT, only when I launch histwar for the first time in a PC session. I mean, after the CTD, if I launch again histwar, I get:
histwar -> lgdn ->histwar -> out, without problems !

Clear ??  

(edit1: On windowed mode, no CTD occurs, I can leave lgdn and then leave histwar without CTD. The problem appears only in full screen mode...  )

(edit2: reinstalling directx June 2010 did NOT solve the problem)

(edit3: I attach a pic of the screen I get and the error message (although in Portuguese I think you will understand))

(edit4: To clarify: the CTD is not catastrophic, the windows session continues OK, I do not have to reboot the PC, it's just annoying)

Again, thank you for your patience !

[Franciscus]

Looking at the error message, could this be related to our "old" d3dx9_42.dll ? Or is it just a generic message ?

(for your info, I updated both directx and my ATI drivers (currently on version 11.3))