P3D v4.5 wont launch, CTD immediately, new install d3d9.dll

[ssirhc]

Hello to all!

I reinstalled (no addons) my sim, and it crashed inmadeatly, when I tried to start.
My event log:

Faulting application name: Prepar3D.exe, version: 4.5.12.30293, time stamp: 0x5cd47aad
Faulting module name: d3d9.dll, version: 10.0.18362.329, time stamp: 0x1ac9a115
Exception code: 0xc0000005
Fault offset: 0x00000000000ac44e
Faulting process id: 0x728
Faulting application start time: 0x01d56a89dd9976c4
Faulting application path: C:\FS\Lockheed Martin\Prepar3D v4\Prepar3D.exe
Faulting module path: C:\WINDOWS\SYSTEM32\d3d9.dll
Report ID: cf438089-5e1a-4927-9d29-0a0e5a253c87
Faulting package full name:
Faulting package-relative application ID:

I tried to reinstall this: DirectX End-User Runtimes (June 2010)

In my system32 library the d3d9.dll file has the 01/09/2019 date. According the event log there was a windows update on 01/09

What can I do?

[RRVyper]

You should be able to uninstall the latest Windows update (possibly kb4515384) and pause updates for 7 days. MS is aware of issues with this update (which was supposed to fix a previous update) and should release a fix shortly. It doesn’t affect everyone, though. My system is fine.

Randy

[ssirhc]

Thank you Randy!

[ssirhc]

I think, I solved the problem. I toke an older version of the d3d9.dll, that in the KB4512941 windows update, older than 10.0.18362.329, and I copied it into the main P3D installation folder. Now I can start the sim. Thank you the tip again Randy.

[RRVyper]

Strange that reinstalling the DirectX runtimes didn't fix it for you. I guess the only issue is that there must be a reason MS updated those files so your fix may cause issues elsewhere. Perhaps Win 10 v1909 will behave better for everyone and will bring your system back up-to-date. But, in the meantime you can enjoy flying. 😉

Randy

[ssirhc]

I made a try. I copied the newest d3d9.dll file into my main folder of the sim, and traraaa... the sim works fine. So I don't know, but I can use it. :-)

[RRVyper]

Lol. You like living on the edge. I doubt that file will get used as it should reside in the C:\Windows\System32 folder. You can use Resource Monitor (available through Task Manager) to browse the associated modules in use by Prepar3D.exe. I suspect you will see the d3d9.dll being used is the one in C:\Windows\System32. But, perhaps not. :^)

Randy

[ssirhc]

According the Resource Monitor, the sim uses the .dll from the main sim installation folder.

[RRVyper]

Thanks for the update. So, if I'm following correctly, you now have the latest version of d3d9.dll in both folders. You should be able to remove the one in the P3D folder.

Randy

[ssirhc]

If I remove the file from the main installation folder, the sim doesn't start. But if I place it again there, it runs like a charm. A littlebit strange... And sorry, yes I have the file in the ../system32 folder too, of course, in the folder of the sim is its copied one.

[RRVyper]

That is certainly strange. I assume you are running P3D as Administrator. Have you tried running the DxDiag tool to see if any problems were found (save then view the text file)? Also, have you tried updating your graphics drivers? Other than that, perhaps running the System File Checker to check/repair system files.

Or, you can just skip it all, since you found a workaround. :^)

Randy

[ssirhc]

Thank you for your reply Randy. My DxDiag says: no problems found. My graphics driver always up to date, my Geforce Expereince updates the drivers every time, if it releases. If I run a System File Checker, it says at the end: Windows Resource Protection did not find any integrity violations. Sooo.... I don't know. But I can use the sim on my way, so.... LOL.

[ssirhc]

Probably a windows reinstall can solve this issue, but it is not so important, I have a two years old son, so my time is very poor. I can use my sim. :-) Thank you Randy, Best Regards: Chris

[RRVyper]

Understood, Chris. I agree with your assessment on the reinstall. All the best.

Randy

[maxam]

Thank you Randy! I cannot remember the last time I had a CTD with Prepar3D. I removed KB4515384 as per your earlier post and the issue is resolved. Thanks for the help.

Regards,
Robert