Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Omnikuken]

Played the game for 6+ hours yesterday, nothing. Tried again this morning : 2 ATI driver crashes leading to BSODs. DDU'd the driver and installed the newest 1 (optionnal 19.8.5 from 8/12/2019). 1st launch : Java crashed on title screen

Problem signature:
  Problem Event Name:   AppHangB1
  Application Name:   java.exe
  Application Version:   7.0.790.15
  Application Timestamp:   552827be
  Hang Signature:   73cf
  Hang Type:   0
  OS Version:   6.1.7601.2.1.0.256.1
  Locale ID:   1033
  Additional Hang Signature 1:   73cf2bb9a36334f62c4cddf7ad0a9abd
  Additional Hang Signature 2:   3075
  Additional Hang Signature 3:   3075c6ee31a664ea147286f0f8bfc0be
  Additional Hang Signature 4:   73cf
  Additional Hang Signature 5:   73cf2bb9a36334f62c4cddf7ad0a9abd
  Additional Hang Signature 6:   3075
  Additional Hang Signature 7:   3075c6ee31a664ea147286f0f8bfc0be

I know AMD/ATI blows some major ass on OpenGL, but having to DDU and reinstall drivers daily gets old fast (not blaming the game nor the dev(s)) 

[Alex]

Argh! Hmm. Is there an hs_err_pid<number>.log file somewhere in Starsector/ or Starsector/starsector-core? Might possibly help to see what's in it, though I'd expect there's a stack trace in there saying it crashed in the graphics driver. Still, wouldn't hurt to make sure.

But, yeah, a BSOD to me indicates some kind of system-level or (less likely) hardware issue. It could be that it's only triggered when you run something using OpenGL...

[Omnikuken]

Nope, no hs_err anywhere.

Maybe unrelated (since it crashed on title screen) : 1 of them BSOD screwed my save and had to "un-bak" them and remove the originals, which the game loaded fine before dying in a blazing hell of crap drivers

[Alex]

No hs_err is not a great sign, means it's crashing very ungracefully.

You're not running with mods, are you? If so, might make sense to disable GraphicsLib from its settings file.

Also: did the crashing seem related to saving or loading? I guess at *this* point it's crashing at the title screen so that isn't, but before.

[Omnikuken]

Yes, I run mods. Though not running mods means not playing the game at all (since I already got most of vanilla done and not much point playing it now)

Got another Java crash while in Codex scolling around ship hulls

Problem Event Name:   AppHangB1
  Application Name:   java.exe
  Application Version:   7.0.790.15
  Application Timestamp:   552827be
  Hang Signature:   a843
  Hang Type:   0
  OS Version:   6.1.7601.2.1.0.256.1
  Locale ID:   1033
  Additional Hang Signature 1:   a8439c20c800a0095fb6771b1ed6cb4e
  Additional Hang Signature 2:   80cb
  Additional Hang Signature 3:   80cbd220ad6b85640db46f709494fc45
  Additional Hang Signature 4:   a843
  Additional Hang Signature 5:   a8439c20c800a0095fb6771b1ed6cb4e
  Additional Hang Signature 6:   80cb
  Additional Hang Signature 7:   80cbd220ad6b85640db46f709494fc45

And again, no crash dump/log

For your question : most BSOD happen either in space travel or in combat, though always randomly and not really replicable (like said in OP, played non-stop for 5-6 hours yesterday and nothing happened)

[Alex]

Re: mods - right, that's why I was suggesting disabling GraphicsLib from its settings file, so you can still run with mods but without the graphics modifications it provides. A different and less-demanding rendering path might well avoid those crashes.

Let me move this to the modded bug reports subforum - unless you're seeing the same crashes in vanilla as well? Well, either way, doesn't matter too much where the thread is.

[Omnikuken]

Put Graphicslib's ini to false (shaderlib, hope that was the right 1), loaded into the game fine and Java crashed during 1st fight

Problem Event Name:   AppHangB1
  Application Name:   java.exe
  Application Version:   7.0.790.15
  Application Timestamp:   552827be
  Hang Signature:   a619
  Hang Type:   0
  OS Version:   6.1.7601.2.1.0.256.1
  Locale ID:   1033
  Additional Hang Signature 1:   a619ebb8f9cc8e0f704b1f370d2373a7
  Additional Hang Signature 2:   6a33
  Additional Hang Signature 3:   6a330381b5257df1b4ad1a1deee2ffc5
  Additional Hang Signature 4:   a619
  Additional Hang Signature 5:   a619ebb8f9cc8e0f704b1f370d2373a7
  Additional Hang Signature 6:   6a33
  Additional Hang Signature 7:   6a330381b5257df1b4ad1a1deee2ffc5

Still no report and dunno why it keeps dying like that. Guess powering down PC for the night and reloading the game this morning screwed all of my stuff .... I still blame AMD for everything though

[Alex]

Hmm, it ought to be GraphicsLib, not ShaderLib. If it's ShaderLib, then that makes me wonder what version of the game you're running, since that's from a while back.

[Omnikuken]

# GLOBAL OPTIONS #
    "enableShaders":false, # Default: true
        # If you set this to false, ShaderLib will do nothing
        # Set to false only if your computer cannot handle ShaderLib but you need it active for compatibility
        # Requires GeForce FX 5500, Radeon 9500, Intel GMA 4500, or newer
        # Recommended GeForce 6800, Radeon X850, Intel HD Graphics 3000, or better
    "use64BitBuffer":true, # Default: false
        # This causes various usages of the auxiliary texture buffer to be more accurate, but is unsupported by older cards and uses more GPU memory
        # If you are getting strangely bad performance, try turning this off
    "extraScreenClear":false, # Default: true
        # This clears the screen an extra time, which can lead to cleaner shaders and behavior
        # Takes a hit on fill rate; low-end graphics cards should turn this option off
    "toggleKey":197, # Default: Pause/Break (197)
    "reloadKey":68, # Default: F10 (68)
        # This key reloads the settings, making it easier to tweak the graphics options

That's what I get in graphicslib.ini, there's a bunch of stuff after that but it's just lights and shader options

[Alex]

No yeah that looks right, I just meant that if your folder is named ShaderLib, then that's pretty out-of-date and thus potentially problematic or at least relevant.

[Omnikuken]

Game and most mods aren't a week old on this HDD. I'm still wondering whose fault is the more prominent to blame : AMD for sucking ass on OpenGL or Java for not liking the game. My PC is too godly to even think of blaming it for the woes (joke) ..... Even more thoughtful : how in the infinite depths of coding hell can 1 game/program work flawlessly for 6 hours 1 day and BSOD/crash every 2 mins the next, with no changes made anywhere 

[Alex]

AMD is definitely... let's say not ideal. But, if something worked and then all of a sudden doesn't, them something definitely changed.

It could be something that got auto-updated - either a driver, or some piece of software. It could be something that's running now that wasn't running before. For example, MSI Afterburner is known to cause major issues. Something like an anti-virus conceivably could, as well. Or it could be a hardware issue.

Have you tried running the game in compatibility mode for Windows 7, btw? Might be worth a shot. I'd also try running it as administrator. (Right-click, run as administrator.)

[Omnikuken]

No anti-virus, no MSI stuff and already on Win 7 ....

It really seems to be 1 of the mods crapping itself overnight, just did a vanilla tutorial run and nothing died. Now to check which 1 is the culprit ......

Random thought : default vmparams is 1.5GB for -xms, maybe juggling with that could do something ? Have mine on 3GB since before the crashes and maybe that's what's choking it down to the point of crashing. Really random. Or do another clean install and re-mod everything ?

[Alex]

Depends on how much RAM you have - if you have 4 gigs or less, then 3 gigs in vmparams is too much, but otherwise should be fine. Make sure you set both the Xms and Xmx values, though, not just one of them.

(Running checkdisk may be worth a shot, but I suppose that's not without its risks...)

[Omnikuken]

Most probable culprits : AMD drivers being the crap they are, random mod going crazy, my card dying slowly on me (and only for this game) ....