After a nice start with a clean install of P3D v2.1, the tides have turned. Tonight I had two CTDs of unknown origin. The only addon installed is ORBX FTX Global. I even had Windows tell me that it has applied compatibility settings to the program (Win 7 64 Pro) after the last CTD. Sadly I have to give up on P3D v2 for now. I'm too busy for more beta testing. I'm back to 1.4 for now.

 

 

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

Process ID: ffc

Start Time: 01cf2a845b37b34f

Termination Time: 76

Application Path: D:\Prepar3D v2\Prepar3D.exe

Report Id: f8faca84-9684-11e3-92df-c86000022084

 

 

Faulting application name: Prepar3D.exe, version: 2.1.9936.0, time stamp: 0x52f904b8

Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000

Exception code: 0xc000041d

Fault offset: 0x73fc4f0d

Faulting process id: 0x6ec

Faulting application start time: 0x01cf2a91ffc051c3

Faulting application path: D:\Prepar3D v2\Prepar3D.exe

Faulting module path: unknown

Report Id: 34e2b842-968a-11e3-92df-c86000022084

Did you tell LM about it?

No. The forum over there is an unmoderated mayhem, so I don't bother visiting anymore. P3D is currently the only way forward, but I'm taking a break from v2. I've got 3-4 hrs a week to spend on this hobby, so I will wait for 2.2 before I give it another go.

No. The forum over there is an unmoderated mayhem, so I don't bother visiting anymore. P3D is currently the only way forward, but I'm taking a break from v2. I've got 3-4 hrs a week to spend on this hobby, so I will wait for 2.2 before I give it another go.

 

Hey, this is a long shot, but Windows 7 64 bit had an update in October, can't remember which one, and it caused CTDs. It has since been rectified, but I had been encountering CTDs for the first time ever, believe it or not, following the installation of this update. After deleting the update the CTDs ceased. It may be worth investigaing. It was Jim (Firehawk44) on this forum that posted the info some time ago. Do give it a shot, 'cos it may be the culprit and not P3D at all.

Thanks Howard! Don't think it is it though. I was doing fine with 2.0 in terms of CTDs, and all my other software is working flawlessly, and have been for years.

Thanks Howard! Don't think it is it though. I was doing fine with 2.0 in terms of CTDs, and all my other software is working flawlessly, and have been for years.

 

Ah, sure, a long shot but worth mentioning. Cheers...