Jump to content

CTD after working perfectly for ages


cooperwarner8
 Share

Recommended Posts

Hi guys

 

I have been using V5 pretty much non stop. I got a few "device hung" errors a few weeks ago but no issues since runnings some tips i found.

 

Now using the PMDG 747 it seems to crash upon switchings viewsm (chaseplane) with the device hung error. Would anyone know why this would be doing this all of a sudden when no software, hardware or settings have changed?

 

This is right at the start of my flight in a default airport and VRAM usage on my RTX2080ti 11GB card is very low

 

My specs are in my signature

 

I went into event viewer and found these two items but not sure what they mean or the cause.

 

Faulting application name: Prepar3D.exe, version: 5.0.24.34874, time stamp: 0x5eab3677

Faulting module name: VCRUNTIME140.dll, version: 14.25.28508.3, time stamp: 0x5e155520

Exception code: 0xc0000005

Fault offset: 0x000000000000137b

Faulting process id: 0xa40

Faulting application start time: 0x01d63fd3686494de

Faulting application path: D:\Lockheed Martin\Prepar3D v5\Prepar3D.exe

Faulting module path: C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll

Report Id: 589ba620-b80d-4492-8a5e-7f4b166a8bba

Faulting package full name:

Faulting package-relative application ID:

 

 

 

The program Prepar3D.exe version 5.0.24.34874 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.

Process ID: 3934

Start Time: 01d63fd218c31b37

Termination Time: 4294967295

Application Path: D:\Lockheed Martin\Prepar3D v5\Prepar3D.exe

Report Id: 75f8563e-f0b8-4416-9710-d031edc3f686

Faulting package full name:

Faulting package-relative application ID:

Hang type: Top level window is idle

AMD Ryzen 3800X 3.9 GHz

GeForce RTX 2080 Ti Windforce 11GB

32GB 3200MHz RAM

1TB Crucial SSD

Link to comment
Share on other sites

Hi guys

 

I have been using V5 pretty much non stop. I got a few "device hung" errors a few weeks ago but no issues since runnings some tips i found.

 

Now using the PMDG 747 it seems to crash upon switchings viewsm (chaseplane) with the device hung error. Would anyone know why this would be doing this all of a sudden when no software, hardware or settings have changed?

 

This is right at the start of my flight in a default airport and VRAM usage on my RTX2080ti 11GB card is very low

 

My specs are in my signature

 

I went into event viewer and found these two items but not sure what they mean or the cause.

 

Faulting application name: Prepar3D.exe, version: 5.0.24.34874, time stamp: 0x5eab3677

Faulting module name: VCRUNTIME140.dll, version: 14.25.28508.3, time stamp: 0x5e155520

Exception code: 0xc0000005

Fault offset: 0x000000000000137b

Faulting process id: 0xa40

Faulting application start time: 0x01d63fd3686494de

Faulting application path: D:\Lockheed Martin\Prepar3D v5\Prepar3D.exe

Faulting module path: C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll

Report Id: 589ba620-b80d-4492-8a5e-7f4b166a8bba

Faulting package full name:

Faulting package-relative application ID:

 

 

 

The program Prepar3D.exe version 5.0.24.34874 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.

Process ID: 3934

Start Time: 01d63fd218c31b37

Termination Time: 4294967295

Application Path: D:\Lockheed Martin\Prepar3D v5\Prepar3D.exe

Report Id: 75f8563e-f0b8-4416-9710-d031edc3f686

Faulting package full name:

Faulting package-relative application ID:

Hang type: Top level window is idle

 

Vcruntime140 Dll errors are most commonly caused by corrupted or missing dynamic-link library (DLL) files.

Errors related to it usually occur when a program mishandles the file during use.

Rebuild the Prepar3d cfg fle.

Link to comment
Share on other sites

The PMDG 747 is known to have issues in v. 5, many threads in the Lockheed-Martin forums deal with that.

 

For the VCRuntime errors you could install whatever you can find about Visual C and C++ at Microsoft (get both the x86 and the x64 versions), then run Windows Update and make sure that under Advanced options the switch "Receive updates for other Microsoft products" is set to On.

 

Jorgen

Link to comment
Share on other sites

Vcruntime140 Dll errors are most commonly caused by corrupted or missing dynamic-link library (DLL) files.

 

No, they're most commonly caaused by passing bad pointers to the functions within that library. And you will never get a 0xc0000005 error (access denied) from a missing DLL; it's a bad pointer referencing a memory area the process isn't allowed to read to/write from.

 

Luke

Link to comment
Share on other sites

 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...