BSOD playing Dark Souls, error 0x00000124

[axe0]

I understand you get a crash at cutscenes?
If so, does a crash also happen when you simply skip them?

 

[Solus]

Not quite. So far all other cutscenes have played just fine; this one is special, apparently. I can pinpoint the moment when it happens, it includes a kind of visual distortion effect which causes my computer to panic for some reason. The fact that these crashes and blue screens only happen in conjunction with certain graphical effects (though apart from this one scene, not reliably) made me suspect a GPU issue but I feel like all the trouble-shooting so far says otherwise.

So, no, when I skip the cutscene, it doesn't happen.

 

[axe0]

It is more like a bug in the game self.

 

[Solus]

Well, I figured. What I wonder is why I'm affected while 99% of the people who play this aren't (that rough estimate based on so many unsuccessful Google searches). Is this too specific an issue to be solved without black magic?

 

[axe0]

How long does it take to get to that scene?

 

[Solus]

Quite a while, thanks to the autosave system. Though I could probably get my instant-crash spell back by allowing the game to use six cores instead of four and/or not downclocking the GPU anymore, if that helps.

 

[axe0]

I wouldn't try that yet.
It happens often that a simple game setting could cause crashes too, have you checked the settings?
It may take a while to find it out, or to find a stable configuration.

 

[Solus]

Oh yes. Not that DS has many settings to begin with, but I've tried. Lower resolutions, anti-aliasing/motion blur on/off, full screen, windowed. That's kind of as far as the settings go, plus I've tried borderless full screen with the help of a tool and various settings in RadeonPro and CCC (when it was still around).

 

[axe0]

Other then a small unusual glitch in the game, I am out of ideas unfortunately

 

[Solus]

D'oh. :< Black magic it is, then.

On a serious note, it does look like a conflict between the game and something specific on my side and not a "generic" problem with Windows or something which probably makes it more complicated to isolate. It's uncommon, it's obscure, and you've given me advice for almost six weeks now! That, it seems, has at least ruled out issues with my computer itself which is a good thing.

I dunno, I suppose I'll live with it for now. Maybe I'll accidentally run into a solution some day. Cheers, Mr Axe, you've nonetheless been very helpful!