Archived

This topic is now archived and is closed to further replies.

nandrews

Video corruption after an hour or so

Recommended Posts

Help AVSIM continue to serve you!
Please donate today!

Idea I got from another forum : Grab this tool Filemon http://technet.microsoft.com/en-us/sysinte...s/bb896642.aspxRun itRun FSXFly until freezethen go to the tool and filter the "Result" column for "file not found"Who knows !
Jerome,I'd be willing to try it as well, but in my case FSX doesn't actually crash. What happens is I get extreme graphics corruption that makes the sim immediately unplayable, and requires me to then exit the sim and restart it. So, I don't know right now if that utility will give me any results. I can tell you that I tried a suggestion from the other ongoing thread. The suggestion was to try and lower FSXs priority to "Below Normal" or "Low" through taskmanager. So, far it did not have any effect on "Below Normal", but I haven't tried "Low" yet.Jay

Share this post


Link to post
Share on other sites

jaybird1nyc,I see that your system is overclocked. It does not matter how much you stress test your system with prime95 or OCCT or any other overclocking stress test utility, FSX will stress your system to a whole new level above a beyond the overclocking utilities.. It has been my experience and many others experience that the problem this thread is discussing is caused by an unstable overclock. That could be voltages that are to low or memory and timing being to aggressive (this can also be heated related i.e. your system memory cannot dissipate the heat efficiently).I can stress test my system all day long with my memory running at 1600MHz and play titles other than FSX and the system will run just fine. The minute I run FSX with memory set at 1600MHz (evening raising NB, SB anad memory voltages) FSX will crash with graphics corruption.There are way too many people out there that do not heed this advice and chase their tails for months on end, the they end up bad mouthing MS as well as video card manufacturers for bad drivers and its just not the case.So, try relaxing your overclock and you mat very well fix your problem.

Share this post


Link to post
Share on other sites
So, try relaxing your overclock and you mat very well fix your problem.
I've got exactly the same problem as him, and got stock speed.No CPU OC, no GPU OC, PCI-E bus at stock speed too. :(

Share this post


Link to post
Share on other sites
jaybird1nyc,I see that your system is overclocked. It does not matter how much you stress test your system with prime95 or OCCT or any other overclocking stress test utility, FSX will stress your system to a whole new level above a beyond the overclocking utilities.. It has been my experience and many others experience that the problem this thread is discussing is caused by an unstable overclock. That could be voltages that are to low or memory and timing being to aggressive (this can also be heated related i.e. your system memory cannot dissipate the heat efficiently).I can stress test my system all day long with my memory running at 1600MHz and play titles other than FSX and the system will run just fine. The minute I run FSX with memory set at 1600MHz (evening raising NB, SB anad memory voltages) FSX will crash with graphics corruption.There are way too many people out there that do not heed this advice and chase their tails for months on end, the they end up bad mouthing MS as well as video card manufacturers for bad drivers and its just not the case.So, try relaxing your overclock and you mat very well fix your problem.
Sarge, Thanks for the suggestion, however it didn't fix the problem. First I tried backing off on just the memory speed (which wasn't over the rated speed to begin with), then I just put everything back to stock speeds, no OC at all. No joy :(
I've got exactly the same problem as him, and got stock speed.No CPU OC, no GPU OC, PCI-E bus at stock speed too. :(
Jerome,In addition to reverting back to stock speeds, I ran with no weather, no clouds. No luck... :( Also had no bufferpools set, tbm=40, tried different frame lock settings; 20, 24, 30 and unlimited w/frame lock utility enabled.Have you had any luck at all???Jay

Share this post


Link to post
Share on other sites

jaybird1nyc,Let's try and get you sorted out first. Can you to please post your FSX slider settings, your nHancer settings and any changes you made to your fsx.cfg file. Have you at anytime changed the drivers you are using for you GTX260? If you have changed your drivers, how exactly did you go about uninstalling your existing driver and installing your new driver?

Share this post


Link to post
Share on other sites
Jerome,Have you had any luck at all???Jay
I made a first flight in FSX for 35 minutes using default cessna from LFMN to LIMG, VFR conditions using TileProxy.I started to have some display freeze - corruption or degradation, but it was still flyable (normal 30+ FPS recovering after a 10 sec freezee period).While flying i monitored a bit the processes. I notice jqs.exe and wscntfy.exe popping up and down during the freezes.- disabled "Security Center" in the windows services (start/run services.msc then click security center then stop). Source of process wscntfy.exe.- killed jqs.exe (java quick start)- Killed vlc.exe (had an instance running)- disabled antivirus (I forgot to do it - usually always do)Did another flight in south miami, still VFR/TP, and experienced no freezes at all this time.Maybe it's just a placebo effect, probably I should have tested in the same place, always with the same protocol (LDS767 or another memory eater), but maybe there's an improvement here.Can you give it a try as well ? PS : still necessary to run a filemon _during_ the freeze, I would like to make sure fsx doesn't seek for non-existing files (usually textures) when the freezes occurs. I've seen many posts about this FSX file seek issue, that can potentially be related as well.

Share this post


Link to post
Share on other sites
I made a first flight in FSX for 35 minutes using default cessna from LFMN to LIMG, VFR conditions using TileProxy.I started to have some display freeze - corruption or degradation, but it was still flyable (normal 30+ FPS recovering after a 10 sec freezee period).While flying i monitored a bit the processes. I notice jqs.exe and wscntfy.exe popping up and down during the freezes.- disabled "Security Center" in the windows services (start/run services.msc then click security center then stop). Source of process wscntfy.exe.- killed jqs.exe (java quick start)- Killed vlc.exe (had an instance running)- disabled antivirus (I forgot to do it - usually always do)Did another flight in south miami, still VFR/TP, and experienced no freezes at all this time.Maybe it's just a placebo effect, probably I should have tested in the same place, always with the same protocol (LDS767 or another memory eater), but maybe there's an improvement here.Can you give it a try as well ? PS : still necessary to run a filemon _during_ the freeze, I would like to make sure fsx doesn't seek for non-existing files (usually textures) when the freezes occurs. I've seen many posts about this FSX file seek issue, that can potentially be related as well.
Jerome,I believe now that my (and others) problems are due to some Vista/DX9 issue that has no known soulution at the present time. After looking thru the PMDG forum, I came across numerous threads about the same problem I've been having. This thread: http://forums1.avsim.net/index.php?showtopic=240029, is just the latest of many. You can go to the PMDG forum and do a search on 'corruption' to get an idea. The only solution I can come up with are to run in DX10 mode or run FSX under XP64, possibly in a dual-boot scenario. For right now I'm going with DX10 only when I want to fly PMDG a/c. I'm still considering going the XP64 route, but I dread the thought of having to re-install FSX + everything again. That is supposedly the sure-fire fix, but it's alot of work getting everything set up, and I just don't have the time to devote to it right now.Jay

Share this post


Link to post
Share on other sites

Jay,I doubt it has anything to do with Vista and DX9 since there are countless others including myself that run PMDG products under Vista without issue. I would be more inclined to believe that possibly some bios updates would cure these problems for many especially in the case of i7 owners. The i7 technology is new and it may take a while for bioses to play catch up. There is also alot to say theses days about making sure that the memory you purchase for a particular motherboard is on the mobo manufacturer's approved vendor list. The majority of bios updates I see these days are memory compatibility updates.

Share this post


Link to post
Share on other sites

im running XP32 SP3... Dx9 is the only option for me... and I experience(d) these video freezes/corrupt too..Therefore Im not sure it has a link with Vista...

Share this post


Link to post
Share on other sites
Jay,I doubt it has anything to do with Vista and DX9 since there are countless others including myself that run PMDG products under Vista without issue. I would be more inclined to believe that possibly some bios updates would cure these problems for many especially in the case of i7 owners. The i7 technology is new and it may take a while for bioses to play catch up. There is also alot to say theses days about making sure that the memory you purchase for a particular motherboard is on the mobo manufacturer's approved vendor list. The majority of bios updates I see these days are memory compatibility updates.
Sarge,Now that you mention it, my memory is NOT on the 'approved' list for my mb. Could be something worth looking into. It's just that it's so time consuming to troubleshoot this type of problem, it happens only after some time has gone by while flying. So, each attempt eats a good hour or two, and to have absolutely no success at all to this point, it's getting a little frustrating.Thanks for your suggestion about the memory, I'm definitely going to ask Asus about that. Oh, and I have already updated to the latest bios, so I can rule that one out.Jay
im running XP32 SP3... Dx9 is the only option for me... and I experience(d) these video freezes/corrupt too..Therefore Im not sure it has a link with Vista...
Jerome,Wow, it's getting harder to even come up with some factor that we all have in common. That, of course, would go a long way in figuring out why this is happening. When I started reading those threads on the PMDG forum, it sure sounded like the Vista/DX9 issue was the cause, but you may be right. I don't know what to think anymore, it's getting a little frustrating. Not giving up, just need to step back for a minute or two :( Jay

Share this post


Link to post
Share on other sites
Oh, and I have already updated to the latest bios, so I can rule that one out.Jay
Well, you most definitely cannot rule out the bios yet. If your issue is your memory not play nice with your board and it has not specifically been addressed in the bios update you just installed, you could still be waiting for the appropriate update. Just keep positive, sooner or later you will get it sorted. My experience with graphic corruption in FSX has usually come down to a memory issue wether it be system memory or video card memory. Once in a great while a new video driver can cause a problem.

Share this post


Link to post
Share on other sites
Well, you most definitely cannot rule out the bios yet. If your issue is your memory not play nice with your board and it has not specifically been addressed in the bios update you just installed, you could still be waiting for the appropriate update. Just keep positive, sooner or later you will get it sorted. My experience with graphic corruption in FSX has usually come down to a memory issue wether it be system memory or video card memory. Once in a great while a new video driver can cause a problem.
Good point, Sarge. Apparently the memory issue was not addressed in the latest bios update, according to the release notes. My memory is not listed in the latest QVL on Asus' website, so that may indicate something. I did purchase all the components back in Nov so they had ample time to add it the QVL by now, don't you think?I have tried various drivers and although I don't use any driver cleaner, I do unistall the driver from the control panel, reboot, and then make sure that windows is using the generic VGA driver before installing the new driver. Never had any issues doing it that way. What do you think?Thanks for your input, btw, just in case I haven't mentioned it before :( Jay

Share this post


Link to post
Share on other sites

Jay,I now always use a driver cleaner just in case. I used to uninstall via the control panel just as you describe but had issues. The right remnant of a previous driver can cause ALOT of headaches.Nowadays, I go into the device manager, choose the video card and then choose uninstall. I will then reboot the computer into safe mode and use Driver Cleaner pro to uninstall any left behind remnants (there always seem to be a few). I will then boot the computer normally, install the updated driver, then reboot.

Share this post


Link to post
Share on other sites
Jay,I now always use a driver cleaner just in case. I used to uninstall via the control panel just as you describe but had issues. The right remnant of a previous driver can cause ALOT of headaches.Nowadays, I go into the device manager, choose the video card and then choose uninstall. I will then reboot the computer into safe mode and use Driver Cleaner pro to uninstall any left behind remnants (there always seem to be a few). I will then boot the computer normally, install the updated driver, then reboot.
Sarge,I gave the driver re-install procedure a shot. I followed your method to uninstall, safe mode, driver cleaner pro, reboot, installed latest nVidia drive (182.08), reboot. All went ok. I also set back ALL memory timings to the slowest available, in my case it was DDR3-1059 for speed, and 9-10-10-25-2T on the timings. I did not run nHancer at all, and I deleted my CFG and let FSX rebuild. Ran my usual test flight using the PMDG MD-11. FSX ran great.... butThe same problem happened. (where's that smiley with the gun to it's head???)Jay

Share this post


Link to post
Share on other sites

jay,Sorry to hear you still have the same results. When you get your video corruption, does it just happen or does it seem to happen when you are in the process of switching views? Also have you checked your Vista error logs to see if you have any display driver stopped responding errors?

Share this post


Link to post
Share on other sites
jay,Sorry to hear you still have the same results. When you get your video corruption, does it just happen or does it seem to happen when you are in the process of switching views? Also have you checked your Vista error logs to see if you have any display driver stopped responding errors?
Sarge,The problem happens when going into any ALT menu selection that takes you out of the cockpit, such as map, weather, PMDG menu, etc. Upon returning to the cockpit view is when the corruption occurs. It will also be triggered by switching between full-screen and windowed mode. But, it is unpredictable just when it will occur, sometimes I can complete an entire flight without it happening. However, I can ALWAYS trigger it by going into instant replay after landing. It has NEVER happened just when flying, or simply by switching views using the hat switch, for example. It has to be a function that takes you completely out of the cockpit view, and then back. I hope I'm being detailed enough trying to explain exactly what is happening. As I said, there are numerous threads in the PMDG forum regarding this exact problem, and the only solution they've come up with is to switch to XP64.Im off to find these error logs, maybe something there, never thought to look...ThanksJay

Share this post


Link to post
Share on other sites
Sarge,The problem happens when going into any ALT menu selection that takes you out of the cockpit, such as map, weather, PMDG menu, etc. Upon returning to the cockpit view is when the corruption occurs. It will also be triggered by switching between full-screen and windowed mode. But, it is unpredictable just when it will occur, sometimes I can complete an entire flight without it happening. However, I can ALWAYS trigger it by going into instant replay after landing. It has NEVER happened just when flying, or simply by switching views using the hat switch, for example. It has to be a function that takes you completely out of the cockpit view, and then back. I hope I'm being detailed enough trying to explain exactly what is happening. As I said, there are numerous threads in the PMDG forum regarding this exact problem, and the only solution they've come up with is to switch to XP64.Im off to find these error logs, maybe something there, never thought to look...ThanksJayUPDATE: I checked the error logs, and there wasn't any entries regarding video drivers or nvidia or display drivers. However, there were numerous entries related to 'volmgr', which is the service that controls the pagefile, I'm guessing. It was complainimng about not being the correct size, or not able to create one the correct size or something along those lines. Now, I did set the page file as fixed at 3072mb, according to Nick's guide. I then tried setting the page file to NONE, rebooted, deleted pagefile.sys from the c: root, then set it for let windows control the page file, blah-blah-blah. I reboted again, checked the page file, and it was there again, this time it was over 6gb, which corresponds to the amount of system ram I have installed. I guess that's what windows wants.However, all this led nowhere because on the very first flght after doing this the exact same problem happened...

Share this post


Link to post
Share on other sites

I have had the same problem since day one with my rig. For me, the event viewer was reporting the dreaded nvlddmkm error. The web is full people trying to fix it. I think I solved it as I can complete a 4 hour flight in the MD11. Of course by the time I get there, the airport buildings won't draw. The MD11 is the succubus of memory! :) The following MS article provides background of the cause, but offers no solution for the end user. It does explains why the solution is unique for each user. http://www.microsoft.com/whdc/device/displ...dm_timeout.mspxI can fly without the video corruption of the PFD/MFD and hard crash. I went back to the 178.19 drivers (pre-physics accelerator thingy), upped the dram voltage slightly and manually set the GPU fan speed at 60 percent. The fan speed and VDram were in auto, however, neither were at the recommended the values. My GPU was running in mid 70c which can result in instability. My mb is an ASUS 5PND and the nforce drivers apparently hosed the ability of GPU fan to run in auto. I don't trust the bios 'auto' function for vdram and manually set it at 1.9v. So far (1 week) so good. :)Bob..

Share this post


Link to post
Share on other sites
I have had the same problem since day one with my rig. For me, the event viewer was reporting the dreaded nvlddmkm error. The web is full people trying to fix it. I think I solved it as I can complete a 4 hour flight in the MD11. Of course by the time I get there, the airport buildings won't draw. The MD11 is the succubus of memory! :) The following MS article provides background of the cause, but offers no solution for the end user. It does explains why the solution is unique for each user. http://www.microsoft.com/whdc/device/displ...dm_timeout.mspxI can fly without the video corruption of the PFD/MFD and hard crash. I went back to the 178.19 drivers (pre-physics accelerator thingy), upped the dram voltage slightly and manually set the GPU fan speed at 60 percent. The fan speed and VDram were in auto, however, neither were at the recommended the values. My GPU was running in mid 70c which can result in instability. My mb is an ASUS 5PND and the nforce drivers apparently hosed the ability of GPU fan to run in auto. I don't trust the bios 'auto' function for vdram and manually set it at 1.9v. So far (1 week) so good. :)Bob..
Wow thanks for thisDo you have a tool for setting the fan speed?EDIT : ok Rivatunner will do the job for the fanUnclear why do you change your dram voltage ? a dram issue would hang or bsod the whole system isn't it ?

Share this post


Link to post
Share on other sites
Wow thanks for thisDo you have a tool for setting the fan speed?EDIT : ok Rivatunner will do the job for the fanUnclear why do you change your dram voltage ? a dram issue would hang or bsod the whole system isn't it ?
Hi!You're assuming I know what I'm doing. LOL I'm just throwing darts at the darn thing. I applied some of the fixes that others stated had worked for them. I'm honestly not sure which one or if all of them are needed for ME. I do know if I forget to up the fan speed I will get the crash frequently. I use the EVGA 'Precision' gizmo for fan speed and GPU clock numbers. (EVGA 8800GTS).Bob..

Share this post


Link to post
Share on other sites
You're assuming I know what I'm doing. LOL
LoL yeah, but you put me and jaybird on the right path to successful flight :)Now I just need to find couple of hours to make a test flight ;)

Share this post


Link to post
Share on other sites

ok tested with all mentioned above and i still manage to get black display in the fsx window after a 20 minutes.... just being at the gate starting various parts of the plane and few alt-tabs :(physx disabled, vdram forced to 1.9v, fan speed at his best

Share this post


Link to post
Share on other sites
Unclear why do you change your dram voltage ? a dram issue would hang or bsod the whole system isn't it ?
Nooon,No, that is not correct. If the voltage on your DRAM is not high enough, it can result in some bad data (intermittent if you will) being sent to the rest of the system. This does not necessarily mean your computer will crash....I can pretty much guarantee you that if you send send bad data to your video card you will have issues. So, raising the DRAM voltage and the problem disappearing is completely logical in this situation.Garbage In = Garbage OutAlso try running FSX without without ALT-Tabbing. ALT-Tabbing has been known for quite sometime to cause FSX to crash on a multitude of machines.

Share this post


Link to post
Share on other sites
Sarge,I gave the driver re-install procedure a shot. I followed your method to uninstall, safe mode, driver cleaner pro, reboot, installed latest nVidia drive (182.08), reboot. All went ok. I also set back ALL memory timings to the slowest available, in my case it was DDR3-1059 for speed, and 9-10-10-25-2T on the timings. I did not run nHancer at all, and I deleted my CFG and let FSX rebuild. Ran my usual test flight using the PMDG MD-11. FSX ran great.... butThe same problem happened. (where's that smiley with the gun to it's head???)Jay
Jay,There are many opinion and honest advise but no cure to the problems. I am suffering this type problems with PMDG models any some times with LDS-767X. Dell replaced two times Graphic cards, and exchanged entire PC two times also..I upgraded to Vista 64. No solution. Only solution I found was I select the FSX DX;10 review and no more OOM/GRaphic cards/scneries and screen changes problems. I realized Vista 64 is in DX:10 mode. my graphic crad Nvdia GTX280 DX;10. I flew 140 hours with PMDX-MD11X, 747-X and LDS-767x in DX:10 mode. NO single problems,but as soon as I switched to DX:9, problems starts all over again.I post DX:10 results in some key forums. It didn't get much response. I wish some FSX , Vista or Graphic Cards developer/ experts can see these clues and put their attention to FSX DX;10 review.There are some area needs to improve with DX;10, but these are minor problems comparison, what I am getting with DX:9.Pictures says the thousand words. Please see my DX;9 mode results.RegardsSanal :(

Share this post


Link to post
Share on other sites