A320 v1.31 start with crash

[chc4513 0]

Hi guys~

I got a big problem about the P3D v3 crashed.

When I load the a320, It work fine at loading.

Then when load complete , the cockpit works , but the panelbar doesn't came out and then the p3d crashed.

I found the report that shows it's d3d11.dll crashed.

This problem just happen when i used a320, and it's fine with other payware.

Does anyone have ideas?? 

Win10 64b p3d v3

 0

[mopperle 4162]

I've closed your other topic, as one topic is enough.;)

Just loaded a A320 in P3dv3 an it works fine, no crash at all.

So please post the complete error message.

Are your drivers and DirectX up-to-date?

When did you download the 1.31?

[chc4513 0]

Nvidia Drivers : 358.87 

DirectX: DX12

I try to reinstall the latest 1.31 and get the same issue.

來源
Prepar3D exe

摘要
已停止運作

日期
‎2015/‎11/‎6 下午 03:47

狀態
報告已傳送

描述
失敗的應用程式路徑:    E:\Lockheed Martin\Prepar3D v3\Prepar3D.exe

問題簽章
問題事件名稱:    APPCRASH
應用程式名稱:    Prepar3D.exe
應用程式版本:    3.0.10.14945
應用程式時間戳記:    560b4abe
錯誤模組名稱:    d3d11.dll
錯誤模組版本:    10.0.10240.16384
錯誤模組時間戳記:    559f3c11
例外狀況代碼:    c0000005
例外狀況位移:    00049458
作業系統版本:    10.0.10240.2.0.0.256.48
地區設定識別碼:    1028
其他資訊 1:    bdcb
其他資訊 2:    bdcb33e65a9843796b7ec31cc25bda3b
其他資訊 3:    689d
其他資訊 4:    689d12abf00dd47c453b5e1a156c0fa3

問題的額外資訊
貯體識別碼:    1338af87b39e3261a189901b6811b986 (107650715038)
 

[Dekpol 2]

Hello,

I have the same problem. I download the A320/321 1.31 today morning. 

Source
Prepar3D exe

Summary
Stopped working

Date
‎11/‎7/‎2015 2:16 PM

Status
Report sent

Description
Faulting Application Path:    D:\Lockheed Martin\Prepar3D\Prepar3D.exe

Problem signature
Problem Event Name:    APPCRASH
Application Name:    Prepar3D.exe
Application Version:    3.0.10.14945
Application Timestamp:    560b4abe
Fault Module Name:    d3d11.dll
Fault Module Version:    10.0.10240.16384
Fault Module Timestamp:    559f3c11
Exception Code:    c0000005
Exception Offset:    00049527
OS Version:    10.0.10240.2.0.0.256.48
Locale ID:    1033
Additional Information 1:    bdcb
Additional Information 2:    bdcb33e65a9843796b7ec31cc25bda3b
Additional Information 3:    689d
Additional Information 4:    689d12abf00dd47c453b5e1a156c0fa3

Extra information about the problem
Bucket ID:    1faf994e59cd267749e94542e220c895 (107641890594)
 

My system: Windows 10 Pro, i7-6700K 4.00 GHz, G.Skill F4-3000C15D-32GTZ.

Only Prepar3D v3 installed.

[mopperle 4162]

Guys, all similar reported issues so far were related to Windows systems not being up-to-date. So make 100% that your complete environment is up-to-date!

[Dekpol 2]

Hey,
Can someone explain to me how to do the update?  I really do not know where I have a problem. I'm asking just help.
Prepar3D exe

Summary
Stopped working

Date
‎11/‎8/‎2015 7:32 AM

Status
Report sent

Description
Faulting Application Path:    D:\Lockheed Martin\Prepar3D\Prepar3D.exe

Problem signature
Problem Event Name:    APPCRASH
Application Name:    Prepar3D.exe
Application Version:    3.0.10.14945
Application Timestamp:    560b4abe
Fault Module Name:    d3d11.dll
Fault Module Version:    10.0.10240.16384
Fault Module Timestamp:    559f3c11
Exception Code:    c0000005
Exception Offset:    00097260
OS Version:    10.0.10240.2.0.0.256.48
Locale ID:    1033
Additional Information 1:    bdcb
Additional Information 2:    bdcb33e65a9843796b7ec31cc25bda3b
Additional Information 3:    689d
Additional Information 4:    689d12abf00dd47c453b5e1a156c0fa3

Extra information about the problem
Bucket ID:    f83a12f3147681c9b07880c4614ac6d5 (107645542760)
 

Please login to display this image.

Please login to display this image.

[kpeecee 5]

I've just looked at the steam forum and some have had the same situation, The faulting module seems to be DX11, does your card support DX11

[Dekpol 2]

I have GPU GeForce GTX 780, driver 358.87. P3D is default configurations.

[stook2005 1]

I get the startup crash with P3DV3 and A318/319/320/321 v1.31.  All other payware like PMDG 777/737, IRIS Warhog, Aerosoft Otter, etc works fine.  Only Aerosoft Airbus crashes on startup.   Here's my system.

 

Win 10 Pro

Skylake i6700K

16Gigs DDR4

2xGTX 970 SLI

Nvidia driver: 358.87

Windows Setup tells me I'm up to date.

 

 

Log Name:      Application
Source:        Application Error
Date:          11/8/2015 9:40:04 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      JimmyPC
Description:
Faulting application name: Prepar3D.exe, version: 3.0.10.14945, time stamp: 0x560b4abe
Faulting module name: d3d11.dll, version: 10.0.10240.16384, time stamp: 0x559f3c11
Exception code: 0xc0000005
Fault offset: 0x00049527
Faulting process id: 0x29bc
Faulting application start time: 0x01d11a482b883031
Faulting application path: C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Prepar3D.exe
Faulting module path: C:\WINDOWS\SYSTEM32\d3d11.dll
Report Id: 7821edf2-3918-47a8-b11e-952adecdb75d
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="2015-11-08T17:40:04.000000000Z" />
    <EventRecordID>12190</EventRecordID>
    <Channel>Application</Channel>
    <Computer>JimmyPC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Prepar3D.exe</Data>
    <Data>3.0.10.14945</Data>
    <Data>560b4abe</Data>
    <Data>d3d11.dll</Data>
    <Data>10.0.10240.16384</Data>
    <Data>559f3c11</Data>
    <Data>c0000005</Data>
    <Data>00049527</Data>
    <Data>29bc</Data>
    <Data>01d11a482b883031</Data>
    <Data>C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Prepar3D.exe</Data>
    <Data>C:\WINDOWS\SYSTEM32\d3d11.dll</Data>
    <Data>7821edf2-3918-47a8-b11e-952adecdb75d</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

[JRA 0]

I have the similar crash to desktop running Windows 10 Pro.  Finally got it to work by NOT selecting "Generate load Sheet" in the fuel planner.  I also set the Fuel Planner Executable to run in Windows 7 comparability mode. Have not gone back and selected this to cause the CTD since its working now.

Windows 10 may be causing some problems, but I could be wrong.

My configuration below.

Win 10 Pro 64Bit

Skylake i6700K

32Gigs DDR4 3000

EVGA GTX 980Ti

Nvidia driver: 358.87

Windows up to date.

 

[stook2005 1]

48 minutes ago, JRA said:

I have the similar crash to desktop running Windows 10 Pro.  Finally got it to work by NOT selecting "Generate load Sheet" in the fuel planner.  I also set the Fuel Planner Executable to run in Windows 7 comparability mode. Have not gone back and selected this to cause the CTD since its working now.

Windows 10 may be causing some problems, but I could be wrong.

My configuration below.

Win 10 Pro 64Bit

Skylake i6700K

32Gigs DDR4 3000

EVGA GTX 980Ti

Nvidia driver: 358.87

Windows up to date.

 

 

Where is the "fuel planner" installed?  I can't find it at

c:\Program Files (x86)\Lockheed Martin\Prepard3D v3\aerosoft\Airbus A318_A319

c:\Program Files (x86)\Lockheed Martin\Prepard3D v3\aerosoft\Airbus A320_A321

 

jimmy

 

 

[Tom A320 4915]

Hi Jimmy,

just right click on the fuel planner icon in the Start menu and then select "Properties".

There you will find the installation folder.

[Tom A320 4915]

15 hours ago, stook2005 said:

...

Log Name:      Application
Source:        Application Error
Date:          11/8/2015 9:40:04 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      JimmyPC
Description:
Faulting application name: Prepar3D.exe, version: 3.0.10.14945, time stamp: 0x560b4abe
Faulting module name: d3d11.dll, version: 10.0.10240.16384, time stamp: 0x559f3c11

...

This is a file being provided by Microsoft. If you google for it you find tons of pages explaining how to fix problems with it. It seems like there a a lot of people around don't having luck with the file.

Here is a link with a number of useful suggestions. Please go through to them as far as they apply:

http://pcsupport.about.com/od/findbyerrormessage/a/d3d11-dll-not-found-missing-error.htm

 

Please note, that this problem does not show up on any AS developer machine, internal test machines or external beta tester machines. As it is not reproducible for AS there is not much, AS can do about it at the moment, sorry.

[fpoa347 1]

Was anyone here able to get anywhere with this? I'm also crashing on d3d11.dll on startup. If not on startup, I just crash with no error at some point in the flight or within first minute or so. It's been happening for some time.

I used to be able to get away with a system reboot, but now just a hit or miss. All other free and paid craft complete flights perfectly.

Have tried reinstalling everything sans antivirus, short of a fresh Windows install at this point. All SDKs and redists required to my knowledge installed (is there a complete list of dependencies somewhere?) Extraneous audio drivers/devices disabled from video card. Force ECAM rendering on/off. sfc has been run. cfg deleted. Even tried UIautomationcore as a shot in the dark, but this causes stranger problems most of the time. Endless appcrashviews available on request. Each test trial has been after a computer reboot, a/v off.

A bit lost now and any direction will help. Hosing Windows install is nearby.

Updated Win 10, 970s in SLI 358.91, i5 Skylake, 'bus 1.31, p3dv3 (edit:) not on C:/

Trick with fuel planner doesn't seem to impact things over here.

[torkermax 2]

Add me to the list V1.31 A318/319.

[stook2005 1]

fuel planner trick didn't work for me.  

[fpoa347 1]

Copied d3d11.dll from c:/win/sys32 into the p3d folder - almost through a 2.5 hour flight with no crash. Will have to do many more tests with this to confirm. Throwing it out there for others to try. Didn't expect to make it this far.

Edit: landed and unloaded. next trials not promising. Crashing for other reasons - viewer shows loading d3d.dll from C:/win location anyway.

[Tom A320 4915]

I don't see why this should do any change, as the D3D11.DLL is a Windows file being directly provided by Microsoft. I haven't seen any manufacturer so far who replaces the Microsoft version.

And also, if you expect any positive outcome of this, you should have taken the version from the C:\Windows\SysWOW64 folder, as that's that one that is needed (and used by the 32bit emulation layer of a 64bit Windows) for P3D (assuming that you have 64bit Windows installed of course).

[chrisal 5]

I've just had this problem with a clean p3d install and copying the file from C:\Windows\SysWOW64 has worked for me - so far!

I had previously tried everything - updating, re-installing removing scenery etc. This did it.

Chris

[stook2005 1]

3 hours ago, chrisal said:

I've just had this problem with a clean p3d install and copying the file from C:\Windows\SysWOW64 has worked for me - so far!

I had previously tried everything - updating, re-installing removing scenery etc. This did it.

Chris

Copying d3d11.dll into my p3dv3 installation directory works for me.  No more CTD when using aerosoft airbus.

[Tom A320 4915]

That is a clear sign that you have some kind of application installed that brought it's own (crappy) version of the file and placed it into a folder that is listed in the PATH environment variable.

Please do a file search for "d3d11.dll" on all your drives. Maybe that will lead to the culprit.

[fpoa347 1]

^ tests with d3d from syswow64 have been successful over here as well

[Joshua Che. 1601]

Do any of you have FSSpotlights?

[fpoa347 1]

I do not.

(For what it's worth, with respect to lighting I do have to cycle the landing / taxi lights on then off for them to appear off. For some reason they load and appear on when all switches are in the off position. Interior lights behave normally. I consider this to be a super small non-issue though, throwing that out there if it's related to any investigation with lighting)

[VoltageAviation 9]

On 11/15/2015, 7:42:47, Tom A320 said:

That is a clear sign that you have some kind of application installed that brought it's own (crappy) version of the file and placed it into a folder that is listed in the PATH environment variable.

Please do a file search for "d3d11.dll" on all your drives. Maybe that will lead to the culprit.

Thanks for the suggestion of the Syswow64 folder. Myself included no longer has this issue. I literally installed windows 7 followed by a W10 upgrade so no idea why it happened but yeah, atleast its solved (for now). These were the only D3D11.dll's on my system and nothing out of the ordinary (in my opinion anyway) http://prntscr.com/9am7ex

Thanks