Display driver nvlddmkm stopped responding and has successfully recovered.Event ID: 14EventData \Device\Video5 CMDre 00000001 00000000 00000000 00000001 00000001 0000000002003000000000000E00AAC0000000000000000000000000000000000000000000000000
Hello,Every so often, R1Q2 freezes and stops responding. Well, there is not much to add to that problem description. I suspect that R1GL might be the culprit, since for each time R1Q2 freezed, there is a corresponding nvlddmkm error in Event Viewer, as follows:QuoteDisplay driver nvlddmkm stopped responding and has successfully recovered.Event ID: 14EventData \Device\Video5 CMDre 00000001 00000000 00000000 00000001 00000001 0000000002003000000000000E00AAC0000000000000000000000000000000000000000000000000 I tried several versions of the NVidia drivers to no avail. This happens neither in Windows nor in any other OpenGL/DirectX game. Turning off link state power managament in Power Options didn't help. I ran 3DMark for a couple hours and Intel Burntest without any errors, so I am pretty sure it's not a hardware issue.Windows 7 x64, GTX465, Core i7.Anyone got any suggestions?
idk... turn off multithreading in your nvidia control panel? old games dont like new hardware
How often does this happen? Maybe you can try a different version of r1gl.
It still freezes with R1GL 0.1.4. I don't think it's worth trying even older versions, since the 0.1.4 version was released in 2004.
Have you tried the original ref_gl, just for diagnostic purposes?
I guess you could "pinpoint" the problem by trying the default opengl renderer. Does r1q2 crash then?
Yes. The default renderer is rather old anyway for a modern 400-series NVidia card (and is long unsupported), so in light of my card being stable during stress-testing, I thought I'd not mention it.
Quote from: LohmatiyYes. The default renderer is rather old anyway for a modern 400-series NVidia card (and is long unsupported), so in light of my card being stable during stress-testing, I thought I'd not mention it.
Quote from: Lohmatiy on September 04, 2010, 12:12:50 PMQuote from: LohmatiyYes. The default renderer is rather old anyway for a modern 400-series NVidia card (and is long unsupported), so in light of my card being stable during stress-testing, I thought I'd not mention it.Oh. Sorry, somehow I don't quite understand what you've said there.