Just got this and it keeps crashing with access violation 0xc0000005

[Vanderdoink]

I got this to play Spring 1944 with my brother, and it worked fine at first, but now whenever I zoom in to a point where I'd be able to see my units' models the game crashes with access violation 0xc0000005. Here's an infolog.txt from my latest few sessions if it helps. Sorry if there's already a thread somewhere or if this is the wrong spot.

Background: I have Win10 64bit, a Vega 64, and an i5-6600k. I tried clean installing/rolling back the graphics driver like it said, no luck.

infolog.txt

(68.26 KiB) Downloaded 16 times

[gajop]

Using old engine and also:

[f=-000001] Warning: This stack trace indicates a problem with your graphic card driver. Please try upgrading or downgrading it. Specifically recommended is the latest driver, and one that is as old as your graphic card. Make sure to use a driver removal utility, before installing other drivers.

[Vanderdoink]

Using old engine and also:

[f=-000001] Warning: This stack trace indicates a problem with your graphic card driver. Please try upgrading or downgrading it. Specifically recommended is the latest driver, and one that is as old as your graphic card. Make sure to use a driver removal utility, before installing other drivers.

Spring 1944 doesn't work with 104, only 103. And, like I said, I tried a clean install of the latest and first driver for my card. Didn't help anything.

[gajop]

Then I think the first step should be to get s44 to 104.x. One of my projects started working better for some users when I updated the engine.

[FLOZi]

S44 was running fine under 103 afaik, so 'get someone to update the game to 104.0' is hardly going to help the chap.

[Vanderdoink]

I got it to work finally -- Turns out my graphics card doesn't play nice with 103's shadows. Just had to disable those, but I can run everything else on max.

[gajop]

Try some other game with 104 and see if just updating the engine (while enabling shadows) will solve problems for you. ZK could work.

[Jools]

Using old engine and also:

[f=-000001] Warning: This stack trace indicates a problem with your graphic card driver. Please try upgrading or downgrading it. Specifically recommended is the latest driver, and one that is as old as your graphic card. Make sure to use a driver removal utility, before installing other drivers.

That's a bullshit message though, I think it's always written in the infolog even though not relevant.

Old engines are also not necessarily worse.

[Silentwings]

That message is given in the case of: "your graphics driver crashed". (Specifically, when the stacktrace of the crash gives a code position from the gfx driver - https://github.com/spring/spring/blob/3 ... r.cpp#L344)

[FLOZi]

Try some other game with 104 and see if just updating the engine (while enabling shadows) will solve problems for you. ZK could work.

Having investigated, S44 does run under 104 but with varying results depending on graphics hardware. If his hardware is failing on 103, it seems unlikely that it will be better on 104 which has stricter graphics requirements.

[gajop]

Maybe unlikely, but worth checking still.
Keep in mind I'm not just randomly throwing suggestions. I personally had issues with shadows and an engine update fixed those.
It *might* work for him, but it's likely it might not. Worth trying in any case.

[Jools]

That message is given in the case of: "your graphics driver crashed". (Specifically, when the stacktrace of the crash gives a code position from the gfx driver - https://github.com/spring/spring/blob/3 ... r.cpp#L344)

Then there's something wrong with that stacktrace, because my experience is that there are many false positives from that logic. Maybe the gfx driver is somehow indirectly involved then, but I have never regarded that message as very useful and honestly I thought it was just a placemark message.