December 26, 20196 yr My installation is a clean install on a brand new machine. FSX-SE installed to c:\Program Files (x86)\Steam\SteamApps\common\fsx and I get the Generating Scenery files and Building Scenery database each launch. Was able to Attach fsx.exe to a debugger and this is the output: 'fsx.exe' (Win32): Loaded 'C:\Windows\SysWOW64\hid.dll'. Symbols loaded. 'fsx.exe' (Win32): Loaded 'C:\Windows\SysWOW64\XInput9_1_0.dll'. Symbols loaded. ***Exception thrown at 0x794374E2 (simprop.dll) in fsx.exe: 0xC0000005: Access violation reading location 0x00000008. 'fsx.exe' (Win32): Unloaded 'C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_77e6900053c33f6f\nvd3dum.dll' 'fsx.exe' (Win32): Unloaded 'C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_77e6900053c33f6f\nvwgf2um.dll' 'fsx.exe' (Win32): Unloaded 'C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_77e6900053c33f6f\nvldumd.dll' 'fsx.exe' (Win32): Unloaded 'C:\Windows\SysWOW64\wtsapi32.dll' The thread 0x183c has exited with code 1 (0x1). 'fsx.exe' (Win32): Unloaded 'C:\Program Files (x86)\Steam\tier0_s.dll' 'fsx.exe' (Win32): Unloaded 'C:\Program Files (x86)\Steam\vstdlib_s.dll' 'fsx.exe' (Win32): Unloaded 'C:\Windows\SysWOW64\secur32.dll' 'fsx.exe' (Win32): Unloaded 'C:\Program Files (x86)\Steam\steamclient.dll' 'fsx.exe' (Win32): Unloaded 'C:\Program Files (x86)\Steam\Steam.dll' 'fsx.exe' (Win32): Unloaded 'C:\Windows\SysWOW64\rmclient.dll' 'fsx.exe' (Win32): Unloaded 'C:\Windows\SysWOW64\twinapi.appcore.dll' 'fsx.exe' (Win32): Unloaded 'C:\Windows\SysWOW64\D3DSCache.dll' 'fsx.exe' (Win32): Unloaded 'C:\Windows\SysWOW64\D3D12.dll' 'fsx.exe' (Win32): Unloaded 'C:\Windows\SysWOW64\dxdiagn.dll' The thread 0x11b8 has exited with code 0 (0x0). The thread 0x59a0 has exited with code 0 (0x0). The thread 0x15c8 has exited with code 0 (0x0). The thread 0x49c has exited with code 0 (0x0). The thread 0x5be4 has exited with code 0 (0x0). The thread 0x42a8 has exited with code 0 (0x0). The thread 0x5f70 has exited with code 0 (0x0). The thread 0x5b64 has exited with code 0 (0x0). The thread 0x520 has exited with code 0 (0x0). The thread 0x3b60 has exited with code 0 (0x0). The thread 0x5d8c has exited with code 0 (0x0). The thread 0x5f4c has exited with code 0 (0x0). The thread 0x5e84 has exited with code 0 (0x0). The thread 0x3d48 has exited with code 0 (0x0). ***Exception thrown at 0x790BC6BD (g3d.dll) in fsx.exe: 0xC0000005: Access violation reading location 0x00000008. ***Unhandled exception at 0x790BC6BD (g3d.dll) in fsx.exe: 0xC0000005: Access violation reading location 0x00000008. This is the Event Viewer Log entry: Fault bucket 107583622141, type 1 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: fsx.exe P2: 10.0.62615.0 P3: 559f9a9a P4: g3d.dll P5: 10.0.62615.0 P6: 559f9ab4 P7: c0000005 P8: 000cc6bd P9: P10: Attached files: \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6354.tmp.mdmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6FF8.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7028.tmp.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7026.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7065.tmp.txt These files may be available here: \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_fsx.exe_8fd82b41ae4da935ca31c3a17b81ea4f43e8f042_a37f3a76_a3e50d22-fb5a-4f46-bef0-0bf6271a4fc9 Analysis symbol: Rechecking for solution: 0 Report Id: 210739c8-66ae-47b3-921d-48ce3a4cf771 Report Status: 268566528 Hashed bucket: 943b7872f525407ec97124c0c68b13ea Cab Guid: 0 Edited December 26, 20196 yr by lonewolf00708
Archived
This topic is now archived and is closed to further replies.