Mastermind replied to computer reboots after launching the game September 26, 2022 @ 9:05:27 pm PDT
Well... If it is software issue, I doubt it's Valheim. Not impossible... But not the first thing that comes to mind.
Assuming you are playing on Windows...
If it's the OS that is crashing (not sure how likely if you don't see a blue screen before the reboot), there should be a file created in (default folder) C:\windows\minidump. The file contains information that can be analysed by a utility supplied by Microsoft called WinDbg. WinDbg will usually be able to point you toward the faulty application/drivers causing the crash (At least, the file seemingly causing the crash). The process the get the minidump analysed isn't that complicated. You can google it and see if you are comfortable doing it.
If you don't feel comfortable with that process, there's the option of throwing darts in the dark.
On the software side, I'd first check drivers, most likely the graphic card's. Most crash I've seen, the graphic drivers were at fault.
On the hardware side, I'd check if the fan of your CPU and GPU are still properly spinning. Overheating components could cause the computer to restart like that. If it's about heat, I believe there should be an entry mentioning it in Windows' Event Viewer, probably in the "System" logs. Those logs might also contains extra information about what the source of the crash is (or nothing at all, if Windows isn't "made aware" the system is about to reboot).
And... If it's some hardware that failed... God knows what it could be. RAM, GPU, PSU ... maybe even CPU.
RAM might be easiest to test. If you have 2 stick of RAM, you can test with just 1 plugged in, and then just the other. If 1 crash and not the other, you know it's defective RAM.
But... testing hardware without replacement part is... not exactly trivial? (or at least, beyond my knowledge).
Assuming you are playing on Windows...
If it's the OS that is crashing (not sure how likely if you don't see a blue screen before the reboot), there should be a file created in (default folder) C:\windows\minidump. The file contains information that can be analysed by a utility supplied by Microsoft called WinDbg. WinDbg will usually be able to point you toward the faulty application/drivers causing the crash (At least, the file seemingly causing the crash). The process the get the minidump analysed isn't that complicated. You can google it and see if you are comfortable doing it.
If you don't feel comfortable with that process, there's the option of throwing darts in the dark.
On the software side, I'd first check drivers, most likely the graphic card's. Most crash I've seen, the graphic drivers were at fault.
On the hardware side, I'd check if the fan of your CPU and GPU are still properly spinning. Overheating components could cause the computer to restart like that. If it's about heat, I believe there should be an entry mentioning it in Windows' Event Viewer, probably in the "System" logs. Those logs might also contains extra information about what the source of the crash is (or nothing at all, if Windows isn't "made aware" the system is about to reboot).
And... If it's some hardware that failed... God knows what it could be. RAM, GPU, PSU ... maybe even CPU.
RAM might be easiest to test. If you have 2 stick of RAM, you can test with just 1 plugged in, and then just the other. If 1 crash and not the other, you know it's defective RAM.
But... testing hardware without replacement part is... not exactly trivial? (or at least, beyond my knowledge).
5:13 am, September 27, 2022