Bay 12 Games Forum

Please login or register.

Login with username, password and session length
Advanced search  

Author Topic: [40d11] Getting a crash and Nvidia OpenGL error 13  (Read 911 times)

smjjames

  • Bay Watcher
    • View Profile
[40d11] Getting a crash and Nvidia OpenGL error 13
« on: June 09, 2009, 02:07:12 pm »

I don't know why, but sometimes the game hangs up and a crash message pops up saying that the Nvidia opengl has encountered an error and the program must close, and it says the error is error 13.

I didn't get this with 40d. Also, sometimes when it happens, the whole screen goes blank for a few seconds (like graphics card was bieng wierd) and it comes back with the game hung up. It stays there for a few minutes before the error message comes up.

I have NVIDIA GeForce 8600M GT on this comp which is a laptop.

Edit: Oh yea, my error log says RANDOM BUFFER OVERLOAD and it has hundreds of lines, 140 MB size file. I decided to delete that file so that a new one is created since I'm not sure whether the latest is at the top or bottom.   actually, maybe I'll hold onto that....
« Last Edit: June 09, 2009, 02:18:43 pm by smjjames »
Logged

Jay

  • Bay Watcher
  • ☼Not Dead Yet☼
    • View Profile
Re: [40d11] Getting a crash and Nvidia OpenGL error 13
« Reply #1 on: June 09, 2009, 04:40:22 pm »

RBO would seem to indicate that you don't have enough RAM.  Possibly VRAM.  Which would make sense, with the error and all..

As for the graphics error, I get that when I'm running too many GPU-using programs at the same time.
I suspect, with an 8600M, which are substantially weaker than even an 8600, that that threshold would be much lower.
Try closing some programs you're not using.
Logged
Mishimanriz: Histories of Pegasi and Dictionaries

Toady One

  • The Great
    • View Profile
    • http://www.bay12games.com
Re: [40d11] Getting a crash and Nvidia OpenGL error 13
« Reply #2 on: June 09, 2009, 06:07:37 pm »

Random Buffer Overload means it is pushing on too many random seeds to track, which it should never do.  Have you been doing anything unusual during world generation?
Logged
The Toad, a Natural Resource:  Preserve yours today!

smjjames

  • Bay Watcher
    • View Profile
Re: [40d11] Getting a crash and Nvidia OpenGL error 13
« Reply #3 on: June 09, 2009, 06:18:13 pm »

I did change the good/evil balance more towards good and bumped up the volcano number, also bumped up the cave numbers. I didn't change anything else I don't think. At least there aren't any radical changes.

I do regenerate new worlds several times until I find one that I like, well, as well as deleting the region save for it if I didn't like it or changed my mind. Don't think that has anything to do with it.

Anyways, here is my current worldgen.

Edit: The seed, history seed, and name seed are all actually set to random in the advanced worldgen screen. Just letting you know.

Edit2: Would this random buffer overload be what's causing this openGL error? The crash itself seems to be random, although I often have unexplainable slowdowns in FPS after playing for a long while, but a save, quit and reload fixes this.

Created in DF v0.28.181.40d11.

[WORLD_GEN]
   [TITLE:LARGE]
   [SEED:1686955714]
   [HISTORY_SEED:4121625530]
   [NAME_SEED:2493024494]
   [DIM:257:257]
   [END_YEAR:1050]
   [BEAST_END_YEAR:300:80]
   [REVEAL_ALL_HISTORY:1]
   [CULL_HISTORICAL_FIGURES:1]
   [ELEVATION:1:400:800:800]
   [RAINFALL:0:100:400:400]
   [TEMPERATURE:25:75:400:400]
   [DRAINAGE:0:100:400:400]
   [VOLCANISM:0:100:400:400]
   [SAVAGERY:0:100:400:400]
   [ELEVATION_FREQUENCY:1:1:1:1:1:1]
   [RAIN_FREQUENCY:1:1:1:1:1:1]
   [DRAINAGE_FREQUENCY:1:1:1:1:1:1]
   [TEMPERATURE_FREQUENCY:1:1:1:1:1:1]
   [SAVAGERY_FREQUENCY:1:1:1:1:1:1]
   [VOLCANISM_FREQUENCY:1:1:1:1:1:1]
   [GOOD_SQ_COUNTS:150:1500:3000]
   [EVIL_SQ_COUNTS:50:500:1000]
   [PEAK_NUMBER_MIN:50]
   [OCEAN_EDGE_MIN:2]
   [VOLCANO_MIN:30]
   [REGION_COUNTS:SWAMP:1032:7:6]
   [REGION_COUNTS:DESERT:1032:7:6]
   [REGION_COUNTS:FOREST:4128:13:12]
   [REGION_COUNTS:MOUNTAINS:8256:9:9]
   [REGION_COUNTS:OCEAN:8256:7:6]
   [REGION_COUNTS:GLACIER:0:0:0]
   [REGION_COUNTS:TUNDRA:0:0:0]
   [REGION_COUNTS:GRASSLAND:8256:13:12]
   [REGION_COUNTS:HILLS:8256:13:12]
   [EROSION_CYCLE_COUNT:250]
   [RIVER_MINS:400:400]
   [PERIODICALLY_ERODE_EXTREMES:1]
   [OROGRAPHIC_PRECIPITATION:1]
   [SUBREGION_MAX:2750]
   [CAVE_MIN_SIZE:5]
   [CAVE_MAX_SIZE:50]
   [MOUNTAIN_CAVE_MIN:200]
   [NON_MOUNTAIN_CAVE_MIN:300]
   [ALL_CAVES_VISIBLE:1]
   [SHOW_EMBARK_RIVER:2]
   [SHOW_EMBARK_POOL:2]
   [SHOW_EMBARK_M_POOL:2]
   [SHOW_EMBARK_M_PIPE:2]
   [SHOW_EMBARK_CHASM:2]
   [SHOW_EMBARK_PIT:2]
   [SHOW_EMBARK_OTHER:2]
   [SHOW_EMBARK_TUNNEL:2]
   [TOTAL_CIV_NUMBER:50]
   [TOTAL_CIV_POPULATION:20000]
   [PLAYABLE_CIVILIZATION_REQUIRED:1]
   [ELEVATION_RANGES:8256:16512:8256]
   [RAIN_RANGES:8256:16512:8256]
   [DRAINAGE_RANGES:8256:16512:8256]
   [SAVAGERY_RANGES:8256:16512:8256]
   [VOLCANISM_RANGES:8256:16512:8256]
« Last Edit: June 09, 2009, 06:25:19 pm by smjjames »
Logged

Jay

  • Bay Watcher
  • ☼Not Dead Yet☼
    • View Profile
Re: [40d11] Getting a crash and Nvidia OpenGL error 13
« Reply #4 on: June 10, 2009, 02:56:53 pm »

I'll shove those params on my vanilla copy and see what I get.
I'd think being on a relatively high-end desktop vs a middling laptop will make a big difference, but...
EDIT: I'm noticing it's doing a lot more calculations during legends-creation then it normally does, thus it's freezing at years more often..
No error log yet.
« Last Edit: June 10, 2009, 03:03:44 pm by jaybud4 »
Logged
Mishimanriz: Histories of Pegasi and Dictionaries

smjjames

  • Bay Watcher
    • View Profile
Re: [40d11] Getting a crash and Nvidia OpenGL error 13
« Reply #5 on: June 10, 2009, 03:06:33 pm »

That's probably what I'm seeing with the freezing briefly during worldgen. I think it may have to do with the size of the world.
Logged

GenericOverusedName

  • Bay Watcher
    • View Profile
Re: [40d11] Getting a crash and Nvidia OpenGL error 13
« Reply #6 on: June 13, 2009, 07:25:57 pm »

Huh. I've been getting this error every once in a while, but now that I think about it, it only has occurred when I have a world made with some insane parameters. I'll try a vanilla world in d11 and see what I can contribute.
Logged