Thanks for link.

 

Those links to Microsoft Visual C++ 2010 are already installed when you install P3D (if it is not already located on your system).  Check the Add/Remove Program folder to see which versions you have installed. 

 

Best regards,

Hi everyone

 

I am new here, but have been dealing with the cursed R6025 error for the better part of a year now. I have meticulously followed the many suggestions to diagnose and otentia fix this annying fault, all to no avail.

 

I have recently (Nov. 2014) completely reinstalled Win7, P3D and v2 compatible addons to a new HDD. I still get the cursed error. Sometimes after 15 minutes, sometimes after 4 hours.

 

Hoping 2.5 might have a "fix" I unstalled 2.4 and did a fresh 2.5 install, confirming UAC was off, the P3D folder shared, AV was off, and for the hell of it I even cancelled the 2 ring circus. I have run Dependency Walker to see if the MSCR100.DLL shows any compatiblity errors - curiously it doesn't. But I still get that cursed error.

 

I am very disappointed by what I feel is LM's brushing my concerns off. I had an idea that all of us getting this error maybe politely inform LM we are considering a class action suit? Maybe that would motivate them to take this fault a little more seriously (granted not everybody is getting it, but to my eyes more and more people are reporting it).

 

What can I do. The last stable version I had was 1.4 and I am seriously thinking of going back to that. At least it worked!

I had an idea that all of us getting this error maybe politely inform LM we are considering a class action suit?

 

Then why don't you initiate a class section against Lockheed Martin?

Do you have Tessellation enabled? I switched off Tessellation the other day for some reason, and then forgot about it. When I attempted a quick test flight yesterday, I got my first ever Runtime R6025 error just after I cleared the trees at the end of the runway. It was only then that I remembered that I had forgotten to switch Tessellation back on! After doing so, I did not experience any further problems.

Yep. Tessellation is on and the necessary program shutdown restart. Every single step has been followed, from the CTD guide(s) and suggestions made by many people. I am seriously banging my head against the wall with this.

 

I have gone through every startup process in Win7 and none use MSCVR100.DLL (the program dependencywalker is a great debugging tool, although it hasn't revealed anything as to why MSVCR100 is causing hassles, I wanted to see if it maybe is caused by something outside of P3D).

OK an update: since posting I have had a cross-Atlantic flight going for over 5 hours now. This is by far the longest flight without the R6025 error since they started appearing 12 months ago.

 

What I did is located the MSVCR100.DLL in the Nvidia files and replaced it with the older version (10.0.30319.01) which I also have in my System32 folder. I have paused the program, started my browser several times, and minimized the P3D screen and it is still running.

 

Update:make that 6 hours and still running

 

 

Update:make that 6 hours and still running

 

Amazing how anyone can fly for 6 hours in a flight simulator but many people, like you, do it.  Personally, anything longer than 2 hours is a wasted day for me. 

 

I think the Microsoft Visual C++ 2010 is the likely culprit for this crash.  So far, since upgrading to P3Dv2.5, I have not seen the error.  I was getting it mainly when shutting down P3D so I had enabled the setting for P3D to confirm whether you want to quit or not and that fixed the problem.  So far in P3D2.5 I have not seen the crash at shutdown.  There are many P3D addons that need/use Microsoft Visual 2010 to install their programs so there is a slight possibility that the Visual gets corrupted for some (as this crash does not occur to everyone and that's what is truly strange).  If we could have everyone replicating the crash with JUST P3D installed, then we could safely blame LockHeed Martin.  But that's not happening.  Hope you continue to enjoy P3D w/o this crash in the future.  It is frustrating especially after a long flight and P3D stops near the end or in the middle of the flight.  No fun!

 

Best regards,

Hi Firehawk44,

 

ordinarily I usually do 90 minute flights tops, but this is a system check, so I have set auto pilot and done other things while the sim is running. Mind you, just once I want to do a Frankfurt - Sydney flight in real time - just to see if I really am that crazy. As of now it is 6 1/2 hours no error. No sign of Canada just yet, but the map says it should pop on the horizon any tick of the clock.

 

Thanks to this board I was able to narrow down my probable causes. Like you said, a CTD right at the end of a flight ticked me off to no end. I really hope I have seen the end of it.

 

Cheers,

 

Dwight

OK 12 hours fault free. I will write up a detailed step by step guide to everything I did here after another long haul test tommorrow.

OK 12 hours fault free. I will write up a detailed step by step guide to everything I did here after another long haul test tommorrow.

Good show! 

 

Best regards,

The update on phase 2 long haul: over 3 hours and no crash. Again I am stopping, starting, running other programmes and generally overstressing system resources. So far, so good. I am compiling all the data, but it looks very much like the Nvidia MSCVR100.DLL was causing the conflict (found in the Nvstreaming folder). Since the dll fault starting appearing, I have not had such long unbroken flights until yesterday when I changed that file to the same as in my System32 folder.

 

I wonder if P3D via the nvidia driver was trying to access a streaming function of the card, which it wasnt set up to do?

 

If anyone else is having the CTD R6025 error, could they replicate my solution to see if it works for them?

 

UPDATE: After 3.2 hours I got the crash. But in all these days were the most successful since I started getting the errors. To be honest a crash after 3.2 hours is something I can live with as most of my flights dont go beyond 90 minutes.

Well, now that darned R6025 is back with a vengance. I am going to reinstall FSX and if that doesn't crash, looks like I will give P3D the flick. I am sorry but considering I do high end video work on my setup, I have trouble accepting that the R6025 error is because my rig has a problem. If that is so, why is P3D the only program encountereing this fault?

 

I can only thank my better judgement for _not_ starting my private commercial sim endeavour with P3D as the software base. I would have had to file for bankruptcy had I done that, as there is no way in hell I could have run a commercial venture with a sim crashing every 10 minutes.

Have you tried to reset your p3d settings to the default?  I think this error is caused by high settings, in the p3d.cfg or the nVidia display drivers.  I was getting it earlier in the 2.4 version but have not seen it yet in 2.5.  My settings are extremely close to the default (except I turned on AI as LM thinks my i7 4770K w/the GTX780 video card can't handle AI).  I had to return to the default as my high settings were simply causing lower fps and the sim crashed a couple of times.  I always recommend members lower their settings and I don't know what I was thinking by pushing most of my sliders to the max but actually I was just testing 2.5 and max settings do not work for most situations.

 

Best regards,

Thanks Jim,

 

it seems to be holding for now. I am ready to jump back to P3D 1.4 as that was the last truly stable version I was running. If the system hold for around 3 hours, I will stay with 2.5.

 

One question regarding graphic cards/displays. I have noticed the price on 2560x1080 wide widescreen monitors has come down considerably. Do you happen to know if P3D/FSX like those displys?

I have a Dell 30" screen and my resolution is 2560 x 1600 and it has worked very well for me the past 5 years.  I think fps will suffer a little more though the higher the resolution but it is still playable.

 

Best regards,