1. What did you do?
Installed Factorio from the Steam launcher, and opened the game.
2. What happened?
Factorio started loading as usual, and when it hit 95% while loading sprites, crashed and gave me a text file log containing the report of what happened, as well as a dump file.
3. What did you expect to happen instead? It might be obvious to you, but do it anyway!
I expected Factorio to start up as it always had without fail.
[1.1.5] Crash on start in msvcrt.dll
-
- Manual Inserter
- Posts: 3
- Joined: Thu Dec 10, 2020 12:45 am
- Contact:
[1.1.5] Crash on start in msvcrt.dll
- Attachments
-
- GameStart.zip
- (2.2 MiB) Downloaded 97 times
-
- factorio-current.log
- (12.89 KiB) Downloaded 100 times
Re: [1.1.5] Crash on start in msvcrt.dll
Was this a one time issue?
Post the corresponding dump file please, it's in the logs directory.
Post the corresponding dump file please, it's in the logs directory.
-
- Manual Inserter
- Posts: 3
- Joined: Thu Dec 10, 2020 12:45 am
- Contact:
Re: [1.1.5] Crash on start in msvcrt.dll
Dump file postedLoewchen wrote: Thu Dec 10, 2020 1:16 am Was this a one time issue?
Post the corresponding dump file please, it's in the logs directory.
- Attachments
-
- factorio-dump-current.dmp
- (710.17 KiB) Downloaded 86 times
-
- Manual Inserter
- Posts: 3
- Joined: Thu Dec 10, 2020 12:45 am
- Contact:
Re: [1.1.5] Crash on start in msvcrt.dll
UPDATE
As it turns out, the problem was with Windows having somehow not updated despite the OS saying it had. The OS build was severely out of date and causing issues everywhere.
Before reinstalling the game prior to this issue, I had just upgraded my hardware and done a clean install of WIndows 10 onto an M.2 drive, hence some of the issues.
It's working fine now!
As it turns out, the problem was with Windows having somehow not updated despite the OS saying it had. The OS build was severely out of date and causing issues everywhere.
Before reinstalling the game prior to this issue, I had just upgraded my hardware and done a clean install of WIndows 10 onto an M.2 drive, hence some of the issues.
It's working fine now!