Hi,
can you please help to me to fix this issue?
Thank you
AttilA
Faulting application name: Prepar3D.exe, version: 4.5.14.34698, time stamp: 0x5e94b5c2
Faulting module name: D3D10Warp.dll, version: 10.0.19041.546, time stamp: 0x50c1f389
Exception code: 0xc0000005
Fault offset: 0x00000000000b48b0
Faulting process ID: 0x10fc
Faulting application start time: 0x01d6fa067be63fec
Faulting application path: C:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe
Faulting module path: C:\Windows\SYSTEM32\D3D10Warp.dll
Report ID: 10cc515a-de64-4de2-826c-b1c72f110c88
Faulting package full name:
Faulting package-relative application ID:
CRASH
Re: CRASH
If you google this string:
d3d10warp.dll crash p3d
you'll get a number of threads dealing with this issue. However, since your error report also includes this:
Exception code: 0xc0000005
you can be reasonably certain that the crash is caused by an incompatible or badly programmed add-on.
The exception code means that someone or something tried to write to an area of RAM where they had no permission to write - typical for such an add-on.
Jorgen
d3d10warp.dll crash p3d
you'll get a number of threads dealing with this issue. However, since your error report also includes this:
Exception code: 0xc0000005
you can be reasonably certain that the crash is caused by an incompatible or badly programmed add-on.
The exception code means that someone or something tried to write to an area of RAM where they had no permission to write - typical for such an add-on.
Jorgen
System: i5-12600K@4.9 GHz, ASUS ROG STRIX Z690-I motherboard, 32 GB 4800 MHz DDR5 RAM, Gainward RTX 3060 w/ 12 GB DDR6 VRAM, Windows 10 Pro.
All views and opinions expressed here are entirely my own. I am not a Lockheed-Martin employee.
All views and opinions expressed here are entirely my own. I am not a Lockheed-Martin employee.
Re: CRASH
@atesz76 ,atesz76 wrote: ↑Wed Feb 03, 2021 10:41 am Hi,
can you please help to me to fix this issue?
Thank you
AttilA
Faulting application name: Prepar3D.exe, version: 4.5.14.34698, time stamp: 0x5e94b5c2
Faulting module name: D3D10Warp.dll, version: 10.0.19041.546, time stamp: 0x50c1f389
Exception code: 0xc0000005
Fault offset: 0x00000000000b48b0
Faulting process ID: 0x10fc
Faulting application start time: 0x01d6fa067be63fec
Faulting application path: C:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe
Faulting module path: C:\Windows\SYSTEM32\D3D10Warp.dll
Report ID: 10cc515a-de64-4de2-826c-b1c72f110c88
Faulting package full name:
Faulting package-relative application ID:
What were you flying / doing when you got the error ?
Is the situation repeatable?
Best Regards,
Vaughan Martell PP-ASEL (KDTW)
Vaughan Martell PP-ASEL (KDTW)
Re: CRASH
Hi ,
I have an other crash ,
Can you help me?
Faulting application name: Prepar3D.exe, version: 4.5.14.34698, time stamp: 0x5e94b5c2
Faulting module name: D3D10Warp.dll, version: 10.0.19041.546, time stamp: 0x50c1f389
Exception code: 0xc0000005
Fault offset: 0x00000000000b48b0
Faulting process ID: 0x27a8
Faulting application start time: 0x01d706c69f158ab5
Faulting application path: C:\P3D\Prepar3D.exe
Faulting module path: C:\Windows\SYSTEM32\D3D10Warp.dll
Report ID: 0ec8bddd-06e0-41f4-9998-014527012949
Faulting package full name:
Faulting package-relative application ID:
Thanks
Attila
I have an other crash ,
Can you help me?
Faulting application name: Prepar3D.exe, version: 4.5.14.34698, time stamp: 0x5e94b5c2
Faulting module name: D3D10Warp.dll, version: 10.0.19041.546, time stamp: 0x50c1f389
Exception code: 0xc0000005
Fault offset: 0x00000000000b48b0
Faulting process ID: 0x27a8
Faulting application start time: 0x01d706c69f158ab5
Faulting application path: C:\P3D\Prepar3D.exe
Faulting module path: C:\Windows\SYSTEM32\D3D10Warp.dll
Report ID: 0ec8bddd-06e0-41f4-9998-014527012949
Faulting package full name:
Faulting package-relative application ID:
Thanks
Attila
Re: CRASH
You need to find the incompatible or badly programmed add-on.
Unless you do that, this issue will not go away.
The add-on can be scenery and/or aircraft and/or any other add-on - you will have to find it yourself.
One tip though: the D3D10Warp.dll could point to Aerosoft - I repeat could, according to a search I did for that error.
Jorgen
Unless you do that, this issue will not go away.
The add-on can be scenery and/or aircraft and/or any other add-on - you will have to find it yourself.
One tip though: the D3D10Warp.dll could point to Aerosoft - I repeat could, according to a search I did for that error.
Jorgen
System: i5-12600K@4.9 GHz, ASUS ROG STRIX Z690-I motherboard, 32 GB 4800 MHz DDR5 RAM, Gainward RTX 3060 w/ 12 GB DDR6 VRAM, Windows 10 Pro.
All views and opinions expressed here are entirely my own. I am not a Lockheed-Martin employee.
All views and opinions expressed here are entirely my own. I am not a Lockheed-Martin employee.
Re: CRASH
I would start by checking the developer websites for updates and compatibility information.
If you only get the error flying over a certain area, then it would be reasonable to assume that a scenery add-on in that area might be the culprit. Likewise, if it occurs while flying one particular aircraft, then that might be suspect.
If you have many add-ons, then this could take a while. There is unfortunately no information in the error log that points to a certain add-on, it only says somebody/someone/something violated the rules.
Jorgen
If you only get the error flying over a certain area, then it would be reasonable to assume that a scenery add-on in that area might be the culprit. Likewise, if it occurs while flying one particular aircraft, then that might be suspect.
If you have many add-ons, then this could take a while. There is unfortunately no information in the error log that points to a certain add-on, it only says somebody/someone/something violated the rules.
Jorgen
System: i5-12600K@4.9 GHz, ASUS ROG STRIX Z690-I motherboard, 32 GB 4800 MHz DDR5 RAM, Gainward RTX 3060 w/ 12 GB DDR6 VRAM, Windows 10 Pro.
All views and opinions expressed here are entirely my own. I am not a Lockheed-Martin employee.
All views and opinions expressed here are entirely my own. I am not a Lockheed-Martin employee.