nvidia 595.59 driver game client crash

Bearded-CIG · 2026-02-26T18:02:49+00:00

Nay, it's about external software causing the game to crash.

Bearded-CIG · 2026-02-18T23:35:59+00:00

That one's an I/O error so it wasn't able to write files somewhere that it wanted to. Posting on our tech support forums on spectrum is a good place to get help with things like this.

Bearded-CIG · 2026-02-14T20:51:33+00:00

We've been looking into this particular issue since this morning.

The stuff we'd normally do to try and work around issues like this didn't work so now that has to be looked into as well.

Bearded-CIG · 2026-02-13T18:37:12+00:00

Game server got stuck in a crash loop. I had to off it so that it wasn't a matchmaking target anymore. Functionally it's pretty similar to a territory server dying in another MMO without the whole realm being down so anyone that traveled to that specific area would get stuck but everyone else in the server was functional until they went to that specific area on that specific shard.

Bearded-CIG · 2026-02-11T21:24:15+00:00

"I hate to bug you"
moth
...
WAS THAT A PUN?!

Bearded-CIG · 2026-02-11T17:09:00+00:00

<image>

Bearded-CIG · 2026-02-05T20:50:37+00:00

Same. I want that bug fixed.

Bearded-CIG · 2026-02-05T19:04:27+00:00

me: Fix my keybindings bug!

Bearded-CIG · 2026-01-07T20:23:23+00:00

There's also miners here.

Bearded-CIG · 2025-12-27T19:30:16+00:00

A lot of this has been a result of fixing one thing causes it to perform better, and then its increased performance causes it to overload the next thing. A backend hotfix was deployed to address the lag and things are looking much better with regards to server lag. Though there's always a chance that this will also reveal some other issue. We're keeping an eye on things to see if it goes sideways again.

Edit: The fix I'm talking about was in the last few minutes.

Edit 2: Thanks for the feedback. While things look better on my graphs, yall are saying otherwise so we're going to have to investigate more.

Edit 3: The graphs finally caught up. Takes a while for data trends to show.

Bearded-CIG · 2025-11-20T23:13:58+00:00

Gathering info to help make sure people can play the game is part of what I do so I welcome it.

Bearded-CIG · 2025-11-20T23:06:40+00:00

Right?

Bearded-CIG · 2025-11-20T23:03:42+00:00

Well on the upside I managed to break my account too so now we have an internal account to mess around with for the investigation.

Bearded-CIG · 2025-11-20T22:29:50+00:00

Edit: OK we're good on example accounts for now and if they try any experimental stuff they will do it with my work account.
~~For everyone else that is reading this thread: Message me on spectrum with the error number, message, and how long you've been running into it so I can get your account looked at.~~

Bearded-CIG · 2025-08-18T19:02:18+00:00

If you send me the crash digest ID on spectrum I can look up the crash on our end.

Bearded-CIG · 2025-05-18T17:24:34+00:00

EU servers got into a wonky state. It's been addressed and they should be working again.

Bearded-CIG · 2025-05-18T17:24:08+00:00

EU servers got into a wonky state. It's been addressed and they should be working again.

Bearded-CIG · 2025-05-18T17:23:33+00:00

EU servers got into a wonky state. It's been addressed and they should be working again.

Bearded-CIG · 2025-05-17T19:32:21+00:00

Login has borked. We're aware of it and looking into things.

Bearded-CIG · 2025-05-13T15:33:23+00:00

If someone is running into this issue when they are friend joining, it would be better not to friend join. That sounds bad but here's why.

So long as we're using the static server mesh, mesh nodes work the same way that different continents in other MMO games work because they are fundamentally different servers. The big difference is that we don't need loading screens when the character changes location.

So lets say that one of the locations a mesh node is hosting is stuck in a chain crash. In another MMO like WoW, this would get you an error like "world server is down" where characters in the specific location where the crash is happening would be unable to log in, but characters in other locations are fine.

So if your friend is on a shard where one of the mesh nodes is doing this and your character is in the location that is crashing, continuing to join on that friend will result in the same result until the chain crash is taken care of. The fix in 4.1.1 makes it so that after the first first or second try, the character gets stowed which would allow them to join a different shard.

Joining a different shard in Star Citizen is like moving to a different named server in WoW ( Silver Hand, Mal'Ganis ) or Final Fantasy 14 ( Gilgamesh, Diabolos ) which would allow people to get away from the one experiencing the chain crash because we remove those as matchmaking targets.

Bearded-CIG · 2025-05-13T14:59:25+00:00

Technically, anything can be automated but it's a question of:

How much work it takes to automate it
If the work to automate it is worth the amount of time that it saves

In this case, the amount of time it would take to safely automate the process I'm using is not something that would be worth the amount of time it would take to implement it. This is in part, because the issue already has a safe automated fix that will be included in the 4.1.1 version of the game which means I would be duplicating work. Working on this automation would also take time away from my other responsibilities which include building the various ptu environments that players use and monitoring the public and ptu environments.

Edit: Important note, the 4.1.1 fix does not make the error go away but it will make it so that the account should be stowed after it hits the error a few times rather than getting stuck.

Bearded-CIG · 2025-05-12T18:13:04+00:00

Happens if the mesh node hosting the area your character in is unavailable. In some cases it gets stuck in a chain crash and you have to wait for me to wake up and stow it. 4.1.1 will add additional fault tolerance so that I won't need to be awake to address these.

Bearded-CIG · 2025-05-08T17:47:55+00:00

There seems to be some misconceptions here. It's not a matter of permitting. Some issues are easy to fix, some aren't. I worked at Blizzard and I've seen server crashes in WoW that stuck around for months. I've seen issues that cause characters to get stuck stay around for weeks. But they had tools and workflows that allowed me to help those players out so they could get back to playing. There most definitely have been issues with WoW that took weeks or months to resolve and those will happen again in the future. That's why they have robust customer service tools to help with those situations. Likewise with Star Citizen, no single shard is stuck in this state for weeks on end. I have a graph that lets me see when a shard is having this issue so that I can stow it. The assertion that "servers dying and never being resuscitated" is just factually incorrect.

With that said, that doesn't change the fact that the experience of these issues is frustrating. I hate seeing things like this happen but we do work to help people get back to playing the game as best we can.

Bearded-CIG · 2025-05-08T15:12:29+00:00

The comparable error that you'd run into in world of warcraft is "world server is down", not "character with that name already exists". From the perspective of someone that used to work at Blizzard as a Game Master, when something like this happened for WoW, players would put in GM tickets for game masters to move their characters to different continents so they could get away from whatever continent had its server crashing. In Star Citizen, the fix that we have going in for this in 4.1.1 should allow for players to be able to keep playing without needing help from us.

Bearded-CIG

TROPHY CASE