Alberto Zanot

P3D v4.3 Crash Analysis and final result

Recommended Posts

During last six months (yes, SIX months) i've been troubleshooting P3D v4.3 because of crashes happening suddenly and not expected.
Test flights done: 623 tests
What happens: after a period range of 45 to 90 minutes, P3D crash to desktop, 95% with no event log, 5% with some DLL failures, but they are not the point (keep on reading).
Scenarios i tested: 
P3D v4.3 fresh install + every in-game settings combinations
P3D v4.2 fresh install + every in-game settings combinations
P3D v4.1 fresh install + every in-game settings combinations
Each of these versions tried with every Nvidia drivers version, from newest 416.34 back to 382.05
Every suggestion in the CTD guide
Every basic and advanced common troubleshooting (i am also a P3D addon developer so i can say i know quite good what i am doing)

As told, sometimes, very rarely, event log come out with some dll faults but considering that i tried every possible scenarios this cannot be taken in consideration (i.e. some NVidia driver versions are known to be not 100% compatible with P3D, and some other well-known situations)

But there is a constant fact in every of the 623 tests i made:

Just one or two seconds before the crash, event log shows this:

Event 916, ESENT
DllHost
(or svchost sometimes) ( "some numbers and letters" ) The beta feature EseDiskFlushConsistency is enabled in ESENT due to the beta site mode settings 0x800000.

So the answer is only one: six months ago my Windows updated, introducing this BETA (...beta... no comment) feature (EseDiskFlushConsistency), and on my system this is causing these crashes.

Since there is no way to disable this beta feature (and reinstalling windows is not an option because this feature will be there again), i am very sad to say that i will give up on playing Prepar3D, once and for all.
Have a nice flight, if you can.

Share this post


Link to post
Help AVSIM continue to serve you!
Please donate today!

You should post this in the windows support forum instead of here and in the P3D one .

 

Jorge

Share this post


Link to post

That is interesting...and taken under advisement.   I can't help but wonder if you have a hardware issue though.  If it were P3D itself, why wouldn't this cause widespread crashes with all sorts of P3D users?

Share this post


Link to post

Might sound great,

but have you tried unplugging then plugging your graphics card?

Edited by arwasairl

Share this post


Link to post

@aeronauta I take this as a very nice joke 😄 😄 😄

@Mace i really have no idea. but you know, there are infinite hardware configs... bytheway i've heard of P3D users fighting with ESENT errors.

@arwasairl O_O Really?!?! I will try this! could you motivate your suggestion? thanks

 

Share this post


Link to post
3 minutes ago, Alberto Zanot said:

could you motivate your suggestion?

Oh yeah, it's done

Share this post


Link to post
Just now, arwasairl said:

Oh yeah, it's done

You mean? (sorry, my english is poor)

Share this post


Link to post
2 hours ago, arwasairl said:

Might sound great,

I motivated my suggestion 

Share this post


Link to post

This error is related to Windows and not P3D, do a quick google search and you will see for your self, your disk setup in MBR or GPT? what is your boot setup is well.

Share this post


Link to post

I will suggest this (it worked for me) if you didn't already do;

disable XMP (use auto mode) to control your memory in system BIOS.

Edited by penta_a

Share this post


Link to post

I highly doubt this error has anything to do with P3D as it also appears when P3D is not running. Just google for EseDiskFlushConsistency.

Too sad, but our flightsim is just unstable and will it ever be. My sim also crashes from time to time, usually on every second flight without any chance to determine the cause...

Share this post


Link to post

@ade555 yes infact it is windows related. I think disk is MBR. Boot setup, what do yo mean?

@penta_a Yes, i tried with XMP profile and without. Same result.

@fly_edds Yes, events 916 have nothing to do with P3D, but they make it crash :) They are not caused by P3D, they are caused by Windows, making P3D crash.

Share this post


Link to post
3 minutes ago, Alberto Zanot said:

@ade555 yes infact it is windows related. I think disk is MBR. Boot setup, what do yo mean?

@penta_a Yes, i tried with XMP profile and without. Same result.

@fly_edds Yes, events 916 have nothing to do with P3D, but they make it crash :) They are not caused by P3D, they are caused by Windows, making P3D crash.

I'm sure I read somewhere that mbr disk partition have effect on this fault, do you use uefi boot or legacy on your system? 

Share this post


Link to post
4 minutes ago, ade555 said:

I'm sure I read somewhere that mbr disk partition have effect on this fault, do you use uefi boot or legacy on your system? 

I can tell you UEFI for sure.

How can i check if disks are MBR or GPT? Are those "inter-changeable"?

Thanks for your help!!

Share this post


Link to post

Need to open disk utility tool in Windows or have a quick Google read, I am at work at the moment so is hard to post back right now. 

https://social.technet.microsoft.com/Forums/en-US/9054b832-d001-4543-b3b0-bcbb729d5f24/esediskflushconsistency-win10-1709?forum=win10itprogeneral

 

 

Have a read 2nd to last post, I would suggest if you have been struggling for 6 months I would just wipe the windows disk and do complete fresh install. 

Edited by ade555

Share this post


Link to post

😄 i know that thread, as you can see last post is mine (tonaz)

At least i am not alone.

i just have to hope for MS to fix this problem. (never going to happen 😄 )

Share this post


Link to post
6 minutes ago, Alberto Zanot said:

😄 i know that thread, as you can see last post is mine (tonaz)

At least i am not alone.

i just have to hope for MS to fix this problem. (never going to happen 😄 )

Well from what I can read and I never experienced this problem my self you just format HDD do clean install job done instead of waiting and hoping that MS will sort some sort of update beta bug, 

Share this post


Link to post

well, a reinstall is not an option, that beta bugged feature would be there anyways, would you agree?

Share this post


Link to post

I think you may be chasing the wrong error message. Very possibly this comes up anyway at some time whatever the apps running. When P3D crashes, this probably just invokes that message. If you could try crashing P3D on purpose that message would probably come up as a result.

I'm not certain I have enough to go on in the description of the setup of Windows and P3D. I would like to know if that's a stock install of Win10 and P3D - is it certain that P3D is stock? If it's not picking up some old stuff, addon dll or scenery files, whatever, then it's worth trying out a few replacement parts - for example: Swap out the memory or GPU for some tests.

Share this post


Link to post

Hello @SteveW !!

No, unfortunately i have to disagree: EVENT 916 comes up, and P3D crashes after one or two seconds. Not the opposite, never.

In my 600+ test flights i also included a P3D stock install (and every combinations with it), i swapped the memory slots, i swapped the PCI 3.0 slot for the GPU (my mobo got 2 PCI3.0).

The only thing i didn't did is trying on a Windows 10 fresh install. Because to be honest, it is not a valid and sensful option, i mean, Windows 10 get updated anyways to latest version, with latest "features", including beta faulty stuff 🙂 so why reinstall?

Edited by Alberto Zanot

Share this post


Link to post
50 minutes ago, Alberto Zanot said:

well, a reinstall is not an option, that beta bugged feature would be there anyways, would you agree?

Well I would say if you do fresh install and make sure is above ver 1709 you should be good. New update don't necessarily mean that the bug will be unistalled or anything, I can tell you 1 thing you chasing this error now 6 months and everything you done till now hasn't solved it. 

 

Download Windows creator toll let's do its magic save as ISO, download ruffus make bootable USB with uefi and just run new install job done, is not hard, 

Share this post


Link to post

Open your disk utility tool and let's have a look how your hdd's are configured, 

Share this post


Link to post
1 hour ago, Alberto Zanot said:

Hello @SteveW !!

No, unfortunately i have to disagree: EVENT 916 comes up, and P3D crashes after one or two seconds. Not the opposite, never.

In my 600+ test flights i also included a P3D stock install (and every combinations with it), i swapped the memory slots, i swapped the PCI 3.0 slot for the GPU (my mobo got 2 PCI3.0).

The only thing i didn't did is trying on a Windows 10 fresh install. Because to be honest, it is not a valid and sensful option, i mean, Windows 10 get updated anyways to latest version, with latest "features", including beta faulty stuff 🙂 so why reinstall?

Hi Alberto! 😊

It still could possibly be part of the message chain when P3D crashes so it may well come up before your P3D has crashed message in the log as it may be part of making the logs.

 

Edited by SteveW

Share this post


Link to post
On 11/3/2018 at 5:00 PM, Alberto Zanot said:

Test flights done: 623 tests

This is a Windows10 issue that P3DV4 triggers.  When I have Windows 10 issues I cannot resolve by searching the Internet for a solution, I reinstall Windows, P3DV4.3, and all of my add-ons.  If one is waiting for Microsoft techs to find a solution to this issue or one of the thousands of MVP techs who frequent the Internet with "solutions", you will have to wait a long time as it is rare when they are able to correctly diagnose anything.  There are just too many computer and Windows configurations.  I did a search for "The beta feature EseDiskFlushConsistency is enabled in ESENT due to the beta site mode settings 0x800000" and there are solutions that worked for many but none I found were the same fix.  One had two anti-virus programs running at the same time and he uninstalled one of them and the problem went away.  The crash scenarios for those reporting this error to Microsoft was not always the same and I did not find others getting this error running P3D.  Some were running other games and some just other software when the error occurred.  Since this appears to be a Windows 10 update related error, I would simply reinstall Windows 10 and move on with your life.  I did this several times a month or two ago when I rebuilt my current system.  I was getting a different error msg after every crash of P3DV4.3.  Sometimes P3D did not crash.  Sometimes P3D crashed two hours out in the flight.  Sometimes soon after loading P3D and during the process of setting up a flight.  Some were BSOD's.  Some were just CTD's.  I followed every suggestion in the AVSIM CTD Guide without success.  I finally found that one memory module out of 4 installed was not working properly.  I have not seen any additional problems since removing this bad module and currently have my system overclocked to 5.0GHz.

I have checked my Event Viewer and see I only received one ESENT error with Event 455.  I have the latest version of Windows 10 installed (V1809, OS Build 17763.55) installed on 4 October.

On 11/3/2018 at 5:00 PM, Alberto Zanot said:

(and reinstalling windows is not an option because this feature will be there again)

You are wrong about this.  There are thousands, including me, who have the latest version of Windows 10 and are not getting this error.  Something happened during an update.  You will never know exactly what.  It is your only option to fix this issue as no one should be working six months trying to find a solution to an error.  You will go insane and conduct over 600 test flights....and still have no solution.

Share this post


Link to post

@Jim,

    I am directing this question / comment to you about the steps we should take BEFORE  we do a windows 10 reinstall. Maybe this info - after suitable editing by several of us - should be pinned for this forum title. I just had to reinstall Windows 10 and erroneously thought that my scenario files would be left alone but I was wrong - anything that has to do with the "Documents" folders was erased. I would suggest that as much as possible of the control files be backed up. Here is a list for me:

Scenarios  - "C:\Users\USERNAME\OneDrive\Documents\Prepar3D v4 Files

CFG files - "C:\Users\USERNAME\AppData\Roaming\Lockheed Martin\Prepar3D v4"   (Only some of these files will be needed or used for reference )

Scenery.cfg and more - "C:\ProgramData\Lockheed Martin\Prepar3D v4"    (Only some of these files will be needed or used for reference )

 

I also recommend each user developing a reinstall_apps folder with each application of interest setup.exe or xxx.msi type files plus website URLs - example for me, Anti-virus, DCS, GIMP, Irfanview, Java, Notepad++, OCCT, Oculus, Prepar3d_Aircraft_Scenery, Printer, Steam, Joystick, USB, Video Card, VisualStudio, WinRAR, etc..

Then reinstall Prepar3D (you won't be able to uninstall Prepar3D if you had to reinstall Windows 10 because you couldn't repair it )

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now