Jump to content

Question about crash


Recommended Posts

Im having a problem and am asking for help. When i start up vintage story i get a black screen and after 3 or 5 sec a pop up comes up "Vintage story stop working" and then it turns off to display without any error messages nor reports on why it crashed. I have a Win7 profesional with 6GB RAM, i played vintage story on win 10 but my laptop is too old for win 10 so basicly i backup to win 7. Any suggestion how to fix that?

Link to post
Share on other sites

Your data folder (default: %appdata%\vintagestorydata) has a logs subfolder, in which you will find client-main.txt. This file should log everything that happens during startup. See if an error message can be found towards the bottom of it after you provoke a crash.

Prime suspects are driver issues (Win7 is old), or an out-of-memory error.

  • Thanks 1
Link to post
Share on other sites
On 2/26/2021 at 7:31 PM, Streetwind said:

Your data folder (default: %appdata%\vintagestorydata) has a logs subfolder, in which you will find client-main.txt. This file should log everything that happens during startup. See if an error message can be found towards the bottom of it after you provoke a crash.

Prime suspects are driver issues (Win7 is old), or an out-of-memory error.

So i'm using that suggestion and wow that's a big problem i guess:

Event Log entries containing Vintagestory.exe, the latest 3 ================================== {TimeGenerated = 2021-02-28 13:28:05, Site =, Source = Application Error, Message = Faulting application name: Vintagestory.exe, version: 1.14.8.0, time stamp: 0x6033ac5b Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Error offset: 0x0000000000000000 Faulting process id: 0x13b8 Faulting application start time: 0x01d70dcd1f99b9f6 Faulting application path:  \ VS \ Vintagestory \ Vintagestory.exe Faulting module path: unknown Report ID: 67734f76-79c0-11eb-a5b1-782bcbd66532} -------------- {TimeGenerated = 2021-02-28 13:28:03, Site =, Source = .NET Runtime, Message = Application: Vintagestory.exe Architecture version: v4.0.30319 Description: The process aborted due to an unhandled exception. Exception Info: System.AccessViolationException at OpenTK.Graphics.OpenGL.GL.DepthRange (Single, Single) w _idIkJkIueHHf3Oz2WNlBdD0E1XR._DvzT6D0wN3fMakeuDyljJJ09hok (Single) w _idIkJkIueHHf3Oz2WNlBdD0E1XR._V5piYzG7beYPldE6UVxY58dqacE (Single) at Vintagestory.Client.NoObf.ClientPlatformWindows.window_RenderFrame (System.Object, OpenTK.FrameEventArgs) w System.EventHandler`1 [[System .__ Canon, mscorlib, Version = 4.0.0.0, Culture = neutral, PublicKeyToken = b77a5c561934e089]]. Invoke (System.Object, System .__ Canon) at OpenTK.GameWindow.RaiseRenderFrame (Double, Double ByRef) at OpenTK.GameWindow.DispatchRenderFrame () in OpenTK.GameWindow.Run (Double, Double) w _YrS2W1MoaeqC4xqH8ItdZB6vADN._8t1BmEWVlCT9mjx5M0vFIzU9tif (_7T00Rjby4si0wyEBez5dXNqLm7h, System.String []) w _ejKuc6cg0k8V39o8jDIzquyczbO._8t1BmEWVlCT9mjx5M0vFIzU9tif (System.Threading.ThreadStart) in _YrS2W1MoaeqC4xqH8ItdZB6vADN._M1VY8jQRHnZmSa0tV4cFASebLsH (System.String []) } -------------- {TimeGenerated = 2021-02-26 18:14:33, Site =, Source = Application Error, Message = Faulting application name: Vintagestory.exe, version: 1.14.4.0, timestamp: 0x5ff4340e Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Error offset: 0x0000000000000000 Faulting process id: 0x1b6c Faulting application start time: 0x01d70c62d6dc3865 Faulting application path: \ Programs \ Vintagestory \ Vintagestory.exe Faulting module path: unknown Report ID: 1795f74f-7856-11eb-a9ea-782bcbd66532}

I will try to fix it myself but would appreciate any suggestion to fix it :3 

Link to post
Share on other sites
12 minutes ago, Arbin said:

Exception Info: System.AccessViolationException at OpenTK.Graphics.OpenGL.GL.DepthRange

Error messages are always really big and bloaty, but this here is the relevant line. It describes that a graphics process died.

As I mentioned before, driver issues are a prime suspect here. Make sure you have the latest graphics driver that is available for your OS/graphics card combo.

  • Thanks 1
Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.