Hard Light Productions Forums
Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Topic started by: Thrawn123 on February 02, 2009, 09:32:46 pm
-
Hello,
I am a noobie to freespace 2 and the mods, but I am having a major issue. Randomly during the game (in mission), I get a solid white screen and the application has stopped responding. In the windows event viewer I see the following:
Display driver nvlddmkm stopped responding and has successfully recovered.
So, for some reason my Nvidia driver is crashing in game I assume. Now, I am able to play other 3D games without a problem, but not FreeSpace 2 :shaking:. I am using the latest driver from Nvidia's website (7.15.11.8122 dated 1/14/2009). I know this is a general problem and not the mod (it happens when the mod is disabled), but does anyone have any ideas? Should I try an older version of the driver? Would that even help? Thanx in advance on any advice.
Vista x64, 8 GB RAM, GeForce 8800 512, Creative X-Fi, Saitek Cyborg Evo, 1080p monitor...
BTW, I am using FreeSpace 2 from gog.com, the latest nightly builds, and the latest launcher. Everything seems to be installed ok. If I keep trying, I eventually can get threw a mission, but it takes a donzen or so trys to no crash mid mission.
-
Hate to say it but this sounds like a problem with hardware not software. Usually when you get a display driver recovering from an error like that it's either the video card over heating or it's not getting enough power. Try making sure all your fans and heat syncs are clean.
-
Damn. Well, I appreciate the fast reply.
-
Thanx again for your help. I actually think I solved the issue. I uninstalled my anti-virus and so far I haven't crashed yet! Fingers crossed man... ;7
-
This would be a first at least for single player. What anti-virus software you running?
-
Actually, it is still crashing (though not as much), so no dice. Anyway, the issue appears to be on my end. I will continue to troubleshoot. Thanx though.
-
I stand by my original diagnosis then. One less process running = less power = less heat = fewer lock ups.
-
I would have to disagree with that prognosis.
I'm having the exact same issue in MP, with almost the same exact hardware layout. Vista 32bit, 8800GTS 640mb, Saitek Cyborg 3D Gold, Realtek HD audio. And I'm having the random driver crash.
My thought is that it's either FS2, FS2 Open or Vista related. I can play HL2, Crysis, Left 4 Dead and other high end games with no driver crash what so ever, as soon as I play FS2 my driver randomly crashes.
-
Tell me you've done this before coming here... :rolleyes:
Google (http://lmgtfy.com/?q=nvlddmkm+stopped+responding)
To save you from 113 pages of troubleshooting (which you should read nonetheless... :P), the discussion boiled down to this:
This driver failure can be caused by:
a) insufficient power to your card (PLUG IT IN)
b) bad RAM speed (adjust it from BIOS)
c) faulty hardware (Oooops, I hope your warranty is still good)
d) ...something else, that nobody seems to be able to identify :D
Bottom line: it's a well known problem, that has happened to lots of people (not only FSO players or Vista users) and that has never been resolved. I solved it by switching to an ATI card :doubt:
-
Thanx again for your help. I actually think I solved the issue. I uninstalled my anti-virus and so far I haven't crashed yet! Fingers crossed man... ;7
Anti virus software can mess up your driver installation, if you don't deactivate it during the installation.
Never happened to me, but I heard it happens sometimes for some anti virus software + driver constellations.
Try reinstalling your drivers, after removing them from the system.
Did you have problems in any other OpenGL games?
-
Tell me you've done this before coming here... :rolleyes:
Google (http://lmgtfy.com/?q=nvlddmkm+stopped+responding)
To save you from 113 pages of troubleshooting (which you should read nonetheless... :P), the discussion boiled down to this:
This driver failure can be caused by:
a) insufficient power to your card (PLUG IT IN)
b) bad RAM speed (adjust it from BIOS)
c) faulty hardware (Oooops, I hope your warranty is still good)
d) ...something else, that nobody seems to be able to identify :D
Bottom line: it's a well known problem, that has happened to lots of people (not only FSO players or Vista users) and that has never been resolved. I solved it by switching to an ATI card :doubt:
Been through most of that yeah. This is the first and only game I've ever had the happen to me on.
a) More than enough power for my video.
b) RAM is good, everything is set spot on and have done hours of scans with memtest.
c) Seeing as the issue has only occurred in one game and no where else, I can't see it being faulty hardware.
d)...****ty drivers is the only other thing I can come up with, and I've tried 3 different versions. All resulting in the same problem.
-
you're not the only one. i have crashes here as well, same thing. almost same hardware. E8400, 8800gts 512, 2gb 800mhz, vista 32 (no overclocking at all). 3.6.10 binary, 3.6.10 mediavps, all displaying correctly, 5.5d launcher, tried to turn off graphics features, disabled antivirus (avast) and adaware. tried nightly builds as well (currently running the latest). checked temperature history of all sensors using speedfan, everything is quite cool, nothing out of ordinary.
bought freespace (both) from GOG.com, and installed fs2_open with turey's java installer.
the only thing that actually helps a bit is running debug binary, reduces crashes to a, barely acceptable level. still you wont get rid of the completely, but it certainly helps.
most surprising thing is that it seems that it doesn't affect BtRL, that one runs quite well (but maybe thats caused by rather short missions). none of my other games crash (mainstream hardware id say). tried Doom3 to be sure its not a problem with OpenGL. i too think it might be caused by some old long forgotten bug in nvidia drivers (using 182.06). if so, either someone can spot it and coding guyz can come up with some work around, or we're screwed....well...not that much since i've had so much patience that i already played whole FS1, ST and FS2 campaign. i can take it with other mods as well, but i doubt guyz in multiplayer are going to be so forgiving :P.
-
the only thing that actually helps a bit is running debug binary, reduces crashes to a, barely acceptable level. still you wont get rid of the completely, but it certainly helps.
:wtf: Weird, since debug builds should crash even on more insignificant errors. If the debug build crashes at some point, could you try running it up to the crash and then post the fs2_open.log file from your \freespace2\data\ folder? It could provide some information on what happens when the game crashes.
-
fine working on it....seems ive been somewhat "lucky" in last few hours of playing. not being able to spot a reason for apps crashing is actually bad thing so maybe "lucky" is not the proper word.
tried about 10 different missions in tech room, none crashed. so i decided to create yet another pilot profile (yes IVE BEEN CAREFUL, I DID CREATE A NEW PILOT FOR EACH MOD even fsport, sry for caps, but if i were you id become suspicous about it :)) to go through the campaign again, not yet a single crash so far (my current mission is A Game of Tag now), except for one team != 1 assertion in Enif Station evac (The Sixth Wonder), i suppose you dont want this one (at least not now). normally playing this long would result in like 2-3 crashes. this doesnt count as "barely acceptable i know", but later missions were more crashy. this is not true for the release build.
i hope ill come up with the log soon.
-
GOT IT!!!! and i think i found the reason too! first, when i created new profile for playing i didnt set up all graphics to max IN-GAME. i did set them in the original profile. just a custom from retail versions of freespace, then in the test profile i just ignored it. i know i shouldnt change circumstances when looking for bug but i was suspicous. nevertheless i did it. about half and hour ago, my conscience got the best of me and i created another profile, where i DID set graphics settings to max in-game. played first mission no problem, then the second mission. second mission (ntf cargo base raid, meet ntf iceni) went just fine up until i began subspace jump back to base, about half a second before i got through, the game crashed. one more thing before the logs. i just noticed that i have greyscale asteroid explosions, but that is a known glitch, so theres no real need to get excited about it.
and now the logs:
fs2_open.log is cut off just after warp event.
theres no dump in errorlog.txt, last one is from 1st March, some exception of sorts. doesnt matter now i suppose.
so, enjoy the work :( and the glory :) of bug fixing :P. or maybe just forget it and put a huge warning into readme.
[attachment deleted by admin]
-
You probably shouldn't have any VPs in your Freespace 2\data\movies\ folder. Granted it would appear to be empty, but I don't even know what it's doing there in the first place. In fact, that movies folder is unnecessary since you have the OGG cutscene pack, you can probably just delete it, but I have no idea what might still be in there besides that one VP file.
Here's something bizarre...
Yours:
Initializing OpenGL graphics device at 1280x1024 with 32-bit color...
Initializing WGL...
Requested WGL Video values = R: 8, G: 8, B: 8, depth: 32, double-buffer: 1
Actual WGL Video values = R: 8, G: 8, B: 8, depth: 32, double-buffer: 1
OpenGL Vendor : NVIDIA Corporation
OpenGL Renderer : GeForce 8800 GTS 512/PCI/SSE2
OpenGL Version : 3.0.0
...
Shader Version: 1.30 NVIDIA via Cg compiler
Mine:
Initializing OpenGL graphics device at 1680x1050 with 32-bit color...
Initializing WGL...
Requested WGL Video values = R: 8, G: 8, B: 8, depth: 32, double-buffer: 1
Actual WGL Video values = R: 8, G: 8, B: 8, depth: 32, double-buffer: 1
OpenGL Vendor : NVIDIA Corporation
OpenGL Renderer : GeForce 8800 GTS 512/PCI/SSE2
OpenGL Version : 2.1.2
...
Shader Version: 1.20 NVIDIA via Cg compiler
How do you have the same card as I do and a different OpenGL version? May I ask what driver version you have installed? I think I'm using the 185.20 beta Ambient Occlusion driver from here (http://forums.techpowerup.com/showthread.php?t=80520). The newest drivers might have changed something though.
-
didnt noticed that vp. maybe that was one of my attempts to figure out why the crashes are happening, and i didnt thought that it might be browsing movies folder for vps as well, but that shouldnt screw anything up should it. what is actually better? ogg cutscene pack or original freespace 2 movies? my current forceware version is 182.06, running on vista32
-
didnt thought that it might be browsing movies folder for vps as well, but that shouldnt screw anything up should it.
No. Due to its location, it is read after all the other files, so it couldn't override any data. And as chief said, it is empty so there's no overriding data to begin with.
what is actually better? ogg cutscene pack or original freespace 2 movies?
Really a matter of opinion. The original (.mve) cutscenes have insignificantly better quality, but they take up more space. The pack might be a bit handier since all you have to do is to punch it to \freespace2\. Separate cutscenes would have to be placed to \freespace2\data\movies\.
Of course, if you plan on playing retail FS2, you'll need to have the .mve cutscenes since Ogg support is an FSO feature.
-
fine, chose the original cutscenes. not really have to worry about space.
thanks
-
Same things happening to me.