P3D Hotfix 5.1 causes DXGI Graphics card error

[Martyson]

@ MarkOtten1996,

"I think I found the solution. It was MSI Afterburner."

MSI Afterburner has been known to cause problems.

[quid21]

@ MarkOtten1996,

"I think I found the solution. It was MSI Afterburner."

MSI Afterburner has been known to cause problems.

I don't have MSI afterburner, so that might be why mine has carried on working. Or it means I haven't tested enough.

So is there a problem with DX12 and VRAM of modern cards? Is that a P3D issue or a card issue?

[Sky_King]

@ MarkOtten1996,

"I think I found the solution. It was MSI Afterburner."

MSI Afterburner has been known to cause problems.

I don't have MSI afterburner, so that might be why mine has carried on working. Or it means I haven't tested enough.

So is there a problem with DX12 and VRAM of modern cards? Is that a P3D issue or a card issue?

The issue is with DX12, not P3D or a card issue. A number of DX12 games have the VRAM issue.

[Adam_WMids_UK]

Hi All

Just to add my name to the list of users with this issue...

My 5.1 worked fine with all of my addons. I updated client/content/scenery with the component installers with admin rights to 5.1HF1 and now get the DXGI hung error. This is with the same A2A 182 aircraft at the same airport with the same scenery as I last flew in 5.1 without errors. The crash occurs a number of minutes into pre-flight after the scenario has fully loaded. My VRAM is about half full at the time as per the Shift-Z readout. It has occurred before and after engine start, but I have never gotten as far as taxiing without it happening yet.

I did also update ASP3D at the same time as required.

I have the latest BIOS and NVidia drivers for my system which is:

Ge-Force RTX 2080 Ti, 11GB GDDR6, Driver: 460.89
i9-7900X @ 3.30GHz
32GB DDR4 RAM
Windows 10 Pro (64bit) Build: 2004

I don't overclock anything.

As this isn't a CTD and instead a pop up message box with the option to close P3D, the error logs are not of type "error", with the following:

IN WINDOWS LOGS > SYSTEM (1 event)

Level: Warning
Source: Display
Event ID: 4101
Task Category: None

"Display driver nvlddmkm stopped responding and has successfully recovered."


IN WINDOWS LOGS > APPLICATION (2 events - very similar and recorded at the same date/time)

EVENT 1:
Level: Information
Source: Windows Error Reporting
Event ID: 1001
Task Category: None

"Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:
P1: 141
P2: ffff8b0b1aaaa460
P3: fffff8062ed4372c
P4: 0
P5: 1c0c
P6: 10_0_19041
P7: 0_0
P8: 256_1
P9:
P10:

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20201221-1436.dmp
\\?\C:\WINDOWS\TEMP\WER-5353687-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC181.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC191.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC190.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC1B1.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_141_8cf7e43c55618a561f70bc76ef3d1c88f350672_00000000_43f83822-244e-49fa-821d-785d1b0df938

Analysis symbol:
Rechecking for solution: 0
Report Id: 43f83822-244e-49fa-821d-785d1b0df938
Report Status: 4
Hashed bucket:
Cab Guid: 0"


EVENT 2:
Level: Information
Source: Windows Error Reporting
Event ID: 1001
Task Category: None

"Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:
P1: 141
P2: ffff8b0b1aaaa460
P3: fffff8062ed4372c
P4: 0
P5: 1c0c
P6: 10_0_19041
P7: 0_0
P8: 256_1
P9:
P10:

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20201221-1436.dmp
\\?\C:\WINDOWS\TEMP\WER-5353687-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC181.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC191.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC190.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC1B1.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_8cf7e43c55618a561f70bc76ef3d1c88f350672_00000000_cab_43f83822-244e-49fa-821d-785d1b0df938

Analysis symbol:
Rechecking for solution: 0
Report Id: 43f83822-244e-49fa-821d-785d1b0df938
Report Status: 2049
Hashed bucket:
Cab Guid: 0"

Would love to get back to flying without this! I don't particularly want the hassle of rolling back to 5.1, but do still have the component installers for that downloaded if necessary. Would it be possible to just run the client installer or would I need to run all three if it came to that? Or would it need to be a full reinstall... which I REALLY don't fancy!

Thanks

Adam

[quid21]

Hi Adam,

I read that the DXGI error can be caused by running out of VRAM on the graphics card.

I found that if I set FPS to 30 rather than 60 that this 'fixed' it for me. What is your FPS set at?

[Adam_WMids_UK]

Hi Quid21

I will try limiting the FPS to 30. Did you do it through NVidia Control Panel or in the P3D Settings?

Mine is currently unlimited.

However when the crash occurs my VRAM is around 50% full and steady.

Cheers

Adam

[quid21]

I did it through the P3D settings. Hope it works!

[Adam_WMids_UK]

Hello All

To report back, I have undertaken one short, 30 minute flight so far, but have found that setting the frame rate limiter in-Sim to 30 has, indeed fixed the issue for me.

The only difference in flight is that today's weather does not include rain, whereas yesterday's did.

I don't think this is a VRAM issue as even when I was getting the 'hung' message, my VRAM was only about half full and since I was stationary and sometimes programming the GNS430 (so not even changing my view), there would not be any reason to have to load a whole load of further VRAM hungry scenery... To go from half full to overfull would require another 6GB of scenery to suddenly be demanded!

Instead, I believe that what is happening is that the GPU itself is either being overworked or given a bad command. This error message from DX usually indicates that a DX command has been issued and that the results of the processing of this command are taking longer than expected to be returned from the GPU. This could be due to either a bad command or because the GPU is responding slowly and this is causing a time-out which prompts the error message to appear.

Having a frame rate limit fixing the issue seems to suggest too much demand on the GPU is the culprit as this would reduce the number of instructions needed to be be processed in a given second. If it were a bad DX instruction, the lower framerate would be unlikely to solve the issue as the same instructions are still being given albeit more slowly. Although I have a high end graphics card, my settings ARE demanding across most of the settings (why pay that much for a card then not use it?!). I can therefore understand the crash... however, between 5.1 and 5.1HF1, things are meant to be made more efficient I would have thought, so this shouldn't have INCREASED the likelihood of a crash!

My guess, and this is pure speculation on my part, is that LM are aware that the main source of crashes are VRAM issues. Under DX12, the onus for managing VRAM is on the software developer, rather than DX automatically managing it, as was the case in previous versions of DX. Since VRAM was getting full, I would guess LM have added more instructions to the GPU to achieve improved management of the VRAM. This will reduce VRAM full errors, but increase the load on the GPU.

Anyhow, TLDR: Setting framerate to 30 fixes it for me; Question as to why HF1 introduces the issue and whether this can be improved in HF2.

Cheers

Adam

[sanamshukla]

I have an Nvidia RTX 3080 with the current Nvidia driver 27.21.14.5730, Intel i9 10900, 32Gb on a Gigabyte Z490 board.

Every time I load the default flight, I get a CTD with a DXGI error. I've deleted my shader cache, no joy.

event viewer says:

Fault bucket 2231108943598576057, type 5
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
P1: Prepar3D.exe
P2: 5.1.12.26829
P3: 5fb44f72
P4: febc
P5: 67247104
P6:
P7:
P8:
P9:
P10:


Analysis symbol:
Rechecking for solution: 0
Report Id: e5f7ad07-7870-4424-b755-609e05a0f43d
Report Status: 268435456
Hashed bucket: 6da5a8521ad9559e3ef67dc36663e1b9
Cab Guid: 0

<?xml version="1.0" encoding="UTF-16"?>

-<WERReportMetadata>


-<OSVersionInformation>
<WindowsNTVersion>10.0</WindowsNTVersion>
<Build>19041</Build>
<Product>(0x65): Windows 10 Home</Product>
<Edition>Core</Edition>
<BuildString>19041.630.amd64fre.vb_release.191206-1406</BuildString>
<Revision>630</Revision>
<Flavor>Multiprocessor Free</Flavor>
<Architecture>X64</Architecture>
<LCID>2057</LCID>
</OSVersionInformation>

<ProblemSignatures>
<EventType>AppHangB1</EventType>
<Parameter0>Prepar3D.exe</Parameter0>
<Parameter1>5.1.12.26829</Parameter1>
<Parameter2>5fb44f72</Parameter2>
<Parameter3>febc</Parameter3>
<Parameter4>67247104</Parameter4>
</ProblemSignatures>

<DynamicSignatures>
<Parameter1>10.0.19041.2.0.0.768.101</Parameter1>
<Parameter2>2057</Parameter2>
<Parameter22>febc87d67bc3c48ed954cbddb2529c65</Parameter22>
<Parameter23>6202</Parameter23>
<Parameter24>62020e30b7f40e95773e5328361396fb</Parameter24>
<Parameter25>febc</Parameter25>
<Parameter26>febc87d67bc3c48ed954cbddb2529c65</Parameter26>
<Parameter27>6202</Parameter27>
<Parameter28>62020e30b7f40e95773e5328361396fb</Parameter28>
</DynamicSignatures>

<SystemInformation>
<MID>E1BC6E44-A39E-4C0D-B626-8CD33B53CA8A</MID>
<SystemManufacturer>Gigabyte Technology Co., Ltd.</SystemManufacturer>
<SystemProductName>Z490 GAMING X</SystemProductName>
<BIOSVersion>F5c</BIOSVersion>
<OSInstallDate>1595009040</OSInstallDate>
<OSInstallTime>1601-01-02T20:35:26Z</OSInstallTime>
<TimeZoneBias>00:00</TimeZoneBias>
</SystemInformation>

<SecureBootState>
<UEFISecureBootEnabled>NotCapable</UEFISecureBootEnabled>
</SecureBootState>

<ReportInformation>
<Guid>3d29a849-cbb7-4e06-ac17-84c9174bfb72</Guid>
<CreationTime>2020-11-29T18:26:21Z</CreationTime>
</ReportInformation>
</WERReportMetadata>

<?xml version="1.0" encoding="UTF-16"?>
Omegle Tv
-<WERReportMetadata>

-<OSVersionInformation>
<WindowsNTVersion>10.0</WindowsNTVersion>
<Build>19041</Build>
<Product>(0x65): Windows 10 Home</Product>
<Edition>Core</Edition>
<BuildString>19041.630.amd64fre.vb_release.191206-1406</BuildString>
<Revision>630</Revision>
<Flavor>Multiprocessor Free</Flavor>
<Architecture>X64</Architecture>
<LCID>2057</LCID>
</OSVersionInformation>

<ProcessMetadata>
<d3ddredDataPresent>0</d3ddredDataPresent>
</ProcessMetadata>

<ProblemSignatures>
<EventType>D3DDRED2</EventType>
<Parameter0>VEN_10DE</Parameter0>
<Parameter1>27.21.14.5730</Parameter1>
<Parameter2>0x887A0006</Parameter2>
<Parameter3>7</Parameter3>
<Parameter4>Prepar3D.exe</Parameter4>
<Parameter5>5.1.12.26829</Parameter5>
</ProblemSignatures>

<DynamicSignatures>
<Parameter1>10.0.19041.2.0.0.768.101</Parameter1>
<Parameter2>2057</Parameter2>
</DynamicSignatures>

<SystemInformation>
<MID>E1BC6E44-A39E-4C0D-B626-8CD33B53CA8A</MID>
<SystemManufacturer>Gigabyte Technology Co., Ltd.</SystemManufacturer>
<SystemProductName>Z490 GAMING X</SystemProductName>
<BIOSVersion>F5c</BIOSVersion>
<OSInstallDate>1595009040</OSInstallDate>
<OSInstallTime>1601-01-02T20:35:26Z</OSInstallTime>
<TimeZoneBias>00:00</TimeZoneBias>
</SystemInformation>

<SecureBootState>
<UEFISecureBootEnabled>NotCapable</UEFISecureBootEnabled>
</SecureBootState>

<ReportInformation>
<Guid>afb0ba11-271c-4780-a123-c303c61ccc22</Guid>
<CreationTime>2020-11-29T18:24:12Z</CreationTime>
</ReportInformation>
</WERReportMetadata>

The program Prepar3D.exe version 5.1.12.26829 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
Process ID: 43e0
Start Time: 01d6c67cc08d63e6
Termination Time: 4294967295
Application Path: C:\Program Files\Lockheed Martin\Prepar3D v5\Prepar3D.exe
Report Id: e5f7ad07-7870-4424-b755-609e05a0f43d
Faulting package full name:
Faulting package-relative application ID:
Hang type: Top level window is idle

Did you install this version of P3D from scratch, or did you upgrade from an earlier version?

If you installed from scratch, did you then run the installer as Administrator?

sanamShuklaa

[dennya]

I came back to P3D V5.1 after an MSFS hiatus because I picked up the A2A B-17 on sale, and also figured it'd be fun to fly some of my other military planes. (And I'm not a fan of "hack" portovers into MSFS.)

But I keep getting crashes that I'm out of graphics memory, particularly when using VR. (RTX 3080 with 11GB of RAM!) Lowered the resolution, most graphics settings are at mid-range, and still having problems.

Anyone found magic settings to cure this? It's shocking how unstable 5.1 is due to this issue compared to earlier versions. I'd revert to 4.5, but I like using VR and it's much better in 5.1 than 4.5. Not to mention I spent the money on 5.x so it'd be nice to be able to use it...

Just finished a flight with no crashes in flight and got a "texture compositor/prepar3d will break" error at the end of the flight.

Hope Lockheed's F-35 software is more stable than this. :)

[quid21]

I have an Nvidia RTX 3080 with the current Nvidia driver 27.21.14.5730, Intel i9 10900, 32Gb on a Gigabyte Z490 board.

Every time I load the default flight, I get a CTD with a DXGI error. I've deleted my shader cache, no joy.

event viewer says:

Fault bucket 2231108943598576057, type 5
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Did you install this version of P3D from scratch, or did you upgrade from an earlier version?

If you installed from scratch, did you then run the installer as Administrator?

sanamShuklaa

I upgraded from an earlier V5.1 version following the instructions as usual - the issue did not exist with V5.1, only when the hotfix was applied does the issue occur. I am administrator on my PC.

[quid21]

Hello All

To report back, I have undertaken one short, 30 minute flight so far, but have found that setting the frame rate limiter in-Sim to 30 has, indeed fixed the issue for me.

The only difference in flight is that today's weather does not include rain, whereas yesterday's did.

I don't think this is a VRAM issue as even when I was getting the 'hung' message, my VRAM was only about half full and since I was stationary and sometimes programming the GNS430 (so not even changing my view), there would not be any reason to have to load a whole load of further VRAM hungry scenery... To go from half full to overfull would require another 6GB of scenery to suddenly be demanded!

Instead, I believe that what is happening is that the GPU itself is either being overworked or given a bad command. This error message from DX usually indicates that a DX command has been issued and that the results of the processing of this command are taking longer than expected to be returned from the GPU. This could be due to either a bad command or because the GPU is responding slowly and this is causing a time-out which prompts the error message to appear.

Having a frame rate limit fixing the issue seems to suggest too much demand on the GPU is the culprit as this would reduce the number of instructions needed to be be processed in a given second. If it were a bad DX instruction, the lower framerate would be unlikely to solve the issue as the same instructions are still being given albeit more slowly. Although I have a high end graphics card, my settings ARE demanding across most of the settings (why pay that much for a card then not use it?!). I can therefore understand the crash... however, between 5.1 and 5.1HF1, things are meant to be made more efficient I would have thought, so this shouldn't have INCREASED the likelihood of a crash!

My guess, and this is pure speculation on my part, is that LM are aware that the main source of crashes are VRAM issues. Under DX12, the onus for managing VRAM is on the software developer, rather than DX automatically managing it, as was the case in previous versions of DX. Since VRAM was getting full, I would guess LM have added more instructions to the GPU to achieve improved management of the VRAM. This will reduce VRAM full errors, but increase the load on the GPU.

Anyhow, TLDR: Setting framerate to 30 fixes it for me; Question as to why HF1 introduces the issue and whether this can be improved in HF2.

Cheers

Adam

Glad it worked Adam. Fingers crossed for HF2 if and when it appears. Would be nice to have this issue at least acknowledged by a member of the Dev team.

[sportpilot67]

Running a 6800XT (not overclocked), Z-370 (default settings) and a I7-9700K on water (not overclocked) and yet I cannot fly without the risk of wasting my time on a device hung error on P3D 5.1 HF1. End of story!

Yet I can fly all day long on a GTX1080 with my RAM overclocked and my CPU overclocked and stable at 5.1 and only crash the sim when I fly into a VRAM intensive scenery like LatinVFR KFLL without reducing the settings!

Fault bucket 1334594581079243969, type 5
Event Name: D3DDRED2
Response: Not available
Cab Id: 0

Problem signature:
P1: VEN_1002
P2: 27.20.14533.1000
P3: 0x887A0006
P4: 7
P5: Prepar3D.exe
P6: 5.1.12.26829
P7:
P8:
P9:
P10:

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFABC.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFACC.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFAEA.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFAFA.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_VEN_1002_488ba8686744579cfc2b8781215ee97c7b7a9f_00000000_a58a7e9a-b2cc-4206-9e70-622c8d2f64ed

Analysis symbol:
Rechecking for solution: 0
Report Id: a58a7e9a-b2cc-4206-9e70-622c8d2f64ed
Report Status: 2147487744
Hashed bucket: 84ac1c0abfaf67ee02856eb35463bcc1
Cab Guid: 0

[JorgenSA]

Ray,

As mentioned in your other posting, we will need to see the error entry in Windows Event Viewer at the time of the crash.

Jorgen

[sportpilot67]

Jorgen,

I guess I am confused. In my latest posting I pasted the entire Event Viewer entry. What else are you looking for?

Ray