The title really says it all. I'll go into depth a bit more however. Firstly, I tried the demo before I bought the game. Fairly reasonable I would think, and I fell in love with it. In the demo I was able to play with 1000 bots running. Fairly smooth for about I'd say 20 minutes before the game crashed on me. Didn't lock up. Figured it must have been a weird thing, shrugged it off. It's after all in Beta, so go figure. Anyway, bought the game, un-installed the demo, and now I don't crash, but rather my entire laptop locks up, completely unresponsive whenever I try to start a new game. It does this within approximately 5 seconds.

Now understand, this is a very new computer I'm playing on, I just purchased this 2 weeks ago, got it delivered a week and a half. I'll list the specs, then I'll give the config and other file info that I've seen in other topics.

Specs:
OS: Win7 64 bit (Home Premium)
HD Space: 500 gig, split between 2 partitions of 250gig each.
Processor: AMD A6-3400 RM (Quad Core 1.40gz each) w/ Radeon Graphics
Graphics: Radeon HD 6720G2 w/ 1 gig memory dedicated
Ram: 4 gigs of ram (3.48 usable)

I can post the config files and all that jazz when I actually know where they are. Because I can't find em.

The log files are at C:\ProgramData\Running with rifles\. It's a hidden folder (actually it's a virtual folder that takes you to another place entirely), just enter that in your explorer address bar at the top and you should get there.

camelfilters had an issue which sounds similar, it was discussed here viewtopic.php?f=5&t=404&p=2496, and he also had somewhat similar processor "CPU ID: AuthenticAMD: AMD A6-3650 APU with Radeon(tm) HD Graphics" you've got.

In his case updating the BIOS worked wonders, which might indicate a problem in the CPU/motherboard related software. Updating BIOS can be harmful stuff to your PC, so study the topic carefully if you're willing to try that and before you do anything.

Let's see the logs before you even consider that though, it might just be something else.

Apparently I've fixed it. Amusingly it was a simple enough fix as well, run in windowed mode, then turned off shadows. How very interesting.