Jump to content

Adam_WMids_UK

Verified Members
  • Content Count

    13
  • Joined

  • Last visited

Community Reputation

1 Neutral

About Adam_WMids_UK

  • Rank
    Member

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

125 profile views
  1. Hi Naruto-kun I can confirm that my P3D is set to run as administrator. I started it this time with right click > Run as administrator, just to be doubly sure. I also inspected the file properties you mentioned. There was indeed an 'Unblock' tick box. However, even after I ticked this and it disappeared, I found the sim still crashed in the same way as previous. Aircraft worked fine until the WX Radar Power is clicked and then the sound stops a second or less before the sim stops responding and then within a further second, CTDs. This time however, as well as the error event, there were TWO information events associated with the crash as opposed to the usual ONE. I have again posted the latest error event along with BOTH the information events below (please let me know if these are not helpful and I'll stop posting them!): Faulting application name: Prepar3D.exe, version: 4.5.12.30293, time stamp: 0x5cd47aad Faulting module name: ntdll.dll, version: 10.0.18362.267, time stamp: 0xc00f8a30 Exception code: 0xc0000374 Fault offset: 0x00000000000f9269 Faulting process ID: 0x1ea4 Faulting application start time: 0x01d551fb4770df9a Faulting application path: F:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report ID: 030448f9-05d3-4e20-a0a4-18c1b253bf87 Faulting package full name: Faulting package-relative application ID: And the first associated information event: Fault bucket 1923782830446885784, type 5 Event Name: FaultTolerantHeap Response: Not available Cab Id: 0 Problem signature: P1: Prepar3D.exe P2: 4.5.12.30293 P3: 5CD47AAD P4: ffffbaad P5: P6: P7: P8: P9: P10: Attached files: \\?\C:\WINDOWS\SERVIC~1\LOCALS~1\AppData\Local\Temp\FTHDCDF.tmp\fthempty.txt \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDCEF.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDD00.tmp.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDCFE.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDD1E.tmp.txt These files may be available here: Analysis symbol: Rechecking for solution: 0 Report Id: e881157c-3692-4b14-83d0-f6697b6d8faf Report Status: 268435456 Hashed bucket: aaf1955bc3c969dfdab2a64aa9c83b98 Cab Guid: 0 And the second associated information event: Fault bucket 2112560671202190167, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: Prepar3D.exe P2: 4.5.12.30293 P3: 5cd47aad P4: StackHash_3b9c P5: 10.0.18362.267 P6: c00f8a30 P7: c0000374 P8: PCH_4D_FROM_ntdll+0x000000000009CBB4 P9: P10: Attached files: \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDEC3.tmp.dmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE1E1.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE1F2.tmp.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE1F2.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE212.tmp.txt These files may be available here: \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Prepar3D.exe_f62a59d7f59c257efddc3da15be1d0d6e079c6_1d3b734a_736a2792-e7f0-43aa-a795-adedec5127fb Analysis symbol: Rechecking for solution: 0 Report Id: 030448f9-05d3-4e20-a0a4-18c1b253bf87 Report Status: 268435456 Hashed bucket: 2f0fed2227d46b6f1d5152bcd577a357 Cab Guid: 0 Regards Adam
  2. Hi Naruto-kun I did exactly as you suggested in the PM. There was no change as far as I could see. The same crash occurred as soon as the WX Radar was powered in the MD88. Immediate CTD. Aircraft runs fine until that point. Also I noted that the file and product versions were identical between the file you sent and the version I already had in the Modules folder (but just to be clear, I still deleted the old file and pasted the one you sent there). But may have been the same file anyway? The resulting Error Event is pasted below: Faulting application name: Prepar3D.exe, version: 4.5.12.30293, time stamp: 0x5cd47aad Faulting module name: ntdll.dll, version: 10.0.18362.267, time stamp: 0xc00f8a30 Exception code: 0xc0000374 Fault offset: 0x00000000000f9269 Faulting process ID: 0x4d7c Faulting application start time: 0x01d551cedfa2dc89 Faulting application path: F:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report ID: 6701bb9b-74da-4d62-896f-5016643261d6 Faulting package full name: Faulting package-relative application ID: and associated Information Event: Fault bucket 2000263954575569057, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: Prepar3D.exe P2: 4.5.12.30293 P3: 5cd47aad P4: StackHash_737d P5: 10.0.18362.267 P6: c00f8a30 P7: c0000374 P8: PCH_4D_FROM_ntdll+0x000000000009CBB4 P9: P10: Attached files: \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER44A7.tmp.dmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4803.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4814.tmp.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4812.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4832.tmp.txt These files may be available here: \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Prepar3D.exe_7ad15cfec859166cf7fefa1eebec252a6d8f53ce_1d3b734a_9e4ae3ee-bbb7-42ce-8f91-43e2d40a3a71 Analysis symbol: Rechecking for solution: 0 Report Id: 6701bb9b-74da-4d62-896f-5016643261d6 Report Status: 268435456 Hashed bucket: 414bb716fec6f22abbc25d78057eb0a1 Cab Guid: 0 Regards Adam
  3. Hi Naruto-kun I'm away from my PC for an hour or so now. I'll respond to your PM once I'm back. Cheers Adam
  4. Hi Naruto-kun There are two version numbers displayed (file version and product version) but BOTH are the same number which is: 4.5.12.30293 Kind regards Adam
  5. Morning! Just generated a new one for you. Text is as follows for the Error Event: Faulting application name: Prepar3D.exe, version: 4.5.12.30293, time stamp: 0x5cd47aad Faulting module name: ntdll.dll, version: 10.0.18362.267, time stamp: 0xc00f8a30 Exception code: 0xc0000374 Fault offset: 0x00000000000f9269 Faulting process ID: 0x5370 Faulting application start time: 0x01d54dda77b1b63c Faulting application path: F:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report ID: def6c37e-9279-4c60-8ae2-08af1d6bd068 Faulting package full name: Faulting package-relative application ID: There is also an associated Information event generated three seconds afterwards: Fault bucket 2000263954575569057, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: Prepar3D.exe P2: 4.5.12.30293 P3: 5cd47aad P4: StackHash_737d P5: 10.0.18362.267 P6: c00f8a30 P7: c0000374 P8: PCH_64_FROM_ntdll+0x000000000009CBB4 P9: P10: Attached files: \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5127.tmp.dmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5464.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5484.tmp.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5482.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER54A3.tmp.txt These files may be available here: \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Prepar3D.exe_a3f32366d3b72153526ea019b06779a7b753d0a9_1d3b734a_8d6c8815-d5af-4cc3-8486-7b3e202d7352 Analysis symbol: Rechecking for solution: 0 Report Id: def6c37e-9279-4c60-8ae2-08af1d6bd068 Report Status: 268435456 Hashed bucket: 414bb716fec6f22abbc25d78057eb0a1 Cab Guid: 0 NOTE: of the files referred to above, only one actually exists (the one in program data), and I have attached that to this reply. Regards Adam Report.wer
  6. Hi there Please find attached my gauge installer log file. However, please also be aware that the Maddog X SHIPS with the option to use WX Radar through its inbuilt systems, so I haven't used the "WX Advantage Radar - Gauge Management Tool" to install the gauge. My system specs are as follows: EVGA Geforce GTX 1080Ti - 11GB DDR5 32GB DDR4 RAM Intel Core i9 7900X CPU (Skylake Architecture) Windows 10 Pro 64bit (Version 1903, Build 18362.267) P3D v4.5HF1 (Client version 4.5.12.30293) Antivirus - McAfee - But this is always disabled, along with the firewall when I am using P3D. Thanks Adam gauge_installer_log.txt
  7. Hi On July 12th somebody posted a very similar issue as I am experiencing. However, the topic is locked and being dealt with via email. No update has been added to the post. I wondered if any solution has been found? I haven't tried other aircraft such as the 717 or Das8 which use the WX Advantage Radar since I noticed this issue. I'm running the latest P3Dv4.5 build and my REX software is up to date. I run AS and REX Env Force alongside my sim for weather generation and depiction. The Maddog X loads and works fine until I power the WX Radar, then repeatable CTD. There is an option to use the AS weather radar or REX/Milviz radar in the Maddog... switching to the AS radar fixes the issue. Regards Adam
  8. Issue resolved: http://www.majesticsoftware.com/forums/discussion/457/ctd-with-wx-radar-REX-environment-force-axtive-sky-asp4#latest Odd, since I didn't get the crash when using ASP4 with the Q400 previously until I started using REX EF... however, this tweak DOES fix my issue. Regards Adam
  9. Hello All I have found that running Active Sky (ASP4 version) and Environment Force on P3Dv4.5(HF1) results in a CDT in the Majestic Dash 8 when the WX Radar mode is turned from Test to On. If the WX Radar is left turned off or standby or even test, there is no issue. Within a half second of turning it on, a CTD occurs. The issue is present in all locations, weather conditions and times I have tried it so far. The issue is repeatable and persistent. It stops happening when EF is disabled with ASP4 active OR if EF is active with ASP4 disabled. It is the combination of the two being active which seems to cause the issue. Regards Adam
  10. Apologies. Possibly I wasn't clear in my explanation. What I meant was that I understand that SF selects cloud models and 'pipes' them into the sim when the SF app is running and connected to the sim. When the SF app wasn't running nothing would be injecting the models into the sim. Hence my follow up question as to whether EF provides this functionality, meaning SF does not need to be running for the 3D models to be used. Thanks for everybody's input and further explanation. That more than answers my original question. Cheers Adam
  11. Thanks for the reply. One of the features I used from SF was the dynamic generation of 3D cloud models. Obviously when it is not running, it can't be doing this. Therefore, from your reply, am I correct in understanding that EF does generate its own 3D cloud models influenced by weather conditions (when in auto mode)? Thanks in advance for further clarication on this. Adam
  12. Hello All I notice a number of similar questions relating to the use of EF and SF - as a suggestion, might it be worth clarifying the use of these two together in the manual? Possibly with further recommendations for using with ActiveSky (since most simmers use this for weather)? My specific question relates to using SF for the 3D Cloud Models dynamically... If I wish to have REX software provide 3D Cloud Models (as opposed to ASCA for example), should I use SF with EF? Or does EF duplicate this functionality and therefore this would cause a conflict? (I use AS so have the weather engine in SF turned off). Thanks Adam
×
×
  • Create New...