None of this proves that it is not a hardware problem. The save might be in such a state that it is generating a load that your hardware is unstable with. The 120 hours before this could have been generating loads that your system is stable with. If you have a second computer system or know someone willing to run the save to check for the crash on their system this would be quite helpful. If it also crashes on these different systems it is very likely to be an X4/save problem rather than a hardware problem.thadir wrote: ↑Tue, 21. Jun 22, 00:361. It happens with that save ONLY --> loading another save and playing hours leads to no issue --> Not a hardware problem
2. I could play 5 days (which is 120 hours of play) with no issue at all --> Are you saying that my hardware works fine for 120 hours than needs a vacation? --> Not a hardware problem
3. No change in driver/software/OS was made and if I load any other save , no issue happens --> Not a sw update/hw issue
The problem is that this is not reasonable to debug. Not only does it take ~30 minutes to occur, it has a huge variance and can take as long as 90 minutes, and possibly not even occur at all. During this time the system being used to try and recreate the crash is busy and likely cannot be used for other activities. If this is a developer's main system this will potentially impact their productivity for the day, or even days.
This is where having any other system verify the reproducibility of the crash would be very helpful. If the crash is certain to be unrelated to hardware and is very likely to occur eventually when they test it then justifying such resources to debugging it makes more sense.