Events log Win 11 P3d V6.1..11

[Emile]

Hello, 

I have a problem in the last 2 days , P3d "exits" , no error message near some airports in south America (exemple SVMT) 

I do not find how to search in the Win 11 Events any created entry

Can some one tell me "how to search"  in the Events???

Thanks in advance

 

[simfan1983]

If it always happens in a certain part of the world that sounds like a scenery index issue or some incorrectly installed scenery.

Open Event Viewer, look in Windows Logs - Application and you will see a list of events. Scroll down and see if there is a red event around the time that P3D CTDs and click on that event if you have one. In the lower panel it will tell you the application and also the related dll that failed. You don't always get an event recorded in event viewer and sometimes it is not much help, for example it's just a ntdll.dll generic failure. If it's a scenery issue then it may be terrain.dll that is listed.

There are a few steps I take if I have CTDs in P3D that may help. You can search how to do these if you are not familiar:

Flush the P3D shaders
Rebuild the scenery indexes
If you use Orbx scenery use the insertion point tool in the settings in Orbx Central to re-order your scenery (I'm guessing you are not using Orbx with v6 as it is a bit complicated to set up). 

You can also delete your p3d.cfg and let P3D rebuild it next time you open P3D (this will reset your sim settings so take a backup of the controls settings and graphics settings before you do this).

In Windows open a command prompt with administrator rights and run sfc /scannow to check for any corrupt windows files. It will fix any errors if it finds them.

Delete all the content in users/yourname/appdata/local/temp

In Windows run disc clean-up and delete the Direct-X shader cache.

If none of this helps please report back.

 

 

 

 

 

[Emile]

Ok I found some information

System

- Provider       [ Name] Application Error       [ Guid] {a0e9b465-b939-57d7-b27d-95d8e925ff57}

EventID 1000

Version 0

Level 2

Task 100

Opcode 0

Keywords 0x8000000000000000

- TimeCreated       [ SystemTime] 2024-07-22T16:06:26.0337222Z

EventRecordID 28008

Correlation

- Execution       [ ProcessID] 17404       [ ThreadID] 4848

Channel Application

Computer E1000

- Security       [ UserID] S-1-5-21-1759496656-769038791-2976545376-1001

-

EventData

AppName

Prepar3D.exe

AppVersion

6.1.11.31619

AppTimeStamp

65c97d5a

ModuleName

DSOUND.dll

ModuleVersion

10.0.22621.3527

ModuleTimeStamp

85222e5b

ExceptionCode

c0000005

FaultingOffset

000000000001c7fe

ProcessId

0x46dc

ProcessCreationTime

0x1dadc4d1e4fb6f1

AppPath

X:\Prepar3D.exe

ModulePath

C:\Windows\SYSTEM32\DSOUND.dll

IntegratorReportId

ff3b9ec4-45de-4b57-82c4-cac533708927

PackageFullName

PackageRelativeAppId

[Ray Proudfoot]

@Emile, that’s a new one. As this is a relatively new problem ask yourself what has changed on your setup.

Is this using a third party aircraft at a default airport? If so, try the same airport with a default aircraft. If the problem goes away then the aircraft is suspect.

If the problem remains then the airport is suspect. If it’s a third party airport disable it and repeat the test.

Come back after trying that.

One last thing. Is drive X a standard internal SSD? It’s unusual for P3D to be installed away from C or possibly D.

[dave2013]

If it's only happening near those particular airports, then the problem is likely related to the location.

Are you using any payware scenery, including airports, for that area?

It's interesting that the faulting module is DSOUND.dll.  There is no DLL file with this name for P3Dv6, so it must be an addon, either scenery or aircraft. 

If it's an aircraft that's causing this, where the DLL is in the gauges or aircraft folder, then it should happen anywhere.  It could also be that this DLL is conflicting with some payware scenery in that area.

Update: there is a Windows system file named dsound.dll.  So, it's either a particular scenery or aircraft that's using it for sound.

Dave

Edited July 23, 2024 by dave2013

[fadde]

This is annoying, I recieve this log quite often in 6.1.11

After a computer restart i can do the same flight again without problem

Faulting application name: Prepar3D.exe, version: 6.1.11.31619, time stamp: 0x65c97d5a
Faulting module name: terrain.dll, version: 6.1.11.31619, time stamp: 0x65c97cbf
Exception code: 0xc0000005
Fault offset: 0x00000000000deec0
Faulting process id: 0xF70
Faulting application start time: 0x1DB40F44561C9F5
Faulting application path: F:\P3Dv6\Prepar3D.exe
Faulting module path: F:\P3Dv6\terrain.dll
Report Id: 6097bc8f-f77a-4c81-bfa3-ad345b133c0b
Faulting package full name: 
Faulting package-relative application ID: 

 

Anyone more having this problem?

//Mikael

[G-RFRY]

Try posting on the LM P3D Forum. this could a corrupted Windows PowerShell.

[fadde]

Thanks, I try that!

[Emile]

Hello

My problem is solved

I removed some old airport .bgl

Have a nice day