14 Minutes, 2 BSOD's, 1 WTF?

[LRonHubbard]

My set-up I'm running should have zero issues running this game:

Ryzen 7 7700x
4070 Ti Super
32gb RAM

First run through after the cutscenes in the beginning it began to audio stutter the moment it was transitioning then bam, BSOD and restart.

Open NVIDIA app, lower all settings to low and global illum, off.

Still BSOD' again.

Like wtf? How is this happening?
I've also read of it bricking peoples ssd's?

I really want to play the game but I don't want to put my hardware at risk. How is a game even doing this?

[Mandalorian Deathknight]

if you are getting a blue screen then its something with the cooling on your side
check the pump if you dont feel a constant kicking in the lines then the pump is dying
also check the temps

[LRonHubbard]

Originally posted by Mandalorian Deathknight:

if you are getting a blue screen then its something with the cooling on your side
check the pump if you dont feel a constant kicking in the lines then the pump is dying

My aio is completely fine. I hear it 24/7. Never had this issue until I literally installed and ran the game.

I run unreal engine and blender completely fine when I do renders. I'm on top of my machine. This is not "user error".

[Heineken]

The game crashes, it most likely is not the caused of BSOD. You might need to T/S some more. It sounds like a faulty hardware..

[Doomvora]

Originally posted by go_djentle:

My set-up I'm running should have zero issues running this game:

Ryzen 7 7700x
4070 Ti Super
32gb RAM

First run through after the cutscenes in the beginning it began to audio stutter the moment it was transitioning then bam, BSOD and restart.

Open NVIDIA app, lower all settings to low and global illum, off.

Still BSOD' again.

Like wtf? How is this happening?
I've also read of it bricking peoples ssd's?

I really want to play the game but I don't want to put my hardware at risk. How is a game even doing this?

The minidump should give you an indication as to possible causes.

[Quibz]

Verify game files and check file permissions for the game. It shouldn't cause BSODs unless its trying to interact with an outside file system it doesnt have access to or some file system is corrupted.

Crashing is happening to me now this patch, but BSODs are a you problem

[LRonHubbard]

Originally posted by Heineken:

The game crashes, it most likely is not the caused of BSOD. You might need to T/S some more. It sounds like a faulty hardware..

I literally got a message from the games engine for a crash report after the 1st 2 bsod's. I'm telling you all, it's not faulty hardware. I run diagnostics on my machine nearly every day. I have ran games since this occurred, other games have not caused this issue. I'm not the only person this is happening to either regarding this specific game.

[Atomicdeath]

45 hours in an i've only had one ctd. If you're getting a blue screen it's an error on your end.

[Quibz]

Originally posted by go_djentle:

Originally posted by Heineken:

The game crashes, it most likely is not the caused of BSOD. You might need to T/S some more. It sounds like a faulty hardware..

I literally got a message from the games engine for a crash report after the 1st 2 bsod's. I'm telling you all, it's not faulty hardware. I run diagnostics on my machine nearly every day. I have ran games since this occurred, other games have not caused this issue. I'm not the only person this is happening to either regarding this specific game.

Engine crashing is happening to everyone, yes. BSODs is 100% on your system. Literally no other way to put it.

Saying the game is "causing" your BSODs is a vague way of saying that the engine the game is using is trying to access something it doesn't have access to, but should. Or that its accessing something that is corrupt. You aren't BSODing from other games because they don't require said values like Helldivers wants to use, so you don't experience them there.

[Heineken]

Originally posted by go_djentle:

Originally posted by Heineken:

The game crashes, it most likely is not the caused of BSOD. You might need to T/S some more. It sounds like a faulty hardware..

I literally got a message from the games engine for a crash report after the 1st 2 bsod's. I'm telling you all, it's not faulty hardware. I run diagnostics on my machine nearly every day. I have ran games since this occurred, other games have not caused this issue. I'm not the only person this is happening to either regarding this specific game.

You don't know what you're talking about buddy. I'm a networks Engineer took like 1 year studying hardware. I'm telling you it's not the game it's your hardware.

[Dealman]

Originally posted by go_djentle:

I literally got a message from the games engine for a crash report after the 1st 2 bsod's. I'm telling you all, it's not faulty hardware. I run diagnostics on my machine nearly every day. I have ran games since this occurred, other games have not caused this issue. I'm not the only person this is happening to either regarding this specific game.

I would still wager lots of money on the fact the issue is on your end, not the game since it runs fine for hundreds of thousands of players.

Stress test your system, start with stress testing your CPU and then your GPU. And after that, stress test both at the same time. If it seems stable, run a memtest.

A BSoD can be caused by a lot of things, could even be related to audio due to a faulty or bad audio chipset (*cough* realtek *cough*). It should generate some minidumps you can look at with some software such as BlueScreenView.

[Heineken]

Originally posted by Dealman:

Originally posted by go_djentle:

I literally got a message from the games engine for a crash report after the 1st 2 bsod's. I'm telling you all, it's not faulty hardware. I run diagnostics on my machine nearly every day. I have ran games since this occurred, other games have not caused this issue. I'm not the only person this is happening to either regarding this specific game.

I would still wager lots of money on the fact the issue is on your end, not the game since it runs fine for hundreds of thousands of players.

Stress test your system, start with stress testing your CPU and then your GPU. And after that, stress test both at the same time. If it seems stable, run a memtest.

A BSoD can be caused by a lot of things, could even be related to audio due to a faulty or bad audio chipset (*cough* realtek *cough*). It should generate some minidumps you can look at with some software such as BlueScreenView.

Basically this.
It could just be the game that triggers it, but 100 percent is due to some hardware failing.

[LRonHubbard]

Originally posted by Heineken:

Originally posted by Dealman:

I would still wager lots of money on the fact the issue is on your end, not the game since it runs fine for hundreds of thousands of players.

Stress test your system, start with stress testing your CPU and then your GPU. And after that, stress test both at the same time. If it seems stable, run a memtest.

A BSoD can be caused by a lot of things, could even be related to audio due to a faulty or bad audio chipset (*cough* realtek *cough*). It should generate some minidumps you can look at with some software such as BlueScreenView.

Basically this.
It could just be the game that triggers it, but 100 percent is due to some hardware failing.

here's my mini dump:

bug check string-SYSTEM_SERVICE_EXCEPTION
bug check code-0x0000003b
parameter 1-00000000`c0000005
parameter 2-fffff807`36631bca
P3-ffffe101`d0d29900
P4-00000000`00000000
Caused by driver-ntoskrnl.exe
caused by address-ntoskrnl.exe+417380
file description-NT Kernel & System
product name-Microsoft® Windows® Operating System
company-Microsoft Corporation
file version-10.0.22621.3235 (WinBuild.160101.0800)
processor-x64
crash address-ntoskrnl.exe+417380

[SelfCursed]

While I do agree that faulty hardware is usually the likely fault to BSODs when games crash... There's the problem with this game taking over at the kernel level due to nProtect GameGuard.

I've had three BSOD's over the course of the game, every single one has been an access violation fault. A pointer reading outside of bounds. If someone understands more, feel free to tell me what can cause these violations. However, to add some implications to the cause, allow me to paste a part of the latest log:

"FAILURE_BUCKET_ID: AV_R_(null)_GGKernel64!unknown_function"
A (Access) V (Violation) R (Read?) GG (GameGuard) Kernel64.

The first couple of access violations I saw were "System" related to Nvidia. They were most likely driver related, so I ignored it and did a fresh install as well as updated my drivers. Didn't see those anymore.

The last one though makes me think that Game Guard at kernel level was not exactly helping with the first two BSODs either. I haven't had a single BSOD on any games other than Helldivers 2 on my current PC. Before anyone suggests overheating, it's definitely not it; I have been making sure of it.

To further emphasize my point: PROCESS_NAME: GameMon64.des is what caused the issue.

GameMon64.des is counted as a malware virus online because it's a rootkit, but the official version of this process is actually a part of nProtect GameGuard.

GameGuard is the cause of a lot of BSODs here. This program has been notorious for a long time if you take the time to research it, and it's clearly not written well enough as a universal program. The code is not universal and hence doesn't work on all systems properly.

Furthermore, crashes happen when a game puts too much strain on your PC (usually the CPU or graphics card). And if a game puts a strain on your PC, things like GameGuard that run in tandem/parallel with the game struggle also. Any stutters, a single mismatch, at the kernel level can cause a regular crash to go beyond just closing the program, but shut down the entire PC through BSOD. Blue Screens of Death are essentially warnings/logs that the PC went through an error in which the PC tried to save itself from bricking. If the BSOD protection fails, what windows needs to prevent/correct immediately fails, your PC might suffer and be irreparably bricked.

[Doomvora]

Originally posted by go_djentle:

here's my mini dump:

bug check string-SYSTEM_SERVICE_EXCEPTION
bug check code-0x0000003b
parameter 1-00000000`c0000005
parameter 2-fffff807`36631bca
P3-ffffe101`d0d29900
P4-00000000`00000000
Caused by driver-ntoskrnl.exe
caused by address-ntoskrnl.exe+417380
file description-NT Kernel & System
product name-Microsoft® Windows® Operating System
company-Microsoft Corporation
file version-10.0.22621.3235 (WinBuild.160101.0800)
processor-x64
crash address-ntoskrnl.exe+417380

This unfortunately doesn't tell us much, but as SelfCursed mentioned it's possible, likely even that it's something caused by nprotect, it could also be caused by gpu drivers. Perhaps DDUing your display drivers and installing them again might alleviate the issue.

I wonder if each blue screen is getting the same stop code or if it's different every time. Service exception makes me think it could be a driver issue but it's probably a conflict between windows and nprotect.

You could try turning all the settings down and seeing if that makes a difference, then slowly turn them up until the bsod happens to try and narrow down the possible culprit.

While BSODs are typically hardware related, there's still the possibility of it being software related.

Sorry I can't be more help, perhaps someone more knowledgeable will be able to step in and provide a better solution.

[Doc]

before the update i had maybe 2 crashes in 70h
today i had 5, plus 3 random disconnects that instantly put me back on the ship