Jump to content

VoidSquid

Members
  • Posts

    1,841
  • Joined

  • Last visited

Community Answers

  1. VoidSquid's post in Not seeing any of the expansion parts was marked as the answer   
    I see a lot of entries like "UnauthorizedAccessException: Access to the path "C:\Program Files\KSP_win64\GameData\SquadExpansion\Serenity\Parts\Aero\Assets\noseconeVS.mu" is denied.", quite possible that the NTFS permissions are causing the problem. I suggest you copy the complete KSP folder to the root directory and try playing from that.
  2. VoidSquid's post in FMRS "Jump to Separation" causes crash (1.7.3, modded) was marked as the answer   
    WinDebug says:
    Another of the typical and hard to analyze access violations (ExceptionCode: c0000005 (Access violation))
    These 4 DLL's are mentioned in particular as WinDebug for obvious reasons can't .load the respective symbol files:
    *** WARNING: Unable to verify timestamp for K_FPS64.dll
    *** WARNING: Unable to verify timestamp for mono.dll
    *** WARNING: Unable to verify timestamp for atidxx64.dll
    *** WARNING: Unable to verify timestamp for tasks_core.dll
    Looking for the best (worst) candidate to blame here:
    k_fps64.dll is part of RazerCortex and developed by Razer Inc. 
    mono.dll is part of KSP
    atidxx64.dll belongs to the ATI/AMD graphics drivers
    tasks_core.dll belongs to Microsoft Visual Studio
    My take: the crash is either caused by the Razor driver (mouse, I'd assume), or, my personal candidate here, by the ATI/AMD graphics driver.
    I suggest you update/revert graphic driver in the first place. If that doesn't help, update/revert your Razor driver/software.
  3. VoidSquid's post in Strange behaviour in modded install was marked as the answer   
    This is the WinDbg output from your second dump file:
    A very common error, c0000005 means access violation. Here the application tried to read from memory with an invalid address: APPLICATION_FAULT_NULL_CLASS_PTR_READ_INVALID_POINTER_READ
    What is interesting: 
    The fault address in not in any loaded module
    And:
    ERROR: Module load completed but symbols could not be loaded for nvoglv64.dll
    ERROR: Module load completed but symbols could not be loaded for mono.dll
    Per my understanding, the module causing the invalid call would then be in either mono.dll, or, and this is my candidate number one, in nvoglv64.dll
    nvoglv64.dll belongs to your Nvidia graphics driver, I suggest you try updating it.
×
×
  • Create New...