I’m trying to launch Batman Arkham Asylum, which I downloaded via Steam. This game is protected with Securom.
When I start the game, I always get the error “Securom Launcher has stopped working”
The Windows error log shows the following message:
Name der fehlerhaften Anwendung: BmStartApp.exe, Version: 0.1.0.8, Zeitstempel: 0x00000000
Name des fehlerhaften Moduls: BmStartApp.exe, Version: 0.1.0.8, Zeitstempel: 0x00000000
Ausnahmecode: 0xc0000005
Fehleroffset: 0x00164c64
ID des fehlerhaften Prozesses: 0x608
Startzeit der fehlerhaften Anwendung: 0x01ce607adca7395c
Pfad der fehlerhaften Anwendung: D:\Steam\SteamApps\common\Batman Arkham Asylum GOTY\Binaries\BmStartApp.exe
Pfad des fehlerhaften Moduls: D:\Steam\SteamApps\common\Batman Arkham Asylum GOTY\Binaries\BmStartApp.exe
Berichtskennung: 1ab1fad6-cc6e-11e2-aaca-98bbcbf40726
So, after much investigation I found the following thread with the exact same problem and the exact same approaches to solve the problem: click (the only difference is that the issue occurs with Bioshock 2)
The last tip to uninstall Avast is the only one that worked. It isn’t enough to stop all Avast modules. Even stopping the Avast service completely and all corresponding processes in the task manager isn’t enough. You have to uninstall Avast for Securom to launch.
It would be great, if the devs could reproduce this issue and come up with a fix for it. Avast is IMHO the best anti-virus programme out there and I don’t want to switch to another one, just because of a compatibility issue.
Thanks for looking into it.
Specs:
AMD Phenom II X4 955
AMD Radeon 5850 1GB
8GB RAM
Windows 7 x64 SP1 fully patched
Avast 8.0.1489 with latest signatures
Ya know…steam installing malware into your machine is technically up to the user. But why should everyone have to wonder what Avast closes their eyes too because it conflicts with another company?
DRM in many cases is far worse than many viruses and it is a well known fact many problems arise because of it AND does damage to computers!
It shouldn’t be changed on Avast’s part. The user should have it on an ignore list if they choose to infect their property with it. It should still be flagged by Avast so the user can determine if they want to ignore/allow it. It shouldn’t be flatly ignored by Avast >;/
I uploaded the file, but I’m not sure if it was received on the server, because I couldn’t see it on the server. At least Filezilla reported a successful transmission.
Thanks for looking into it.
Sorry for the delayed reply.
I followed your instructions and activated hardware-assisted virtualization before rebooting. It seems to work: Batman starts up fine.
Thanks for the great support.
Should I replace the patched file with the original (backuped) one? Or should I just wait for the next Avast update and keep it until then?