January 27, 201511 yr Commercial Member The only difference between FSX and FSX:SE, is the default value used internally by FSX when there's no setting. In FSX, the default value is the same as the OS value, which is "use all cores", which translates into a 15 on a quad core system. There's no difference between FSX-MS and FSX-SE when the app starts and affinity is applied with no JOBSCHEDULER setting, which would enable all Logical Processors (LPs), which is the same as AffinityMask=0. However, remember that not all apps and functions regard zero as 2^LPs - 1 in these cases. Steve Waite: Engineer at codelegend.com
January 27, 201511 yr There are two reports on that thread which both point to the same offset in TERRAIN.DLL for the access violation which is occurring. The offset is 00059BE8. No one here has yet posted any details of the crash offset in TERRAIN.DLL, so I don't know if this is the main or only one. If it is a frequent one, then maybe I can implement a temporary workaround in FSUIPC as I did with he most prevalent G3D.DLL crash in FSX. I've had a brief look at the code and I think avoidance action might be feasible, though whatt the graphics results would then be I couldn't say. So, could all of you experiencing this crash please post the actual crash details -- the module offset is really all I need, and confirmation that the error code is C0000005 (= access violation). If I do manage to do anything I'll need a tester who can guarantee to get the crash happening in a reasonable timeframe. I haven't got the time nor patience to wait till something might or might not happen! ;-) [LATER] Okay. Any registered users who does get (or knows he can get) the Terrain crash at 00059BE8, please try an interim test version -- download link: FSUIPC4938gTEST2.zip. Read the "read me" inside. Let me know how you get on, please. Regards Pete Faulting application name: fsx.exe, version: 10.0.62608.0, time stamp: 0x54abe5b4 Faulting module name: g3d.dll, version: 10.0.62608.0, time stamp: 0x54abe5dd Exception code: 0xc0000005 Fault offset: 0x000cb57a Faulting process id: 0x1314 Faulting application start time: 0x01d038cfc320f6ad Faulting application path: E:\Steam\steamapps\common\FSX\fsx.exe Faulting module path: E:\Steam\steamapps\common\FSX\g3d.dll Report Id: ce5df510-a4e6-11e4-bd92-b8975a1871d1 Faulting application name: fsx.exe, version: 10.0.62608.0, time stamp: 0x54abe5b4 Faulting module name: terrain.dll, version: 10.0.62608.0, time stamp: 0x54abe5e1 Exception code: 0xc0000005 Fault offset: 0x00059be8 Faulting process id: 0x1314 Faulting application start time: 0x01d038cfc320f6ad Faulting application path: E:\Steam\steamapps\common\FSX\fsx.exe Faulting module path: E:\Steam\steamapps\common\FSX\terrain.dll Report Id: c76a3911-a4e6-11e4-bd92-b8975a1871d1 Faulting application name: fsx.exe, version: 10.0.62608.0, time stamp: 0x54abe5b4 Faulting module name: g3d.dll, version: 10.0.62608.0, time stamp: 0x54abe5dd Exception code: 0xc0000005 Fault offset: 0x000cb57a Faulting process id: 0x11d8 Faulting application start time: 0x01d033fece13171c Faulting application path: E:\Steam\steamapps\common\FSX\fsx.exe Faulting module path: E:\Steam\steamapps\common\FSX\g3d.dll Report Id: 3ffc22d6-a014-11e4-a8e4-b8975a1871d1 Faulting application name: fsx.exe, version: 10.0.62608.0, time stamp: 0x54abe5b4 Faulting module name: g3d.dll, version: 10.0.62608.0, time stamp: 0x54abe5dd Exception code: 0xc0000005 Fault offset: 0x000cb57a Faulting process id: 0xf24 Faulting application start time: 0x01d0327d6fd261f2 Faulting application path: E:\Steam\steamapps\common\FSX\fsx.exe Faulting module path: E:\Steam\steamapps\common\FSX\g3d.dll Report Id: c3b3db03-9e85-11e4-9898-b8975a1871d1 Faulting application name: fsx.exe, version: 10.0.62608.0, time stamp: 0x54abe5b4 Faulting module name: terrain.dll, version: 10.0.62608.0, time stamp: 0x54abe5e1 Exception code: 0xc0000005 Fault offset: 0x00059be8 Faulting process id: 0xf24 Faulting application start time: 0x01d0327d6fd261f2 Faulting application path: E:\Steam\steamapps\common\FSX\fsx.exe Faulting module path: E:\Steam\steamapps\common\FSX\terrain.dll Report Id: 3bdcead3-9e85-11e4-9898-b8975a1871d1 Faulting application name: fsx.exe, version: 10.0.62608.0, time stamp: 0x54abe5b4 Faulting module name: g3d.dll, version: 10.0.62608.0, time stamp: 0x54abe5dd Exception code: 0xc0000005 Fault offset: 0x000cb57a Faulting process id: 0xf0c Faulting application start time: 0x01d02f936c237d54 Faulting application path: E:\Steam\steamapps\common\FSX\fsx.exe Faulting module path: E:\Steam\steamapps\common\FSX\g3d.dll Report Id: 2aaf4d9e-9be2-11e4-aee5-b8975a1871d1 This is what I found with the newest DTG patch, Pete. I'll try your interim FSUIPIC when I get time later tonight. Daniel Moser
January 27, 201511 yr Commercial Member I noticed that also. That's why I noted in my first post that I "checked the integrity of the game cache" before my second round of testing. But you're correct unfortunately... Same error with a CTD after about an hour and ten minutes. The same offset, with 62608 instead of 62607? Was there any TERRAIN entry in the FSUIPC4.LOG? Pete Win10: 22H2 19045.2728 CPU: 9900KS at 5.5GHz Memory: 32Gb at 3800 MHz. GPU: RTX 24Gb Titan 2 x 2160p projectors at 25Hz onto 200 FOV curved screen
January 27, 201511 yr Commercial Member It was suggested otherwise in this thread: It appears that FSX-SE already sets the affinity mask automatically to 14 for a non-hyperthreded quad-core CPU. It is not necessary to set it specifically in FSX.cfg - doing so only duplicates what is already there. I must say I haven't verified this claim. In fact, it seems that according to DTG release notes notes, only the HIGHMEMFIX is applied in any case, even without the tweak being present. If this is the case, there's no difference when affinity is concerned between FSX and FSX:SE, and in BOTH cases, nothing will change unless the "Save" button is pressed in the Addon Manager and in both cases, 14 is probably a better value than 0, on a quad-core system. Umberto Colapicchioni http://www.fsdreamteam.com FSDT on Facebook
January 27, 201511 yr Commercial Member This is what I found with the newest DTG path, Pete. Al in G3D and all at a different location to the previous report, by "Spesimen". Doesn't bode well for any sort of useful patch. Pete Win10: 22H2 19045.2728 CPU: 9900KS at 5.5GHz Memory: 32Gb at 3800 MHz. GPU: RTX 24Gb Titan 2 x 2160p projectors at 25Hz onto 200 FOV curved screen
January 27, 201511 yr when i remove ftx england or use the default cessna instead of 777. (to see the crash take off in 777 from egll, runway 27L compton 3g departure, will blow up within a few nm away from the airport every time.. doesn't happen with FTX global, but does if you enable hybrid or eu region) Even you do not have ORBX ObjectFlow.dll enabled, ORBX region will still try to load custom objects etc. It's better to wait. I only use ORBX global and Vector at the moment and I have no crash whatsoever. I have not done 4-6 hr flight yet but I will this week-end to see if there is any issue. I have just installed the PMDG 777 SE edition as well, so I will use it for the long haul test. Vu Pham i7-13700K 5.2 GHz OC, 64 GB RAM, RTX5090, SSD for Sim, SSD for system. MSFS2020, XP-12, DCS
January 27, 201511 yr The same offset, with 62608 instead of 62607? Was there any TERRAIN entry in the FSUIPC4.LOG? Pete Sorry, I was just out plowing snow. The CTD info is the same. The log is displayed also: Fault bucket 73797962940, type 1 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: fsx.exe P2: 10.0.62608.0 P3: 54abe5b4 P4: terrain.dll P5: 10.0.62608.0 P6: 54abe5e1 P7: c0000005 P8: 0008fb86 P9: P10: Attached files: C:\Users\Ray\AppData\Local\Temp\WER9AA0.tmp.WERInternalMetadata.xml These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_fsx.exe_b83d3c90e1df2ebd1abb482d2a6c97f9d6d5df57_644ae146_1b1d2c1e Analysis symbol: Rechecking for solution: 0 Report Id: 5884d3ce-a5d5-11e4-8207-001fbc02953f Report Status: 0 Hashed bucket: 646327c53988578e88e5ba18e3dce20f ********* FSUIPC4, Version 4.938g by Pete Dowson ********* Reading options from "D:\Program Files (x86)\Steam\steamapps\common\FSX\Modules\FSUIPC4.ini" Running inside FSX Steam Edition on Windows 8 Module base=59C90000 User Name="Jay Bloomfield" User Addr="[email protected]" FSUIPC4 Key is provided WIDEFS7 not user registered, or expired 141 System time = 26/01/2015 22:14:34 141 FLT path = "C:\Users\Ray\Documents\Flight Simulator X - Steam Edition Files\" 188 NOTE: SimConnect Steam is supported, but it isn't installed. 235 Trying to connect to SimConnect Acc/SP2 Oct07 ... 281 FS path = "D:\Program Files (x86)\Steam\steamapps\common\FSX\" 906 LogOptions=00000000 00000001 906 SIM1 Frictions access gained 938 Wind smoothing fix is fully installed 938 TERRAIN.DLL fix attempt installed ok 938 SimConnect_Open succeeded: waiting to check version okay 938 Trying to use SimConnect Acc/SP2 Oct07 9235 Running in "Microsoft Flight Simulator X", Version: 10.0.62608.0 (SimConnect: 10.0.62608.0) 9235 Initialising SimConnect data requests now 9235 FSUIPC Menu entry added 9250 FLIGHTS\OTHER\FLTSIM.FLT 9250 simobjects\airplanes\Aircreation_582SL\Aircreation_582SL.AIR 81719 Weather Mode now = Custom 208985 Weather Mode now = Theme 208985 C:\Users\Ray\AppData\Roaming\Microsoft\FSX-SE\Previous flight.FLT 239281 Weather Mode now = Custom 247531 simobjects\airplanes\C172\Cessna172SP.AIR 366328 System time = 26/01/2015 22:20:40, Simulator time = 01:14:43 (06:14Z) 366344 Aircraft="Cessna Skyhawk 172SP Paint1" 484891 Weather Mode now = Theme 484891 Weather Mode now = Custom 486125 Starting everything now ... 487438 Advanced Weather Interface Enabled 545328 Weather Mode now = Theme 545328 Weather Mode now = Custom
January 27, 201511 yr Commercial Member Sorry, I was just out plowing snow. The CTD info is the same. The log is displayed also: Problem signature: P1: fsx.exe P2: 10.0.62608.0 P3: 54abe5b4 P4: terrain.dll P5: 10.0.62608.0 P6: 54abe5e1 P7: c0000005 P8: 0008fb86 I'm not familiar with that sort of layout, but if "P8" is the module offset, then I think (hope, really) that's a different TERRAIN crash to the one FSUIPC can trap at present. I've made a note of it and if this location appears to be a common one I'll look into trapping it too. Meanwhile it's 1-4 in favour of the one I am trapping (I hope). Pete Win10: 22H2 19045.2728 CPU: 9900KS at 5.5GHz Memory: 32Gb at 3800 MHz. GPU: RTX 24Gb Titan 2 x 2160p projectors at 25Hz onto 200 FOV curved screen
January 27, 201511 yr I'd like to say that the problem signature list must be different because I am running Win 8, but I don't think it is: http://blogs.msdn.com/b/oanapl/archive/2009/01/30/windows-error-reporting-wer-and-clr-integration.aspx P8 is definitely the offset as you pointed out.
January 27, 201511 yr Commercial Member I'd like to say that the problem signature list must be different because I am running Win 8, but I don't think it is: It probably isn't. it's just that I'm used to this much clearer report style: Faulting application name: fsx.exe, version: 10.0.62608.0, time stamp: 0x54abe5b4 Faulting module name: g3d.dll, version: 10.0.62608.0, time stamp: 0x54abe5dd Exception code: 0xc0000005 Fault offset: 0x000cb57a Faulting process id: 0x1314 Faulting application start time: 0x01d038cfc320f6ad Faulting application path: E:\Steam\steamapps\common\FSX\fsx.exe Faulting module path: E:\Steam\steamapps\common\FSX\g3d.dll Report Id: ce5df510-a4e6-11e4-bd92-b8975a1871d1 Most folks use this. Certainly saves having to guess what the "Pn" lines are about! ;-) Pete Win10: 22H2 19045.2728 CPU: 9900KS at 5.5GHz Memory: 32Gb at 3800 MHz. GPU: RTX 24Gb Titan 2 x 2160p projectors at 25Hz onto 200 FOV curved screen
January 27, 201511 yr Commercial Member I posted both formats in my original post. But not the last one. Sorry, it's just me, I wasn't sure which line was the important one I needed. Pete Win10: 22H2 19045.2728 CPU: 9900KS at 5.5GHz Memory: 32Gb at 3800 MHz. GPU: RTX 24Gb Titan 2 x 2160p projectors at 25Hz onto 200 FOV curved screen
January 29, 201511 yr Hey Pete, I got my guaranteed crash near the southern tip of Greenland, except this time it wasn't terrain.dll or g3d.dll related. aiplayer.dll crash...first time I got that. Faulting application name: fsx.exe, version: 10.0.62608.0, time stamp: 0x54abe5b4 Faulting module name: ai_player.dll, version: 10.0.62608.0, time stamp: 0x54abe5d9 Exception code: 0xc0000005 Fault offset: 0x0003564c Faulting process id: 0x8f4 Faulting application start time: 0x01d03b4f43c34b7c Faulting application path: E:\Steam\steamapps\common\FSX\fsx.exe Faulting module path: E:\Steam\steamapps\common\FSX\ai_player.dll Report Id: 76a98b81-a755-11e4-aa3a-b8975a1871d1 TERRAIN fix: Passes 312255, Null pointers 0, Bad pointers 0, Separate instances 0 from the FSUIPC log. Doesn't seem like it it's terrain related at all. Siiiiiiigh. Why does it always crash over southern Greenland then? Daniel Moser
January 29, 201511 yr Well, I did another transatlantic flight without AI to make sure I don't get aiplayer.dll crashes. I was expecting to get my terrain.dll/g3d.dll crash over Greenland, but it never happened. I completed my EGLL-KORD flight without a single crash for the first time ever in FSX:SE. Weird. FSUIPC reports "TERRAIN fix: Passes 351907, Null pointers 0, Bad pointers 0, Separate instances 0". So no terrain issues to report. Is it possible this could all be AI related? Daniel Moser
January 29, 201511 yr Well, I did another transatlantic flight without AI to make sure I don't get aiplayer.dll crashes. I was expecting to get my terrain.dll/g3d.dll crash over Greenland, but it never happened. I completed my EGLL-KORD flight without a single crash for the first time ever in FSX:SE. Weird. FSUIPC reports "TERRAIN fix: Passes 351907, Null pointers 0, Bad pointers 0, Separate instances 0". So no terrain issues to report. Is it possible this could all be AI related? I'm planning to re-fly my original flight this weekend that also crashed near Greenland, this time with the latest FSUIPC beta patch. FWIW, I've never used AI in FSX, all of my traffic sliders are always at zero. I know that there have been several reports that the other common crash in FSX-SE, (caused by G3D.dll) may be related to corrupt AI models. In my 45 hours flying with SE, I have not experienced the G3D crash, which may be due to the fact that I do not use AI. I was curious what weather program you are using (if any)? Since SE was released, I have been using FSGRW on all of my flights, but it has some issues that make me a bit nervous - specifically white flashes in the sky and ground textures every few minutes whenever the weather updates. I have just gone back to Opus, which I had shelved several months ago when ASN came out. I have to admit that I am quite surprised and pleased at the advances that have been made in Opus since I last used it - many new features and stability improvements - and no graphics artifacts in flight. I will be using OpusFSI when I re-fly the FP near Greenland, as it works perfectly in SE. Jim BarrettLicensed Airframe & Powerplant Mechanic, Avionics, Electrical & Air Data Systems Specialist. Qualified on: Falcon 900, CRJ-200, Dornier 328-100, Hawker 850XP and 1000, Lear 35, 45, 55 and 60, Gulfstream IV and 550, Embraer 135, Beech Premiere and 400A, MD-80.
Create an account or sign in to comment