Dstevenb

Following 2 days of full-on testing, I think I have found the solution to my problem (and also all of those who have the R-6025 error that is present with a vanilla install and only having approved add-ons. So what did I do? I first got so damned sick and tired of the same CTD after 15-30 minutes flight that I was ready to ditch P3D (as you can read a few posts up). However, I decided to test FSX before I ditched P3D, so I did a new install of FSX. No addons, just vanilla. It work flawlessly as I knew it would. Being, however a stubbon old xyz, as LM support forum moderators will gladly tell you, I decided to one last time test to P3Dv2.5. And what do you know? BINGO! P3D suddenly works perflectly. NO R-6025 error!!?? As of today 2 test flights over 5 hours each no R-60256 errors. Now, I would love to know WHY? PS: As I pay for a developer P3D license I'd would like this fix to be known as the "Dwight Fix" - no charge for it.

I may have found a solution to this problem. I am just testing my theory right now.

I am about to instal FSX again. If that doesn't crash then it is bye bye Prepar3d.

No not yet. I am very much considering jumping back to P3Dv1.4 as I can't stand this error. Simming is no fun. If P1.4 starts playing up I'll go back to FSX and seriously consider pumping my cash in X-plane. For LM and ORBX, and any other developer I can say that I have stopped buying any add ons No point buying flashy tires if the car won't start.

Uh-oh. I completed successful tests with ORBX Global Base. I then went to the next step of adding Austrralia and England regions. Once again the R6025 is back. This time worse than before. If I turn all settings to their lowest I get no error, but in 2.5 I also get no airports buildings, trees or any other buildings. I don't see the motivation to shovel money to LM for that type of performance, whether it is or isn't their fault. However an Inno 770 nvidia 4Gb card should _not_ be insisting on such pathetic settings. A half months wages makes me expect it works as advertised. If I want terrible graphics I'll go to MSFS95. I cannot live with that. Sorry but my frustrations are getting the better of me. I am getting fed up with every step forward equalling two steps backwards. Nothing on my hex-core system says I should be even considering a non-performing flight sim. What can I do?

Thanks for your (and this board's) help in getting me error free flights. Lowering the settings seems to have done the trick, although having forked out some serious cash for a 4GB 770 card doesn't fill me with awe that everyone is quite on the ball with correct implementation. I would understand the headache if I was running a €20 card, but not one that cost €500. At any rate, the error goes with low settings. I can live with that.

A-ha! I completed 3 tests each over 3 hours with no R6025 error. I then proceeded to the next level and installed ORBX global. Bang 10 minutes into flight the dreaded error again. I dropped video settings and am now approaching 1 hour fault free. Jim. How do the scenery settings have any bearing on a function call? I dont get why that would have any bearing on the sim.

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?

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.

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.

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.

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 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

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).

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!