Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

DXGI_ERROR_DRIVER_INTERNAL_ERROR

Featured Replies

Hi, I get this error when I start up p3dv4. I have a potato computer, but it should be able to run v4. I have reinstalled windows about 3 times now and have replaced the driver countless times, but to no avail.

Is this a problem on my PC? or is it a problem with p3d?

unknown.png

 

unknown.png

 

unknown.png

Edited by AviationGaming

  • Author

Oh, sorry about that, I am so used to saying v4. Yes, I am running v5 obviously. I believe that is the same error as mine, my crash is caused by dwite.dll.

 

Log Name:      Application
Source:        Application Error
Date:          4/17/2020 1:11:40 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-NIOM1NJ
Description:
Faulting application name: Prepar3D.exe, version: 5.0.21.34709, time stamp: 0x5e95060d
Faulting module name: dwrite.dll, version: 10.0.18362.476, time stamp: 0xb43f56a0
Exception code: 0xc00000fd
Fault offset: 0x0000000000039c61
Faulting process id: 0x1604
Faulting application start time: 0x01d614da44d09554
Faulting application path: E:\Prepar3D v5\Prepar3D.exe
Faulting module path: C:\Windows\SYSTEM32\dwrite.dll
Report Id: 5ad771cd-9129-46ce-a98e-0ec040239b92
Faulting package full name: 
Faulting package-relative application ID: 
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2020-04-17T17:11:40.077900400Z" />
    <EventRecordID>1540</EventRecordID>
    <Channel>Application</Channel>
    <Computer>DESKTOP-NIOM1NJ</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Prepar3D.exe</Data>
    <Data>5.0.21.34709</Data>
    <Data>5e95060d</Data>
    <Data>dwrite.dll</Data>
    <Data>10.0.18362.476</Data>
    <Data>b43f56a0</Data>
    <Data>c00000fd</Data>
    <Data>0000000000039c61</Data>
    <Data>1604</Data>
    <Data>01d614da44d09554</Data>
    <Data>E:\Prepar3D v5\Prepar3D.exe</Data>
    <Data>C:\Windows\SYSTEM32\dwrite.dll</Data>
    <Data>5ad771cd-9129-46ce-a98e-0ec040239b92</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

Not sure that GPU of yours is up to the task. 

Could be your graphics card is not DX12 compatible, worth checking😏

  • Author

I have already checked. My GPU is compatible with DX12.

9 hours ago, ha5mvo said:

Not sure that GPU of yours is up to the task. 

I get the same crash and I am running a Titan Xp.

- Kevin

Windows 11 / Ryzen 7 9800X3D / MSI RTX-4080 Super 16G Ventus 3X / Gigabyte B850 Aorus Elite WiFi 7 / Arctic Liquid Freezer III Pro / 64GB Lexar ARES Gen2 RGB DDR5 6000Mhz CL30 RAM / Dell Alienware AW3418DW WQHD 3440x1440 GSync / Samsung 970 EVO Plus M.2 2TB (OS) & 860 EVO 4TB SDD / WD Caviar Black 4TB HDD  / EVGA Supernova 850 G5 PSU / Be Quiet Light Base 600 LX case / Virpil Warbird base with Constellation Alpha grip / MFG Crosswind rudder pedals / Virtual-Fly TQ6+ throttle quadrant / Winwing Orion HOTAS F-18 Throttle / Virpil TCS+ collective base with Hawk-60 grip / Saitek Trim Wheel / Saitek Radio and Switch Panels / Winwing Combat Ready Panel / Tobii 5

I have answered this elsewhere (P3D forums) - I am willing to bet you are running MSI Afterburner/RTSS (I think it is RTSS).

Had the same problem with both 1080Ti and 2080Ti. Turned them off problem gone. Try it?

Edited by Uteman

A.Chryss - near YSCB

1. ASUS TUFF X570E wifi, Ryzen 5950X EK 420x45 RAD, D5 Pump, EK monoblok, 32GBs GSkill Ram, Gig Aorus RTX 3080TiTi, SSung 980 Pro 2TB & 1Tb. XBox controller and Stream Deck XL for  - camera and sim control (non AC)

2. ASUS Tuff Z690 i7-14700K, Zotac RTX 4080Super, 32MHz ram 2x 970EVO 1TBNVME  3x ssd etc.  MSFS2020 & DCS. 49" Predator 240Hz OLED monitor & tablets. Warthog controllers, Honeycomb Yoke, Thrustmaster TPR pedals, TrackIR & KVM.

3 minutes ago, Uteman said:

I have answered this elsewhere (P3D forums) - I am willing to bet you are running MSI Afterburner/RTSS (I think it is RTSS).

Had the same problem with both 1080Ti and 2080Ti. Turned them off problem gone. Try it?

Not running Afterburner or RTSS - don't even have them installed.

This was with the RealAir Turbine Duke - that is the only thing I can think of.  My performance is also really laggy when I point the sim to my A2A addon folder and fire up one of those.  All I can think of is that the v4-compatible aircraft don't necessarily play nice with with v5 and DX12 and need to be optimized, since this error hasn't happened to me with any of the default aircraft.

- Kevin

Windows 11 / Ryzen 7 9800X3D / MSI RTX-4080 Super 16G Ventus 3X / Gigabyte B850 Aorus Elite WiFi 7 / Arctic Liquid Freezer III Pro / 64GB Lexar ARES Gen2 RGB DDR5 6000Mhz CL30 RAM / Dell Alienware AW3418DW WQHD 3440x1440 GSync / Samsung 970 EVO Plus M.2 2TB (OS) & 860 EVO 4TB SDD / WD Caviar Black 4TB HDD  / EVGA Supernova 850 G5 PSU / Be Quiet Light Base 600 LX case / Virpil Warbird base with Constellation Alpha grip / MFG Crosswind rudder pedals / Virtual-Fly TQ6+ throttle quadrant / Winwing Orion HOTAS F-18 Throttle / Virpil TCS+ collective base with Hawk-60 grip / Saitek Trim Wheel / Saitek Radio and Switch Panels / Winwing Combat Ready Panel / Tobii 5

I am running the A2A Skylane and it certainly slows things down compared to default AC but I haven't had the DX12 disconnect error message whilst using it. Did you turn off/rename the windshield.dll in gauges folder as they recommend?

A.Chryss - near YSCB

1. ASUS TUFF X570E wifi, Ryzen 5950X EK 420x45 RAD, D5 Pump, EK monoblok, 32GBs GSkill Ram, Gig Aorus RTX 3080TiTi, SSung 980 Pro 2TB & 1Tb. XBox controller and Stream Deck XL for  - camera and sim control (non AC)

2. ASUS Tuff Z690 i7-14700K, Zotac RTX 4080Super, 32MHz ram 2x 970EVO 1TBNVME  3x ssd etc.  MSFS2020 & DCS. 49" Predator 240Hz OLED monitor & tablets. Warthog controllers, Honeycomb Yoke, Thrustmaster TPR pedals, TrackIR & KVM.

This 9 page DXGI thread has some possible fixes:

https://www.prepar3d.com/forum/viewtopic.php?f=6315&t=130051

I realize that this is not the exact same error, but I do remember one of these solutions fixing my situation. This was a couple of years ago so I'm not going to remember the details.

There is some Registry editing involved. 

1 hour ago, Uteman said:

I am running the A2A Skylane and it certainly slows things down compared to default AC but I haven't had the DX12 disconnect error message whilst using it. Did you turn off/rename the windshield.dll in gauges folder as they recommend?

Yup did that - the sim will not load without doing that step anyway.

- Kevin

Windows 11 / Ryzen 7 9800X3D / MSI RTX-4080 Super 16G Ventus 3X / Gigabyte B850 Aorus Elite WiFi 7 / Arctic Liquid Freezer III Pro / 64GB Lexar ARES Gen2 RGB DDR5 6000Mhz CL30 RAM / Dell Alienware AW3418DW WQHD 3440x1440 GSync / Samsung 970 EVO Plus M.2 2TB (OS) & 860 EVO 4TB SDD / WD Caviar Black 4TB HDD  / EVGA Supernova 850 G5 PSU / Be Quiet Light Base 600 LX case / Virpil Warbird base with Constellation Alpha grip / MFG Crosswind rudder pedals / Virtual-Fly TQ6+ throttle quadrant / Winwing Orion HOTAS F-18 Throttle / Virpil TCS+ collective base with Hawk-60 grip / Saitek Trim Wheel / Saitek Radio and Switch Panels / Winwing Combat Ready Panel / Tobii 5

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.