Grimrock

Hi all,

Normally a really occasional issue which generally goes after a couple of seconds or shutting down and re-opening Grimrock which wasn't a biggy.

Then we have this evening which didn't want to go away. In the Pyramid and it starts up and won't stop and gets worse and worse!

I'm not getting any issues with any other games, drivers are up to date and on defaults. Nothing major running in the background and my system is pretty decent: I5 2500k @ 4.6, GTX 980, SSD, 8GB RAM.

http://youtu.be/wJ66Zwwwzes

That's no input lag.
Your system or GPU hangs, easy visible by 0:35 when you turn to the left and the display just freezes, then turns into a black screen.

Check the windows event log. You prolly find reports about nVidia driver freezes.
In case this statement "I5 2500k @ 4.6" is true you prolly overdid it with overclocking.

Dr.Disaster wrote:That's no input lag.
Your system or GPU hangs, easy visible by 0:35 when you turn to the left and the display just freezes, then turns into a black screen.

Check the windows event log. You prolly find reports about nVidia driver freezes.
In case this statement "I5 2500k @ 4.6" is true you prolly overdid it with overclocking.

Na, it's not the OC on the CPU, that's absolutely rock solid on everything and the issue is intermittent with Grimrock 2, although it's now doing the same thing on the startup menu!

As you (and I) suspected it's a GPU driver issue.

"Graphics Exception: ESR 0x405840=0xa2040800"

https://forums.geforce.com/default/topi ... -stopped-/

But, it's only Grimrock 2, tested Alien: Isolation and Shadows of Mordor (with over 50 hours of playtime without a hiccup) and they have zero issues.

You are refering to a 6 year old TDR post and obviously missed the important part:

As a starting note, this is not an nVidia issue. It is not an ATI issue either. These errors are triggered by a Windows service called 'Timeout Detection and Recovery' (TDR). You will only see this error on Windows Vista and Windows 7, as TDR is a feature of the new WDDM driver model (implemented first in Windows Vista).

As you know Windows is run by the CPU, not GPU, so please retry without overclocking your CPU.

I'll take my 25 years experience over yours mate, it's not the OC. It's most likely a bad call from the game to DX or some quirky conflict in my system.

A full reboot, as recommended in the article provided, has fixed the issue temporarily.

RubberbandAU wrote:I'll take my 25 years experience over yours mate, it's not the OC. It's most likely a bad call from the game to DX or some quirky conflict in my system.

A full reboot, as recommended in the article provided, has fixed the issue temporarily.

Hi, while you surely have the temperatures of gpu & cpu in view, could it be still gpu ovetheating instability as grimrock is notorious for? What temeperatures your rig reaches with log2?

badhabit wrote:Hi, while you surely have the temperatures of gpu & cpu in view, could it be still gpu ovetheating instability as grimrock is notorious for? What temeperatures your rig reaches with log2?

Watch his video. His GPU does not even reach 60 degrees Celcius.

The behavior shown in the video is without a doubt video flicker followed by a GPU and/or driver lockup followed by a black screen. The black screen is actually Windows doing his usual TDR routine when it thinks the video driver locked up and needs to be restarted. Now since he massively overclocked his CPU and LoG2 makes intensive use of it i bet his system timings are out of sync causing this.