Visit Captain Sim web site  
  Welcome, Guest. Please Login or Register

 

Page Index Toggle Pages: 1 2 3 [4]  Send TopicPrint
 25 CTD (crash to desktop) (Read 3995 times)
Jim Kaye
Full Member
*
Offline



Posts: 113
Location: Richland, WA
Joined: Aug 20th, 2014
Gender: Male
Re: CTD (crash to desktop)
Reply #45 - May 5th, 2018 at 3:49am
Print Post  
Recently purchased the 757 for P3D, and installed on my new computer system.

Specs - i7 8700K, 16 GB, NVIDIA GeForce GTX 1080Ti, 11 GB.  P3Dv4.2 on 500 GB SSD.  Active Sky 2018 and Plan-G running when CTD occurred.

Attempting flight from KSEA RWY34R to KSFO.  Experienced CTD before reaching BTG waypoint.  Event viewer as follows:

Faulting application name: Prepar3D.exe, version: 4.2.21.24048, time stamp: 0x5a7c832c
Faulting module name: ntdll.dll, version: 10.0.16299.248, time stamp: 0xeffc9126
Exception code: 0xc0000374
Fault offset: 0x00000000000f87bb
Faulting process id: 0x21c4
Faulting application start time: 0x01d3e41389bd7d3d
Faulting application path: C:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 5b1db8ed-d6bf-4fb0-8977-1f9c0ea33d04
Faulting package full name:
Faulting package-relative application ID

Have had several CTD's with the Captain Sim 757, all but one the faulting module was ntdll.dll.  Downloaded latest drovers from, NVIDIA, (24.21.13.9731), did not fix.  Set up FSUIPC so can save the flight every 10 minutes and reload, but need to reboot before doing this.  Always start with a default flight (Beech Baron at KPSC).

The 757 was flying normally at FL250, don't remember specifically what I was doing when it crashed.  Sad Sad
  


Back to top
 
IP Logged
 
Jim Kaye
Full Member
*
Offline



Posts: 113
Location: Richland, WA
Joined: Aug 20th, 2014
Gender: Male
Re: CTD (crash to desktop)
Reply #46 - May 5th, 2018 at 3:55am
Print Post  
Forgot to mention that I am also running UTLive.  Flight plan was KSEA, TCM, BTG, LWG, RBG, MOG, RDD, UK, SGD, OAK, KSFO.
  


Back to top
 
IP Logged
 
Jim Kaye
Full Member
*
Offline



Posts: 113
Location: Richland, WA
Joined: Aug 20th, 2014
Gender: Male
Re: CTD (crash to desktop)
Reply #47 - May 6th, 2018 at 12:15am
Print Post  
Same flight as above, which I had saved and loaded.  CTD 7.36 nm from LWG.

Event viewer:
Faulting application name: Prepar3D.exe, version: 4.2.21.24048, time stamp: 0x5a7c832c
Faulting module name: DSOUND.dll, version: 10.0.16299.15, time stamp: 0x2ccf947e
Exception code: 0xc0000005
Fault offset: 0x000000000003a76d
Faulting process id: 0x2880
Faulting application start time: 0x01d3e4c1a8e8c343
Faulting application path: C:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe
Faulting module path: C:\Windows\SYSTEM32\DSOUND.dll
Report Id: 6d1d9131-e09c-46f4-9a6e-517624b9e935
Faulting package full name:
Faulting package-relative application ID:

Yesterday, re-started flight using flights saved by FSUIPC.  Did not have to reboot.  After loading default flight at KPSC, was able to load and resume flight on way to BTG.  Successfully flew beyond MOG, on way to RDD.  Saved flight, no CTD when I closed P3D last night.

FSUIPC allows me to resume a flight after a CTD, but takes about half an hour to get back to where I was when the failure occurred.   Huh Huh

  


Back to top
 
IP Logged
 
Jim Kaye
Full Member
*
Offline



Posts: 113
Location: Richland, WA
Joined: Aug 20th, 2014
Gender: Male
Re: CTD (crash to desktop)
Reply #48 - May 10th, 2018 at 12:07am
Print Post  
Have recently had several DSOUND.dll errors while flying the Captain Sim 757 from KSEA to KSFO.  Same flight plan as above.  Event viewer gives the following:

Faulting application name: Prepar3D.exe, version: 4.2.21.24048, time stamp: 0x5a7c832c
Faulting module name: DSOUND.dll, version: 10.0.16299.15, time stamp: 0x2ccf947e
Exception code: 0xc0000005
Fault offset: 0x000000000003b4ad
Faulting process id: 0x1db8
Faulting application start time: 0x01d3e7d1bae9e1ce
Faulting application path: C:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe
Faulting module path: C:\Windows\SYSTEM32\DSOUND.dll
Report Id: 23d3b3d4-d00f-4fc6-a782-bdfc94cbf7e8
Faulting package full name:
Faulting package-relative application ID:

In the latest flight I was about 50 nm from BTG.  Will now try flying the same flight plan with an aircraft that is not from Captain Sim.   Sad Sad
  


Back to top
 
IP Logged
 
Jim Kaye
Full Member
*
Offline



Posts: 113
Location: Richland, WA
Joined: Aug 20th, 2014
Gender: Male
Re: CTD (crash to desktop)
Reply #49 - May 11th, 2018 at 11:23pm
Print Post  
I have found that my crash to desktop errors are not limited to the Captain Sim 757.  Last night experienced the ntdll.dll CTD while flying the Carenado EMB505 Phenom 300 from KPSC to KSFO direct.  Also have had CTD errors flying the Majestic Q400, both ntdll.dll and DSOUND.dll.  I am reviewing the AVSIM CDT Guide for further guidance, and will post here if a solution is found.  Sad Sad
  


Back to top
 
IP Logged
 
Jim Kaye
Full Member
*
Offline



Posts: 113
Location: Richland, WA
Joined: Aug 20th, 2014
Gender: Male
Re: CTD (crash to desktop)
Reply #50 - May 12th, 2018 at 6:13am
Print Post  
Following the AVSIM CTD guide, renamed the file Prepar3D.cfg to Prepar3D.cfg.old.  Then started Prepar3dv4 which created a new .cfg file.  Loaded the previously saved 757 flight from KSEA to KSFO.  It worked!!!  Made it all the way with no CTD.  Also used Active Sky 2018 and Plan-G.  Very encouraging!   Smiley Smiley
  


Back to top
 
IP Logged
 
25dollarbills
New Member
Offline



Posts: 1
Joined: May 14th, 2018
Re: CTD (crash to desktop)
Reply #51 - May 14th, 2018 at 7:19am
Print Post  
Hi,
I've recently bought the 757 III for P3D v4
I'm using v4.2
Specs: i5 7600k, Nvidia GeForce GTX 1060 6GB; 16GB; Win10 Pro 64bit

I've made several flights, about 15. Very often the sim crashes without any notification from windows.
Here is the only error message I got:

Name der fehlerhaften Anwendung: Prepar3D.exe, Version: 4.2.21.24048, Zeitstempel: 0x5a7c832c
Name des fehlerhaften Moduls: ai_player.dll, Version: 4.2.21.24048, Zeitstempel: 0x5a7c832a
Ausnahmecode: 0xc0000005
Fehleroffset: 0x000000000004f169
ID des fehlerhaften Prozesses: 0x11a8
Startzeit der fehlerhaften Anwendung: 0x01d3ea2058b4b804
Pfad der fehlerhaften Anwendung: E:\P3D v4\Prepar3D.exe
Pfad des fehlerhaften Moduls: E:\P3D v4\ai_player.dll
Berichtskennung: d6bf7c0d-e0f1-4982-a116-0c44a3117290
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:

This flight was made on a Condor 757-200 from the ACE. The problem appeared only at cruise level or during descent, so I haven't been able to land, until today.

Here are some flights I made. The problem encountered at every single flight.

LEPA-LEIB
EDDF-EDDM
EDDF-EGLL

Since I don't get any message from Windows that P3D crashed, the crashes appeared unexpectedly. I'm using the version 1.0.0.2 (latest hotfix version). The stable version also didn't work (1.0.0.0), so I got the same problem.
I've already deleted the .cfg of P3D, which didn't work. Before each flight I load a default plane, and then I switch to cs757. Unforntunately, the problem only appears with the CS757.
  
Back to top
 
IP Logged
 
Jim Kaye
Full Member
*
Offline



Posts: 113
Location: Richland, WA
Joined: Aug 20th, 2014
Gender: Male
Re: CTD (crash to desktop)
Reply #52 - May 21st, 2018 at 12:48am
Print Post  
Twice again today had CTD with the CS 757.  At 5:34:41 PM the faulting module was ntdll.dll.  At 3:01:42 the faulting module was DSOUND.dll (event viewer).   Renamed Prepare3D.cfg to Prepare3D.cfg.bad and will see what happens.  Sad Sad
  


Back to top
 
IP Logged
 
Page Index Toggle Pages: 1 2 3 [4] 
Send TopicPrint
 
  « Board Index ‹ Board  ^Top