1. Welcome to the Starbound support forums. Please check the support FAQs before posting: http://playstarbound.com/support

Closed "Launch Starbound" Causes Error dialogs.

Discussion in 'Starbound Support' started by NethanielShade, Mar 15, 2015.

Thread Status:
Not open for further replies.
  1. NethanielShade

    NethanielShade Void-Bound Voyager

    [​IMG]
    [​IMG]
    [​IMG]
    [​IMG]

    When I try to launch Starbound, these error messages pop up in quick succession. I recall having this problem and fixing it a long time ago (I just redownloaded Starbound today to play with the new update) but I don't remember what could have caused this. Any ideas?
     
  2. nimmerland

    nimmerland Existential Complex

  3. NethanielShade

    NethanielShade Void-Bound Voyager

    That is caused by the program WebWatcher, which I do not have. He has a similar error going off, yes, but the thing that caused that is different for him. Also deleting the pack.pak didn't work. I will post my log here for anyone to help.

    Start logging at: 2015-03-15 16:41:43.518
    [16:41:43.518] Info: Star::Root using bootstrap file 'C:\Program Files\Steam\steamapps\common\Starbound\win32\sbboot.config'
    [16:41:43.518] Info: Star::Root using storage directory 'C:\Program Files\Steam\steamapps\common\Starbound\giraffe_storage\'
    [16:41:43.518] Info: Preparing Star::Root...
    [16:41:43.519] Info: Loading Configuration with config file: 'starbound.config'
    [16:41:43.519] Info: Loading Star::Configuration from 'Just (.\..\giraffe_storage\starbound.config)'
    [16:41:43.712] Info: Writing Star::Configuration to '.\..\giraffe_storage\starbound.config'
    [16:41:43.720] Info: Initializing Star::Root with 2 assets sources
    [16:41:43.720] Info: Done preparing Star::Root.
    [16:41:43.720] Info: Client version 'Beta v. Upbeat Giraffe - Update 2' Protocol: 668
    [16:41:43.720] Info: Initialized SDL
    [16:41:43.741] Info: Initialized SDL Video
    [16:41:43.762] Info: Initialized SDL Joystick
    [16:41:43.772] Error: Access violation detected at 0x7c83231f (Read of address 0x4e90000)
    [16:41:44.049] Error: Stack Trace...
    SignalHandlerImpl::sehTrampoline()
    IsBadStringPtrA
    0460709C shim_fcfmfbd.dll
    0460737F shim_fcfmfbd.dll
    0460740D shim_fcfmfbd.dll
    04607D30 shim_fcfmfbd.dll
    04602AC6 shim_fcfmfbd.dll
    04609B58 shim_fcfmfbd.dll
    04609BD5 shim_fcfmfbd.dll
    MoveWindow
    MoveWindow
    GetWindowTextLengthW
    KiUserCallbackDispatcher
    TF_UninitSystem
    MoveWindow
    MoveWindow
    GetWindowTextLengthW
    KiUserCallbackDispatcher
    PeekMessageA
    OverlayHookD3D3
    SDL_UnregisterApp
    SDL_PumpEvents
    SDL_PollEvent
    SDL_EventState
    SDL_JoystickEventState
    StarApplicationBase::StarApplicationBase()
    ClientApplication::ClientApplication()
    _SDL_main
    _console_main
     
  4. nimmerland

    nimmerland Existential Complex

    Are you using similar software like WebWatcher (AntiVirus / AntiMalware / preinstalled Bloatware)? The general point is not WebWatcher itself but a program that "hijacks Windows DLLs, and breaks the API calls Starbound uses".
    What about compatibility mode which is mentioned in the second thread above? Does it happen with 32bit OpenGL too?
     
  5. RvLesh

    RvLesh Parsec Taste Tester

    This is caused by the webwatcher engine, which you do have.

    That's the webwatcher engine's DLL.

    It is used by WebWatcher.

    There may be other monitoring garbage using the same series of garbage DLL names, but in exactly zero cases is this a Starbound problem.

    -----

    Run Spybot on the machine if you want to see what specific piece of software is causing the problem. It is the *ONLY* piece of antispyware software that reliable detects any of this borderline-illegal "monitoring software" garbage.
     
    Last edited: Mar 16, 2015
Thread Status:
Not open for further replies.

Share This Page