Installed Prepar 3D V4.3 and nothing but problems from day 1. About to request a refund 😞 Anyway this has started showing up now. I've got a brand new high powered laptop. Anyone have any idea why and what to do to fix this? Thanks and all help appreciated! Graphic card is crashing and I get this error DXGI_ERROR_DEVICE_HUNG.

see if this helps - 

 

http://www.prepar3d.com/forum/viewtopic.php?f=6312&t=130512

 

Vic

I had the problem on the last set of drivers.  This most recent one I only get it on occasion.  I solved it by reverting back to the one 2 cycles ago.  For now I'm back on the most recent driver and I've only had it a couple of times.  If it keeps popping up randomly I'll probably revert back again.

397.64

That's the driver you need 

Well I've tried all these suggestions and the problem continues. This P3D V4.3 has tons of potential but everytime I fix one problem seems like another pop's up. I've about decided this problem has something to do with ChasePlane. Seems to work a little better while I'm not running it. I've invested a ton of money in this program and would sure like to get it running smoothly. Thanks for the suggestions!

Are you using Nvidia Inspector to adjust any settings to the driver profile for P3D?  If so, that is the issue. Any drivers since I believe 391.35 have this issue.

Did you try the driver I suggested.  I also love seeing  Poppet and Rob dodge these topics. It's as if they don't want to acknowledge there's an issue with the software and the driver, heaven forbid

Edited September 2, 20187 yr by tooting

On 8/30/2018 at 10:16 PM, vgbaron said:

see if this helps - 

 

http://www.prepar3d.com/forum/viewtopic.php?f=6312&t=130512

 

Vic

That's the topic that Bradley tells him to uninstall his addons. It's a  conflict with ndivia drivers, capping the frames externally and prepar3d. There's so many topics on this. But no they tell this poor chap to uninstall addons because they don't want the liability of knowing theres an issue with their software and recent drivers, why don't they just be honest and say 'we are aware of the issue with capping frames in NI and are working with Ndivia to solve it' 

Edited September 2, 20187 yr by tooting

Yes Tooting, tried the 397.64 and still having the problem 😞

28 minutes ago, John Snyder Jr said:

Yes Tooting, tried the 397.64 and still having the problem 😞

Did you edit the registry? 

I have no idea how to edit the registry, that's probably way over my head 😞

8 hours ago, John Snyder Jr said:

I have no idea how to edit the registry, that's probably way over my head 😞

Then you'll need to wait for LM to address the problem, and you'll be in for a long wait. This will be way down their list of fixes to look at, unless you got some stars on your lapel.  Pm me and if youre happy I'll teamviewer onto your pc to fix it. I had the same issue the only way I found to fix it for me was to edit the registry as below

 

https://www.prepar3d.com/forum/viewtopic.php?t=130051&start=15

- Exit all Windows based programs,
- Click on the Windows Start button, type regedit in the Search box,double-click regedit.exe from the results above. 
If you are prompted for an administrator password or confirmation, type the password or provide confirmation,
- Browse to and then click the following registry subkey: 
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers
- On the Edit menu, click New, and select the QWORD (64-bit) value from the drop-down menu,
- Type ‘TdrLevel’ as the Name and click Enter,
- Double-click TdrLevel and set the value as 0 (it is set to that by default, but double check) and click OK,
- Close the registry editor and restart your computer for the changes to take effect!

I saw this fix mentioned earlier in this thread, but make sure you create a Qword (64bit) key for Windows 64 bit OS and NOT a Bword (32 bit) key because that wil not give the right result.

Edited September 3, 20187 yr by tooting

Just out of curiosity has anyone reported this to Nvidia on feedback hub.

For me, not using the nVidia frame limiter anymore fixed this error. Also with the newest driver, I did not have any issues without using the frame limiter.