PDA

View Full Version : Crash When Opening Door -*Possilble Spoiler*-



trogdor1138
18th Sep 2009, 23:44
My game is currently crashing right after the first encounter with Scarecrow. I scan the Great White jar, blab to Oracle about meeting Scarecrow, and then head to the door to leave the morgue. As soon as I hit the key to open the door, the game crashes. It's been running great up until this point, and I have no idea what could be causing this. My specs are as follows:

Windows 7 x64 RTM
Intel i7 920 2.6 gHz
6 GB DDR3 1600 mHz RAM
EVGA GTX 285 Video Card
Integrated RealTek High Definition Audio
WD VelociRaptor 300 GB SATA drive

I am currently playing on "High Settings" at 1920x1200 resolution, but I'm pretty sure my system can more than handle this game at these settings, as it's been running great until now. I got a key with my video card, and then registered it on Steam. The game shows that it's version 1.1 at the menu, and it's showed that version since I first downloaded it. Nothing on my system is overclocked. I know this system is great for PhysX because I can also play Mirror's Edge at the same resolution on maximum settings with anti-aliasing without a hiccup. Any help with this issue is greatly appreciated, as I've very much enjoyed the game thus far, and can't wait to continue.

Kill_Medics_First
19th Sep 2009, 05:52
I have the exact same problem, after the first Scarecrow nightmare sequence the game crashes when I try to open the door to exit the morgue. I am not able to progress any further.

My system specs are:

Windows Vista Home 32bit
EVGA Nvidia 790i Motherboard
Intel Core 2 Quad Q9550
EVGA Nvidia GTX 275
4Gb DDR3 1600 RAM
Sound Blaster X-fi Extreme Gamer

oseven
19th Sep 2009, 06:13
*FURTHER SPOILERS*

I have an issue at the 3rd Scarecrow encounter, where, as soon as the nightmare begins... I get the old rainbow checkerboard freeze syndrome from back in the NES days. However, the game does not crash or stop... It simply resumes once the Nightmare cutscene of Joker driving Batman begins and everything clears up.

EVGA GTX275 1792 MB edition
Windows XP 32 bit
6 GB DDR3 RAM at 1400 mhz
Intel I7 920 @ 3.7 GHz
150GB WD VelociRaptor
1920x1200 Resolution

Neon25
19th Sep 2009, 09:17
*FURTHER SPOILERS*

I have an issue at the 3rd Scarecrow encounter, where, as soon as the nightmare begins... I get the old rainbow checkerboard freeze syndrome from back in the NES days. However, the game does not crash or stop... It simply resumes once the Nightmare cutscene of Joker driving Batman begins and everything clears up.

EVGA GTX275 1792 MB edition
Windows XP 32 bit
6 GB DDR3 RAM at 1400 mhz
Intel I7 920 @ 3.7 GHz
150GB WD VelociRaptor
1920x1200 Resolution


Dude... It's on purpose. It's supposed to be one of Scarecrow's hallucinogens.

bbb
19th Sep 2009, 09:19
Do you get a crash dialogue box with more details or does it just bomb out without explanation?

If there's nothing, could you open the Event Viewer (it's in Administrative Tools in the start menu) and see if there are any errors reported at the time of the crash.

ShinyMilbings
19th Sep 2009, 14:25
I'm having the same issue.

Windows 7 RTM
Core i7 920
6GB DDR3 RAM @ 1600 MHz
EVGA GTX 275
500 GB Seagate Barracuda

Here is the crash log from when it happened:
Log Name: Application
Source: Application Error
Date: 9/18/2009 11:00:33 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: shiny
Description:
Faulting application name: ShippingPC-BmGame.exe, version: 1.0.1.0, time stamp: 0x4a8bab8b
Faulting module name: ShippingPC-BmGame.exe, version: 1.0.1.0, time stamp: 0x4a8bab8b
Exception code: 0xc0000005
Fault offset: 0x013cc932
Faulting process id: 0xa10
Faulting application start time: 0x01ca3878b7efd73c
Faulting application path: d:\steam\steamapps\common\batman arkham asylum\Binaries\ShippingPC-BmGame.exe
Faulting module path: d:\steam\steamapps\common\batman arkham asylum\Binaries\ShippingPC-BmGame.exe
Report Id: 65215f6e-a46c-11de-bb9c-002421b43908
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2009-09-18T16:00:33.000000000Z" />
<EventRecordID>1082</EventRecordID>
<Channel>Application</Channel>
<Computer>shiny</Computer>
<Security />
</System>
<EventData>
<Data>ShippingPC-BmGame.exe</Data>
<Data>1.0.1.0</Data>
<Data>4a8bab8b</Data>
<Data>ShippingPC-BmGame.exe</Data>
<Data>1.0.1.0</Data>
<Data>4a8bab8b</Data>
<Data>c0000005</Data>
<Data>013cc932</Data>
<Data>a10</Data>
<Data>01ca3878b7efd73c</Data>
<Data>d:\steam\steamapps\common\batman arkham asylum\Binaries\ShippingPC-BmGame.exe</Data>
<Data>d:\steam\steamapps\common\batman arkham asylum\Binaries\ShippingPC-BmGame.exe</Data>
<Data>65215f6e-a46c-11de-bb9c-002421b43908</Data>
</EventData>
</Event>

Kill_Medics_First
19th Sep 2009, 15:48
Do you get a crash dialogue box with more details or does it just bomb out without explanation?

If there's nothing, could you open the Event Viewer (it's in Administrative Tools in the start menu) and see if there are any errors reported at the time of the crash.

I do get a "message" box when the game crashes saying something about a general protection fault? Here is what it says:

Rendering thread exception:
General protection fault!

History: QA_APPROVED_BUILD_OCTOBER_2008 177051 19-08-2009 13:45.35 FMOD: 42200/42200 Game

NiGetApexSDK() Address = 0x3b6ca98 (filename not found) [in E:\Program Files\Eidos\Batman Arkham Asylum\Binaries\APEX_release.dll]
Address = 0x3dd35e68 (filename not found)
Address = 0x3dd35e68 (filename not found)


QA_APPROVED_BUILD_OCTOBER_2008 177051 19-08-2009 13:45.35 FMOD: 42200/42200 Game

RaiseException() Address = 0x75befbae (filename not found) [in C:\Windows\system32\kernel32.dll]
CxxThrowException() Address = 0x72c48e89 (filename not found) [in C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4016_none_d0893820442e7fe4\MSVCR80.dll]
GetOutermost() Address = 0x5f2831 (filename not found) [in E:\Program Files\Eidos\Batman Arkham Asylum\Binaries\ShippingPC-BmGame.exe]
Address = 0xe872ca4c (filename not found)
Address = 0xe872ca4c (filename not found)

bbb
19th Sep 2009, 17:28
The crash says something about APEX, which is part of the PhysX libraries. Try disabling the additional PhysX features until the next save point and see if that's enough to get you past the crash.

ShinyMilbings
20th Sep 2009, 01:27
Yep, that was it. I had to turn PhysX off altogether but it works now. Thanks!

Doctor Hades
20th Sep 2009, 11:55
I've just encountered this exact same problem in the PC version and replicated it twice... I'd just finished the first Scarecrow encounter, I scanned the jar, listened to Oracle then headed for the door, pressed A (on the wireless Xbox 360 controller I'm using) to open it and the game crashes back to the desktop. The error seems to point to APEX_release.dll v1.1.0.0 being the culprit according to the Event Log.

I'll add that I'm playing the game at 1920x1200 with PhysX on High, 8X AA, V-Sync On and everything else maxed. I've had absolutely no problems with the game until that point.

I'll see if turning off PhysX helps but it's unacceptable for me to play the game without PhysX as that is one of the reasons I bought this version as I already have the Xbox 360 version too.

Doctor Hades
20th Sep 2009, 11:57
For some reason my signature with my specs isn't showing so here they are:

Intel Core i7 920 @ 3.36 GHz
ASUS P6T Deluxe v1604 motherboard
6GB G.Skill DDR3 1600 MHz RAM
1 GB EVGA GeForce GTX 280 graphics,
Creative X-Fi XtremeGamer sound
2 x 500 GB GB 7200 rpm SATAII hard drives
Windows Vista SP2 (64-bit)

Doctor Hades
20th Sep 2009, 12:02
Right, I changed the PhysX setting from High to Normal in the launcher and I can now pass through the door fine without the game crashing. Looks like I don't have to turn it off completely in order to get round this bug. Others might be able to do the same. Could be the bug only occurs when PhysX is set to High?

Doctor Hades
20th Sep 2009, 12:21
Spoke too soon... game crashes with Normal PhysX a little further on at the point where I was exiting the vents leading up to the room where Harley Quinn has Commissioner Gordon held captive. I entered the vent fine but it crashed when I exited it. Same APEX_release.dll error message.

So how come PhysX was working perfectly for the first hour and 10% of the game and suddenly becomes buggy/unstable?

Wolny
20th Sep 2009, 21:03
I had the issue with the game crashing after the first encounter with Scarecrow then i updated my sound card drivers (SB X-FI) and re-installer the directX from the batman disk and soo far soo good im past 3rd scarecrow encounter and no problems.

trogdor1138
21st Sep 2009, 19:34
Sorry I haven't replied in so long; I actually got it working and have been playing again. I didn't really do anything other than a few restarts. I actually set PhysX higher than I originally had it (it's now on the highest setting), maybe that had something to do with it. Other than that, I would just agree with the different advice given above: remove sound and video drivers, run a driver cleaner program, and then re-install drivers. The game definitely runs fine on Windows 7 x64 RTM; I'm almost finished with it. I also second messing around with PhysX to see what effect it has. On my GTX 285, with PhysX on the 'High' setting I get an average FPS of about 50 on the benchmark. Try running the benchmark utility, and if your framerate is much lower than 40 to 50, try disabling PhysX or lowering the resolution and see if that bumps the numbers up. Anti-aliasing can also cause problems. The last thing I could think of is that since opening doors triggers loading, there could be an issue with hard drive, chipset drivers, or RAM. Try checking and defragging the page file, defrag your hard drive, and re-install chipset and disk controller drivers. Also, it should go without saying that if any of your hardware is overclocked, revert to stock settings at least until the issue is resolved.

Doctor Hades
21st Sep 2009, 23:47
I've been able to replicate the crashes at the two points I mentioned, trogdor1138, and each time they related to the APEX_release.dll file, which suggests to me that it's a specific issue related to PhysX.

I was able to get around the issues by reducing PhysX temporarily to Normal and setting it back to High after quitting and restarting the game. I was able to play for almost two hours on High PhysX until I quit the game late last night.

If it really was a driver or hard drive issue of some kind then I would not have been able to replicate the crash as it would be random. That's my theory anyway and I'm sticking with it. :p

cybertron
26th Sep 2009, 13:20
I get the same crash - but only when using the no-cd crack. If I use the normal .exe. with disk in drive - I don't get the problem... are you Pirates? - or do you have the real thing as well? Try with the genuine .exe - you should find it will work fine.