Mass Effect PC (Steam) - General Protection Fault
Thanks for your reply. My version of Mass Effect is 1.02 as it is automatically updated through Steam.
I'm reluctant to roll back my drivers as I would rather not lose support for a lot of more recent games (Mass Effect 3 included) so I'm leaving this as an absolute last resort. I appreciate that while this may be the cause, I've not had issues with any other games released around 2007 or other games that use the Unreal engine.
As I said, the initial crash was caused by wrap_oal.dll which is something to do with audio, so I tried the following fix http://social.bioware.com/forum/1/topic/106/index/656205/2
"1) in /program files/Mass Effect/Binaries locate the OpenAL32.dll and wrap_oal.dll files
2) Rename OpenAL32.dll to OpenAL32.bak
3) Rename wrap_oal.dll to OpenAL32.dll
4) Launch as Admin by using the MassEffect.exe"However, I got another general protection fault error, this time reading as such;
Faulting application name: MassEffect.exe, version: 1.2.20608.0, time stamp: 0x4a55fea1
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18229, time stamp: 0x51fb1116
Exception code: 0x40010006
Fault offset: 0x0000c41f
Faulting process id: 0x3e4c
Faulting application start time: 0x01cee01460f2b6cc
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\Mass Effect\Binaries\MassEffect.exe
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Report Id: deae1d03-4c07-11e3-a6c1-f46d0439bfcbThis time, the faulting module was kernelbase.dll which as far as I am aware is something to do with running 32-bit programs within a 64-bit operating system so this time I assumed the fault lay with compatibility. I ran Steam as an administrater and ran Mass Effect in Windows XP SP2 compatibility mode (I read somewhere to use SP2 specifically but I'm not sure what difference that would make). So far, I've gotten through all the crew dialogue on the Normandy where the crashes originally occurred and played about an hour of the game without any crashes. I'm very reluctant to say that the issue is solved so I'll keep a look out while playing further.
