Ok now i do another test again i have changed a setting in bios related to pcie power management it was set to disabled by default means that aspm will be handled by the bios enabling it allows to os to handle the power management i m flying now on windowed mode switching between other apps obs working and keeps sending data to youtube with CBR set to 6500 process monitor also working and keeps logging as well so far good if everything goes well i will share a screen shot of bios about what i changed in bios. 

Here is stream link if u are interested 

 

I completed the flight without any error this time all the gpu clocks were set to default nvidia control panel settings inspector and everything was default. I am not sure yet this is a permanent solution time will show.

here is what i did in bios. Enabled PCI express naive power management and native aspm.

 

 

Edited December 17, 20187 yr by Aweless

Don't have Native ASPM option in my bios unfortunately.

On 12/17/2018 at 1:28 PM, Rob Ainscough said:

those having this problem of app switching and device hung, have you tried setting full screen compatibility for Prepar3D.exe?

All I could find was "disable fullscreen optimisations". If that is what you mean it didn't work unfortunately but thanks anyway.

6 hours ago, glider1 said:

Don't have Native ASPM option in my bios unfortunately.

Have you ever tried doing a test flight by switching the balanced in power option in windows? Also try enabling the power saver options in your bios settings if any available. try everything that will reduce the load of psu. if you are not sure what to do in bios don't even touch it. unplug all unnecessary devices from the usb ports. BTW i made my second flight and this time i pushed a  bit more harder than the previous flight and set my resolution to DSR X4  also live streamed on the same hardware and i got no error. still not sure but usually i was getting this error within an hour.

 

On 12/16/2018 at 2:19 PM, glider1 said:

I might still do a comprehensive VRAM test just to rule out card once and for all.

Great find! At least it is a lead! It might be something we can show to LM.

What utility do you use to check VRAM?

4 hours ago, Aweless said:

Have you ever tried doing a test flight by switching the balanced in power option in windows? Also try enabling the power saver options in your bios settings if any available. try everything that will reduce the load of psu. if you are not sure what to do in bios don't even touch it. unplug all unnecessary devices from the usb ports. BTW i made my second flight and this time i pushed a  bit more harder than the previous flight and set my resolution to DSR X4  also live streamed on the same hardware and i got no error. still not sure but usually i was getting this error within an hour.

 

I could be wrong but you are actually enabling the power “ saving” feature and this seems similar to what Chris did as the only thing that helped him by reducing the power limit to his GPU to 70% if memory serves me.

Its interesting how a few of the positive results come from either trying to limit the frequency cycling of the GPU because of GPU Boost or reducing the power to it, perhaps this feature that Windows can take advantage of that you are doing by editing your BIOS is having a similar effect?

Joe

37 minutes ago, joepoway said:

I could be wrong but you are actually enabling the power “ saving” feature and this seems similar to what Chris did as the only thing that helped him by reducing the power limit to his GPU to 70% if memory serves me.

Its interesting how a few of the positive results come from either trying to limit the frequency cycling of the GPU because of GPU Boost or reducing the power to it, perhaps this feature that Windows can take advantage of that you are doing by editing your BIOS is having a similar effect?

Joe

You are right Joe. And this is what actually i try do. i should warn that if things set to performance mode in bios no matter you switch to power saver mode within windows power saver plan won't take effect at least on my bios this is what i experienced. i guess switching to auto lets windows to handle the power plan and i plan doubling my power supplies in future so one for gpu one for motherboard and see what happens no need to have more than 300 watt for a 150 watt gpu it's barely peaks at 200 watt and a used one psu would do it. 

Edited December 18, 20187 yr by Aweless

A thought, try disabling in nvidia inspector for the prepar3d profile, Nvidia shadercache

12 hours ago, pgde said:

What utility do you use to check VRAM?

I haven't found one I trust yet so test not done - but it is on the list of things to try if all else fails because there are memtests for GPU out there.

I have completed one more flight today without any error the flight took 4 hours around and the sim run near 5 hours with many apps running in background. switched between full screen and windowed mode from time to time but mostly in windowed mode. If you remember the catch which i discovered the buffer too small warning found by the process monitor gave me the idea that there must something be done with power settings to reduce the power consumption because the buffer too small warning was associated with current control set registery path. And this absolutely confirms those who was keep telling this issue has something to do with power options. And then I went right in to bios looked for settings that won't force the power consumption for the better performance. Switched balanced power plan in Windows and watched cpu speeds on idle cpu kept working between 1 to 2 ghz on idle as i launch the p3d cpu speed increased to 4ghz and never dropped during under load. Also locked the gpu clocks just in case and the gpu core clocks never fall below 1900 mhz. As i stated previously before i go in bios and set some settings i don't remember exactly what i changed but no matter i switch balanced plan in Windows I watched the cpu kept working at maximum speeds. There was something not right It seems in modern motherboards things more complicated than we can imagine. There are some conflicts between modern bioses and os especially with Windows10. So just dont be offended by switching balanced power thinking that u can't take advantage of your super fast hardware and i think balanced power won't force your system beyond what your hardware can't really handle but always will run at maximum speeds as your hardware allows.

1 hour ago, Aweless said:

I have completed one more flight today without any error the flight took 4 hours around and the sim run near 5 hours with many apps running in background. switched between full screen and windowed mode from time to time but mostly in windowed mode. If you remember the catch which i discovered the buffer too small warning found by the process monitor gave me the idea that there must something be done with power settings to reduce the power consumption because the buffer too small warning was associated with current control set registery path. And this absolutely confirms those who was keep telling this issue has something to do with power options. And then I went right in to bios looked for settings that won't force the power consumption for the better performance. Switched balanced power plan in Windows and watched cpu speeds on idle cpu kept working between 1 to 2 ghz on idle as i launch the p3d cpu speed increased to 4ghz and never dropped during under load. Also locked the gpu clocks just in case and the gpu core clocks never fall below 1900 mhz. As i stated previously before i go in bios and set some settings i don't remember exactly what i changed but no matter i switch balanced plan in Windows I watched the cpu kept working at maximum speeds. There was something not right It seems in modern motherboards things more complicated than we can imagine. There are some conflicts between modern bioses and os especially with Windows10. So just dont be offended by switching balanced power thinking that u can't take advantage of your super fast hardware and i think balanced power won't force your system beyond what your hardware can't really handle but always will run at maximum speeds as your hardware allows.

Ok Aweless thanks very much for that you have convinced me to try balanced power settings. I am on prefer maximum power.

There is definitely a relationship between GPU clock speed and stability when the sim doesn't have the window focus. If the sim has the window focus, you can set a higher GPU core clock but I have to reduce the gpu core clock when the sim is sharing time with other apps in the background.

I think your theory is that it is a power issue, and I'll explore that next time.

Cheers

I got your point, to me The relationship between gpu clock speed is to the idea that i got from Joe's earlier post is when the gpu clocks going up and down it accumulates some stress on the gpu by requesting a different power level each time. There are two things to eliminate in this case, one a faulty psu that can't feed the requested power frequencies to the gpu properly, resulting in gpu to reset and disconnect from the simulator  i wish the p3d could by pass this kind of resetting and keep running as well just like in Linux systems.Well maybe in future. second a faulty gpu that requests excessively unachievable frequencies at its peak so this also leads the gpu to reset and disconnects from the sim. In my case maybe i got a faulty gpu but somehow locking the gpu clocks fixes the unachievable frequency requests so it keeps working more stable. I will know this when i add a secondary psu to my system. But let's say the psu is ok, in this case considering the gpu is faulty in terms of p3d when everything else working great its completely up to one's own wish. Maybe we shouldn't compare p3d with other games neither any other benchmark tools. If it is up to me i can live without p3d too quit the sim and consider my gpu isn't faulty. But i already consider my self won this battle against this error besides with a faulty hardware long time ago by doing some cheap tricks. I think i m done with this thread and i hope anyone who deal with this error can come up with positive results in short time. Thanks to everyone who tried to help and shared their experiences their ideas you are such a great community.

Good luck! 

9 hours ago, Aweless said:

I got your point, to me The relationship between gpu clock speed is to the idea that i got from Joe's earlier post is when the gpu clocks going up and down it accumulates some stress on the gpu by requesting a different power level each time. There are two things to eliminate in this case, one a faulty psu that can't feed the requested power frequencies to the gpu properly, resulting in gpu to reset and disconnect from the simulator  i wish the p3d could by pass this kind of resetting and keep running as well just like in Linux systems.Well maybe in future. second a faulty gpu that requests excessively unachievable frequencies at its peak so this also leads the gpu to reset and disconnects from the sim. In my case maybe i got a faulty gpu but somehow locking the gpu clocks fixes the unachievable frequency requests so it keeps working more stable. I will know this when i add a secondary psu to my system. But let's say the psu is ok, in this case considering the gpu is faulty in terms of p3d when everything else working great its completely up to one's own wish. Maybe we shouldn't compare p3d with other games neither any other benchmark tools. If it is up to me i can live without p3d too quit the sim and consider my gpu isn't faulty. But i already consider my self won this battle against this error besides with a faulty hardware long time ago by doing some cheap tricks. I think i m done with this thread and i hope anyone who deal with this error can come up with positive results in short time. Thanks to everyone who tried to help and shared their experiences their ideas you are such a great community.

Good luck! 

Aweless

In an attempt to summarize your path to a solution tell me if this is correct, please:

Limited ( not locked to one frequency ) your GPU clock frequency using the method described above. This method helped but did not fix the problem? I saw it was not the solution for CJ

Then you went into the bios and enabled PCIE power saving features coupled with Windows 10 balanced power features turned on

You also set all NVI settings to default which would clearly not be running Preferred Power Maximum that most all of us use with NVI or NCP

So it appears ironically you are holding the frequency variations of you GPU  at higher settings (more power consumed but fewer spikes). However through enablement of the power options in the bios and Windows you are allowing the CPU to throttle up and down In a power saving mode. This is something I have always disabled in my overclocks and just run at the continuous overclock speed on all cores all the time to limit flucuations. I’m a bit surprised the PCIE bios change was what allowed your CPU to downclock usually there are other bios features to accomplish this. My Gigabyte board is 6 years old and I don’t have the PCIE feature you changed but have always disabled the CPU throttling features.

So to summarize you totally enabled CPU and PCIE Windows/Intel throttling features, tried your best to lock GPU frequencies (ironically the opposite approach to CPU), and disabled all NVI max performance settings. Is this correct?

Finally I assume the GPU frequency “locking” and no max performance NVI setting didn’t solve your issue it took the combination of limiting GPU frequency spikes with allowing Windows to use the Intel CPU power management functions, correct?

Thanks in advance

Joe

Edited December 19, 20187 yr by joepoway

3 hours ago, joepoway said:

Aweless

In an attempt to summarize your path to a solution tell me if this is correct, please:

Limited ( not locked to one frequency ) your GPU clock frequency using the method described above. This method helped but did not fix the problem? I saw it was not the solution for CJ

Then you went into the bios and enabled PCIE power saving features coupled with Windows 10 balanced power features turned on

You also set all NVI settings to default which would clearly not be running Preferred Power Maximum that most all of us use with NVI or NCP

So it appears ironically you are holding the frequency variations of you GPU  at higher settings (more power consumed but fewer spikes). However through enablement of the power options in the bios and Windows you are allowing the CPU to throttle up and down In a power saving mode. This is something I have always disabled in my overclocks and just run at the continuous overclock speed on all cores all the time to limit flucuations. I’m a bit surprised the PCIE bios change was what allowed your CPU to downclock usually there are other bios features to accomplish this. My Gigabyte board is 6 years old and I don’t have the PCIE feature you changed but have always disabled the CPU throttling features.

So to summarize you totally enabled CPU and PCIE Windows/Intel throttling features, tried your best to lock GPU frequencies (ironically the opposite approach to CPU), and disabled all NVI max performance settings. Is this correct?

Finally I assume the GPU frequency “locking” and no max performance NVI setting didn’t solve your issue it took the combination of limiting GPU frequency spikes with allowing Windows to use the Intel CPU power management functions, correct?

Thanks in advance

Joe

Joe there is a misunderstanding to be cleared.

To summarize my solution

1: As long as i kept my gpu clocks locked i had no dxgi error at all.

2: All i wanted to find what sort of solution i could figure rather than locking the gpu clocks not to get the DXGI so i managed this by leaving power management up to windows by doing some extra changings in bios so this is why i dig in here.

3: I should mention this additionally: in your terms before i enable the PCIE power saving feature i seen that the gpu clocks were going down to 139 MHZ on default clocks while on idle even though nvidia profile was set to prefer high performance. After enabling the PCI Express Native power management in combination with Native Active power management which lets the windows interfere to regulate the power drawing in GPU and then i seen that the gpu clocks kept remaining around 900 MHZ on default clocks while on idle even though nvidia profile set to default in global. And yes this sound way more ironic and yes i think there are some conflicts in between bios windows ncp etc who know what else trying to take the control… I guess being able to lock Gpu clocks that easy is something special to pascal cards.

4: To clear one thing that misunderstood: Enabling PCIE ASPM has nothing to do with CPU interaction. Thats something i discovered later on after i figured something must be done to reduce power drawing from the psu. To let the windows manage cpu clocks there are a few modes in my bios that i had to dig in these modes: EPU, PERFORMANCE, Max Power saving and AUTO Cpu C states and intel SpeedStep i don't exactly remember what i changed in my bios i may also have changed c states to auto or SpeedStep to Auto to let the windows take the control of cpu speeds. Here are a few screen shots to my current bios configuration to make the windows to control the cpu speeds it must look like this: 

 But i think it won't make much difference no matter i keep the cpu working @4ghz. Balanced power plan has just became my preference to avoid in case if the psu feeds insufficient power to the system or a faulty gpu wants to draw much more power from the psu at times. these are my assumptions so i go balanced that the system could stabilize it self by reducing the frequencies as needed, just a precaution. I had to perform at least one action of two options not to get dxgi, 1: Lock Gpu clocks. 2: Enable Pcie power management feature in bios and leave the gpu clocks alone. But now i use two options together both locked gpu and enabled pcie aspm also balanced power plan enabled in windows and works good and i haven't seen any fps drop in simulator comparing the previous setups. 

I hope i could clear the questions in your head.

All the best.

 

Edited December 19, 20187 yr by Aweless