DXGI_ERROR_DEVICE_HUNG

[klisura]

It happened since I updated Chaseplane to v. 1.509 Alpha.
Did you do the same?? Could it be the guilty?

**

Is this product in testing / not approved for P3D yet?

https://fsfxpackages.com/en/ChasePlane/
ChasePlane is currently in Alpha. That means that ChasePlane is not a stable, final product and that tests, changes, addition or removal of features are possible.

Sure, I asked to others that reported the same error if they have chaseplane updated in order to understand if it's the guilty

[Jeast]

Or pdf kneeboard

[DaveCT2003]

Okay, add me to the list of those who suffer from this.

I'll check everything that has been posted.

Best wishes.

[Hans K]

Same error here so please, add me to the list too.

Best wishes!

[klisura]

Same error here so please, add me to the list too.

Best wishes!

Adding you to the list brings no solution to the problem. You have to describe when the error came out for the first time, after which action on your pc (new software install, new updates etc). Only by comparing our experiences we can find the way

[Beau Hollis]

Hell all,

Thanks for your reports. Please keep them coming and be as specific as you can. We have not been able to reproduce the crashes which makes it difficult to determine a cause. With a graphics driver crash/hang, the cause could actually be an issue with Windows, the graphics driver, or any application on the system which uses the graphics card. What we added to the recent hot fix is not a fix for driver crashes, but rather new code to detect and report driver crashes. We were able to force the driver to crash with some intentionally bad calls to the GPU in order to add this new detection feature, and to work around crashes caused when Prepar3D tries to use the crashed driver.

[Beau Hollis]

Here are some things to try (In addition to Adams instructions)

If all or some of these fix the issue, that will help us narrow down the cause.
- Disable MSAA
- Turn off any custom driver overrides (especially AA settings)
- Disable NVSurround or EyeFinity if you are using it
- Hide the menu bar and close the ATC window
- Try running with only one monitor enabled

This information would also help use track things down:
- what is your GPU model and driver version?
- If multi-monitor or multi-gpu:
- which monitors are plugged into which gpu?
- what kind of windows/panels are on each monitor?
- does moving that app to another monitor affect your results?
- Are any driver overrides (such as AA overrides) being set
- Are window management features like nvsurround or eyefinity?
- if Win7, is there an Aero theme enabled? (eg transparent window title bars)

Finally, one more thing to try is to modify this entry in your prepar3d.cfg.
[PANELS]
PANELS_ALWAYS_ON_TOP=0

It may not be related, but we did modify our the window ordering code a bit for v3.4 to allow panels to stay on top of 3d views. It's possible these additional window ordering commands are tripping up some graphics drivers. This is an optional feature which can be disabled with the setting above.

Thanks again for your reports and your patients in dealing with this issue.

[Sabre57]

Not sure if this is related. If it's not I'll start a new thread. After updating to Nvidia driver 376.33 I started to get Nvidia driver crashes on every flight. I cleared shaders and still get the error. I updated to this driver so I could also run BF1 on the same machine. So I went backwards to 375.95 and am still getting the error. Sometime this crashes P3D sometimes not. When it doesn't crash I lose my view group and my undocked panels and cannot get them back except to restart P3D. This only started with updating the drivers. I going to go back to my original drivers and see if that changes anything.

The message I captured in the windows log was:
------------------------
Log Name: System
Source: nvlddmkm
Date: 1/5/2017 4:33:44 PM
Event ID: 13
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Battlestation
Description:
The description for Event ID 13 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

\Device\000000d8
NVRM: Graphics TEX Exception on (GPC 2, TPC 0): TEX FORMAT

the message resource is present but the message is not found in the string/message table


System specs:
• P3D 3.4 hotfix 1
• Addons; REX Direct w/Soft Clouds, SPAD.Next, AirManager 2.1
• I5 4670K
• 16 GB RAM
• GPUs; GTX970 8GB, GTX660 3GB
• Drives; 130 GB SDD, 1 TB HDD
• Monitors; 4 acer 23", 1 USB 16", 2 USB 10" touch screens

[Martyson]

"After updating to Nvidia driver 376.33 I started to get Nvidia driver crashes on every flight."

Just for info.
Nvidia Driver 376.33 Ok here ... no errors ... (P3D HF2 and FSX Accel).

[klisura]

I'm not suffering nvidia hung error since two days.
I have updated to the latest nvidia drivers; restored the original SHSL shader directory (after have applied PTA 2.1); updated Chaseplane to latest release.
I don't know which of these actions (or others maybe) solved the issue (if it has been solved as it seems to be)

[Martyson]

I'm not suffering nvidia hung error since two days.
I have updated to the latest nvidia drivers; restored the original SHSL shader directory (after have applied PTA 2.1); updated Chaseplane to latest release.
I don't know which of these actions (or others maybe) solved the issue (if it has been solved as it seems to be)

What is PTA 2.1 ?

Is Chaseplane still in testing or has it officially been released for P3D v3.4 HF2?

[pikimatte]

Also same error for me. Where I Chaseplane??

[Stratocruiser]

I was having the same problem after I installed the hotfix # 2. Installed Nvidia driver 376.33 for my old GTX660 card and all is good again.

[DaveCT2003]

It happened since I updated Chaseplane to v. 1.509 Alpha.
Did you do the same?? Could it be the guilty?

This problem occurred when I reinstalled and updated Chase Plane. I disabled CP for another reason (not to troubleshoot the referenced CTD), and I did a few things on my system to try and correct the CTD.... made three flight without a CTD and thought I was fine. Then today I decided to reinstall CP, and I got the CTD again.

I'm not ready to say it's CP, but I just uninstalled it and will try another flight later today. I'll report back.

If its not CP, then I'll revert back to pre- December NVIDIA drivers to see if that's it. I have a high degree of confidence that it's not any other software in my flight sim load.

NOTE: I'm currently using NVIDIA Driver 276.33 (December 13, 2016).

Best wishes.

Dave

[baptista333]

I started to get this error constantly after the last update Nvidia driver 376.33
Currently the P3D Hotfix 2 GPU version nvidia FTX970 Windows 10 64bit,16GB Ram , I7 6700k
I do not use Chaseplane or similar. Only Rex SoftClouds, ASX 16, FTX adds
In addition to Adams's instructions I also followed Mr. Beau Hollis.
Thanks and I await instructions.