Game Crashes on Startup

Xerter · October 27, 2019

So, i just Bought the Game had my fun and after around 16 Hours of Playtime the game won't start anymore. did a clean re-install and everything but didn't work, obviously.

EDIT: Here is the errorlog https://filebin.net/9q0wp7k3mpcyhw88

Edited October 27, 2019 by Xerter

Commodore_32 · October 27, 2019

Well, thats bad, your log is filled with errors!!

And in a error line appears this: Es wurde versucht, auf eine unzulÃ¤ssige Adresse zuzugreifen.

In english that means:An attempt was made to access an invalid address.

So the cause maybe because there are missing files, or changed directory, etc.

I just can tell that the error is something about the files.

Curveball Anders · October 28, 2019

Actually:

"Read from location 0000000000000000 caused an access violation."

Is normally an indication of a bad mod or a driver issue.

Xerter · October 28, 2019

18 hours ago, Commodoregamer118 said:

Well, thats bad, your log is filled with errors!!

And in a error line appears this: Es wurde versucht, auf eine unzulÃ¤ssige Adresse zuzugreifen.

In english that means:An attempt was made to access an invalid address.

So the cause maybe because there are missing files, or changed directory, etc.

I just can tell that the error is something about the files.

Okay that quite helps.

Just wondering why the game Stopped working after running without any problems.

Come to think of it, sincce i had to set up my PC a had problems with .dll files.

linuxgurugamer · October 28, 2019

On 10/27/2019 at 7:56 AM, Xerter said:

So, i just Bought the Game had my fun and after around 16 Hours of Playtime the game won't start anymore. did a clean re-install and everything but didn't work, obviously.

EDIT: Here is the errorlog https://filebin.net/9q0wp7k3mpcyhw88

Could you get us the Player.log, please? But first, try verifying the files through Steam.

And did you install any mods?

Xerter · October 28, 2019

58 minutes ago, linuxgurugamer said:

Could you get us the Player.log, please? But first, try verifying the files through Steam.

And did you install any mods?

If you tell me where i can Find the Player.log, sure. If you mean to leat steam seach for any errors, than i already did that.

No mods

Jacke · October 28, 2019

1 hour ago, Xerter said:

If you tell me where i can Find the Player.log, sure. If you mean to leat steam seach for any errors, than i already did that.

Be sure you verify your files through Steam.

Log on Windows is located here now in KSP 1.8: C:\Users\<username>\AppData\LocalLow\Squad\Kerbal Space Program\Player.log

VoidSquid · October 28, 2019

This:

Kerbal Space Program by Squad [version: Unity 2019.2.2f1_ab112815d860]

dxgi.dll caused an Access Violation (0xc0000005)
  in module dxgi.dll at 0033:8845ec68.

dxgi.dll is the "DirectX Graphics Infrastructure" library.

So DirectX had an issue, a graphics problem then.

Suggestions: reinstalling DirectX, updating graphics driver, also make sure you're using the correct graphics mode (KSP 1.8 uses DX11, earlier versions used DX9)

Xerter · October 28, 2019

46 minutes ago, Jacke said:

Be sure you verify your files through Steam.

Log on Windows is located here now in KSP 1.8: C:\Users\<username>\AppData\LocalLow\Squad\Kerbal Space Program\Player.log

I added the Player.log to the filebin

49 minutes ago, VoidSquid said:
This:
Kerbal Space Program by Squad [version: Unity 2019.2.2f1_ab112815d860]

dxgi.dll caused an Access Violation (0xc0000005)
  in module dxgi.dll at 0033:8845ec68.
dxgi.dll is the "DirectX Graphics Infrastructure" library.

So DirectX had an issue, a graphics problem then.

Suggestions: reinstalling DirectX, updating graphics driver, also make sure you're using the correct graphics mode (KSP 1.8 uses DX11, earlier versions used DX9)

I reinstalled DirectX 11 and nothing changes. My Drivers are up to date.

VoidSquid · October 28, 2019

Any additional software/drivers doing something graphically? E.g. Riva Tuner, MSI Dragon Eye, Duet Display, ...? Maybe try an older graphics driver, a few versions back?

21 hours ago, Commodoregamer118 said:

I just can tell that the error is something about the files.

I disagree, the access violation was about an attempt to read/write an address in memory, not a file.

linuxgurugamer · October 28, 2019

2 hours ago, Xerter said:

If you tell me where i can Find the Player.log, sure. If you mean to leat steam seach for any errors, than i already did that.

No mods

Take a look at my signature:

Read this BEFORE asking for support: http://forum.kerbalspaceprogram.com/index.php?/topic/83212-how-to-get-support-read-first/

Commodore_32 · October 28, 2019

14 minutes ago, VoidSquid said:

I disagree, the access violation was about an attempt to read/write an address in memory, not a file

Thats what i meant

VoidSquid · October 28, 2019

Just as @linuxgurugamer said

3 minutes ago, linuxgurugamer said:

Read this BEFORE asking for support: http://forum.kerbalspaceprogram.com/index.php?/topic/83212-how-to-get-support-read-first/

And if you have a crash.dmp, we could see was the debugger says.

Xerter · October 28, 2019

4 minutes ago, VoidSquid said:

Just as @linuxgurugamer said

And if you have a crash.dmp, we could see was the debugger says.

crash.dmp has been uploaded .o7

VoidSquid · October 28, 2019

Blarg... as you can see the Microsoft Symbols Server isn't available (same with Steam, btw, they seem to have worldwide issues atm) , I tried from two different computers, two different ISPs with different backbones:

Spoiler

Loading Dump File [E:\Downloads\crash.dmp]
User Mini Dump File: Only registers, stack and portions of memory are available

************* Path validation summary **************
Response Time (ms) Location
Deferred srv*c:\symbols*https://msdl.microsoft.com/download/symbols
Symbol search path is: srv*c:\symbols*https://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8.1 Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: SingleUserTS Personal
6.3.9600.17031 (winblue_gdr.140221-1952)
Machine Name:
Debug session time: Mon Oct 28 21:03:58.000 2019 (UTC + 1:00)
System Uptime: not available
Process Uptime: 0 days 0:00:08.000
................................................................
......
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(1b60.1b10): Access violation - code c0000005 (first/second chance not available)
For analysis of this file, run !analyze -v
DBGHELP: Timeout to store: c:\symbols*https://msdl.microsoft.com/download/symbols
DBGHELP: Timeout to store: c:\symbols*https://msdl.microsoft.com/download/symbols
*** WARNING: Unable to verify timestamp for ntdll.dll
DBGHELP: Timeout to store: c:\symbols*https://msdl.microsoft.com/download/symbols
DBGHELP: Timeout to store: c:\symbols*https://msdl.microsoft.com/download/symbols
*** WARNING: Unable to verify timestamp for KERNELBASE.dll
ntdll+0x9b13a:
00007ffb`78dfb13a c3 ret
0:000> !analyze -v
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************

*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: $ntdllsym!_CONTEXT ***
*** ***
*************************************************************************
***** OS symbols are WRONG. Please fix symbols to do analysis.

DBGHELP: Timeout to store: c:\symbols*https://msdl.microsoft.com/download/symbols
Unable to load image C:\Windows\System32\ole32.dll, Win32 error 0n2
DBGHELP: Timeout to store: c:\symbols*https://msdl.microsoft.com/download/symbols
*** WARNING: Unable to verify timestamp for ole32.dll
DBGHELP: Timeout to store: c:\symbols*https://msdl.microsoft.com/download/symbols
Unable to load image C:\Windows\System32\combase.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for combase.dll
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_CONTEXT ***
*** ***
*************************************************************************
DBGHELP: Timeout to store: c:\symbols*https://msdl.microsoft.com/download/symbols

KEY_VALUES_STRING: 1

PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1

DUMP_CLASS: 2

DUMP_QUALIFIER: 400

CONTEXT: (.ecxr)
rax=0000000000000000 rbx=000000521d2bb590 rcx=0000000000000000
rdx=00007ffb59febcc0 rsi=000000521d2bb5a0 rdi=0000000000000000
rip=00007ffb7315ec68 rsp=0000005212fcee00 rbp=0000005212fcee40
r8=00000052167bffe8 r9=00007ffb59febcc0 r10=00007ffb5a3efca0
r11=0000005212fceb80 r12=0000000000000780 r13=0000000000000008
r14=00000052167bffe8 r15=00007ffb59febcc0
iopl=0 nv up ei pl zr na po nc
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010246
dxgi+0xec68:
00007ffb`7315ec68 488b01 mov rax,qword ptr [rcx] ds:00000000`00000000=????????????????
Resetting default scope

FAULTING_IP:
dxgi+ec68
00007ffb`7315ec68 488b01 mov rax,qword ptr [rcx]

EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 00007ffb7315ec68 (dxgi+0x000000000000ec68)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000000
Attempt to read from address 0000000000000000

BUGCHECK_STR: 530895AF

WRONG_SYMBOLS_TIMESTAMP: 530895af

WRONG_SYMBOLS_SIZE: 1aa000

FAULTING_MODULE: 00007ffb78d60000 ntdll

DEBUG_FLR_IMAGE_TIMESTAMP: 530895af

ADDITIONAL_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbol path and load symbols. ; Followup set based on attribute [Is_ChosenCrashFollowupThread] from Frame:[0] on thread:[PSEUDO_THREAD]

ANALYSIS_SESSION_HOST:

ANALYSIS_SESSION_TIME: 10-28-2019 21:18:36.0590

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

STACK_TEXT:
00000052`12fcee00 00007ffb`7315ec68 dxgi+0xec68
00000052`12fcee08 00000052`1fd4fb80 unknown!unknown+0x0
00000052`12fcee10 00000052`1d2bb590 unknown!noop+0x0
00000052`12fcee18 0000d94b`00000000 unknown!unknown+0x0
00000052`12fcee20 00000052`1d2bb590 unknown!noop+0x0
00000052`12fcee28 00000052`167bffe8 unknown!unknown+0x0
00000052`12fcee30 00000052`167bffc0 unknown!unknown+0x0

THREAD_SHA1_HASH_MOD_FUNC: 9ba6f6d8c93fe29708a322a89fd281940a460f75

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 1fe9e56676d31b9c7c0eb0655bf3a19e34ab9a80

THREAD_SHA1_HASH_MOD: 53f6baec93d5a2afff2de0c1e3c776fb5d828345

FOLLOWUP_IP:
dxgi+ec68
00007ffb`7315ec68 488b01 mov rax,qword ptr [rcx]

FAULT_INSTR_CODE: ff018b48

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

STACK_COMMAND: .ecxr ; kb ; ** Pseudo Context ** Pseudo ** Value: 4440340 ** ; kb

EXCEPTION_CODE: (NTSTATUS) 0x530895af - <Unable to get error code text>

EXCEPTION_CODE_STR: 530895AF

EXCEPTION_STR: WRONG_SYMBOLS

PROCESS_NAME: ntdll.wrong.symbols.dll

IMAGE_NAME: ntdll.wrong.symbols.dll

MODULE_NAME: ntdll_wrong_symbols

SYMBOL_NAME: ntdll_wrong_symbols!530895AF1AA000

BUCKET_ID: WRONG_SYMBOLS_X64_6.3.9600.17031_(winblue_gdr.140221-1952)_TIMESTAMP_140222-121855

DEFAULT_BUCKET_ID: WRONG_SYMBOLS_X64_6.3.9600.17031_(winblue_gdr.140221-1952)_TIMESTAMP_140222-121855

PRIMARY_PROBLEM_CLASS: WRONG_SYMBOLS

FAILURE_EXCEPTION_CODE: 530895AF

FAILURE_IMAGE_NAME: ntdll.wrong.symbols.dll

BUCKET_ID_IMAGE_STR: ntdll.wrong.symbols.dll

FAILURE_MODULE_NAME: ntdll_wrong_symbols

BUCKET_ID_MODULE_STR: ntdll_wrong_symbols

FAILURE_FUNCTION_NAME: 530895AF1AA000

BUCKET_ID_FUNCTION_STR: 530895AF1AA000

BUCKET_ID_OFFSET: 0

BUCKET_ID_MODTIMEDATESTAMP: 0

BUCKET_ID_MODCHECKSUM: 0

BUCKET_ID_MODVER_STR: 0.0.0.0

BUCKET_ID_PREFIX_STR: WRONG_SYMBOLS_X64_6.3.9600.17031_(winblue_gdr.140221-1952)_TIMESTAMP_140222-121855

FAILURE_PROBLEM_CLASS: WRONG_SYMBOLS

FAILURE_SYMBOL_NAME: ntdll.wrong.symbols.dll!530895AF1AA000

FAILURE_BUCKET_ID: WRONG_SYMBOLS_X64_6.3.9600.17031_(winblue_gdr.140221-1952)_TIMESTAMP_140222-121855_530895AF_ntdll.wrong.symbols.dll!530895AF1AA000

TARGET_TIME: 2019-10-28T20:03:58.000Z

OSBUILD: 9600

OSSERVICEPACK: 17056

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 768

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 8.1

OSEDITION: Windows 8.1 WinNt SingleUserTS Personal

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2014-03-20 02:17:16

BUILDDATESTAMP_STR: 140221-1952

BUILDLAB_STR: winblue_gdr

BUILDOSVER_STR: 6.3.9600.17031

ANALYSIS_SESSION_ELAPSED_TIME: 1ebf3

ANALYSIS_SOURCE: UM

FAILURE_ID_HASH_STRING: um:wrong_symbols_x64_6.3.9600.17031_(winblue_gdr.140221-1952)_timestamp_140222-121855_530895af_ntdll.wrong.symbols.dll!530895af1aa000

FAILURE_ID_HASH: {b0c35623-8a9b-7b21-9a64-21306a0277f6}

Followup: MachineOwner
---------

The little I can say from this without the symbols, it is clear that this is a problem between Unity, DirectX, and your graphic card/driver, but we knew that before...

Interestingly (but that might be due to the lacking symbols) I don't see a single dll from a graphics driver mentioned, only DirectX and normal Windows stock stuff. But as I said, w/o the symbols, can't make any good statement.

Xerter · October 28, 2019

Come to think of it, when i had to set this PC up again , i had massive Problems with .dll files because they weren't installe the right way. Would another reset maybe change that, or could it be that there are corrupted Files?

VoidSquid · October 28, 2019

I wouldn't go that far yet.

As per the error log, you have an "HP Pavilion 15 Notebook PC" with an Nvidia 840M. Many notebooks (including my own) have two graphic card chips nowadays, can you check the Nvidia one is enabled for KSP? Can you try the other, not-enabled chip (there should be a utility program allowing you to select which graphics chip would be used by what application)?

Quite possible the low-power-consumption standard chip is used and that that one can't do DX11 properly.

Xerter · October 28, 2019

The Standart chip wasn't used, i changed that, just to test out what might happen and the game works.Stuttering to a point where it is unplayable, but it works. Might be really a problem with DirextX. But that doesn't make any sense to me because the game worked 16 hours. And out of nothing without me doing anything it stopped working.

VoidSquid · October 28, 2019

Not the first time I read about similar issues with KSP 1.8 in the last couple of days, check the others threads, you'll find some which have the same issue, suddenly out of the blue KSP 1.8 stopped working.

Well, guess that's all I can do for you right now, glad it works at least partially (stuttering) for you now

As an alternative, you could get yourself KSP 1.7.3, that one has an older engine and works w/o such issues. Right now though, Steam is down...

Edited October 28, 2019 by VoidSquid

Xerter · October 28, 2019

Yeah, i guess so. Thanks a lot~

VoidSquid · October 28, 2019

yw

Xerter · October 31, 2019

IMPORTANT!

So i also contacted the KSP Support and they suggested to create a new Local User on your PC. There is a known issue with KSP and the main User. It worked perfectly fine for me and i can now use my Nvida graphic card again.

Just letting you know if someone has the same problems. Maybe check this solution.

VoidSquid · October 31, 2019

So a Microsoft problem then, UAC and that?

Not that I'm surprised...

Part of my work is being System Administrator, about 90% of my work requires admin privileges and ofc some knowledge of Windows. For myself, I have disabled this whole UAC thingy, way less hassle, I don't have time for this nor am I willing to deal with that nonsense, I just need the work done.

Of course, Microsoft thinks this is a bad idea, in particular when you completely disable the UAC stuff, giving yourself direct and full admin rights, the OS doesn't allow you to run any Metro apps... brilliant idea, ain't it?

This whole UAC thingy is a big nonsense imo: either you know what you're doing, then UAC stands just in the way, best case: more clicks (and more often than not, this is not sufficient). Or we have the ordinary user who get's occasionally a UAC popup he neither understands nor is interested in (and why would he?), so he simply clicks it away without even bothering to read it.

But I'm digressing, important here: you got your problem resolved!

Edited October 31, 2019 by VoidSquid

Game Crashes on Startup

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Join the conversation