BSOD

[petemack]

after flying for over an hour with everything going well the sim 'hung' briefly started again then crashed out. the event file showed this.
EventData

Prepar3D.exe
4.5.14.34698
5e94b5c2
terrain.dll
4.5.14.34698
5e94b52d
c000041d
00000000000e0341
854
01d74671ceb3da84
C:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe
C:\Program Files\Lockheed Martin\Prepar3D v4\terrain.dll
f0bae850-a428-4e23-b3dd-cfa56ca33d1c
any ideas?

[Martyson]

@ petemack ,

Search the forum for terrain.dll
The search function in P3D is here (or you can also use your favorite Internet search engine):



Do the General Debugging Steps :

viewtopic.php?f=6312&t=123246

[JorgenSA]

Petemack,

This is a so-called "Unhandled exception error" - a Windows error, so forget about the debugging steps.

Instead, get every download you can for C++ and .NET Framework from Microsoft, and get both the x86 and x64 versions of all the downloads.

Install them all, then run Windows Update, and make sure in Update, under Advanced options, to set the switch "Receive updates for other Microsoft products" is set to On. Leave this switch set to On in the future.

You may need to run the update a couple of times to make sure you have all updates.

Jorgen

[Martyson]

@ petemack ,

You do not have to worry about decoding or searching any vague WIN10 exception codes / errors.
Anybody can search the internet for those errors or ask on the WIN10 support forum.
After all the searching you end up right back here on the forum.


Just search the forum as I mentioned (terrain.dll ) then do the General Debugging steps.
Which BTY also mentions updating your system:

From the debugging steps:
1) Update Prepar3D to the newest available version. Support will not be provided for legacy versions.

2) Fully update your system.
This should include running Windows Update and updating any drivers to the newest version.
It is critical that the newest graphics card drivers are installed on your system.

3) Restart your system.

Then continue with the next steps.

[JorgenSA]

"vague WIN10 exception codes / errors"

Those codes are absolutes, nothing vague about them.

Try to troubleshoot root cause for a change.

Jorgen

[Martyson]

"vague WIN10 exception codes / errors"

Those codes are absolutes, nothing vague about them.

Try to troubleshoot root cause for a change.

Jorgen

Try using the Debugging steps after you look up the WIN10 code and it tells you nothing useful ... it tells something is wrong but the cause it not known. That is what is known before searching the vague code info.... or just call Windows Support.

[JorgenSA]

With such a disdainful attitude towards Windows error codes you are hardly qualified to comment on them, or on their relevance to root cause troubleshooting.

Jorgen

[Martyson]

@ petemack ,

I assume searching the forum or doing the P3D debugging Steps solved you problem, correct?