Problems with getting WA to run in Win7 on a ATi Gfx card...

You need to be more specific.

but check out:
http://worms2d.info/Troubleshooting_FAQ

Hi Sorry for last post - total newbie to forums (well posting in them anyway)

I've read the sticky topics but the help for installing still doesn't work for me...

I've got WA CD, downloaded patch (v3), WA_update-3.6.28.0_Beta_Installer and GfxUpdate-3.6.22.1, I've run them in that order.

I've got a batch file to close file explorer in Win7.

I set the compatability mode to WinXP (tried others too).

Every time I load WA I get the same error (after restarting, deleting / uninstalling and repeating all steps above)

"wa caused an Access Violation (0xc0000005)
in module wa.exe at 0023:004094ab.
Exception handler called in ExceptionAttacher.cpp - AfxWinMain.
Error occurred at 6/17/2011 20:57:08.
D:\wa2\wa.exe, run by ChRisC.
Operating system: unknown Windows version (6.1.7600).
4 processor(s), type 586.
46% memory in use.
0 MBytes physical memory.
2209 MBytes physical memory free.
0 MBytes paging file.
3572 MBytes paging file free.
2048 MBytes user address space.
1875 MBytes user address space free.
Read from location 00000000 caused an access violation."

Can anyone help?

You must be following an outdated installation guide. Uninstall everything related to the game, and only install the game and the latest Beta update (3.6.31.0), which you can download from the official Worms Armageddon website (http://wa.team17.com/main.html?page=supp&area=upda&file=15).

@CyberShadow,

Thanks.

Tried it and I thought it worked but two things... firstly, the update file "WA_update-3.6.31.0_Beta_Installer" doesn't work - tried downloading it 3 separate times and it seems to be downloaded fine, but none of them run. Even with admin access, nothing happens after I run the executable.

Secondly, using the update file "WA_update-3.6.28.0_Beta_Installer", which runs fine, the same error occurs, namely....

wa caused an Access Violation (0xc0000005)
in module wa.exe at 0023:00409144.
Exception handler called in ExceptionAttacher.cpp - AfxWinMain.
Error occurred at 6/18/2011 12:06:58.
D:\wa\wa.exe, run by ChRisC.
Operating system: unknown Windows version (6.1.7600).
4 processor(s), type 586.
5% memory in use.
256 MBytes physical memory.
225 MBytes physical memory free.
1793 MBytes paging file.
1775 MBytes paging file free.
2044 MBytes user address space.
1879 MBytes user address space free.
Read from location 00000000 caused an access violation.

Context:
EDI: 0x00001db0 ESI: 0x00000002 EAX: 0x00000000
EBX: 0x00000001 ECX: 0x00000000 EDX: 0x00189654
EIP: 0x00409144 EBP: 0x0018974c SegCs: 0x00000023
EFlags: 0x00010212 ESP: 0x00189634 SegSs: 0x0000002b

Bytes at CS:EIP:
8b 08 8b 15 3c 5f 6b 00 52 8b 41 58 ff d0 c7 45

Any ideas?

Tried it again changing a few things, like the batch file (with and without /nointro),

with and without XP compatibility, Win98, Win95....

Tried with Windows Explorer loaded and unloaded...

Unfortunately still same "Read from location 00000000 caused an access violation" error.

FYI this is my setup:

Intel Quad Core Q9400
4 GB Ram
Asus P5Q Pro
Windows 7 64bit
HDD Windows (C:)
2nd HDD for games (D:)
Ati 4850 512 Mb with Jan2011 ATi drivers (v8.821.0.0)
(Catalyst Control Center Version 2010.1125.2142.38865)
LG DVDRW with WA CD on drive (K:)
Directx 11

Thanks.

Using an outdated version of W:A is not supported and will not allow you to play online. I would suggest investigating why you are unable to install the latest update. You may want to check if any antivirus software is blocking the update installer's execution, as multiple antivirus vendors have reported false positives for the latest updates.

OK,

Tried with and without my Avast anitvirus checker enabled and made no difference.

When I double click on "WA_update-3.6.31.0_Beta_Installer" it simply does nothing (that I can see).

I've even watched Task Manager and nothing loads (within its refresh rate).

It is very strange indeed why this doesn't run!
(again, tried with and without admin access; WinXP, Win2K & Win98 compatibility modes; with and without virus checker)...

http://www.memtest86.com/

Please run this software, let it loop the tests 3 to 4 times. If any errors appear then your computer RAM is faulty and causing the problem. If no errors appear then perform test 11 at least twice.

These procedures will take 6 to 24 hours~ depending on your computer configuration to complete but is well worth the time as it can help avoid future headaches caused by seemingly random problems! Do not trust the memory tester that is included in Windows 7.

http://www.memtest86.com/

Please run this software, let it loop the tests 3 to 4 times. If any errors appear then your computer RAM is faulty and causing the problem. If no errors appear then perform test 11 at least twice.

These procedures will take 6 to 24 hours~ depending on your computer configuration to complete but is well worth the time as it can help avoid future headaches caused by seemingly random problems! Do not trust the memory tester that is included in Windows 7.
You may also want to check all your RAM modules separately and/or in different memory banks.
That way you can determine if it's not a faulty RAM module, but the memory bank itself that is damaged and causes memory-related errors.

I had that problem and all modules separately in the same bank (primary 0) worked fine, but as soon as I added the second module in bank primary 1, it instantly locked up and crashed at the start of the test.

Did a 4 hour long test - zero errors in memtest

Also did OCCT for 30 minutes and all totally fine.

Have been running the computer with other games for almost a year with not a single issue / reboot / BSOD / or crash.

I'm thinking its software. I'm almost at the point of re-installing windows...

You might be able to get around this problem by manually extracting the files from the installer using 7-Zip (http://www.7-zip.org/).

OK, tried that, extracted the "$_OUTDIR" directory from the 7z file into the wa directory, now the wa.exe does absolutely nothing - it doesn't appear to even load or do anything.
Talk about puzzled :-/

Tried again but using the wa.exe file from the 3.6.28 version and the file runs, accesses the CD, then screen goes black, then on another screen flicker, it comes back with the error message and the error log. (as before).

I retried it with the wa.exe file from 3.6.31 and nothing happens when I run that. It definitely seems to me that the .exe is not liking something on my PC!???

I retried it with the wa.exe file from 3.6.31 and nothing happens when I run that. It definitely seems to me that the .exe is not liking something on my PC!???

Or something on your PC is not liking the EXE. I suspect that some antivirus software is silently blocking it, despite being "disabled".

Maybe try installing it in Safe Mode? Since it loads just the necessary dlls to run Windows and all.

@CyberShadow
Yeah, you're absolutely right, most likely something on PC stopping the executable.

@CakeDoer,
Excellent suggestion! :D
The installer worked in safe mode totally fine - thus proving its something in background.

Tried running game in safe mode, I got to the Team17 logo, but then crashed.
Decieded to reboot normally and run game...

Unfortunately that was a no go :(

Something definitely not liking that exe file for some reason. I tried deactivating my Avast Anti virus again, still no go. (I do see WA.exe 32bit flash up in Task Manager though).

So I am now looking at active programs and services, trying to see if I have any anti malware/spyware/virus services running. I've spotted Ad-Aware service which I didn't know ran in background.
Interestingly I just ran Ad-aware and it thought WA.exe was spyware. I've added it to ignore list but I got a feeling it isn't ignoring it.
I'm going to uninstall it now...

It was Ad-Aware (by Lavasoft)'s background service that was blocking WA.exe all along. Just played and even tried to access online - seems to be working.

Thanks very much for all the help guys!

:D
:cool:


(p.s. avast antivirus was running when playing the game - so its ok to use that one...)

It's pretty funny how anti-malware software turns out to be malware itself more often than it protects against malware.

I don't use any locally-installed anti-malware software. Instead, if I'm ever faced with a suspicious executable (.exe, .dll, .ocx, .sys, .scr, .drv, .cpl), I upload it to VirusTotal with the VirusTotal Uploader shell extension. Since I started using this method ~5 years ago, I haven't experienced any malware issues. This method isn't for everyone, though, since I'm sure there are people who can't tell what's suspicious and what isn't. It's a good method for generally-experienced Windows users who don't have much reverse-engineering experience (like me).

It seems I spoke too soon.

I keep getting errors now when trying to setup or change team details.

This error appears (with wa.exe still running in background):

WA caused an Access Violation (0xc0000005)
in module ntdll.dll at 0023:77b2e3be.
Exception parameters: 00000000 002c7474
CyberShadow beta, version 3.6.31.0

Error occurred at 6/23/2011 20:11:54.
D:\wa\WA.exe [003EDAA8], run by ChRisC.
Operating system: Windows 7 (6.1.7600).
4 processor(s), type 586.
5% memory in use.
256 MBytes physical memory.
225 MBytes physical memory free.
1793 MBytes paging file.
1775 MBytes paging file free.
2044 MBytes user address space.
1844 MBytes user address space free.
Read from location 002c7474 caused an access violation.

Context:
EDI: 0x00bde418 ESI: 0x002c7470 EAX: 0x5b0b74f0
EBX: 0x00bde420 ECX: 0x00250000 EDX: 0x00bde420
EIP: 0x77b2e3be EBP: 0x0017b4ac SegCs: 0x00000023
EFlags: 0x00010202 ESP: 0x0017b478 SegSs: 0x0000002b

Bytes at CS:EIP:
8b 46 04 89 45 f4 c6 47 07 80 c6 47 06 00 8b 5e

I can reload the game. Funny because the first time I ran WA I edited the first team details fine.... ?

Please post the entire error log.

Here's my error log...

Looks like a case of this (http://worms2d.info/Troubleshooting_FAQ#WA_crashes_when_I_try_to_edit_ or_create_a_team_on_Windows_Vista_.2F_7).

Once again thanks CyberShadow. Worked great.
Sorry I missed that one!

Cheers

ChRisC

It's pretty funny how anti-malware software turns out to be malware itself more often than it protects against malware.

I don't use any locally-installed anti-malware software. Instead, if I'm ever faced with a suspicious executable (.exe, .dll, .ocx, .sys, .scr, .drv, .cpl), I upload it to VirusTotal with the VirusTotal Uploader shell extension. Since I started using this method ~5 years ago, I haven't experienced any malware issues. This method isn't for everyone, though, since I'm sure there are people who can't tell what's suspicious and what isn't. It's a good method for generally-experienced Windows users who don't have much reverse-engineering experience (like me).

Quoted for truth.