Jump to content
  • 2

Game crashes on startup with Unity window


Question

When I start KSP with fullscreen mode i see Unity crash window instead of the game window (borderless mode also crashes). If I start in Windowed Mode game starts correctly.

No mods. Version 1.8 & 1.9 (if I switch to 1.7 game starts correctly). When I run with "-force_opengl" I see game window but game freezing after loading screen. My specs: 4Gb RAM, AMD A4-4300 with Radeon HD 7420G + Radeon HD 8750M (both supports DX11.1).

I tried to reinstall game and video drivers. Also tried "Disable FullScreen Optimizations" in windows.

In C:\Users\warra\AppData\Local\Temp\Squad\Kerbal Space Program\Crashes\Crash_2020-02-13_182522997 I see: aticfx64.dll caused an Access Violation (0xc0000005)


MFRnyKY.png?1

Edited by warranty97
Link to post
Share on other sites

Recommended Posts

  • 0

This guy on the thread below appears to have a similar issue (but I'm guessing). Try to run KSP 1.9 in DX9 mode. If this works, give @pmborg a thanks - I'm just the messenger. :)

 

Link to post
Share on other sites
  • 0
1 hour ago, Vladokapuh said:

mine does the same thing, doesnt even create logs.
forcing neither opengl nor dx9 works.
1.7.3 still works perfectly fine.

Same for me too

Link to post
Share on other sites
  • 0

Hey @Nigel J. Cardozo, your log says that there should be a crash.dmp 

A crash has been intercepted by the crash handler. For call stack and other details, see the latest crash report generated in:
 * C:/Users/WIN7~1/AppData/Local/Temp/Squad/Kerbal Space Program/Crashes

I'd like to check it with a debugger, mind to upload it too?

Link to post
Share on other sites
  • 0

Also, just coming to my mind: a couple of days ago another fellow KSP player had almost the same issue after upgrading to 1.9, turned out, the graphics settings in the settings.cfg he had with his previous KSP weren't working with 1.9.

Just give it a try and rename the settings.cfg to something else, KSP should then create a new settings.cfg and startup with minimal settings.

Link to post
Share on other sites
  • 0
1 hour ago, VoidSquid said:

Also, just coming to my mind: a couple of days ago another fellow KSP player had almost the same issue after upgrading to 1.9, turned out, the graphics settings in the settings.cfg he had with his previous KSP weren't working with 1.9.

Just give it a try and rename the settings.cfg to something else, KSP should then create a new settings.cfg and startup with minimal settings.

Ok

3 hours ago, VoidSquid said:

Hey @Nigel J. Cardozo, your log says that there should be a crash.dmp 

A crash has been intercepted by the crash handler. For call stack and other details, see the latest crash report generated in:
 * C:/Users/WIN7~1/AppData/Local/Temp/Squad/Kerbal Space Program/Crashes

I'd like to check it with a debugger, mind to upload it too?

Ok 

Link to post
Share on other sites
  • 0

Tried: install 1.8.1 and patching it to 1.9; force DX12; DX9 mode; delete settings.cfg; reinstall windows;

1.7 works fine; 1.8 & 1.9 doesn't work;

My crash report:
...\AppData\Local\Temp\Squad\Kerbal Space Program\Crashes:
https://drive.google.com/open?id=1tPjL9oJ5VEYJQPjrGnQxpFk2Nu9wgihR

Link to post
Share on other sites
  • 0

The crash dump is pretty clear:

Spoiler


Microsoft (R) Windows Debugger Version 10.0.18362.1 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [E:\Downloads\Crashes\Crash_2020-02-23_101729012\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 10 Version 18363 MP (2 procs) Free x64
Product: WinNt, suite: SingleUserTS
18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Debug session time: Sun Feb 23 11:17:29.000 2020 (UTC + 1:00)
System Uptime: not available
Process Uptime: 0 days 0:00:11.000
................................................................
.................
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(36c8.22dc): Access violation - code c0000005 (first/second chance not available)
For analysis of this file, run !analyze -v
ntdll!NtWaitForMultipleObjects+0x14:
00007ffa`4f25cc14 c3              ret
0:000> !analyze -v
*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************

*** WARNING: Unable to verify timestamp for UnityPlayer.dll
*** WARNING: Unable to verify timestamp for mono-2.0-bdwgc.dll

KEY_VALUES_STRING: 1

    Key  : AV.Dereference
    Value: NullClassPtr

    Key  : AV.Fault
    Value: Read

    Key  : Timeline.Process.Start.DeltaSec
    Value: 11


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1

Timeline: !analyze.Start
    Name: <blank>
    Time: 2020-02-23T11:01:10.515Z
    Diff: 2621515 mSec

Timeline: Dump.Current
    Name: <blank>
    Time: 2020-02-23T10:17:29.0Z
    Diff: 0 mSec

Timeline: Process.Start
    Name: <blank>
    Time: 2020-02-23T10:17:18.0Z
    Diff: 11000 mSec


DUMP_CLASS: 2

DUMP_QUALIFIER: 400

CONTEXT:  (.ecxr)
rax=0000000000000000 rbx=000002b65e0b9f28 rcx=000002b65e0b9f28
rdx=000002b660dc60f0 rsi=000002b660dc60b8 rdi=000002b65e0b0010
rip=00007ffa45c0f4fe rsp=000000f62c57c650 rbp=0000000000000000
 r8=00007ffa4aefa9a0  r9=000000f62c57c8c0 r10=0000000000000011
r11=0000000000000000 r12=000000f62c57cba0 r13=00000000ffffffff
r14=000002b659400860 r15=0000000000000001
iopl=0         nv up ei pl nz na po nc
cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
aticfx64+0x4f4fe:
00007ffa`45c0f4fe 8b4008          mov     eax,dword ptr [rax+8] ds:00000000`00000008=????????
Resetting default scope

FAULTING_IP: 
aticfx64+4f4fe
00007ffa`45c0f4fe 8b4008          mov     eax,dword ptr [rax+8]

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

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_READ

PROCESS_NAME:  KSP_x64.exe

FOLLOWUP_IP: 
aticfx64+4f4fe
00007ffa`45c0f4fe 8b4008          mov     eax,dword ptr [rax+8]

READ_ADDRESS:  0000000000000008 

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000008

WATSON_BKT_PROCSTAMP:  4614489d

WATSON_BKT_PROCVER:  9.18.944.0

PROCESS_VER_PRODUCT:  Microsoft® DirectX for Windows®

WATSON_BKT_MODULE:  aticfx64.dll

WATSON_BKT_MODSTAMP:  55d4b4af

WATSON_BKT_MODOFFSET:  4f4fe

WATSON_BKT_MODVER:  8.17.10.1404

BUILD_VERSION_STRING:  18362.1.amd64fre.19h1_release.190318-1202

MODLIST_WITH_TSCHKSUM_HASH:  cf26939bde8b1938ee6fc1fe17553071303e4b46

MODLIST_SHA1_HASH:  b6b8e99f74ef27ef557987b790d2359333613c88

DUMP_FLAGS:  0

DUMP_TYPE:  2

ANALYSIS_SESSION_HOST:  

ANALYSIS_SESSION_TIME:  02-23-2020 12:01:10.0515

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

THREAD_ATTRIBUTES: 
BUGCHECK_STR:  APPLICATION_FAULT_NULL_CLASS_PTR_READ_NULL_CLASS_PTR_DEREFERENCE_INVALID_POINTER_READ

PRIMARY_PROBLEM_CLASS:  APPLICATION_FAULT

PROBLEM_CLASSES: 

    ID:     [0n313]
    Type:   [@ACCESS_VIOLATION]
    Class:  Addendum
    Scope:  BUCKET_ID
    Name:   Omit
    Data:   Omit
    PID:    [Unspecified]
    TID:    [0x22dc]
    Frame:  [0] : aticfx64

    ID:     [0n285]
    Type:   [INVALID_POINTER_READ]
    Class:  Primary
    Scope:  BUCKET_ID
    Name:   Add
    Data:   Omit
    PID:    [Unspecified]
    TID:    [0x22dc]
    Frame:  [0] : aticfx64

    ID:     [0n309]
    Type:   [NULL_CLASS_PTR_DEREFERENCE]
    Class:  Primary
    Scope:  BUCKET_ID
    Name:   Add
    Data:   Omit
    PID:    [Unspecified]
    TID:    [0x22dc]
    Frame:  [0] : aticfx64

    ID:     [0n310]
    Type:   [NULL_CLASS_PTR_READ]
    Class:  Primary
    Scope:  DEFAULT_BUCKET_ID (Failure Bucket ID prefix)
            BUCKET_ID
    Name:   Add
    Data:   Omit
    PID:    [0x36c8]
    TID:    [0x22dc]
    Frame:  [0] : aticfx64

IP_ON_HEAP:  000000f600000000
The fault address in not in any loaded module, please check your build's rebase
log at <releasedir>\bin\build_logs\timebuild\ntrebase.log for module which may
contain the address if it were loaded.

FRAME_ONE_INVALID: 1

LAST_CONTROL_TRANSFER:  from 000000f600000000 to 00007ffa45c0f4fe

STACK_TEXT:  
000000f6`2c57c650 000000f6`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000038 : aticfx64+0x4f4fe
000000f6`2c57c658 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000038 00007ffa`45bfec76 : 0x000000f6`00000000


THREAD_SHA1_HASH_MOD_FUNC:  28b6623ceb5ef079100f7dfbfdc904bc14dc5914

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  1322ea1548378c44025efe474e2f1c2258ece846

THREAD_SHA1_HASH_MOD:  28b6623ceb5ef079100f7dfbfdc904bc14dc5914

FAULT_INSTR_CODE:  f08408b

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  aticfx64+4f4fe

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: aticfx64

IMAGE_NAME:  aticfx64.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  55d4b4af

STACK_COMMAND:  ~0s ; .ecxr ; kb

FAILURE_BUCKET_ID:  NULL_CLASS_PTR_READ_c0000005_aticfx64.dll!Unknown

BUCKET_ID:  APPLICATION_FAULT_NULL_CLASS_PTR_READ_NULL_CLASS_PTR_DEREFERENCE_INVALID_POINTER_READ_aticfx64+4f4fe

FAILURE_EXCEPTION_CODE:  c0000005

FAILURE_IMAGE_NAME:  aticfx64.dll

BUCKET_ID_IMAGE_STR:  aticfx64.dll

FAILURE_MODULE_NAME:  aticfx64

BUCKET_ID_MODULE_STR:  aticfx64

FAILURE_FUNCTION_NAME:  Unknown

BUCKET_ID_FUNCTION_STR:  Unknown

BUCKET_ID_OFFSET:  4f4fe

BUCKET_ID_MODTIMEDATESTAMP:  55d4b4af

BUCKET_ID_MODCHECKSUM:  17948d

BUCKET_ID_MODVER_STR:  8.17.10.1404

BUCKET_ID_PREFIX_STR:  APPLICATION_FAULT_NULL_CLASS_PTR_READ_NULL_CLASS_PTR_DEREFERENCE_INVALID_POINTER_READ_

FAILURE_PROBLEM_CLASS:  APPLICATION_FAULT

FAILURE_SYMBOL_NAME:  aticfx64.dll!Unknown

WATSON_STAGEONE_URL: http://watson.microsoft.com/StageOne/KSP_x64.exe/9.18.944.0/4614489d/aticfx64.dll/8.17.10.1404/55d4b4af/c0000005/0004f4fe.htm?Retriage=1

TARGET_TIME:  2020-02-23T10:17:29.000Z

OSBUILD:  18363

OSSERVICEPACK:  329

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  256

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  unknown_date

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  2666

ANALYSIS_SOURCE:  UM

FAILURE_ID_HASH_STRING:  um:null_class_ptr_read_c0000005_aticfx64.dll!unknown

FAILURE_ID_HASH:  {a6e5443b-580c-7a9b-a68f-9eb9bf7676f7}

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

FAILURE_IMAGE_NAME:  aticfx64.dll

It's the combination of some settings and the ATI graphics driver.

In the last couple of months, there have been several reports here as well as at bugs.kerbalspaceprogram.com about issues with ATI/AMD graphic cards, as far as I know this hasn't been resolved completely yet, the issues started to appear with KSP 1.8, i.e. the new unity version 2019.2.2f1

Edited by VoidSquid
Link to post
Share on other sites
  • 0

Let's have a look then:

Spoiler

 


Microsoft (R) Windows Debugger Version 10.0.18362.1 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


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 7 Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: SingleUserTS
Machine Name:
Debug session time: Sun Feb 23 12:39:26.000 2020 (UTC + 1:00)
System Uptime: not available
Process Uptime: 0 days 0:00:06.000
................................................................
.....
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(1af4.1604): Access violation - code c0000005 (first/second chance not available)
For analysis of this file, run !analyze -v
ntdll!NtWaitForMultipleObjects+0xa:
00000000`77b8186a c3              ret
0:005> !analyze -v
*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************

*** WARNING: Unable to verify timestamp for UnityPlayer.dll
*** WARNING: Unable to verify timestamp for mono-2.0-bdwgc.dll

KEY_VALUES_STRING: 1

    Key  : AV.Dereference
    Value: NullClassPtr

    Key  : AV.Fault
    Value: Write

    Key  : Timeline.Process.Start.DeltaSec
    Value: 6


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1

Timeline: !analyze.Start
    Name: <blank>
    Time: 2020-02-23T14:40:28.857Z
    Diff: 10862857 mSec

Timeline: Dump.Current
    Name: <blank>
    Time: 2020-02-23T11:39:26.0Z
    Diff: 0 mSec

Timeline: Process.Start
    Name: <blank>
    Time: 2020-02-23T11:39:20.0Z
    Diff: 6000 mSec


DUMP_CLASS: 2

DUMP_QUALIFIER: 400

CONTEXT:  (.ecxr)
rax=0000000005b9e510 rbx=0000000000000007 rcx=0000000000000100
rdx=0000000005b9e520 rsi=0000000005b9e510 rdi=0000000000000078
rip=000000018000df66 rsp=0000000005b9e2d8 rbp=0000000000000100
 r8=0000000000000001  r9=0000000000000110 r10=0000000000000001
r11=0000000000000003 r12=0000000000000100 r13=0000000000000000
r14=0000000005b9e510 r15=00000000082fa68c
iopl=0         nv up ei pl nz na pe nc
cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
igd10umd64+0xdf66:
00000001`8000df66 660fe701        movntdq xmmword ptr [rcx],xmm0 ds:00000000`00000100=????????????????????????????????
Resetting default scope

FAULTING_IP: 
igd10umd64+df66
00000001`8000df66 660fe701        movntdq xmmword ptr [rcx],xmm0

EXCEPTION_RECORD:  (.exr -1)
ExceptionAddress: 000000018000df66 (igd10umd64+0x000000000000df66)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000001
   Parameter[1]: 0000000000000100
Attempt to write to address 0000000000000100

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_WRITE

PROCESS_NAME:  KSP_x64.exe

FOLLOWUP_IP: 
igd10umd64+df66
00000001`8000df66 660fe701        movntdq xmmword ptr [rcx],xmm0

WRITE_ADDRESS:  0000000000000100 

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:  0000000000000001

EXCEPTION_PARAMETER2:  0000000000000100

WATSON_BKT_PROCSTAMP:  4614489d

WATSON_BKT_PROCVER:  9.18.944.0

PROCESS_VER_PRODUCT:  Microsoft® DirectX for Windows®

WATSON_BKT_MODULE:  igd10umd64.dll

WATSON_BKT_MODSTAMP:  4d41a18a

WATSON_BKT_MODOFFSET:  df66

WATSON_BKT_MODVER:  8.15.10.2291

BUILD_VERSION_STRING:  6.1.7601.18015 (win7sp1_gdr.121129-1432)

MODLIST_WITH_TSCHKSUM_HASH:  8c36dece631afc29ced4dfb9e3e31a93be6d3e88

MODLIST_SHA1_HASH:  290dc421144788eeb8f7e199b7a1507d8dbf2b96

DUMP_FLAGS:  0

DUMP_TYPE:  2

ANALYSIS_SESSION_HOST:

ANALYSIS_SESSION_TIME:  02-23-2020 15:40:28.0857

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

THREAD_ATTRIBUTES: 
BUGCHECK_STR:  APPLICATION_FAULT_NULL_CLASS_PTR_WRITE_NULL_CLASS_PTR_DEREFERENCE_INVALID_POINTER_WRITE

PRIMARY_PROBLEM_CLASS:  APPLICATION_FAULT

PROBLEM_CLASSES: 

    ID:     [0n313]
    Type:   [@ACCESS_VIOLATION]
    Class:  Addendum
    Scope:  BUCKET_ID
    Name:   Omit
    Data:   Omit
    PID:    [Unspecified]
    TID:    [0x1604]
    Frame:  [0] : igd10umd64

    ID:     [0n286]
    Type:   [INVALID_POINTER_WRITE]
    Class:  Primary
    Scope:  BUCKET_ID
    Name:   Add
    Data:   Omit
    PID:    [Unspecified]
    TID:    [0x1604]
    Frame:  [0] : igd10umd64

    ID:     [0n309]
    Type:   [NULL_CLASS_PTR_DEREFERENCE]
    Class:  Primary
    Scope:  BUCKET_ID
    Name:   Add
    Data:   Omit
    PID:    [Unspecified]
    TID:    [0x1604]
    Frame:  [0] : igd10umd64

    ID:     [0n311]
    Type:   [NULL_CLASS_PTR_WRITE]
    Class:  Primary
    Scope:  DEFAULT_BUCKET_ID (Failure Bucket ID prefix)
            BUCKET_ID
    Name:   Add
    Data:   Omit
    PID:    [0x1af4]
    TID:    [0x1604]
    Frame:  [0] : igd10umd64

LAST_CONTROL_TRANSFER:  from 00000001800693c4 to 000000018000df66

STACK_TEXT:  
00000000`05b9e2d8 00000001`800693c4 : 00000000`082fa68c 00000000`00000000 00000000`00000028 00000000`083668fc : igd10umd64+0xdf66
00000000`05b9e2e0 00000000`082fa68c : 00000000`00000000 00000000`00000028 00000000`083668fc 00000000`00000078 : igd10umd64+0x693c4
00000000`05b9e2e8 00000000`00000000 : 00000000`00000028 00000000`083668fc 00000000`00000078 00000001`80069dc5 : 0x82fa68c


THREAD_SHA1_HASH_MOD_FUNC:  0e11eba51ec6651b5299eb77d1b420393281ba25

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  e8f488a0c8eda1c76a601c868a5452eda9a5e7f3

THREAD_SHA1_HASH_MOD:  0e11eba51ec6651b5299eb77d1b420393281ba25

FAULT_INSTR_CODE:  1e70f66

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  igd10umd64+df66

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: igd10umd64

IMAGE_NAME:  igd10umd64.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  4d41a18a

STACK_COMMAND:  ~5s ; .ecxr ; kb

FAILURE_BUCKET_ID:  NULL_CLASS_PTR_WRITE_c0000005_igd10umd64.dll!Unknown

BUCKET_ID:  X64_APPLICATION_FAULT_NULL_CLASS_PTR_WRITE_NULL_CLASS_PTR_DEREFERENCE_INVALID_POINTER_WRITE_igd10umd64+df66

FAILURE_EXCEPTION_CODE:  c0000005

FAILURE_IMAGE_NAME:  igd10umd64.dll

BUCKET_ID_IMAGE_STR:  igd10umd64.dll

FAILURE_MODULE_NAME:  igd10umd64

BUCKET_ID_MODULE_STR:  igd10umd64

FAILURE_FUNCTION_NAME:  Unknown

BUCKET_ID_FUNCTION_STR:  Unknown

BUCKET_ID_OFFSET:  df66

BUCKET_ID_MODTIMEDATESTAMP:  4d41a18a

BUCKET_ID_MODCHECKSUM:  0

BUCKET_ID_MODVER_STR:  8.15.10.2291

BUCKET_ID_PREFIX_STR:  X64_APPLICATION_FAULT_NULL_CLASS_PTR_WRITE_NULL_CLASS_PTR_DEREFERENCE_INVALID_POINTER_WRITE_

FAILURE_PROBLEM_CLASS:  APPLICATION_FAULT

FAILURE_SYMBOL_NAME:  igd10umd64.dll!Unknown

WATSON_STAGEONE_URL: http://watson.microsoft.com/StageOne/KSP_x64.exe/9.18.944.0/4614489d/igd10umd64.dll/8.15.10.2291/4d41a18a/c0000005/0000df66.htm?Retriage=1

TARGET_TIME:  2020-02-23T11:39:26.000Z

OSBUILD:  7601

OSSERVICEPACK:  18015

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  256

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 7

OSEDITION:  Windows 7 WinNt (Service Pack 1) SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2012-11-30 06:43:54

BUILDDATESTAMP_STR:  121129-1432

BUILDLAB_STR:  win7sp1_gdr

BUILDOSVER_STR:  6.1.7601.18015

ANALYSIS_SESSION_ELAPSED_TIME:  bf00

ANALYSIS_SOURCE:  UM

FAILURE_ID_HASH_STRING:  um:null_class_ptr_write_c0000005_igd10umd64.dll!unknown

FAILURE_ID_HASH:  {ae773b41-5a3f-d876-adcc-3192e9f9992d}

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

Luckily, again, a clear result (which is not always the case):

FAILURE_IMAGE_NAME:  igd10umd64.dll

A quick search gives:

igd10umd64.dll is part of Intel Graphics Accelerator Drivers for Windows (R) and developed by Intel Corporation according to the igd10umd64.dll version information.

igd10umd64.dll's description is "LDDM User Mode Driver for Intel(R) Graphics Technology"

So, again an issue with the graphics driver, this time Intel, not AMD/ATI.

The usual recommendation: update the graphics driver, try lowering your graphic settings. If that doesn't help, try with an older graphics driver, happened more than once to me that that approach helped until the graphics card vendor finally fixed the issue some time later.

Link to post
Share on other sites
  • 0
36 minutes ago, VoidSquid said:

update the graphics driver, try lowering your graphic settings. If that doesn't help, try with an older graphics driver, happened more than once to me that that approach helped until the graphics card vendor finally fixed the issue some time later.

How?

Link to post
Share on other sites
  • 0

Current Intel drivers to be found here: https://downloadcenter.intel.com/product/80939/Graphics-Drivers

Windows allows you to revert to the previous driver: https://www.lifewire.com/how-to-roll-back-a-driver-in-windows-2619217

And if you want to install an older driver, first uninstall the current driver, reboot, do NOT accept the driver Windows suggests (which would be just the driver you had) but point to the *.inf file in the decompressed older driver directory.

Link to post
Share on other sites
  • 0
15 minutes ago, VoidSquid said:

Current Intel drivers to be found here: https://downloadcenter.intel.com/product/80939/Graphics-Drivers

Windows allows you to revert to the previous driver: https://www.lifewire.com/how-to-roll-back-a-driver-in-windows-2619217

And if you want to install an older driver, first uninstall the current driver, reboot, do NOT accept the driver Windows suggests (which would be just the driver you had) but point to the *.inf file in the decompressed older driver directory.

Never mind

Edited by Nigel J. Cardozo
Link to post
Share on other sites
  • 0
1 hour ago, VoidSquid said:

Current Intel drivers to be found here: https://downloadcenter.intel.com/product/80939/Graphics-Drivers

Windows allows you to revert to the previous driver: https://www.lifewire.com/how-to-roll-back-a-driver-in-windows-2619217

And if you want to install an older driver, first uninstall the current driver, reboot, do NOT accept the driver Windows suggests (which would be just the driver you had) but point to the *.inf file in the decompressed older driver directory.

Isn't there any other option?

Link to post
Share on other sites
  • 0
32 minutes ago, VoidSquid said:

I don't see any other options right now, maybe another fellow KSP player has some additional ideas?

I reverted back to the previous driver and I got some good and bad news

The bad news: I messed up my monitor. My screen is now like I have magnified my screen

The good news: KSP 1.9 is finally working

Edited by Nigel J. Cardozo
Link to post
Share on other sites
  • 0
2 minutes ago, Nigel J. Cardozo said:

My screen is now like I have magnified my screen

The good news: KSP 1.9 is finally working

Now that sounds like the resolution has changed, probably lower now, mind to check the numbers?

Edited by VoidSquid
Link to post
Share on other sites
This thread is quite old. Please consider starting a new thread rather than reviving this one.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...