My PC shuts off completely when playing helldivers out of nowhere over and over again?

[DreadfulDrummer]

is this a known issue. im afraid my pc is broken. It started happening after a typical crash that would freeze my game and i had to hard reset. my hard drive health is fine and psu seems fine. pc runs perfectly normal its just helldivers. Only thing ive been doing differently is using discord while playing. Anyone know what this could be? i have an rtx 3080 32gb ddr4 and i7 12700k with decent temps

[DreadfulDrummer]

Diposting pertama kali oleh AoD_lexandro:

Diposting pertama kali oleh Master Roshi:

When helldivers crashes, I end up with Windows full crashing as well, straight to a reboot.
If I had to guess, it's because of the game installed rootkit crashing Windows.
But I'm sure that statement will get me reported to a democracy officer..

You could stop guessing and find out instead from event viewer. Dollars to donuts its a memory error with the game and the graphics card drivers.

i tried looking at that but honestly dont understand what the messages mean. is there something specific i should look for if its a non hardware/psu/hard drive issue?

[AoD_lexandro]

Diposting pertama kali oleh DrummerGuy90:

Diposting pertama kali oleh AoD_lexandro:

You could stop guessing and find out instead from event viewer. Dollars to donuts its a memory error with the game and the graphics card drivers.

i tried looking at that but honestly dont understand what the messages mean. is there something specific i should look for if its a non hardware/psu/hard drive issue?

Sorry that was no meant for you but the chap stating "he has to guess". In your own case its simply a memory issue with the game. It does not like to share resources from the graphics card atm and will crash if its commands get interrupted.

[DreadfulDrummer]

im gonna test it out without discord even on.. or am now. when booted i did get this error if you know what it means.

The Open procedure for service "WmiApRpl" in DLL "C:\WINDOWS\system32\wbem\wmiaprpl.dll" failed with error code The device is not ready.. Performance data for this service will not be available.

[Kackstift]

shutdown is 90% a overheating or voltage issue.

[Master Roshi]

Diposting pertama kali oleh AoD_lexandro:

Diposting pertama kali oleh DrummerGuy90:

i tried looking at that but honestly dont understand what the messages mean. is there something specific i should look for if its a non hardware/psu/hard drive issue?

Sorry that was no meant for you but the chap stating "he has to guess". In your own case its simply a memory issue with the game. It does not like to share resources from the graphics card atm and will crash if its commands get interrupted.

Yeah I'm guessing, because I shouldn't have to check any of that.
I don't think I've had a game crash Windows since Windows XP.

If there's something specific you'd like me to check for, I can check my event viewer, but otherwise I'm gonna assume the rootkit is probably causing the issue.
I don't mind having an anti-cheat rootkit as long as it's reliable and just works.

[W]

This is a known bug. Ignore the trolls.

[AoD_lexandro]

Diposting pertama kali oleh Kackstift:

shutdown is 90% a overheating or voltage issue.

Indeed. In this case I think the OP system has got his drivers crashing and causing the fans to stall out then overheat and BSOD restart.

[Buntkreuz]

Diposting pertama kali oleh DrummerGuy90:

Diposting pertama kali oleh Buntkreuz:

No but seriously, if i remember correctly (and roughly), this could mean your PC runs out of memory or heats up too fast and performs an emergency shutdown to protect itself.
But considering your comment, that seems to not be it.

I also have the game freeze (when i quit), but i just close it via taskmanager

this game has freezed in the past and only game where i cant get to task manager. The windows allow me click through like everything is running fine but cant leave the screen. its happened 4-5 times since game came out. This time it happend i hard reset and my pc didnt even recognize the harddrive it was on.. i had to replug it in

Im not sure whether its the same i sometimes have. But in that case i sometimes can sign out of my windows profile, which sends me to the windows login page.
Another trick i found was "restart" and then windows opens a window telling that some program takes longer (like Steam) and it offers the option to cancel the restart.
That action closes the game windows and other stuff, so im basically sent back to a clean windows.
However needs me to restart steam.
Maybe that helps.

[SinglePoorIan]

Check your sytem event viewer log (event viewer -> windows -> system) for a error entry just before it says the PC started. It should list a blue screen code that you can use to look up the problem.

A full PC shutdown is usually a memory error or a cpu error. And in some cases a weak power supply that cant handle a transient spike when a sudden demand is put on it.

It should say something like this:

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001a (0x0000000000041790, 0xfffffb800bf6a3f0, 0x0000000000000000, 0x0000000000000001). A dump was saved in: C:\WINDOWS\Minidump\022824-16687-01.dmp. Report Id: 5f0e34af-2c7d-4481-a9e1-386dc984265f.

The hex value after "bugcheck was" is what you google, in this case its a 0x0000001a
which is Bug Check 0x1A: MEMORY_MANAGEMENT. (https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x1a--memory-management)

Read the articles from learn.microsoft.com to get accurate answers for the bugcheck code.

In my case I had bad XMP memory timings and tightened them up and havent had this error in a while.

[DreadfulDrummer]

Diposting pertama kali oleh BONERLORD THE FIRM:

Check your event viewer for a error entry just before it says the PC started. It should list a blue screen code that you can use to look up the problem.

A full PC shutdown is usually a memory error or a cpu error.

i get this on boot event Metadata staging failed, result=0x80070490 for container '{B150A81E-9E06-D5D9-A402-AFBDF56219E1}'

also this idk what it means?

The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
Windows.SecurityCenter.WscBrokerManager
and APPID
Unavailable
to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

and this is the critical when it shuts itself down The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

any help on this will be greatly appreciated. im reinstalling game just in case it got corrupted or something during a crash

[Snowfunk]

Diposting pertama kali oleh AoD_lexandro:

Disable hardware acceleration in Discord. Job done.

Disable hardware acceleration in everything, ever, that is possible, period.
But yea, in Discord in particularly.

[Master Roshi]

Diposting pertama kali oleh BONERLORD THE FIRM:

Check your event viewer for a error entry just before it says the PC started. It should list a blue screen code that you can use to look up the problem.

A full PC shutdown is usually a memory error or a cpu error.

I checked all the Event Viewer entries in System before the unexpected shutdown error, but they were all 'Information' and nothing was important.
I also had no BSOD, it just froze, and then hit the MOBO screen.

After the reboot entry I did find a few entries about AMDRyzen not being able to create a file that was already created, and "The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001a (0x0000000000000403, 0xffffc58002b2f3d8, 0x80000003fe6d0867, 0xfffdc58002b2f3d8). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 976d44f9-62f8-47c9-b389-cde3dd7aa475."

Other than those two things, it's almost empty of anything that seems even slightly relevant.

[SinglePoorIan]

Diposting pertama kali oleh DrummerGuy90:

Diposting pertama kali oleh BONERLORD THE FIRM:

Check your event viewer for a error entry just before it says the PC started. It should list a blue screen code that you can use to look up the problem.

A full PC shutdown is usually a memory error or a cpu error.

i get this on boot event Metadata staging failed, result=0x80070490 for container '{B150A81E-9E06-D5D9-A402-AFBDF56219E1}'

also this idk what it means?

The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
Windows.SecurityCenter.WscBrokerManager
and APPID
Unavailable
to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

and this is the critical when it shuts itself down The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

any help on this will be greatly appreciated. im reinstalling game just in case it got corrupted or something during a crash

Nah what youre looking for is the source to be "BugCheck" You can filter the log so show only critical entries to find it easier.

[SinglePoorIan]

Diposting pertama kali oleh Master Roshi:

Diposting pertama kali oleh BONERLORD THE FIRM:

Check your event viewer for a error entry just before it says the PC started. It should list a blue screen code that you can use to look up the problem.

A full PC shutdown is usually a memory error or a cpu error.

I checked all the Event Viewer entries in System before the unexpected shutdown error, but they were all 'Information' and nothing was important.
I also had no BSOD, it just froze, and then hit the MOBO screen.

After the reboot entry I did find a few entries about AMDRyzen not being able to create a file that was already created, and "The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001a (0x0000000000000403, 0xffffc58002b2f3d8, 0x80000003fe6d0867, 0xfffdc58002b2f3d8). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 976d44f9-62f8-47c9-b389-cde3dd7aa475."

Other than those two things, it's almost empty of anything that seems even slightly relevant.

You found it 0x0000001a is a MEMORY_management error like I got a few months ago.

[DreadfulDrummer]

Diposting pertama kali oleh BONERLORD THE FIRM:

Nah what youre looking for is the source to be "BugCheck" You can filter the log so show only critical entries to find it easier.

the critcals list "0" as bugcheck