Frictional Games Forum (read-only)

Full Version: [SOLVED] SOMA - has worked, but now crashes on startup
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
I have successfully played (quite a lot) of SOMA a few months ago ('ish) on a 64-bit Win7 machine with an AMD HD 7700 GPU. Since that time, the PC has been upgraded to Win 10, but still has the same GPU (with the latest AMD drivers - 15.30.1025).

Now, when I try to start SOMA (upgraded to 1.03), I get only a single dialog stating:

"LoadLibrary failed with error 998: Invalid access to memory location."

Some research seems to indicate this is likely graphics related, but my hpl.log doesn't contain much info. It's pasted in full below.

Any assistance is appreciated.

Jeff

Code:
Version 1.04
-------- THE HPL ENGINE LOG ------------
Creating Engine Modules
--------------------------------------------------------
Creating job manager with 3 threads and 1024 jobs
Creating graphics module
Creating system module
Creating resource module
Creating input module
Creating sound module
Creating physics module
Creating ai module
Creating gui module
Creating generate module
Creating haptic module
Creating scene module
Creating script module
Creating lipsync module
--------------------------------------------------------

Initializing Resources Module
--------------------------------------------------------
Creating loader handlers
Creating resource managers
Adding loaders to handlers
--------------------------------------------------------

Initializing Graphics Module
--------------------------------------------------------
Init lowlevel graphics: 1920x1080 bpp:32 rr: 60 fs:0 ms:0 driver: 0 cap:'SOMA Loading...' pos:(-1x-1)
Available drivers:
  (0) - 'windows'
  (1) - 'dummy'
Creating window: (-1,-1) 1920 x 1080 - 32 bpp flags: 3
Install the latest AMD drivers from amd.com and not Windows Update or Device Manager.
(11-30-2015, 11:05 PM)plutomaniac Wrote: [ -> ]Install the latest AMD drivers from amd.com and not Windows Update or Device Manager.

I've already done that - prior to the original report. Specifically, I installed this:

http://support.amd.com/en-us/download/de...0%20-%2064
Don't you need the latest beta drivers for AMD?
(12-01-2015, 01:59 AM)Mudbill Wrote: [ -> ]Don't you need the latest beta drivers for AMD?

Errr... The official drivers I installed are only 7 days old (see above link). Definitely newer than the drivers I had several months ago when SOMA worked. Perhaps I'll completely remove the AMD drives and reinstall them from scratch.

Other ideas welcomed.

Thanks.
OK, crisis averted... Completely removing and then reinstalling the same updated drivers seems to have fixed the problem. Not sure what went wrong the first time, but all is OK now.

Thanks.