Strange Crashes Since Last Update - CRITICAL

[Eyesgood 2134]

Twice today I have had this issue happen AND GIVEN THE EFFECTS OF THIS PROBLEM - I BELIEVE THIS IS A CRITICAL BUG.  

 

Windows 7, 8-core AMD, 16 gigs ram, NVidia GTX 560 with 2 gigs, Dual display running two clients.

 

In the middle of playing, the graphics card locked up and crashed sending me to the desktop.  The first time it happened, I honestly thought my video card had fried.  The issue was so bad that Windows 7 disabled my video card and that is what made me think my card had fried because rebooting Windows 7 put Windows in a 640x480 resolution with many tearing and graphic glitches.  

 

I was able to recover from this problem by going into the control panel, disabling the video card and then re-enabling it.  A reboot fixed the problem.

 

In both cases, I was running two Wurm clients on max settings (except for caves on low).

 

Nothing else has been running.  The NVidia GeForce Experience intercepted the crash and sent me to a webpage with the following information.

 

http://nvidia.custhelp.com/app/answers/detail/a_id/3007

 

 

 

OpenGL message “lost connectionâ€

Answer ID 3007   |    Published 07/14/2011 08:14 AM   |    Updated 02/06/2012 11:37 AM

OpenGL message "lost connection"

I have seen this Event Log Message:

The NVIDIA OpenGL driver lost connection with the display driver due to exceeding the Windows Time-Out limit and is unable to continue.

The application must close.

 

What does it mean?

If you received this message from an application (on a pop up message or in the Event Log), the application was unable to continue rendering because the Microsoft Windows imposed time limit (TDR) was exceeded. This is normally the case when the workload sent to the Graphics Card is greater than what the graphics card can process in the normal timeout of two seconds.

You can find more information in this page:

http://msdn.microsoft.com/en-us/windows/hardware/gg487368.aspx

How can this be fixed?

Two possible solutions to try would be:

1. 
   
   Reduce the graphics workload if possible, such as rendering to a lower resolution or with less detail.
   
   
   
2. 
   
   Increase the timeout to allow more time to complete the really tough rendering parts. Microsoft provides the information on how to modify the Windows Registry to achieve this.
   
   
   

 

 

 

here is the last few lines of my console log:

 

Can't move creature 386454748399106 because it doesn't exist

Can't move creature 386454748399106 because it doesn't exist

Can't move creature 386454748399106 because it doesn't exist

Can't move creature 386454748399106 because it doesn't exist

Can't move creature 386454748399106 because it doesn't exist

Can't move creature 386454748399106 because it doesn't exist

Can't move creature 386454748399106 because it doesn't exist

Can't add effect to 1002517945124354 because it doesn't exist.

Feb 01, 2014 9:54:24 PM class.qO3HnCUoE2 Ma4vZ9hcx8

WARNING: Cannot play animation for 215100687878 because it doesn't exist.

Feb 01, 2014 10:02:10 PM class.qO3HnCUoE2 Ma4vZ9hcx8

WARNING: Cannot play animation for 216409310726 because it doesn't exist.

Can't add effect to 798342346966530 because it doesn't exist.

Feb 01, 2014 10:05:48 PM class.qO3HnCUoE2 Ma4vZ9hcx8

WARNING: Cannot play animation for 216593860102 because it doesn't exist.

Can't remove effect from 1002517945124354 because it doesn't exist.

Can't remove effect from 1002517945124354 because it doesn't exist.

Failed to open fence 876206424071 because it doesn't exist.

Failed to open fence 876206424071 because it doesn't exist.

Decreasing image buffer to 4194304

Failed to open fence 876206424071 because it doesn't exist.

Failed to open fence 876206424071 because it doesn't exist.

Initializing font texture for SansSerif (24, bold). Texture Size: 256

WARNING: Fake did not exist for class.qGftWALRCA@410903

Edited February 2, 2014 by Eyesgood

[Sefra 1]

Turn off GLSL??? Under compatibility??? Profit...

Edited February 2, 2014 by Sefra

[Eyesgood 2134]

I can play Skyrim on max settings with all of the intense village mods....  I don't think my rig is under compatible.  I think Wurm is under-optimized.

[rosedragon 2282]

Wurm sometimes did cause my nvidia (either the experience addon or the driver) to stop responding either.. it is random case and I can't pinpoint why.. happens after long hours.. I think memory leak?

[Sefra 1]

Regardless nVidia is Intel buddy. Intel has lots of problems with Java brotha.

[Zwei 210]

Same with me, but im a lower-end rig so I don't see differences in lag often, since i lag constantly, but I cant tell its very weird that on my XP I never got this problem, but on W7, I have ended up crashing my display driver over 5 times a row in a 1 hour period.

 

I feel like the sudden drop in FPS that happened for alot of people in that past update is something to deal with this. i think a "test search and destroy bug" is needed instead of "tweaking as the updates come along."

[rosedragon 2282]

 

Same with me, but im a lower-end rig so I don't see differences in lag often, since i lag constantly, but I cant tell its very weird that on my XP I never got this problem, but on W7, I have ended up crashing my display driver over 5 times a row in a 1 hour period.

 

that was the same.. tho wurm is the reason i upgrade to win7.. i forgot why tho.. maybe i though the wrong problem

[Budda 2726]

From the lines in console, none of those errors would be to do with this crash.

 

It's possible that there is some issue with memory going on, but we certainly don't use enough of the GPU to cause a 560 to hang for 2 seconds while processing, and the memory issue is likely only on RAM, not on the GPU memory (though could be an option - I don't see it causing this timeout though if it is that).

 

All I can really suggest is forcing an update/reinstall of your graphics drivers, having a good look through to make sure there aren't sneaky programs running in the background that might be taxing your card etc.

 

There will be some debugging going on this week to figure out some (likely unrelated to this) memory issues, so when those are fixed it may also help you out - but I doubt it

 

So yeah, best bet for now would be forcing a reinstall of gfx drivers and seeing if that helps.

 

EDIT: Someone also just mentioned it might be the nVidia driver/application changing the card into low power mode for some reason.

Possibly try changing this setting (only if this crash happens again)

 

Power Management Mode: Available only for the GeForce 9 series and above, this feature makes use of these graphics cards' abilities to support different performance levels depending on how much power is required by a 3D application. The available options here are Adaptive and 'Prefer Maximum Performance'. Adaptive is the default, and when chosen the graphics card automatically steps down in clock speed in 3D applications if they are not drawing much GPU power. Adaptive is the recommended setting for all users because it ensures that the GPU steps down its clock speed and hence power usage when it is not required. In 3D gaming the Adaptive setting should not cause any problems, as the GPU will always run at full speed when required without interruption. Typically only very old games and very basic 3D applications may see the graphics card reduce its power, and even then this may be desirable. However if you are concerned that a game is not performing properly, particularly for troubleshooting purposes, then you can change this setting to 'Prefer Maximum Performance' to ensure that the card is always running at maximum clock speed. Remember that this setting only relates to 3D applications and games, not to the Windows Desktop for example.