July 18, 201411 yr Anyone see this? I'm flying along (typically in an orbx area), switching between VC and external, and the sound stops working. A min or so after that I get a "P3D has stopped working" CTD | My Liveries | FAA ZMP | PPL ASEL | | Windows 11 | MSI Z690 Tomahawk | 12700K 4.7GHz | MSI RTX 4080 | 64GB 6000 MHz DDR5 | 500GB Samsung 860 Evo SSD | 2x 2TB Samsung 970 Evo M.2 | EVGA 850W Gold | Corsair 5000X | HP G2 (VR) / LG 27" 1440p |
July 19, 201411 yr Author This was the lionheart Mooney acclaim, but it has happened in others.... I'm wondering if it's a resources issue.... I was getting around 10-13 fps near Orbx NCA along with FB KSFO.... | My Liveries | FAA ZMP | PPL ASEL | | Windows 11 | MSI Z690 Tomahawk | 12700K 4.7GHz | MSI RTX 4080 | 64GB 6000 MHz DDR5 | 500GB Samsung 860 Evo SSD | 2x 2TB Samsung 970 Evo M.2 | EVGA 850W Gold | Corsair 5000X | HP G2 (VR) / LG 27" 1440p |
July 21, 201411 yr Author Bump! Only a few replies at the P3D forum- checking event viewer etc | My Liveries | FAA ZMP | PPL ASEL | | Windows 11 | MSI Z690 Tomahawk | 12700K 4.7GHz | MSI RTX 4080 | 64GB 6000 MHz DDR5 | 500GB Samsung 860 Evo SSD | 2x 2TB Samsung 970 Evo M.2 | EVGA 850W Gold | Corsair 5000X | HP G2 (VR) / LG 27" 1440p |
July 21, 201411 yr I had something similar happen the other day while checking out the new FTX Global Port Morseby strips in the Aerosoft Twin Otter Extended. Was concentrating on locating the strips and managed to blow up an engine. The sound failure happened less than a minute after the fire warning bell went off. No sound from the point where I turned off the fire alarm. The CTD happened about a minute after that. I'll have to check my event viewer logs, but if I recall correctly, the faulting module was ntdll.dll. If so, the issue might be similar to the old FSX one where the screen would freeze while the sound continued, and the program then crashed. It was always replicable in a given location. In those cases, on my system, the problem was the GPU - I was never sure whether it was lack of VRAM or lack of processing power, but I was able to cure it twice (not cheaply) in successive instances by upgrading the video card. I'm wondering if the problem here isn't a video resource issue, but I'll have to rely on more technically conversant friends to figure it out. Alan Ampolsk"Ah, Paula, they are firing at me!"-- Saint-Exupery
July 22, 201411 yr Author Certainly could be GPU because I haven't upgraded to the gtx770 4gb I was hoping to yet.Before I invest any more money into this sim this has to be solved... Hoping someone from LM could shed some light on it. Here's the details from event viewer.... two separate CTD messages I guess Faulting application name: Prepar3D.exe, version: 2.2.10438.0, time stamp: 0x53468776Faulting module name: ntdll.dll, version: 6.1.7601.18247, time stamp: 0x521ea8e7Exception code: 0xc0000374Fault offset: 0x000ce753Faulting process id: 0xfb0Faulting application start time: 0x01cfa2d558a914a0Faulting application path: A:\Prepar3D v2\Prepar3D.exeFaulting module path: C:\Windows\SysWOW64\ntdll.dllReport Id: e232402e-0ecc-11e4-82be-1c6f65c15b81 Last week I had a CTD but looks like it was a true appcrash: Problem Event Name: APPCRASHApplication Name: Prepar3D.exeApplication Version: 2.2.10437.0Application Timestamp: 533d6c08Fault Module Name: StackHash_41a0Fault Module Version: 6.1.7601.18247Fault Module Timestamp: 521ea8e7Exception Code: c0000374Exception Offset: 000ce753OS Version: 6.1.7601.2.1.0.256.48Locale ID: 1033Additional Information 1: 41a0Additional Information 2: 41a03d10e17fc88727f078b073a35f51Additional Information 3: 6cf4Additional Information 4: 6cf42da9027949e9ad18c02928765f60 | My Liveries | FAA ZMP | PPL ASEL | | Windows 11 | MSI Z690 Tomahawk | 12700K 4.7GHz | MSI RTX 4080 | 64GB 6000 MHz DDR5 | 500GB Samsung 860 Evo SSD | 2x 2TB Samsung 970 Evo M.2 | EVGA 850W Gold | Corsair 5000X | HP G2 (VR) / LG 27" 1440p |
Create an account or sign in to comment