garymcginnis

Welp.... greetings from BWI. I made it without any issues with this older driver. I also tried the power limit and downclock again as well. Next is a newer driver (376.33 since that is FSLabs recommended driver) and going back to stock.

Try 375.70. Way back in October of 2016. Then work your way forward if you want/need to for other games. Personally the computer one does P3D. I'm hoping that tomorrow I can make it to BWI (CLE-BOS-BWI) for my "virtual" layover 🙂

I am currently downloading 375.70. That driver was badda** in FSX with the KINGPIN 980. My hope is to start from there.

That provides 0 help since I don't use any of those tuners. The card is factory overclocked. I have touched nothing. The fans don't spin since the card never reaches the threshold for them to kick on. The power delivery is a monster with 2 8 pin and a 6 pin. I mean what an I suppose to do? Severely down clock this card? If that's the case, that is ridiculous.

I've just got my computer back after a complete reseed of the CPU, RAM sticks, GPU and a new CMOS battery. The guy ran a weeks worth of diagnostic tests. If this continues, its definitely not on my end. What is really annoying me about Lockheed is that they aren't even addressing that many users are having this issue according to reports above. I thought their whole point was to be open and help way back when they took over. This is an issue and sounding like FSDT (blaming others or ignoring) is definitely not being open and helpful. I'm first going to try without HDR. Then if that doesn't work, I'm going to roll back to 357.57 or 375.75 (iirc) as that was the BEST driver for FSX and my card I ever had. If that fails, I'm going to make a craigslist add and post it here 🙂

No, LM's or NVIDIA's poor excuse for a release candidates are the problem. Re-read what others have posted and you'll see OCs have been reduced with no luck.

PSU is fine. Brand new 850 EVGA something platinum something. Idk anymore.

I know it looks nice. Just troubleshooting since that's one of the common variables for me. Because if it is HDR that is causing this, we at least know and can report it to P3D.

I have another hunch..... Can you do me a favor? I had to two successful flights when I first started with P3D. It was FLL-SXM-FLL. Then I think I turned on HDR lightning. In my brainstorming today I thought that HDR was the common variable between the successful flights and the unsuccessful flights. I seem to recall a bug with HDR a few versions back as well. Can you tell me if you've had HDR lightning on or off? Also, if on can you try a few flights with it off if you have some time. Thanks

I've had the guy replace the CMOS battery. Another theory I'm maybe thinking about is the card itself. I guess I'd like some opinions. I currently have the EVGA KINGPIN 980 that was supposedly "super overclocked" from KINGPIN. When I used it for FSX, the driver would crash every few flights but I'd be able to continue with the flight since FSX did not have this DXGI check. Thinking about that last night got me wondering if the card was overclocked to much if that's a thing? Like "stable" but not "stable" for flight sim. Also its only a 4GB card. Could that be causing some issues? I'm asking for opinions only because I can get an 1080ti ASUS ROG card for a reasonable price BUT I don't want to go down another money hole if I don't need to swap out the card or if it won't fix the DXGI errors. Thanks

Wow. Interesting theory. I'll add it to list for the computer store. Thanks

Why cant the driver just restart like FS2004/FSX. Why does it have to crash the sim.

Seriously? P3D is complete word p00p. What a joke.

That's great. Will try. Thanks

Ok interesting. I'll try that in about a week when I get it back and have time. In the mean time can you confirm this works with other DXGI errors? Like today in had a _RESET. What GPU and driver version for my reference? Also, is that it or have you tweak the voltage or clock speeds as well? Thanks

Ok interesting. I'll try that in about a week when I get it back and have time. In the mean time can you confirm this works with other DXGI errors? Like today in had a _RESET. What GPU and driver version for my reference? Also, is that it or have you tweak the voltage or clock speeds as well? Thanks

What do you mean power setting?

What do you mean power setting?

I'm taking this computer over the guy who built it and having him reseed everything and do a bunch of hardware checks. If that or any other suggestions here don't work, look for a craigslist link in a few days 😬 I don't have time to do this anymore if it's going to unstable and unusable. My hobby is to fly (which I have no clue why since I already do it for work but I'm sick I guess) not to troubleshoot. I'm still open to any suggestions.

Yea I cleared the shaders.

Welp...... Finally was able to fire up the sim after 3 weeks. I tired everything in this topic: - Disabled NVI - Rolled back the clock speed - Clean .cfg - Both checker registry hacks - 388.13 (DDU used) Everything was smooth. I was actually getting ready to eat some crow since the VSYNC 1/2 thru the control panel, along with unlimited frames and VSYNC in game was very very smooth. I look away for a minute and get another DXGI error. This time the _RESET. The event viewer provides little help. Only of a LIVEKERNELEVENT. I pushed cancel and it still crashed the sim after about a minute of running it with no display. What can I do? This is bullcrap. I'm open to all suggestions at this point.

In watching Flight Sim best moments on YouTube from last week, two streamers got DXGI crashes and one said he'd been getting a ton lately. How far back driver wise do people think this goes back. I mean I know some aren't getting these errors but I'm curious.

I'll run thru that Tom's link when I get home next. But I believe it's okay. Thanks

No issues with the DXDIAG that I saw. Ran it twice. However, I saw one picture of someone who was discussing dxdiag and windows 10 had both DX11.3 and DX12 in the version (might have been photoshopped for W8 uses). I believe 12 covers 11.3 as well? I have windows updates completely shut off, so I doubt it's a bad DX12 update.

It's not the DX12 issue. However I just added a TDRDELAY as well as the TDRLEVEL that I already had. I out the delay to 60. How many of you not having issues have the TDRLEVEL and DELAY? Thanks