Home Trending Latest threads New posts Developer diaries

Game crashed, OpenGL issue

Jump to latest Follow Reply
  • We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.
U

unmerged(378631)

Corporal
1 Badges
Sep 16, 2011
36
0
  • Cities in Motion
Okay, first of all, I looked around the forums for a bit, I didn't seem to find any solution that I thought I should try. Sorry if I missed anything!

On to the problem. My issue is, that every time I play the Berlin mission, and apparantly, only when I start building some bus stops, I get the following message:

"The NVIDIA OpenGL driver lost connection with the display driver and is unable to continue. The application must close.

Please visit http://www.nvidia.com/page/support.html for help.
Error code: 8"

Now, I have visited the page, and found the error code there. The solutions just did not work for me.

The log_metro shows this:

Opened log in "userdata/log_metro.txt".
Version: 1.0.21
initializing FMOD...
[done]
initializing OpenGL-window...
[done]
Loaded language "en_US"
Engine initialization finished
Loading ui...
[done]
Loading addon "addons/germany"...
[done]
Loading addon "addons/mappack01"...
[done]
Loading addon "addons/munich"...
[done]
Loading addon "addons/stationpack01"...
[done]
Loading addon "addons/tokyo"...
[done]
Loading addon "addons/vehiclepack01"...
[done]
Loading addon "addons/vehiclepack02"...
[done]
Loading addon "addons/vehiclepack03"...
[done]
Loading addon "addons/vehiclepack04"...
[done]
Loading achievements...
[done]
Loading main menu...
[done]
Steam initialized
Start scenario "metro/scenarios/scenario01.scenario"
Loading game...
[done]
Error: Runtime error in "metro/scripts/ui.script" at line 343: Internal error!

To spare you for the spam, the last line is repeated 3 billion times or so.

The solution on nvidia.com tells me to lower graphics etc. I have tried it. I have tried lowereing everything separately, and everything at once. The worst time actually was when I turned off EVERYTHING, lowered my resolution and lowered the monitors ingame hz. It forced a reboot, which it usually does not.

Anyways, before the reboot, the log did NOT show any errors. It did this time though. So I don't know if the error message is from the actual crash report, or from my most recent tries after the reboot.

The only thing I haven't tried, is increasing the rendering time. (Nvidia suggests that could be a solution). I don't really know what to search for, so if anyone knows, I'd be more then happy and willing to give that a shot. It's supposed to be done through the windows registry base.

My specs are:

ASRock X58 Extreme Motherboard
Geforce GTX 570 video card with 1280 MB RAM (With newest drivers and DX11)
6GB triple channel Kingston DDR3 SDRAM (3x2 GB Sticks)

I played the tutorial with NO problems, what so ever. Anyways, if there is anything else you need to know, just say so! I hope someone can help me!
 
Check your graphic card specs again. 1280 MB is not possible. It might be 128 MB, or 1024 MB (sometimes referred as 1 GB).
If it is 128 MB then your graphic card is not supported by the game.
 
What version of the driver are you using? You say latest, but it is all relative :D
I googled around a bit and NVidia support forum talks they possibly fixed that issue in drivers 275.59 and higher (it could be at this point, the latest drivers you want to use are the beta drivers so the latest fix are in)
 
co_damsku said:
What version of the driver are you using? You say latest, but it is all relative :D
I googled around a bit and NVidia support forum talks they possibly fixed that issue in drivers 275.59 and higher (it could be at this point, the latest drivers you want to use are the beta drivers so the latest fix are in)
Click to expand...

280.26. I used the Nvidia downlaod drivers section, and that was the version it came up with.
 
Then they obviously haven't fixed it...
I'm sorry but I unfortunately have no other ideas than the ones you have tried already :/
Your best bet is to do some more googling about this error, it seems a lot of people have been getting it.
 
co_damsku said:
Then they obviously haven't fixed it...
I'm sorry but I unfortunately have no other ideas than the ones you have tried already :/
Your best bet is to do some more googling about this error, it seems a lot of people have been getting it.
Click to expand...

Hmm. I have actually been googling it a lot. And I have found absolutely no one with this problem. I've seen a lot with crashing problems, but none with my exact problem. Do you have any links to people with the same problem?
 
co_damsku said:
I just checked quickly "NVidia error code 8", seems most of the people have that with a different model than your card. But if it's a driver problem, it can very well apply to your model too...
Maybe you could give a shot to the 280.27 drivers: http://www.nvidia.co.uk/object/win7-winvista-64bit-285.27-beta-driver-uk.html
Click to expand...

Is it because it's a beta version that it wasn't suggested I download that when I searched for new drivers for my card?

Anyways, I'll try them out, and get back to you. Thanks for the replies. Are you on for a while?
 
Yes, the beta version are not on the WHQL download page, that's why you didn't see it.
We are really trying our luck here, it might be it won't help or it might be it will work even less (they are beta and they are drivers ! :))
I am not sure how much longer I will be online, but I'll refresh the thread as long as I am around :)
 
co_damsku said:
Yes, the beta version are not on the WHQL download page, that's why you didn't see it.
We are really trying our luck here, it might be it won't help or it might be it will work even less (they are beta and they are drivers ! :))
I am not sure how much longer I will be online, but I'll refresh the thread as long as I am around :)
Click to expand...

It seems for now that the beta drivers are keeping it pretty stabil. I covered almost whole Berlin with bus stops, no crash. Build a tram line, no crash. Played for about 20 minutes, no crash. And 20 minutes is just about the longest I have ever played this mission. So, at first glance, it SEEMS to be working.

Now, another problem. It might not be your area of expertice, but it appeared following a CiM crash+reboot.

Now, when my computer starts up, it detects my ram, harddrives etc. As it used to do of course. But now, it "hangs". When it's done detecting, it hangs for about 20-30 seconds, then some numbers appear, and it moves on. (Too fast to see the numbers).
Then, at the login screen, after I type in my password, it takes forever at the Welcome screen. Used to take 1-2 seconds, now it takes 20 seconds maybe. And if that wasn't enough, when it's done "Welcomming" me, there is just a black screen. I have my mouse, and I can get out the task manager. A forced log off and on again usually does the trick, and some times I have to do it twice. But you can understand it's pretty annoying if I have to do this every time now.

I realise this isn't exactly CiM related, but I figured, since it appeared after a CiM crash.

If you can't help me, no worries about it. Then I shall be on my merry bus, and will thank you for the help fixing my first problem. I will be back here if I jumped the gun here. Thanks again!
 
Good news the beta driver seems more stable !
About your other issue, it ain't really related to CiM but if you had a hard reboot, it might be something went bust with your harddrive. Could be some of the windows files got "messed up" or something.
I would suggest you run a full checkdisk or whatever that was called from the Windows System Tools. It should be able to repair the bad blocks and that might get the machine back to normal.
I think there might also be some other Windows system tools to check/repair possible issues with the machine, you should take a look in that direction. :)
 
co_damsku said:
Good news the beta driver seems more stable !
About your other issue, it ain't really related to CiM but if you had a hard reboot, it might be something went bust with your harddrive. Could be some of the windows files got "messed up" or something.
I would suggest you run a full checkdisk or whatever that was called from the Windows System Tools. It should be able to repair the bad blocks and that might get the machine back to normal.
I think there might also be some other Windows system tools to check/repair possible issues with the machine, you should take a look in that direction. :)
Click to expand...

I will have a looksee. Thanks for the info!
 
Damn. Today I started the game, and got a crash while trying to place bus stops again :( Same message. Although, error code 7 this time. But the link takes me to the same Nvidia support page.

Edit: I have reinstalled my OS. (It was due time). I still have the same problem. Although, now I don't get an error message, the game just crashes whenever I try to build stuff.
 
Last edited:
I am having the same problems.

My error code is 7 TOO. This is due to an detection error in some drivers process call TDRdelay. The defaulr windows value is 2 secondes.... witvh seem not to be enought ... (strange !!!)

In order to modify the TDR you have to modify some key in your registry:
HKEY_LOCAL_MACHINE>SYSTEM>CurrentControlSet>Contro l>GraphicsDrivers

There will probably one key in there called DxgKrnlVersion there as a DWord. Dont change it.

Right click and select to create a new key REG_DWORD, and name it TdrDelay. The value assigned to it is the number of seconds before TDR kicks in - it is currently 2 automatically in Windows (even though the reg. key value doesn't exist until you create it). Assign it with a new value (I tried 4 seconds), which doubles the time before TDR. Then restart PC. You need to restart the PC before the value will work.



Also, you can add the following key:
HKEY_LOCAL_MACHINE>SYSTEM>CurrentControlSet>Contro l>GraphicsDrivers

Right click and select to create a new key REG_DWORD, and name it TdrLimitCount. Assign a value of 999 (in decimal). This will help also ....




Operating System : Win7 Pro 6.1.7601 SP1
QuadCore Intel Core i7-2600K StepD2
Asus Sabertooth P67 Sandy bridge Bios 1850
16360 MB 4X ( 4 GB DDR3-1333 DDR3 SDRAM (9-9-9-24 @ 666 MHz) Corsair CMZ16GX3M4A1600C9
NVIDIA GeForce GTX 580 (1536 MB) GF110 RevA1 Version 70.10.17.0.1 drivers (auto+updates+beta) 285.27
LCD 24" Iiyama ProLite E2407HDS
OpenGL GeForce GTX 580/PCI/SSE2 v4.2.0
Hdd 1TO WDC WD1002FAEX-00Y9A0
 
Last edited:
stratege1401 said:
I am having the same problems.

My error code is 7 TOO. This is due to an detection error in some drivers process call TDRdelay. The defaulr windows value is 2 secondes.... witvh seem not to be enought ... (strange !!!)

In order to modify the TDR you have to modify some key in your registry:
HKEY_LOCAL_MACHINE>SYSTEM>CurrentControlSet>Contro l>GraphicsDrivers

There will probably one key in there called DxgKrnlVersion there as a DWord. Dont change it.

Right click and select to create a new key REG_DWORD, and name it TdrDelay. The value assigned to it is the number of seconds before TDR kicks in - it is currently 2 automatically in Windows (even though the reg. key value doesn't exist until you create it). Assign it with a new value (I tried 4 seconds), which doubles the time before TDR. Then restart PC. You need to restart the PC before the value will work.



Also, you can add the following key:
HKEY_LOCAL_MACHINE>SYSTEM>CurrentControlSet>Contro l>GraphicsDrivers

Right click and select to create a new key REG_DWORD, and name it TdrLimitCount. Assign a value of 999 (in decimal). This will help also ....




Operating System : Win7 Pro 6.1.7601 SP1
QuadCore Intel Core i7-2600K StepD2
Asus Sabertooth P67 Sandy bridge Bios 1850
16360 MB 4X ( 4 GB DDR3-1333 DDR3 SDRAM (9-9-9-24 @ 666 MHz) Corsair CMZ16GX3M4A1600C9
NVIDIA GeForce GTX 580 (1536 MB) GF110 RevA1 Version 70.10.17.0.1 drivers (auto+updates+beta) 285.27
LCD 24" Iiyama ProLite E2407HDS
OpenGL GeForce GTX 580/PCI/SSE2 v4.2.0
Hdd 1TO WDC WD1002FAEX-00Y9A0
Click to expand...

Hello! I already tried this. But I didn't try with the TdrLimitCount. What exactly does that do? I set the delay at some point to 10 seconds. I could see that it had worked what I did, but it still didn't fix the problem. It just meant that it actually lingered longer in the game, before crashing, after I get the "Lost connection" message.

What should the TdrLimitCount do?
 
So, am I just supposed to let this game go, even though I've spent money on it? Some help would be nice.

You mentioned earlier that I might have to wait for some drivers from nvidia. How come it's their drivers that's faulty? Why not your game that has a flaw? I'm by no means a computer geek, but I have some basic knowledge. I just fail to see how it can be nvidias problem when you have created a piece of software that doesn't play well with theirs?

I'm kind of annoyed that a game I bought can't be played on a fairly new, mid-high end computer. And since it's bought on steam, no refund either.
 
Hi Xzoltan,

Unfortunately, the beta drivers did not help. At this point, I would suggest you try to revert to an older version of the drivers. It seems people on the interwebs have been having the same error with their graphics card and for some, reverting to the previous version of the whql driver helped.
I'd like to suggest one more thing, I know you have already tried and lower your graphics settings and the result was not promising. However, did you try to change the cursor to System cursor in the graphics settings? For some very odd reasons, I have read on this forum it had helped some people having issues with drivers... I think you should definitely give it a try too, if you haven't yet. Also, does running the game in windowed mode changes the behaviour in any way? If you haven't tried this yet, it would be worth a try too.
And that is one long shot, but I think if your computer is so you can open it (without voiding guarantee), you should double check the graphics card is not badly pinned by removing it entirely from its slot, blow the potential dust on it and put it back. The error you see can be an hardware malfunction caused by some "misplaced dust".
Cheers,

/D
 
You must log in or register to reply here.
Top Bottom
Back