[SOLVED] SOMA - has worked, but now crashes on startup - Printable Version +- Frictional Games Forum (read-only) (https://www.frictionalgames.com/forum) +-- Forum: Technical Support (https://www.frictionalgames.com/forum/forum-57.html) +--- Forum: Technical Support - SOMA (https://www.frictionalgames.com/forum/forum-74.html) +--- Thread: [SOLVED] SOMA - has worked, but now crashes on startup (/thread-32952.html) |
[SOLVED] SOMA - has worked, but now crashes on startup - jgodfrey - 11-29-2015 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 RE: SOMA - has worked, but now crashes on startup - plutomaniac - 11-30-2015 Install the latest AMD drivers from amd.com and not Windows Update or Device Manager. RE: SOMA - has worked, but now crashes on startup - jgodfrey - 12-01-2015 (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/desktop?os=Windows%2010%20-%2064 RE: SOMA - has worked, but now crashes on startup - Mudbill - 12-01-2015 Don't you need the latest beta drivers for AMD? jeff_godfrey@pobox.com - jgodfrey - 12-01-2015 (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. jeff_godfrey@pobox.com - jgodfrey - 12-01-2015 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. |