Greetings fellow travellers.
I have a PS4 fault which I’m trying to diagnose, which I’m hoping someone very clued on to PS4s running systems can help me with.
I’ll need to give a fair bit of information so bear with me.
I have 2 NMS saves I’m using as I go through my problem.
One is a fresh new NEXT save in the early stages of base building and the other is a very established carry over 1.3 save in the early stages of base building in NEXT but with all the previous carry over from 1.3.
To keep it simple I’ll just call them OLD SAVE or NEW SAVE.
So, My OLD save sometimes starts up and is hugely laggy and eventually becomes a crash displaying an error code of CE34878-0.
My NEW save fires up normal but sometimes it repeatedly crashes like clockwork 2 minutes in.
It also displays an error code CE34878-0.
This is a somewhat generic code stating that an app on the PS4 has crashed and thus provides little diagnosis information other than it is it is related to corrupted memory.
At other times and not necessarily related to a warm or a cold running system, the 2 games fire up beautifully, although the OLD save does show a hint of lagginess around my fairly small base.
So it is not a repeat failure in that it happens every time. It’s quite random but it is regular.
I’m trying to determine if the fault is in the NMS game, in my save files or if I have some sort of deteriorating hardware failure.
I recently did a complete FULL INITIALISATION and a complete reinstall and update of NMS to try and rectify the fault. It seemed to work for a short period but then the issue resurfaced.
Then it goes away.
Then it comes back again.
I’ve tried testing it with cold start ups and warp start ups with no obvious pattern.
I’ve tried testing it while connected and disconnected to the internet, again with no obvious pattern.
I can’t help think that this is some sort of processor error but my understanding of computer tech is limited so I’m struggling to grasp the likely causes. I thought that corrupt data would cause a repeat failure every time, yet this isn’t always happening (although the NEW save has demonstrated a sudden but predictable crash as if it suddenly ‘trips up’ at a certain point.) I also experienced this same repeated ‘2 minute’ crash when trying to start a brand new game with no save file at all…
So… I ask you mighty PS4 gurus of the CSD forum:
- Can a program run in different ways due to a bad save fault? (ie Can the save file affect the entire program’s ability to run?) If so, why would it not happen every time?
- Can a memory failure in the hardware cause this kind of sporadic crash yet at other times just run as it should? How?
- Would a failing processor or drive cause this kind of fault?
With most of the game now 99% housed in system storage due to the code changes since day 1, is it likely any issue with the NMS CD would cause a problem?
My instincts are telling me the PS4 is dying and that it is struggling sometimes to process the demanding environment of NMS but I still would like to know the likely cause.
- Why would it be struggling?
- What is the reason behind it sometimes running great yet other times being utterly awful.
As a bit of testing, I tried installing and playing the MAD MAX game, which has a history of crashing for no apparent reason and could not trigger a crash. Admittedly it does not have the demanding requirements of NMS NEXT.
I also tested my partners NMS game on a separate profile and it is equivalent to my OLD save and it has behaved exactly the same as mine. This indicates to me that it isn’t something in the save files (I hope) but rather something in the running of the game itself. I would note that it seems the more complex the game save is the worse it lags before it crashes. My basic creative save and my newer save simply crash without going laggy first.
Again this points to something screwy going on with the ability to process and render the game environment.
I hope someone out there has some information for me as I’m a bit lost as to what to do at the moment …
Thanks in advance