Page 2 of 9

Re:Crash report

Posted: Sat Apr 17, 2010 10:15 pm
by scraig40
Op Sys: MS XP Professional (5.1, Build 2600)
BIOS: Award Modular BIOS v6.0
Processor: Intel(r) 4 CPU 2.80GHz (2 CPUs)
Memory: 1536MB
Page file: 569MB used, 2865MB available
DirectX Version: DirectX 9.0c (4.09.0000.09.04)
DxDiag 5.03.2600.5512 Unicode

Re:Crash report

Posted: Sun Apr 18, 2010 6:04 am
by ADukes
What's your graphic card? Did you update your DirectX installation and your graphic card drivers? Where does the game crash exactly?

Re:Crash report

Posted: Fri Apr 30, 2010 6:09 pm
by scraig40
NVIDIA GeForce FX 5200 (Microsoft Corporation)

Re:Crash report

Posted: Fri Apr 30, 2010 6:33 pm
by scraig40
Sorry, it took me so long to get back, but I have been on R&R up in Queensland and just got back on deck yesterday. However, a buddy of mine in West Virginia and I have been working on this problem and we came up with 2 possibilities both concerning updating of Drivers. Updated my DirectX drivers and updated my NVIDIA Drivers - after doing both - the Runtime Error has disappeared and game is again fully functional.

Re:Crash report

Posted: Sun May 09, 2010 12:50 am
by scraig40
Some interesting developments in the past week. That is, the Runtime Error I thought I was free of, has returned, but this time no amount of reinstalling of NVIDIA or DirectX made any difference. So, I decided to work backwards to see if I could find root cause. The mystery to me was always why and how this Runtime Error started? I had played plenty of SoW Multiplayer on line without problem for sometime after buying the Game, so it was a case of looking back to see what I had done that was different that may have affected the game. The only thing I could identify was the automatic updates from Microsoft.

It seemed obvious that as reinstalling drivers no longer made any difference then the issue had to be with the firewall/anti virus protection I use, which is through Microsoft Security Essentials. Also, there had been an update from MS not long before the problems started so it was all starting to point to MS Security Essentials. However, I could find no way of shutting MS Security Essentials down to test my theory, so I decided to try opening the game before the firewall became active upon restart of my PC. Low and behold that worked. If I activate the game prior to MS Security Essentials firing up, I have no problem with the game. I have tried and tested this several times now and each time I allow MS Security Essentials to activate before I load the Game - Runtime Error. But, if I activate the Game first, before MS Security Essentials, then the Game works without issue. Just thought I should let you know.

Re:Crash report

Posted: Sun May 09, 2010 3:28 am
by BOSTON
S40

Had a problem with McAfee, contacted them to do an exception to the program, then problem was solved.

BOSTON :)

Re:Crash report

Posted: Sun May 09, 2010 1:33 pm
by norb
I just do not understand these programs that feel they can shut down your computer with no warning. Is there a way to add the game as an exception?

Re:Crash report

Posted: Sun May 09, 2010 2:00 pm
by BOSTON
S40

By the way, my problem started after a security scan/update also. If you contact your security/virus people, try to get a higher support tech, like tier 2, they can make the changes you need.

BOSTON :)

Re:Crash report

Posted: Sun May 09, 2010 8:16 pm
by Davinci
scraig40 wrote:
However, I could find no way of shutting MS Security Essentials down to test my theory.
Have you tried typing msconfig from the Start \ Run Command - and unchecking the check in front of Microsoft Security Essential ?

This should stop the program from loading - you can tell if it works if there is not an icon on the right hand-side of the Taskbar .

This is using Vista - so it may depend on the Operating System!

davinci

Re:Crash report

Posted: Tue May 11, 2010 3:55 am
by scraig40
Actually, no, I haven't tried that. That would work too. However, I think the problem should be resolved by the problem makers - we shouldn't have to apply these "bandaid" approaches/solutions which put our PC's at risk. This problem should be resolved by MS Security Essentials. In the meantime though, you can bet I will use the bandaid, until the issue is patched up by those responsible for creating it - thanks for the help :0}