[2.60] CTD dumps included - Busy doing not a lot [Updated 28/10/2019]

[Terre]

CTD, whilst sitting dock, not doing much at all.

Current version Eng. 2.60 no mods or scripts.

Code: Select all

<?xml version="1.0" encoding="utf-8"?>
<UserInfo>
<data>User='' Contact='' CurTime=897960.26 SessionTime=896372.16
Error in MD cue md.FactionLogic.ScalePlatePactFactionLogic_Manager.Econ_Manager.Request_Factory<inst:18ef9db>: No suitable FactoryGenerator found with tags=null, race=race.teladi, factions=null, ware=ware.majasnails
Error in MD cue md.NPC_Management.Exit_Undocking<inst:18f982c>: Evaluated component 0x18f97f0 does not exist any more
* Expression: $InvolvedNPCs.keys.{$NPCCounter}
Error in MD cue md.NPC_Management.Exit_Undocking<inst:18fa8b3>: Evaluated component 0x18fa7d8 does not exist any more
* Expression: $InvolvedNPCs.keys.{$NPCCounter}
Error in MD cue md.NPC_Management.Exit_Undocking<inst:18fa8bb>: Evaluated component 0x18fa840 does not exist any more
* Expression: $InvolvedNPCs.keys.{$NPCCounter}
Error in MD cue md.NPC_Management.Exit_Undocking<inst:18fa6f0>: Evaluated component 0x18fa88e does not exist any more
* Expression: $InvolvedNPCs.keys.{$NPCCounter}
Error in MD cue md.NPC_Management.Exit_Undocking<inst:20a3099>: Evaluated component 0x20a308d does not exist any more
* Expression: $InvolvedNPCs.keys.{$NPCCounter}
aicontext<move.undock,0x18a4458>: after waiting 5.00096min in queue, MIN Defence Drone (TZP-099) does not have an assigned dock. 
 attention: ingalaxy 
 undocking from: ship_tel_m_frigate_01_b_macro 
 present dock: shipstorage_gen_s_frigate_01_macro 
 assigned dock: null
 => restart
aicontext<move.undock,0x18a43d3>: after waiting 5.00117min in queue, MIN Defence Drone (TQV-828) does not have an assigned dock. 
 attention: ingalaxy 
 undocking from: ship_tel_m_frigate_01_b_macro 
 present dock: shipstorage_gen_s_frigate_01_macro 
 assigned dock: null
 => restart
'Radeon (TM) RX 480 Graphics' AMD-driver v2.0.106 (Vulkan 1.1.119) check=1
*** Context:md.Encounters.Lone_Plunderer_New_Encounter_Check<inst:18c0835>: Warping ANT Marauder Discoverer Vanguard 0x24c6e and subordinates to position.[-141884.296875m, -1403.240356m, 169235.218750m]
*** Context:md.Encounters.Xenon_S_Lone_New_Encounter_Check<inst:18bf1bd>: Warping XEN Raiding Party M 0x14ecf and subordinates to position.[-115836.921875m, 2954.003418m, 185798.312500m]
cluster_09_macro, cluster_09_sector001_macro, zone001_cluster_09_sector001_macro
0 extensions
memory(current: 2413953434 peak=3499236538 reserved=4404084736 current-with-overhead=2675706138 current-allocations=8179772 peak-allocations=8759740)
</data>
</UserInfo>

[Terre]

The hardware has since been changed.

[Terre]

Using DDU I removed both the Vulkan and graphic drivers on my system, but as yet I have not had time to sit and play X4, or NMS, both of which CTD on me, which points to Vulkan as the issue. I still get "WARNING: [Loader Message] Code 0 : ReadDataFilesInRegistry: Registry lookup failed to get layer manifest files." error message when running vulkaninfo.exe.

Update: NMS lasted about 40 minutes before falling over.
Update: X4 ran for just over an hour without fault.

[Terre]

It didn't last, CTD,froze and returned me to the desktop, but any other programmes running in the background carried on just fine.

As aside note, why are there two dumps?

[Terre]

Stability appears to have been restored by the installation of Vulkan runtime 1.1.121.2

[stefanEgo]

Hi Terre,

looking at your dumps it seems to hint towards some system instability on your side. Both crashdumps are unrelated (from the code side point of view) and rather unique (i.e. seems like they only occur to you). Usually this kind of instability hints to some HW/system instability leading to things like memory corruption which ultimately lead to crashing the game.

First thing I'd check in such situation is the system stability (i.e. potential overheating/overclocking issues) and/or check your system for general stability problems (especially if the issues are not limited to just X4). sfc / chkdisk / memcheck would be the keywords to start with here.

[Terre]

Thanks for taking the time to have a look at the dumps.

As for it being a heat issue, I ran FurMark and got my graphics card, an AMD RX 5700, up to a toasty 80°C without any problems.

I've just tried 'sfc' and a number of errors were found, so it looks like it's going to be a clean start.