• We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.

stratege1401

Private
14 Badges
Sep 18, 2011
21
3
n2.rkn.ovh
  • Cities in Motion
  • Cities in Motion 2
  • 500k Club
  • Cities: Skylines - After Dark
  • Cities: Skylines - Snowfall
  • Cities: Skylines - Mass Transit
  • Surviving Mars
  • Surviving Mars: Digital Deluxe Edition
  • Surviving Mars: First Colony Edition
  • Cities: Skylines Industries
  • Prison Architect
  • Surviving Mars: First Colony Edition
  • Hearts of Iron III
  • Cities: Skylines


fixed by hotfix4....


Now, after hotfix3, i bluescreen every time autosave works.
After reboot, the "autosaved" game is corrupted.
on a vanilla no mod game ( all mod files erased, on a fresh steam reinstalled game, after a file verification ), i can replicate the crash.
When changing autosave period to a shorter or longer period, same thing.


Sorry to say, but a bad dlc stays bad !!!

I dont know what going on with your dev team, but there is some bad noise in the net saying the original devs are gone, that new team is fighting against the odd....

Meanwhile, WE, the customers are just paying the price: dead game and rants !!!

Hoping emergency hotfix3 or hotfix4 will fix it without breaking anything else.... so far, dreaming is not forbidden... yet.
 
Last edited:
Upvote 0
@stratege1401

Thank you for your report, could you go to \appdata\roaming\Surviving Mars\ folder? In this folder, you will have several directories that are named crashes, logs and one with a long bunch of numbers.

Please zip and attach the latest save-game file, log file and both the .crash & .dmp files.

cheers,
Mark
 
Hello Mark,

Here the availables files....
As it is a bluescreen of death, i have set W to write all crash data, but it seem it doesnot work...

Thank you.

I will not do a full cleanup/reinstall (mods+games) until next hotfix, so i can try any actions required to debug.

Also, i have some outdated non-active mods. Can clean them if needed.
 

Attachments

  • Surviving Mars.rar
    140,8 MB · Views: 0
Next time you get a BSoD please record the text on it, which can help pinpoint where the problem is.
 
The blue screen is really weird.

WHEA UNCORRECTABLE ERROR​

Absolutely no error code, no nothing.
The system is so broken, it can even write the full memory dump in %SystemRoot%\MEMORY.DMP... the empty folder stay empty.


Of course, i did the usual tricks against WHEA (sfc and stuff ). Nothing.

My hardware is 4 years old. Running almost 24/7. ( i have a website running on it on a DebianVM)
The only time having whea error was with red dead redemption 2 and was due to a bad windows update. Fixed by full scrap and reinstall.

- I did reinstall my Win10pro system from scratch less than 8 month ago ( i do it usually once every years ). I am on 21H1, fully updated.
- My samsung nvme ssd 960 pro is working fine ( samsung magician, only 251.9TO write, temp average is 39. After 10 test, it never failed.
- I tested my ram this WK. Done 100 mem86 loop without a fault.

I have started a new game. Disable off the mods ( present, but non-active ). I did absolutely nothing ( no research, no building, no nothing ). Asap the automatic save kick in, my system crashed to blue/whea...

I have stress my system with my VM running several win/linux. No troubles.

- My next step is to clone my ssd over a HDD, for testing. And see if i still have whea while playing.
- Then, i plan to remove ALL mods, do a full reinstall of the game. ( i have 2 copy, my main game with all dlc from steam, and a free copy from epic game ( not installed, no dlc )
- Last i will scrap my win10 and do a painfull reinstall...

Anyway, my new rig is on the way ... soon.

I will post any breakthrough
 
@stratege1401 I did a quick search on Google, which you probably did and the results mention that a WHEA uncorrectable error is a hardware issue.

Intel have this guide to help narrow down the issue

The error WHEA_UNCORRECTABLE_ERROR"stands for Windows Hardware Error Architecture. If you receive a blue screen error (also known as a stop code) with WHEA_UNCORRECTABLE_ERROR, it means that a hardware issue has occurred on your computer. Issues could be related to such things as hard drives, processor, power supply, bad or corrupted memory (DRAM). It also could be that the device drivers are outdated or corrupted. Another reason could be voltage changes.



To fix it, try the following tips in order, as the first or any following step might resolve your issue.

  • Reboot the system and enter BIOS settings, set the BIOS to its default settings, and reboot the system.
  • Remove any hardware or drivers that were installed recently to see if they are causing the issue.
  • If unable to start with normal mode, start Windows in safe mode.
    • Check if there are any driver errors in the device manager and update the device driver for the devices that are showing errors.
  • Get the latest updates with Windows Update. Go to Settings Update & security Windows Update, and then select Check for updates. When done, reboot your system.
  • Check if there are any hardware issues.
    • Try to boot with minimal hardware settings (for example, one DRAM, fewer hardware components on your system).
    • Test DRAM: Try Windows 10 app called Windows Memory Diagnostic to check for memory issues.
    • Test the processor, using the Intel® Processor Diagnostic Tool which can be downloaded here. For more information about the tool, see The Intel® Processor Diagnostic Tool.
    • Check the power supply.
    • Try to test other hardware in the system. (For example, if another working hard drive is available, then use it instead.)
 
As for 'hardware errors then especially memory can exhibit a variation in behavior depending on task (meaning some programs may provoke an error where another might not) .
Also you do not write if you have OC your hardware !
If we are up against a 'stability issue' where system is not 100% stable always (not saying we are just mentioning the possibility) then in my experience it's important to run system at conservative settings , but also one ought to be careful mixing e.g different models of RAM modules. (That kind of problems with RAM modules used to be quite common but in modern tech mostly seem to have been eliminated, but still if grasping for straws trying to find a reason for an error) (I agree completely when you argue that mem86 ought to show any problems , but still !) .
Also PSU problems at odd times can exhibit a problem in a rather strange and unexpected way , and the same goes for some types of damage to the CPU !
My 'input' here is not meant as some 'fix it' , I am merely trying to tell that sometimes a problem with a specific part can be rather hard to pin-point.
The above may sound extremely strange to some but try to think of it this way : if a certain problem is dependent on e.g. a small variation in e.g. a certain voltage then it could be an odd 'load' dependent issue , and if it is load dependent then you can not even be sure if what fail is PSU, GPU, CPU or RAM because you can not even be sure if the problem is that the PSU fails to deliver or if some component is hyper-sensitive , if about hypersensitivity then if RAM then maybe not all the memory but only part and then only showing in certain situations... I am not even claiming that my 'example' is possible in reality , though it might be, I am just suggesting that sometimes a problem may seem to defy logic because we fail to see all the possible issues !
 
@stratege1401 I did a quick search on Google, which you probably did and the results mention that a WHEA uncorrectable error is a hardware issue.

Intel have this guide to help narrow down the issue

The error WHEA_UNCORRECTABLE_ERROR"stands for Windows Hardware Error Architecture. If you receive a blue screen error (also known as a stop code) with WHEA_UNCORRECTABLE_ERROR, it means that a hardware issue has occurred on your computer. Issues could be related to such things as hard drives, processor, power supply, bad or corrupted memory (DRAM). It also could be that the device drivers are outdated or corrupted. Another reason could be voltage changes.



To fix it, try the following tips in order, as the first or any following step might resolve your issue.

  • Reboot the system and enter BIOS settings, set the BIOS to its default settings, and reboot the system.
  • Remove any hardware or drivers that were installed recently to see if they are causing the issue.
  • If unable to start with normal mode, start Windows in safe mode.
    • Check if there are any driver errors in the device manager and update the device driver for the devices that are showing errors.
  • Get the latest updates with Windows Update. Go to Settings Update & security Windows Update, and then select Check for updates. When done, reboot your system.
  • Check ifthere are any hardware issues.
    • Try to boot with minimal hardware settings (for example, one DRAM, fewer hardware components on your system).
    • Test DRAM: Try Windows 10 app called Windows Memory Diagnostic to check for memory issues.
    • Test the processor, using the Intel® Processor Diagnostic Tool which can be downloaded here. For more information about the tool, see The Intel® Processor Diagnostic Tool.
    • Check the power supply.
    • Try to test other hardware in the system. (For example, if another working hard drive is available, then use it instead.)
My hardware is 100% not concern by this whea error.

This error occurs ONLY when the games is running, and ONLY when autosave is kicking.

None of my other games are causing whea, no other software are causing whea, no VM running on top on my system are causing WHEA.

WHEA happens ONLY when B&B is running and autosaving. EVERYTIMES, ALL THE TIMES, REPRODUCIBLES 100%.

But thanks anyway.
 
HOTFIX 4 FIX THE PROBLEM.

Before B&B hotfix4, whea still happening. ( last games played for 5h17 mns without any troubles AC VALHALA ).

Downloaded the hotfix4 today.

WHEA ERRORS ARE GONE. Autosaves are noxw working....

HOW STRANGE !
 
  • 1Like
Reactions:
I move back in time with acronis

back to B&B hotfix3 ... autosave--whea present.
Desinstall game, done a full unsubscribe for mod.
reinstall from backup to hotfix3, but vanilla.
autosave -- whea

update to hotfix4, no more whea
resubscribe to my favorite mods, one by one, testing if whea kick in. HOPEFULLY, no such things happens.

just to dig further, but now, i am just fine and so happy.
 
  • 2Like
Reactions: