Author Topic: computer lockup during rtmm flight  (Read 4304 times)

shermank

  • Member
  • ***
  • Posts: 254
computer lockup during rtmm flight
« on: October 15, 2022, 01:22:05 PM »
Hi all,

I had a P3D and computer lockup, twice while flying MFCT 0035 Saginaw to Entrance Island
It happened at these coordinates (screenshot below)

LON N57 23.35
LAT W 134 29.64

Here is appview data report on the crash (this is techie stuff way beyond my pay grade, but perhaps one of you knows what this means. The crash occurred with CIGAR BOX active. I duplicated the flight without CB and the same thing happened again. Any help is appreciated. Thanks

Sherm

Version=1
EventType=APPCRASH
EventTime=133103088167760522
ReportType=2
Consent=1
UploadTime=133103088171042067
ReportStatus=268435456
ReportIdentifier=01351c5b-5bae-415d-b1c6-a82ae274cf53
IntegratorReportIdentifier=61f850a0-8479-4843-a558-d20bb02a8e4c
Wow64Host=34404
NsAppName=Prepar3D.exe
OriginalFilename=Prepar3D.exe
AppSessionGuid=00003d98-0001-00ad-c2c2-51ab8de0d801
TargetAppId=W:00008a9af7075a4c74565c60a5a528269a6e0000ffff!00006cc2e3bef4c5936df590450b87335a6e8264cc06!Prepar3D.exe
TargetAppVer=2021//06//29:18:43:11!5ca50!Prepar3D.exe
BootId=4294967295
TargetAsId=701
UserImpactVector=816
IsFatal=1
EtwNonCollectReason=1
Response.BucketId=23a3cb0e6baa296401858600ff6bed85
Response.BucketTable=4
Response.LegacyBucketId=1262562609390677381
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=Prepar3D.exe
Sig[1].Name=Application Version
Sig[1].Value=5.2.22.27615
Sig[2].Name=Application Timestamp
Sig[2].Value=60db69bf
Sig[3].Name=Fault Module Name
Sig[3].Value=GTII-OSD64.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=2.0.6.4
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=5fab9439
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=0000000000010c30
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.19044.2.0.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=ff8c
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=ff8c4af817d043b78cd481330d9dbdd6
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=228c
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=228cd67cd5ec8c677dfe712f8171ea5b
UI[2]=C:\P3D V5\Prepar3D.exe
LoadedModule[0]=C:\P3D V5\Prepar3D.exe
LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\Windows\System32\KERNEL32.DLL
LoadedModule[3]=C:\Windows\System32\KERNELBASE.dll
LoadedModule[4]=C:\Windows\SYSTEM32\apphelp.dll
LoadedModule[5]=C:\Windows\SYSTEM32\AcGenral.DLL
LoadedModule[6]=C:\Windows\System32\msvcrt.dll
LoadedModule[7]=C:\Windows\System32\sechost.dll
LoadedModule[8]=C:\Windows\System32\RPCRT4.dll
LoadedModule[9]=C:\Windows\System32\SHLWAPI.dll
LoadedModule[10]=C:\Windows\System32\USER32.dll
LoadedModule[11]=C:\Windows\System32\win32u.dll
LoadedModule[12]=C:\Windows\System32\GDI32.dll
LoadedModule[13]=C:\Windows\System32\gdi32full.dll
LoadedModule[14]=C:\Windows\System32\msvcp_win.dll
LoadedModule[15]=C:\Windows\System32\ucrtbase.dll
LoadedModule[16]=C:\Windows\System32\ole32.dll
LoadedModule[17]=C:\Windows\System32\combase.dll
LoadedModule[18]=C:\Windows\System32\SHELL32.dll
LoadedModule[19]=C:\Windows\System32\ADVAPI32.dll
LoadedModule[20]=C:\Windows\SYSTEM32\USERENV.dll
LoadedModule[21]=C:\Windows\SYSTEM32\MPR.dll
LoadedModule[22]=C:\Windows\SYSTEM32\SspiCli.dll
LoadedModule[23]=C:\Windows\SYSTEM32\AcLayers.DLL
LoadedModule[24]=C:\Windows\SYSTEM32\sfc.dll
LoadedModule[25]=C:\Windows\SYSTEM32\WINSPOOL.DRV
LoadedModule[26]=C:\Windows\SYSTEM32\sfc_os.DLL
LoadedModule[27]=C:\Windows\System32\IMM32.DLL
LoadedModule[28]=C:\P3D V5\api.dll
LoadedModule[29]=C:\Windows\SYSTEM32\VCRUNTIME140.dll
LoadedModule[30]=C:\Windows\System32\WS2_32.dll
LoadedModule[31]=C:\Windows\System32\CRYPT32.dll
LoadedModule[32]=C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_5.82.19041.1110_none_792d1c772443f647\COMCTL32.dll
LoadedModule[33]=C:\Windows\SYSTEM32\MSWSOCK.dll
LoadedModule[34]=C:\Windows\SYSTEM32\Cabinet.dll
LoadedModule[35]=C:\Windows\SYSTEM32\WINHTTP.dll
LoadedModule[36]=C:\Windows\SYSTEM32\WINMM.dll
LoadedModule[37]=C:\Windows\SYSTEM32\VERSION.dll
LoadedModule[38]=C:\Windows\SYSTEM32\urlmon.dll
LoadedModule[39]=C:\Windows\SYSTEM32\WININET.dll
LoadedModule[40]=C:\P3D V5\acontain.dll
LoadedModule[41]=C:\P3D V5\atc.dll
LoadedModule[42]=C:\P3D V5\controls.dll
LoadedModule[43]=C:\P3D V5\ai_player.dll
LoadedModule[44]=C:\Windows\System32\SETUPAPI.dll
LoadedModule[45]=C:\Windows\System32\cfgmgr32.dll
LoadedModule[46]=C:\Windows\System32\bcrypt.dll
LoadedModule[47]=C:\P3D V5\demo.dll
LoadedModule[48]=C:\Windows\System32\OLEAUT32.dll
LoadedModule[49]=C:\P3D V5\dis.dll
LoadedModule[50]=C:\P3D V5\facilities.dll
LoadedModule[51]=C:\P3D V5\flight.dll
LoadedModule[52]=C:\P3D V5\fe.dll
LoadedModule[53]=C:\P3D V5\g3d.dll
LoadedModule[54]=C:\Windows\System32\COMDLG32.dll
LoadedModule[55]=C:\P3D V5\gps.dll
LoadedModule[56]=C:\Windows\System32\shcore.dll
LoadedModule[57]=C:\P3D V5\g2d.dll
LoadedModule[58]=C:\Windows\System32\WLDAP32.dll
LoadedModule[59]=C:\P3D V5\livingwater.dll
LoadedModule[60]=C:\P3D V5\menus.dll
LoadedModule[61]=C:\P3D V5\main.dll
LoadedModule[62]=C:\P3D V5\multiplayer.dll
LoadedModule[63]=C:\P3D V5\pdk.dll
LoadedModule[64]=C:\P3D V5\panels.dll
LoadedModule[65]=C:\P3D V5\sim1.dll
LoadedModule[66]=C:\P3D V5\simscheduler.dll
LoadedModule[67]=C:\P3D V5\simprop.dll
LoadedModule[68]=C:\P3D V5\sound.dll
LoadedModule[69]=C:\P3D V5\symmap.dll
LoadedModule[70]=C:\P3D V5\terrain.dll
LoadedModule[71]=C:\P3D V5\fs-traffic.dll
LoadedModule[72]=C:\P3D V5\util.dll
LoadedModule[73]=C:\P3D V5\visualfx.dll
LoadedModule[74]=C:\P3D V5\weather.dll
LoadedModule[75]=C:\P3D V5\window.dll
LoadedModule[76]=C:\Windows\SYSTEM32\MSVCP140.dll
LoadedModule[77]=C:\Windows\SYSTEM32\iertutil.dll
LoadedModule[78]=C:\Windows\SYSTEM32\srvcli.dll
LoadedModule[79]=C:\Windows\SYSTEM32\CONCRT140.dll
LoadedModule[80]=C:\Windows\SYSTEM32\netutils.dll
LoadedModule[81]=C:\Windows\SYSTEM32\VCRUNTIME140_1.dll
LoadedModule[82]=C:\Windows\SYSTEM32\HID.DLL
LoadedModule[83]=C:\Windows\SYSTEM32\DINPUT8.dll
LoadedModule[84]=C:\P3D V5\librti1516e.dll
LoadedModule[85]=C:\P3D V5\UltralightCore.dll
LoadedModule[86]=C:\P3D V5\AppCore.dll
LoadedModule[87]=C:\P3D V5\Ultralight.dll
LoadedModule[88]=C:\P3D V5\WebCore.dll
LoadedModule[89]=C:\P3D V5\mplEasyBlendSDKDX1164.dll
LoadedModule[90]=C:\Windows\SYSTEM32\MFReadWrite.dll
LoadedModule[91]=C:\Windows\SYSTEM32\MFPlat.DLL
LoadedModule[92]=C:\Windows\SYSTEM32\dxgi.dll
LoadedModule[93]=C:\P3D V5\gfsdk_waveworks.win64.dll
LoadedModule[94]=C:\P3D V5\GFSDK_Aftermath_Lib.x64.dll
LoadedModule[95]=C:\P3D V5\D3DCOMPILER_47.dll
LoadedModule[96]=C:\Windows\SYSTEM32\DSOUND.dll
LoadedModule[97]=C:\Windows\SYSTEM32\IPHLPAPI.DLL
LoadedModule[98]=C:\Windows\SYSTEM32\MSACM32.dll
LoadedModule[99]=C:\Windows\SYSTEM32\MSIMG32.dll
LoadedModule[100]=C:\P3D V5\audiere.dll
LoadedModule[101]=C:\Windows\SYSTEM32\d3d11.dll
LoadedModule[102]=C:\Windows\SYSTEM32\DWrite.dll
LoadedModule[103]=C:\P3D V5\libfedtime1516e.dll
LoadedModule[104]=C:\P3D V5\OpenRTI.dll
LoadedModule[105]=C:\P3D V5\icuuc63.dll
LoadedModule[106]=C:\P3D V5\icuin63.dll
LoadedModule[107]=C:\P3D V5\d3dx11_43.dll
LoadedModule[108]=C:\P3D V5\D3DCOMPILER_43.dll
LoadedModule[109]=C:\Windows\SYSTEM32\winmmbase.dll
LoadedModule[110]=C:\Windows\SYSTEM32\powrprof.dll
LoadedModule[111]=C:\P3D V5\icudt63.dll
LoadedModule[112]=C:\Windows\System32\bcryptPrimitives.dll
LoadedModule[113]=C:\Windows\SYSTEM32\kernel.appcore.dll
LoadedModule[114]=C:\Windows\SYSTEM32\RTWorkQ.DLL
LoadedModule[115]=C:\Windows\SYSTEM32\UMPDC.dll
LoadedModule[116]=C:\P3D V5\language.dll
LoadedModule[117]=C:\Windows\SYSTEM32\inputhost.dll
LoadedModule[118]=C:\Windows\SYSTEM32\wintypes.dll
LoadedModule[119]=C:\Windows\SYSTEM32\CoreMessaging.dll
LoadedModule[120]=C:\Windows\SYSTEM32\CoreUIComponents.dll
LoadedModule[121]=C:\Windows\SYSTEM32\PROPSYS.dll
LoadedModule[122]=C:\Windows\SYSTEM32\ntmarta.dll
LoadedModule[123]=C:\Windows\system32\uxtheme.dll
LoadedModule[124]=D:\utilities\GPUTweakII-Version2295\GTII-OSD\x64\GTII-OSD64-VK.dll
LoadedModule[125]=C:\Windows\SYSTEM32\vulkan-1.dll
LoadedModule[126]=C:\Windows\SYSTEM32\windows.storage.dll
LoadedModule[127]=C:\Windows\SYSTEM32\Wldp.dll
LoadedModule[128]=C:\Windows\SYSTEM32\profapi.dll
LoadedModule[129]=C:\P3D V5\uiInterface.dll
LoadedModule[130]=C:\Windows\SYSTEM32\mscoree.dll
LoadedModule[131]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\mscoreei.dll
LoadedModule[132]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
LoadedModule[133]=C:\Windows\SYSTEM32\VCRUNTIME140_CLR0400.dll
LoadedModule[134]=C:\Windows\SYSTEM32\ucrtbase_clr0400.dll
LoadedModule[135]=C:\Windows\assembly\NativeImages_v4.0.30319_64\mscorlib\b8493bec853ac702d2188091d76ccffa\mscorlib.ni.dll
LoadedModule[136]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clrjit.dll
LoadedModule[137]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System\b187b7f31cee3e87b56c8edca55324e0\System.ni.dll
LoadedModule[138]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Core\eb2c6c8f7acf8c616044ba327063ffa5\System.Core.ni.dll
LoadedModule[139]=C:\Windows\assembly\NativeImages_v4.0.30319_64\WindowsBase\78a8c55d2e5293ee16a8d495d8ae6890\WindowsBase.ni.dll
LoadedModule[140]=C:\Windows\SYSTEM32\CRYPTSP.dll
LoadedModule[141]=C:\Windows\system32\rsaenh.dll
LoadedModule[142]=C:\Windows\SYSTEM32\CRYPTBASE.dll
LoadedModule[143]=C:\Windows\assembly\NativeImages_v4.0.30319_64\PresentationCore\36f56cab29c451485f9ad49e944784a8\PresentationCore.ni.dll
LoadedModule[144]=C:\Windows\assembly\NativeImages_v4.0.30319_64\Presentatio5ae0f00f#\aadc1f5f0238fb3dc7345c4dfdcb6bc1\PresentationFramework.ni.dll
LoadedModule[145]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Xaml\4f15595ef94cc58c31703115528ad213\System.Xaml.ni.dll
LoadedModule[146]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\WPF\wpfgfx_v0400.dll
LoadedModule[147]=C:\Windows\SYSTEM32\MSVCP140_CLR0400.dll
LoadedModule[148]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\WPF\PresentationNative_v0400.dll
LoadedModule[149]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Configuration\41112824f1c7d55f50fe6fe891911a67\System.Configuration.ni.dll
LoadedModule[150]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Xml\db3df155ec9c0595b0198c4487f36ca1\System.Xml.ni.dll
LoadedModule[151]=C:\Windows\SYSTEM32\MSASN1.dll
LoadedModule[152]=C:\Windows\System32\NSI.dll
LoadedModule[153]=C:\Windows\SYSTEM32\dhcpcsvc6.DLL
LoadedModule[154]=C:\Windows\SYSTEM32\dhcpcsvc.DLL
LoadedModule[155]=C:\Windows\SYSTEM32\DNSAPI.dll
LoadedModule[156]=C:\Windows\SYSTEM32\secur32.dll
LoadedModule[157]=C:\Program Files\Bonjour\mdnsNSP.dll
LoadedModule[158]=C:\Windows\System32\rasadhlp.dll
LoadedModule[159]=C:\Windows\System32\fwpuclnt.dll
LoadedModule[160]=C:\Windows\SYSTEM32\MSXML6.DLL
LoadedModule[161]=C:\Windows\System32\MSCTF.dll
LoadedModule[162]=C:\P3D V5\rad_tm_win64.dll
LoadedModule[163]=C:\Windows\System32\PSAPI.DLL
LoadedModule[164]=D:\utilities\GPUTweakII-Version2295\GTII-OSD\x64\GTII-OSD64-GL.dll
LoadedModule[165]=C:\Windows\SYSTEM32\OPENGL32.dll
LoadedModule[166]=C:\Windows\SYSTEM32\GLU32.dll
LoadedModule[167]=D:\utilities\GPUTweakII-Version2295\GTII-OSD\x64\glew32.dll
LoadedModule[168]=D:\utilities\GPUTweakII-Version2295\GTII-OSD\x64\GTII-OSD64.dll
LoadedModule[169]=C:\Windows\SYSTEM32\d3d10_1.dll
LoadedModule[170]=C:\Windows\SYSTEM32\d3d12.dll
LoadedModule[171]=C:\Windows\SYSTEM32\d3d10_1core.dll
LoadedModule[172]=C:\Windows\SYSTEM32\d3dx9_43.dll
LoadedModule[173]=C:\Windows\SYSTEM32\d3dx10_43.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
OsInfo[0].Key=vermaj
OsInfo[0].Value=10
OsInfo[1].Key=vermin
OsInfo[1].Value=0
OsInfo[2].Key=verbld
OsInfo[2].Value=19044
OsInfo[3].Key=ubr
OsInfo[3].Value=2130
OsInfo[4].Key=versp
OsInfo[4].Value=0
OsInfo[5].Key=arch
OsInfo[5].Value=9
OsInfo[6].Key=lcid
OsInfo[6].Value=1033
OsInfo[7].Key=geoid
OsInfo[7].Value=244
OsInfo[8].Key=sku
OsInfo[8].Value=48
OsInfo[9].Key=domain
OsInfo[9].Value=0
OsInfo[10].Key=prodsuite
OsInfo[10].Value=256
OsInfo[11].Key=ntprodtype
OsInfo[11].Value=1
OsInfo[12].Key=platid
OsInfo[12].Value=10
OsInfo[13].Key=sr
OsInfo[13].Value=0
OsInfo[14].Key=tmsi
OsInfo[14].Value=221835704
OsInfo[15].Key=osinsty
OsInfo[15].Value=2
OsInfo[16].Key=iever
OsInfo[16].Value=11.789.19041.0-11.0.1000
OsInfo[17].Key=portos
OsInfo[17].Value=0
OsInfo[18].Key=ram
OsInfo[18].Value=16303
OsInfo[19].Key=svolsz
OsInfo[19].Value=465
OsInfo[20].Key=wimbt
OsInfo[20].Value=0
OsInfo[21].Key=blddt
OsInfo[21].Value=191206
OsInfo[22].Key=bldtm
OsInfo[22].Value=1406
OsInfo[23].Key=bldbrch
OsInfo[23].Value=vb_release
OsInfo[24].Key=bldchk
OsInfo[24].Value=0
OsInfo[25].Key=wpvermaj
OsInfo[25].Value=0
OsInfo[26].Key=wpvermin
OsInfo[26].Value=0
OsInfo[27].Key=wpbuildmaj
OsInfo[27].Value=0
OsInfo[28].Key=wpbuildmin
OsInfo[28].Value=0
OsInfo[29].Key=osver
OsInfo[29].Value=10.0.19041.2130.amd64fre.vb_release.191206-1406
OsInfo[30].Key=buildflightid
OsInfo[31].Key=edition
OsInfo[31].Value=Professional
OsInfo[32].Key=ring
OsInfo[32].Value=Retail
OsInfo[33].Key=expid
OsInfo[34].Key=fconid
OsInfo[35].Key=containerid
OsInfo[36].Key=containertype
OsInfo[37].Key=edu
OsInfo[37].Value=0
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Prepar3D exe
AppPath=C:\P3D V5\Prepar3D.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=5525F1824403F488D7C2CA108870B8BB
MetadataHash=1413858910

kaha

  • Hero Member
  • *****
  • Posts: 1,442
Re: computer lockup during rtmm flight
« Reply #1 on: October 15, 2022, 02:44:10 PM »
Hello, I know that Asus GPU Tweak II causes such crashes. Did you OC your GPU with that tool?
Maybe you can give it a try without GPU Tweak II?

Karl
i9-9900K@5.0 | RTX 3080TI | 55" 4K | MSFS2020

NeptuneP2V7

  • Sr. Member
  • ****
  • Posts: 973
    • VA-AMC
Re: computer lockup during rtmm flight
« Reply #2 on: October 16, 2022, 03:36:35 AM »
Hi ,

May be an object of this specific scenery cause crash..

if you remember to PASI 2 planes make this same issue . cessna float and beaver amphibian statics object scenery . Because they are outoff date and not compatible .

look at this way ..

May be a solution .

Have Good Sunday
[size=16]Ryzen9 5900X 4.8 GHz / ASUS PRIME X570-P / Corsair Vengeance 32 Go DDR4 3600 MHz / ASROCK - VGA CARDS Radeon RX6800XT Phantom Gaming
Noctua NH-D15 / Samsung SSD 980 PRO M.2 PCIe NVMe 250 Go / Fox Spirit US-850G 80PLUS Gold / Fox Spirit 31.5" LED - PGM315 V2[/size]

shermank

  • Member
  • ***
  • Posts: 254
Re: computer lockup during rtmm flight
« Reply #3 on: October 16, 2022, 09:12:02 AM »
Hello, I know that Asus GPU Tweak II causes such crashes. Did you OC your GPU with that tool?
Maybe you can give it a try without GPU Tweak II?

Karl

Hi Karl and all,
Yes I did use the Asus Tweak which I installed a few days ago...I did uninstall it before testing again, but got the same lockup...also this morning starting out of AGN flying South...the freeze occurred at a spot different from the first, though I was unable to tag the LON and LAT. As for aircraft, the first times was with the Carenado 185 amphib in misty colors. The second this morning was flying the Kodiak Quest amphib.

If I had OC'd the computer using the Tweak (which I am not sure I did), how do I restore the default Clock speed? I guess that would be in the BIOS...anyway, thanks...you have given me some possible solutions.

Sherm

kaha

  • Hero Member
  • *****
  • Posts: 1,442
Re: computer lockup during rtmm flight
« Reply #4 on: October 16, 2022, 10:20:47 AM »
Sherm, there is no OCing active if GPU Tweaker is not running. And the BIOS on your card is not changed. So, if you disabled the setting in GPU Tweaker to start when Windows starts and to Apply OC settings automatically, your card is running on factory settings.

Still. do you say it crashes since you have installed GPU Tweaker and not before? You could uninstall it and then try again. Edit: Oh, I see, you did.

Karl
i9-9900K@5.0 | RTX 3080TI | 55" 4K | MSFS2020

nbrich1

  • Misty Moorings Team
  • Hero Member
  • *
  • Posts: 3,537
  • Misty Flying Club VA, Sim Troubleshooting & Help
    • Misty Flying Club (MFC)
Re: computer lockup during rtmm flight
« Reply #5 on: October 16, 2022, 10:51:39 AM »
Well Sherm, the error log doesn't convey reason for the CTD. I guess, in this case, we have to start from the beginning in order to restore the sim to vanilla almost then build it up again to try to figure out what is causing your CTD.  If there is only two locations the problem is mostly likely a scenery piece conflict for that area.

You have said in RTMM areas. Do you have the correct RTMM scenery on your sim which supports P3Dv5 if you haven't done that? RTMM Add-on P3Dv5?  https://return.mistymoorings.com/s_install/index.php
File you want is: 3. RTMM Add-On for P3D V5 - (XML).

(If you have Tongass - you MUST update the AI models or you will experience CTD everytime if you're in the Tongass area when the scenery calls the AI traffic): Refer to AI Aircraft for Tongass X - By Rod Jackson
https://return.mistymoorings.com/s_getting_started/index.php#5
---------------------------------------------------------

If it is not these two possible scenery issues.. and you still have CTD in various locations, than that is a different matter and would recommend a more extensive process as per the following, (short of reinstalling the sim).

OS-GPU:
1. Update your video driver and your OS. (Make sure all is update to date!)

SIM:
2. Clear your sim shaders folder.
C:\Users\USERNAME\AppData\Local\Lockheed Martin\Prepar3D v5\Shaders (Delete the contents).
Don't delete the folder itself, just the contents.

The sim will rebuild all the shaders according to your system and latest driver indexes on the next sim startup. (Don't start the sim yet)

3. Go to %APPDATA%\Lockheed Martin\Prepar3D v5
And make a backup of your  Prepar3D.cfg file.  (A Copy).
Delete the Prepar3D.cfg file. 
The sim will rebuild this file as per your system: (Settings are reset to default but you can set that back up after). 
----------------------------------------
Try your sim.. It will take longer to boot up as it is rebuilding the Prepar3D.cfg and shader files.
The settings will be at default now, so set them up the way you like them.

4. Fly to the CTD locations... is it still CTD? or ok?

5. If NOT ok, there still is a conflict or non-compatible piece of scenery somewhere which is causing the CTD.

I have no idea how you have setup your scenery/add-ons but turn off your scenery add-ons add-ons (disable Add-ons).
Fire up the sim and turn all of your add-on scenery OFF. Restart your sim and now try to fly in the same spots of your previous CTD locations. Is it ok ? Or still CTD?

If ok now in default scenery, you'll have to start turning add-ons back on to try to isolate what scenery is causing the CTD. (in those areas).  (Recommend turn all off then only turn on scenery that is in that area.

----------------------------------

----------------------------------

That's enough to do for now... try it and report back... If still a no go, we can explore further and we can always get together on TS or Discord and work on it.

Norm
« Last Edit: October 16, 2022, 11:15:08 AM by nbrich1 »
Regards from Toronto, Canada. Home Airport CYYZ.
^----------------- Misty Flying Club -----------------^

NeptuneP2V7

  • Sr. Member
  • ****
  • Posts: 973
    • VA-AMC
Re: computer lockup during rtmm flight
« Reply #6 on: October 16, 2022, 02:22:09 PM »
Hi

Use this is easy to do .. WhoCrashed
Click analyze and you have a report 

https://www.resplendence.com/whocrashed
[size=16]Ryzen9 5900X 4.8 GHz / ASUS PRIME X570-P / Corsair Vengeance 32 Go DDR4 3600 MHz / ASROCK - VGA CARDS Radeon RX6800XT Phantom Gaming
Noctua NH-D15 / Samsung SSD 980 PRO M.2 PCIe NVMe 250 Go / Fox Spirit US-850G 80PLUS Gold / Fox Spirit 31.5" LED - PGM315 V2[/size]

shermank

  • Member
  • ***
  • Posts: 254
Re: computer lockup during rtmm flight
« Reply #7 on: October 16, 2022, 02:39:31 PM »
Thanks to all who offered advice and help. I did complete the flight, albeit with a couple of pauses and whirling cursor icon along the way. But, the sim rebounded back into active state. When these speed bumps developed, I switched off True Sky and closed down Active Sky hoping to ease the load. I also have been monitoring CPU clock speed. Native speed for my I7 10700 is 2.90 Ghz....Task Manager reports actual speed is at or around 4.59 Ghz. I did go into bios and reset back to default, but it remains in the mid 4 range according to Task Manager.
There are some good ideas for me to go over and tweak. As it turns out my wife and I are leaving tomorrow for some oveseas travel until the end of October. So, things will sit for a while until I get back home...
Again, thanks for everything! I really appreciate all of the detailed ideas and suggestions. Without singling out anyone, all were worth exploring and utilizing.
Cheers
Sherm
« Last Edit: October 16, 2022, 02:58:47 PM by shermank »

nbrich1

  • Misty Moorings Team
  • Hero Member
  • *
  • Posts: 3,537
  • Misty Flying Club VA, Sim Troubleshooting & Help
    • Misty Flying Club (MFC)
Re: computer lockup during rtmm flight
« Reply #8 on: October 16, 2022, 03:56:20 PM »
Well, True Sky and Active Sky are the first things you should turn off... these are 3rd party external programs and are well known to cause CTD as tries to grab weather metar/data and injects weather condtions directly into your sim. Any glitch in the process and CTD..  So now, in that light, it's probably not any scenery that is causing those CTD but those weather programs..  Anyways, moving on..   

Have fun on your trip.

« Last Edit: October 16, 2022, 04:02:21 PM by nbrich1 »
Regards from Toronto, Canada. Home Airport CYYZ.
^----------------- Misty Flying Club -----------------^

shermank

  • Member
  • ***
  • Posts: 254
Re: computer lockup during rtmm flight
« Reply #9 on: October 17, 2022, 09:15:05 AM »
thanks Norm,
and, yes I have turned off AS and TS are off, at least for RTMM flights. Neither has ever caused me any problems for any other flights, aircraft, routes, etc.


Sherm