Game makes my computer to restart, with or without BSOD

[Lavrentiy Beria]

It typically happened during/after the 2nd or 3rd game in a row, and I was constantly monitoring my CPU/GPU's temperature during game and they all kinda fine.

So... is this some software/hardware compatibility issue? I'm using 13900k + 1080Ti

I read the BSOD report and it says "ntoskrnl.exe" crashed, which is basically the os kernel, useless info

Windbg's output:
CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.

[Tysakasa]

Without more information on the error (outside of it being ntoskrnl.exe that crashed), would recommend making sure your drivers are up to date (not just your CPU and GPU drivers, but your other hardware as well), run a health check on your drive and maybe do a Windows repair. Haven't had the game take my system out (actually don't remember the last time my system BSOD'd or just peaced out on me after disabling a keyboard related feature).

[MistaM]

Normally you get a protocol/minidump after crash. Google may help for that. Just "ntkoskernl.exe" doesnt help. Maybe it's a driver issue, maybe a RAM issue. Nobody can tell you that. But when checking the protocol/minidump you have a better chance to find what caused that crash. But you could update/reinstall all your drivers for now and see if it happens again after that. You could also test your RAM before.

[Lavrentiy Beria]

Originally posted by Tysakasa:

Without more information on the error (outside of it being ntoskrnl.exe that crashed), would recommend making sure your drivers are up to date (not just your CPU and GPU drivers, but your other hardware as well), run a health check on your drive and maybe do a Windows repair. Haven't had the game take my system out (actually don't remember the last time my system BSOD'd or just peaced out on me after disabling a keyboard related feature).

The reason why I suspect the problem is somehow with this game is because other games, including some AAA ones, works fine on my computer... and me too, I don't remember the last time my system BSOD'd as well, until this thing.
And thanks, I'm gonna check for drivers.

[Tysakasa]

Yeah, it doesn't help that the game is also in early access, so you don't always know where the issue is coming from, could be a configuration that the game doesn't like and throws a fit with it, could just be an old driver that happens to disagree with the game.

[King]

I get a blue screen error sometimes of "kernel security check failure" when launching. Its really inconsistent.

im running a RTX 74070ti with the latest driver released a few days ago.

[mcnoople]

How much ram do you have? How much is being utilized when it crashes. I had this happening last year and doubling the ram cured it. I went from 16 to 32 even though the game only "needed" 16.

[Lavrentiy Beria]

Originally posted by mcnoople:

How much ram do you have? How much is being utilized when it crashes. I had this happening last year and doubling the ram cured it. I went from 16 to 32 even though the game only "needed" 16.

32, and not so much (I closed all other apps including Chrome lol)

I don't quite think this is a performance issue, as temperature, CPU usage, and RAM usage looks good.

[Hurricane]

Sounds like an hardware issue. The usual first suspect is the RAM.
Try running memtest86+ (the + is important) for a few passes (one pass should be enough but more can sometimes find a rare issue). It should take anything between 15 minutes and a few hours.
If the RAM is defective, either lower the clock (some XMP profiles aren't supported on every motherboard, especially with DDR5) or replace them.
Check the appropriate motherboard model/RAM compatibility page.

[Lavrentiy Beria]

Originally posted by Hurricane:

Sounds like an hardware issue. The usual first suspect is the RAM.
Try running memtest86+ (the + is important) for a few passes (one pass should be enough but more can sometimes find a rare issue). It should take anything between 15 minutes and a few hours.
If the RAM is defective, either lower the clock (some XMP profiles aren't supported on every motherboard, especially with DDR5) or replace them.
Check the appropriate motherboard model/RAM compatibility page.

I tried Windows Memory Diagnostic and it succeeded without any error

---
I think if it is RAM defection, I definitely gonna experience similar BSOD in other games/softwares/scenarios... but it only happens in this game in particular.

[Grimmers]

Win Mem DIagnostic rarely finds problems. But yeah, can scour logs and run stability tests for days with these sort of vague issues, but unless it's a low hanging fruit that a driver update or basic testing easily finds you're better off with just the process of elimination.

Is it hardware or software? Install a fresh windows on a 2nd drive or run a LiveUSB, if it's still BSOD'ing there then it's hardware. Is it a bad ram stick? Run your system with 1 stick at a time and see. If you've nearly eliminated everything and it feels like it's making no sense, it's probably motherboard or PSU.

[Hurricane]

Originally posted by realTadokoroKouji:

Originally posted by Hurricane:

Sounds like an hardware issue. The usual first suspect is the RAM.
Try running memtest86+ (the + is important) for a few passes (one pass should be enough but more can sometimes find a rare issue). It should take anything between 15 minutes and a few hours.
If the RAM is defective, either lower the clock (some XMP profiles aren't supported on every motherboard, especially with DDR5) or replace them.
Check the appropriate motherboard model/RAM compatibility page.

I tried Windows Memory Diagnostic and it succeeded without any error

---
I think if it is RAM defection, I definitely gonna experience similar BSOD in other games/softwares/scenarios... but it only happens in this game in particular.

I specified memtest86+ because the one from Windows is worthless (at least last time I've tried it) and the other memtest86 (without the +) isn't to be tried either.
And RAM triggers issues with patterns of value in specific banks. Not everything will trigger the issue and not always. It's why the real test is so long.

Also, this game isn't some kind of magical thing. It cannot crash a system that hasn't got some issue to begin with.

Anyway, I know the test I would be running right now if I were you. The first step is always to eliminate the one culprit that makes sense. (Given you have stated your temps, and thus usage, are all "fine")

You should hope it's the RAM though because any other issue is way more painful to detect an fix.

[Hurricane]

Originally posted by Grimmers:

Win Mem DIagnostic rarely finds problems. But yeah, can scour logs and run stability tests for days with these sort of vague issues, but unless it's a low hanging fruit that a driver update or basic testing easily finds you're better off with just the process of elimination.

Is it hardware or software? Install a fresh windows on a 2nd drive or run a LiveUSB, if it's still BSOD'ing there then it's hardware. Is it a bad ram stick? Run your system with 1 stick at a time and see. If you've nearly eliminated everything and it feels like it's making no sense, it's probably motherboard or PSU.

And if's the issue only happen on dual-channel access, removing the stick will not tell which one is the issue, assuming its not both.
An efficient test is more accurate and doesn't require to fiddle with the hardware.

[Lavrentiy Beria]

Originally posted by Hurricane:

Originally posted by realTadokoroKouji:

I tried Windows Memory Diagnostic and it succeeded without any error

---
I think if it is RAM defection, I definitely gonna experience similar BSOD in other games/softwares/scenarios... but it only happens in this game in particular.

I specified memtest86+ because the one from Windows is worthless (at least last time I've tried it) and the other memtest86 (without the +) isn't to be tried either.
And RAM triggers issues with patterns of value in specific banks. Not everything will trigger the issue and not always. It's why the real test is so long.

Also, this game isn't some kind of magical thing. It cannot crash a system that hasn't got some issue to begin with.

Anyway, I know the test I would be running right now if I were you. The first step is always to eliminate the one culprit that makes sense. (Given you have stated your temps, and thus usage, are all "fine")

You should hope it's the RAM though because any other issue is way more painful to detect an fix.

I tried memtest64+ several times yesterday and all tests passed...

[Dethesius]

Originally posted by realTadokoroKouji:

You're not going to like this response and that's fine. This is my personal, educated opinion on the matter. Take it for what it's worth and do with it as you will.

First: A little background on my answer.

Many games in Early Access aren't often optimized yet and the FPS sometimes run in the thousands. This causes a lot of stress on your resources, especially your GPU. This is just a broad explanation but more or less that is happening.

Sometimes (and you will find this most common in games like this) this extra stress caused by heat and really determine if you bought into the lotto of crappy, bad made cards. They are out there under every manufacturer.

When you apply a lot of heat to a card that may be great in some circumstances (because the resources haven't been fully used) will fail when the resources that are faulty start getting used.

The same is true for Memory.

So... In conclusion.

You could have a faulty GPU or Memory. The only way you'll know is if you benchmark your system until it happens. Benchmark your GPU and Memory separate so you'll know which ones.


I've had this happen a few times over the years. Once was a bag GPU and once were a bad batch of Memory. Both of which I had to run in benchmarks, one for hours before it presented itself but the issue was always the same. In games that ran hot were the only times my card or system had issues in those cases. Never in any other games.

[Dethesius]

btw, this is not a solution but it 'might' help?

Depending on what you have... You can go to your nvidia settings and set your FPS to match your screen resolution or whatever res your're display is set at. This will help keep some of the excess resources from being used. You might also need to turn down some of your settings in here - also depending on your gear.



What do you have in the way of memory?