Display driver stopped responding and has successfully recovered

In 4.0c beta 2, I have been getting frequent crashes of the display driver.

Sometimes Logos just suddenly crashes (apparently randomly). More often the screen will go suddenly blank for
a second, then I get the Windows error "Display driver stopped responding and has successfully recovered". Logos may not crash in this case.

The problem has been happening several times a day over the past few days. I cannot see a pattern yet. It does seem to happen when I have not done anything with Logos for a while and it has just been running side by side with my word processor. When this happens, sometimes the Logos screen will go black, the error message will appear, then I get a Logos crash. Other times, the whole display flashes and then Logos continues running without crashing.

In am running Windows 7 x64, on a Thinkpad W510 laptop with an i7 processor and an NVIDIA Quadro FX880M processor. All of the Windows and display drivers are up to date.

I will try to run with logging enabled and see if I can catch a useful error log. It is unpredictable, however. I know people will blame the display driver, but no other program causes this to happen. I wonder if others have had a similar problem.

Find more posts tagged with

Comments

Daniel Lee

I will try to run with logging enabled and see if I can catch a useful error log. It is unpredictable, however. I know people will blame the display driver, but no other program causes this to happen. I wonder if others have had a similar problem.

I have a similar issue with my ATI card, but not usually in Logos, more if I stress the video card with a graphics-intensive game or application. Could it be that Logos is the most graphically intensive program that you use? If you haven't updated to the latest NVidia driver, I would try that as a first step. It also seems to be an issue restricted to Vista or Windows 7 x64, as I never had the display driver crash in Windows XP but then it crashes periodically after I updated to Vista x64 last year. There are a few other options to try. How much RAM do you have?

Harry Hahne

It took a few hours or running Logogs before the display driver crashed today. First Logos had a blank screen within the program borders. Other programs were still working fine. Then a couple of seconds later I got the message that the Display driver stopped responding and has successfully recovered". I shut down Logos at that point.

Here is the log, for what it is worth.

5340.Logos4.log

Dave Hooton

https://community.logos.com/discussion/comment/116454#Comment_116454

Lots of activity from the Panel Linking Manager, which doesn't do a thing on my system. Were you moving/resizing panels?

Harry Hahne

https://community.logos.com/discussion/comment/116653#Comment_116653

Lots of activity from the Panel Linking Manager, which doesn't do a thing on my system. Were you moving/resizing panels?

At the time I don't believe was doing anything in Logos. It was just running side by side with my word processor while I was typing in my word processor. I had not done any moving panels or opened any resources.

Sometimes this will happen when I just have it open and the focus is elsewhere. The screen in Logos goes back and then a couple of seconds later the crash of the display driver happens. The word processor is not affected. At other times I will click on an open panel in Logos and it will then crash the display driver.

Dave Hooton

https://community.logos.com/discussion/comment/117440#Comment_117440

Ok, we need to hear from Logos as the Panel Linking Manager activity is unusual.