I use Worms Armageddon, latest patch, Windows 7. For some reason, about once a week, when I double-click on #Anything-Goes, everything freezes, commands like ctrl alt esc and ctrl alt del don't work, and the only thing I can do is manually restart. It happened again this morning, and it even froze when I began hosting a game, which hasn't happened for the past thousands of games I've hosted. Any thoughts? Thanks!

Just a thought... does the palette.log file in the main WA folder have a new entry added when this happens?

I'm thinking some firewall or antivirus solution could be trying to stop the game from connecting in the background, though that wouldn't really explain why it only happens sometimes.

No, the latest entry in there is:
[2010-02-19 22.56.48] Palette set by 0x10010 "" [csrss.exe]

Please install WormKit (http://worms.thecybershadow.net/wormkit/) and the following WormKit module: 32227

Run the game via WormKit, reproduce the freeze and press Ctrl+Break. W:A should close, and a file named FREEZE.DMP should be created in your W:A folder. Find and post this file here.

Please install WormKit (http://worms.thecybershadow.net/wormkit/) and the following WormKit module: 32227

Run the game via WormKit, reproduce the freeze and press Ctrl+Break. W:A should close, and a file named FREEZE.DMP should be created in your W:A folder. Find and post this file here.
Unfortunately, I just came back from rebooting from a freeze, because hitting ctrl+break didn't actually undo the freeze or get me out of Worms. I was afraid of that: The computer's frozen, so it won't respond to anything, including ctrl+break. I had previously tested ctrl+break when in-game, to make sure it's working, and it did work at that time, but, as I said, not during an actual freeze when I need it. This time the freeze simply happened after I hit 'Quit' after a hosted game of mine ended, so that I could leave the room (in the room where you can choose to either light up for another round or leave the room). Any thoughts?

Edit: There was also no newly-modified FREEZE.DMP, just the one from when I tested it Aug 10.

The only thing this could mean is a hardware lock-up... it would indicate a problem in your computer's hardware or drivers.