PC Crashes from playing the game

[Gekker]

Crashing constantly here, after being a host.
Except it's not the game that crashes, it's the whole PC. It just goes black screen, without even a BSOD.
Windows logs don't say anything of worth about it, only that the system stopped working unexpectedly.
First i suddenly crash in a middle of a mission, even when playing solo, then, after i try to load the game itself, i crash every time i just load in in the Rig.
What i tried - tried to clean some stuff on the PC (regedit), that didn't work. Then deleted from HDD and installed on SSD, worked for a while. Was ok when i played in someone's lobby, then i started my own lobby, and had the same crash mid-game.
I won't even try to load the game *again*, it will most likely crash the PC again. I don't want to test my hardware's abilities to handle such critical errors.
Don't have that in any other game, don't have such random crashes at all, and didn't have such problems with DRG before, back from Update14 lol.

[RaindropperinG]

I would verify the game files integrity and then restart Steam.

If you're launching DRG in Dx12, try Dx11 ( or the other way around ) and see if anything changes.

On top of that, I would also launch the game in Safe Mode.

Make sure that your antivirus didn't begin interfering with DRG; if it has, you can try placing the game files folder into an Exception category.

By the way, what are your pc specs?

[Johnno]

Make sure to update your graphics drivers as well.

[Gekker]

antivirus is taken care of.
i'll try safe mode maybe.

OS: Win10
GPU: GTX 1060 3GB ASUS
RAM: 16GB x2
CPU: i5-10600KF
and old HDD(like 10 y.o.) and kind-of-new SSD(like1-2 y.o.)

[Gekker]

Originally posted by Johnno:

Make sure to update your graphics drivers as well.

as if that did anything ever

[Gekker]

safe mode didn't do it, though at least only game crashed this time.
sent a report with the ingame tool

[Johnno]

Originally posted by Gekker:

as if that did anything ever

Oookay. And you expect us to give you some miracle fix that solves your issue with zero information?

Yes, updating drivers certainly can help, solved my crashing after season 2 started because they updated the engine and I had old drivers.

But hey don't bother, enjoy crashing.

[Gekker]

Originally posted by Johnno:

Originally posted by Gekker:

as if that did anything ever

Oookay. And you expect us to give you some miracle fix that solves your issue with zero information?

Yes, updating drivers certainly can help, solved my crashing after season 2 started because they updated the engine and I had old drivers.

But hey don't bother, enjoy crashing.

nah i expect to add 1 more ticket for devs to see so they'll notice the issue and look into it, because seems lke i'm not the only one having similar crashes after recent updates.
i did that because i couldn't even send a crash report before because whole PC was crashing.
well if the driver thing worked for you, the i'll try it too. i just was doing it before for different issues with games, several times, and it didn't do a thing so i got used to that.
i'll try that and then launch in the safe mode again, since it doesn't crash my pc.

[ShugoTheRipper]

Has obvious hardware issue, but...

Originally posted by Gekker:

I don't want to test my hardware's abilities to handle such critical errors.

... the issue is hardware or driver related if you system just straight up dies 99.999% of the time.

The game is not causing a rare fault, your system is faulty and you have just been getting lucky. Good luck with fixing it without troubleshooting correctly.

I amazed anyone wasted time on you from reading over the initial post and the follow up conversations.

Edit:

So I dug up my primer on simple testing, not sure if it will help you, but it might help others with better attitudes who stumble across this.

Originally posted by ShugoTheRipper:

I have a couple tips to weed out a unstable GPU or bad GPU drivers.

1: DDU video drivers
https://www.youtube.com/watch?v=xn8z39tiEL0
2: Get Kombustor:
https://geeks3d.com/furmark/kombustor/

3: Get Heaven
https://benchmark.unigine.com/heaven

4: Run the GPU burn in test in Kombustor. (15+ minutes)

5: Run Heaven Synthetic (15+ minutes)

6: Does the system blue-screen?

If NO:
- Probably not the GPU

If YES:
- It could be the GPU
- Try Nvidia Debug mode or Equivalent AMD repeat steps 4 to 6

Tips to weed out a unstable CPU or RAM.

1: Get prime95
https://www.mersenne.org/download/

2: Run Blended torture test

3: Does the system blue-screen?

If NO:
- Probably not the CPU

If YES:
- It could be the CPU or RAM

If it passed all of that

1: Start up prime95 blended torture test

2: Start up Kombustor 4-8K GPU test (The goal is to fully load the GPU while having the CPU do dynamic sweeps.)

3: Does the system blue-screen?

If NO:
- Troubleshooting gets hard at this point as you need to start doing bios level and or registry level stuff.

If YES:
- Something is not playing nice with something else. It could even be a seedy PSU.

NOTE: None of this should make your system overheat. If it does that; that is the fault on the cooling design or setup. Bad temps can hurt stability; but it is more rare with modern hardware.

Blue screen, hard shutdown, same thing. Note temps, and clock speeds. maybe someone will help you then.

[Gekker]

Originally posted by ShugoTheRipper:

Has obvious hardware issue, but...

Originally posted by Gekker:

I don't want to test my hardware's abilities to handle such critical errors.

... the issue is hardware or driver related if you system just straight up dies 99.999% of the time.

The game is not causing a rare fault, your system is faulty and you have just been getting lucky. Good luck with fixing it without troubleshooting correctly.

I amazed anyone wasted time on you from reading over the initial post and the follow up conversations.

Edit:

So I dug up my primer on simple testing, not sure if it will help you, but it might help others with better attitudes who stumble across this.

Originally posted by ShugoTheRipper:

I have a couple tips to weed out a unstable GPU or bad GPU drivers.

1: DDU video drivers
https://www.youtube.com/watch?v=xn8z39tiEL0
2: Get Kombustor:
https://geeks3d.com/furmark/kombustor/

3: Get Heaven
https://benchmark.unigine.com/heaven

4: Run the GPU burn in test in Kombustor. (15+ minutes)

5: Run Heaven Synthetic (15+ minutes)

6: Does the system blue-screen?

If NO:
- Probably not the GPU

If YES:
- It could be the GPU
- Try Nvidia Debug mode or Equivalent AMD repeat steps 4 to 6

Tips to weed out a unstable CPU or RAM.

1: Get prime95
https://www.mersenne.org/download/

2: Run Blended torture test

3: Does the system blue-screen?

If NO:
- Probably not the CPU

If YES:
- It could be the CPU or RAM

If it passed all of that

1: Start up prime95 blended torture test

2: Start up Kombustor 4-8K GPU test (The goal is to fully load the GPU while having the CPU do dynamic sweeps.)

3: Does the system blue-screen?

If NO:
- Troubleshooting gets hard at this point as you need to start doing bios level and or registry level stuff.

If YES:
- Something is not playing nice with something else. It could even be a seedy PSU.

NOTE: None of this should make your system overheat. If it does that; that is the fault on the cooling design or setup. Bad temps can hurt stability; but it is more rare with modern hardware.

Blue screen, hard shutdown, same thing. Note temps, and clock speeds. maybe someone will help you then.

???
Obvious hardware issue?
While i'm playing, none of the hardware i use get loaded to the point where it might be the issue, all the hardware runs at relatively low% load during playing.
More than that, the way the issue is recurring RIGHT during load of the mission, and the way the reinstall HELPED meant that it is NOT a hardware issue. It might've been HDD problem but it's not since i just tested it on a different disk.
MORE than that, it started to occur only after recent updates, and in solo plays.
I'm not going to stress-test all my hardware because of the issue that is obviously not bound to hardware not being capable to handle the load, since it's not even being loaded that much.

Also i don't have anything overclocked.

[Amble]

I think you're too easily discounting the possibility that it's a hardware issue, even though it seems unlikely on paper. I once was in a situation where this game was crashing (not my entire computer, just the game) and it ended up being my GPU's clock speed that was causing it. GPU wasn't overclocked, it was crashing at stock clocks, and lowering the clock by 50Mhz eliminated the crashes, even though no other game was crashing.

In this case it was technically a hardware fault that exclusively this game exposed. I'm sure some other games out there could've done it too, but despite having that GPU for 5 years I only found this game to cause problems.

I've had other cases where overclocks appear 100% stable, sometimes for years, and then something that doesn't even load the overclocked component up heavily causes crashes. When it comes to instability that isn't temperature related system load is a nearly irrelevant factor. Your hardware's age also is a thing to consider, stock clocks are more likely to become unstable over time.

Just an anecdote for your thought, sorry it's so long.

Computer software is complicated and unpredictable with how it will interact with your hardware, and as I just described testing your hardware with strenuous programs might not reveal anything wrong, which would lead you to again believe its DRG's fault while it might still not be the case.

It could also just as easily be the case, this game is not 100% stable, and you should make issue reports with as much info as possible.

However, stress testing your hardware doesn't take too long, and it's important that you do it before you make issue reports as it'll give your claim more validity if it is an issue with the game.

[Gekker]

Originally posted by Amble:

I think you're too easily discounting the possibility that it's a hardware issue, even though it seems unlikely on paper. I once was in a situation where this game was crashing (not my entire computer, just the game) and it ended up being my GPU's clock speed that was causing it. GPU wasn't overclocked, it was crashing at stock clocks, and lowering the clock by 50Mhz eliminated the crashes, even though no other game was crashing.

In this case it was technically a hardware fault that exclusively this game exposed. I'm sure some other games out there could've done it too, but despite having that GPU for 5 years I only found this game to cause problems.

I've had other cases where overclocks appear 100% stable, sometimes for years, and then something that doesn't even load the overclocked component up heavily causes crashes. When it comes to instability that isn't temperature related system load is a nearly irrelevant factor. Your hardware's age also is a thing to consider, stock clocks are more likely to become unstable over time.

Just an anecdote for your thought, sorry it's so long.

Computer software is complicated and unpredictable with how it will interact with your hardware, and as I just described testing your hardware with strenuous programs might not reveal anything wrong, which would lead you to again believe its DRG's fault while it might still not be the case.

It could also just as easily be the case, this game is not 100% stable, and you should make issue reports with as much info as possible.

However, stress testing your hardware doesn't take too long, and it's important that you do it before you make issue reports as it'll give your claim more validity if it is an issue with the game.

sounds interesting, unusual that changing the clock speed made things work.
as it is for me:
1) i'll try other things first, like drivers and stuff.
2) stress-test is a last resort. The reason is simple - if my hardware fails the test, that'd mean i couldn't do much but have to replace it, and pray it wouldn't break before i get a replacement. But i don't have resources to buy a new GPU, and don't want to do so anyway.
If this game is producing such errors, i'll just go play something else. *IF* any *other* game going to produce similar errors, then i'll indeed assume that it's the hardware's fault, and resort to stress-testing, and will work towards that. But i'm not going to assume the hardware fault right away, i will explore all the other possibilities first.

[Amble]

Originally posted by Gekker:

sounds interesting, unusual that changing the clock speed made things work.
as it is for me:
1) i'll try other things first, like drivers and stuff.
2) stress-test is a last resort. The reason is simple - if my hardware fails the test, that'd mean i couldn't do much but have to replace it, and pray it wouldn't break before i get a replacement. But i don't have resources to buy a new GPU, and don't want to do so anyway.
If this game is producing such errors, i'll just go play something else. *IF* any *other* game going to produce similar errors, then i'll indeed assume that it's the hardware's fault, and resort to stress-testing, and will work towards that. But i'm not going to assume the hardware fault right away, i will explore all the other possibilities first.

It's not that unusual, lots of components come out of the factory tuned near their limits. It's possible to roll so badly on the silicone lottery that your CPU or GPU or anything really is unstable at stock speeds, or becomes unstable with age.
I've noticed Unreal Engine games specifically have a tendency to expose really particular hardware faults that other games don't. I have no clue why.

Anyway, I understand where you're coming from. Troubleshooting hardware is never a fun thing to do and one game causing problems is almost never a good reason to go all in doing that.

Drivers are a good place to start if your drivers are actually out of date. Along with other simple and obvious things like shutting off every background process, disabling overlays, or even resetting Windows. I hope you figure it out and get back in the mines with us.

[Gekker]

so...
I updated Nvidia drivers, played several games fine, with no crashes.
I thought that was it, everything works fine now, but then i updated "riva tuner statistics server", a completely different program(to check the GPU load during the game), and game started crashing the PC even earlier now, during first loading, even in "safe mode".

Of course, i disabled that program i just updated, and tried to launch again - nope, still a PC crash on load. Even if it was just 10 minutes ago that i finished a mission in the game.

i don't understand anything at this point, screw this, i'll go play something else.
Maybe the issue is in GPU indeed, but for now i'm not going to delve into this.
Thanks for suggestions everyone.

[Gekker]

1) now i have this problem not only in DRG. same type of crashes.
2) both GPU and CPU stress-tests has shown good results, no crashing in process(furmark,cpu-z. No overheating, highest temps - 70 on GPU and 57 on CPU).
3) some other games do not cause the crashes, it seems, even if they are too GPU\CPU heavy (elden ring).
4) returning Nvidia settings to default didn't help
5) noticed a weird thing - it crashes when i'm about to load something "heavy", like loading a level after a cutscene, or loading a new cave in DRG after passing though dirt. Though both GPU\CPU tests succeded.
What i think it could be - either some software, or power supply issue, where it struggles to give a lot of power in a moment (though such thing sholdn't be the issue for DRG since it keeps up about the same load during levels, no?...)
What i will try now is just reinstall windows, and if that doesn't work, open the power supply and just visually check if anything is wrong (it doesn't overheat as well btw, i oil the fan inside it from time to time).
Oh, i also should check the SSD that has my OS installed on, before doing all that.

[Paintbrush]

highly anecdotal, but recently had to replace my sata cables as they kept falling out from apparently being too old after ~ 10 years.

also wouldn't hurt to do a check disk, memory test, or fresh install.