Aweless

@glider1 Have you tried locking your gpu clocks via CMD? here a few commands that might be useful: Run cmd administrator navigate via CMD to cd \Program Files\NVIDIA Corporation\NVSMI\ nvidia-smi -lgc 4104,1620 This command will set gpu clocks 4104 Vram 1620 core clock. You can also check the gpu power limits: nvidia-smi -i 0 --format=csv --query-gpu=power.limit To set power limit: nvidia-smi -i 0 -pl 160 You can define any number instead 160. Here you can log power draw: nvidia-smi -i 0 --loop-ms=1000 --format=csv,noheader --query-gpu=power.draw For more detailed information you can also give a look nvidia-smi pdf file that placed C:\Program Files\NVIDIA Corporation\NVSMI folder. Regards

Nope, And i really didn't say so neither to convince you nor anybody else to switch win10 my intention wasn't that and never will be and why should it be? We are performing brain storm here and that's just amazing. the subject of this thread wasn't influenced by the choice of operating system i just shared what i experienced by the intention of maybe that would be a beacon for someone else who suffering from what i suffer. Regards.

In new motherboards it might be related to the OS with modern hardware gpu cpu etc. And it is another story being able to install win 7 in new motherboards whatever you do despite new mobo allows win 7 installation you are facing some troubles during install and after install.

Yes i know the story Rob. it's been reported by some users that the October update had deleted user files at first release and then Microsoft cancelled the update. It looks like one of my nightmare bug has gone after updating to 1809. I was getting some stuttering on the desktop on idle at times before the update and this is what made me think my gpu could be faulty. i Assume for your issue you may have to wait network driver updates for the new 1809 build for all your pc's that running on the network. I would suggest you to look for new driver updates via an app as driver easy for your network adapters if you haven't done something similar to this so. If your secondary network pc's are older then your issue may have something to do with incompatible network hardware too. Have you ever tried running only two computers on the network and run your both weather app and flight planning app in one computer?

There might be good news in windows10 1809 October update for those who facing the dxgi error . i am up to date today and there are noticeable improvements. You can also watch the the power usage per apps in task manager. I haven't performed a flight yet but i will do by rolling back any changes i made previously.

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.

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!

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.

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.

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

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

The only reliable way to test is p3d, from now on i consider all the benchmark tools are trash. My card is Gtx 1070 ichill inno3D x4.

Ok now i can confirm the exact time when the dxgi came. i figured by watching my streamed video. when the time second was stepping to 31 from 30 i started count till dxgi appear and it came after 45 seconds and there is only one unique event logged at that time is ''BUFFER TOO SMALL'' associated with this path: HKLM\System\CurrentControlSet\Control\Notifications\41C61629A3BC60B5 here is a SS: https://prnt.sc/lvr5k8

Hi cj just letting you know this might be a sign for us and my card also brand inno3D x4 and i am facing this issue too in p3d strangely. i hope i can find a way to eliminate this by the support of process monitor. have you ever run the process monitor while p3d get this error and i think we can compare our monitoring results and see what differences are there in the logs.