Internal Error

[CrankyOldDave]

Okay, so I've played 17 hours so far and am loving it. This afternoon I go in and all my save files are corrupted. Damn. But alpha so whatever. So I try and start a new game. Internal error.

Huh. Okay. Validate files. All validate successfully.

Completely delete game. Reload. Internal error.

Make sure drivers are updated. Google the crap out of the issue. Delete the game, then also delete the Save directory and the Log directory. Reload game.

Internal error. NO error log generated.

So yeah. I'm dead in the water unless someone has a few bright ideas I haven't tried.

[piddlefoot]

Sounding like a Steam error somewhere.

When you re-installed was that just the game, or steam as well ?

Did you update NetFramework ?

Did you drag thesaved folder back into the new installation before running game ?

Did you go through the proper un-instal system through windows, or did you just delete the folder?

You could un-instal Steam properly then re-instal it, then let steam download the game again and instal it, then run the game before doing anything else and see what it does, it should work.

Also you can go to Windows Start button and do a search for Windows Event Log and just see what its saying at the TIME of the crash.

[CrankyOldDave]

Yeah uninstalling Steam isn't happening. All my other games work perfectly fine and uninstalling Steam would cause me to also uninstall all of my games. So if Empyrion doesn't work then it's just tough noogies.

I completely removed the save folder so when I reinstalled from scratch it recreated the folder.

The event log is a good idea, though. I'll check that out.

[CrankyOldDave]

And just because I needed to do some housecleaning, I uninstalled & reinstalled Steam (which freed up almost a TB of disk space!) And it didn't work. Internal error.

[Sparrowhawk65]

Originally posted by Edrondol:

Okay, so I've played 17 hours so far and am loving it. This afternoon I go in and all my save files are corrupted. Damn. But alpha so whatever. So I try and start a new game. Internal error.

Just checking... does Empyrion load ok but you get an error when you try to start a new game or does it crash before getting to the menu? If the menu works do you get an error if trying to start an SP game, scenario and a Creative game?

[CrankyOldDave]

It’s when I try and start a new game. The type of game does not matter, although I have not tried creative yet to test. I’ll do that tonight when I get home from work.

[Sparrowhawk65]

Would it be worth going on the experimental branch to teast that? It's the same as standard at the moment, but might be worth a try. On that vein, maybe when 8 lands on experimental, that might fix the problem.

[CrankyOldDave]

Already tried. I went to experimental but the game did not change anything or even download a change. Which is why I completely removed and then reinstalled Steam.

[CrankyOldDave]

I hoped maybe the update to experimental 8.0 would fix this. Nope.

Regular game: Get to selection screen and as soon as I try and start ANY game, I get the Internal error.

Alpha 6: Get to selection screen and as soon as I try and start ANY game, I get the Internal error.

Experimental v. 8.0: The game won't start and goes straight to the Internal error.

[TwitchyJ]

You never answered what Windows Event Viewer has to say at the time of the errors.
If no logs are generated by the game then the answers will be in Event Viewer.

It sounds like you've got a hardware issue/limitation or a software issue preventing the game from running properly if it can't even generate it's own logs.

[CrankyOldDave]

So the system that I have that literally runs every other game in existence except this ONE GAME IN ALPHA is the issue. I don't buy it. But to humor you, I cleared my Event Viewer and ran it again.

After it hung I checked the Event Viewer and the only error on the Application log was a 1002 ID, which means the program hung. And that was probably because I had to kill it in task manager.

I've done all of this and tried to troubleshoot. It's not my computer. I rather don't think it's Steam as I uninstalled/reinstalled. All drivers are up to date. I validated the game files.

I've seen others had gotten this error before, but that was for a much earlier build. Those issues were fixed when the dev updated the game. This is much more trouble than it's worth. I mean, it's a great game and all, but there are several in the same genre that are not in Alpha phase. I might just have to be patient and check back after a few iterations to see what changes.

And I also realize I never put in specs to see if there are known conflicts:

* GTX 1080
* 32 GB RAM
* i7-4770 processor
* Windows 10

Again, all drivers, programs, firmware, everything is up to date. There was a Windows 10 update between when it worked and when it stopped, but I haven't heard of this happening to anyone else in the time frame, so I'm assuming that the Window 10 update didn't cause major issues with the program.

[TwitchyJ]

Sounds very similar to other issues people had in the past.
Could be a conflict with your antivirus program. Check exceptions and try disabling it temporarily as a test.

Don't at all just dismiss windows updates as the cause. Windows 10 updates especially have caused MANY gaming related issues that affect some users and not others. This is very common.
Also, if the game worked and then you had a windows update and the game no longer worked, that is one of the first places I would be checking myself. It's really easy to roll back to before the update, run the game and check, then run the update and check the game again.

[CrankyOldDave]

Now antivirus is something I haven't considered. That would update all the time, wouldn't it?

And sorry for sounding snarky. I'm just hitting a high level of frustration. I don't mean to take it out on people trying to help.

[TwitchyJ]

We've all been there once or twice in our lives. I totally understand the frustration of being unable to figure something out.
We really are just trying to spitball and help though. This game is worth it IMO.
The problem is all we can do is guess and check without proper error logs being generated.

[Sparrowhawk65]

Sorry you're having this problem. I'd be frustrated if I couldn't run it.

[CrankyOldDave]

Are you ^%$^ING kidding me?!? I turned off BitDefender. Bam. It ran.

So all I have to do is put in a rule to exclude the directory and/or application from scanning and it'll be gold.

Holy crap on a cracker.

1) Thanks for the idea. I'd tried everything else from every thread on any place I could find.
2) Head desk. Head desk. HEAD DESK!

I think maybe I overthought this. Son of a-!