Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Discussions Rules and Guidelines
Report this post
Youy can also look at your event viewer logs to see why the pc restarts but PSU sounds like the easy culprit.
It appears to be a very common issue and I personally believe Nvidia or the game devs will eventually patch it.
No point looking at events. If software caused the shutdown, you'd have gotten a blue-screen (and seen the cause for said blue-screen in the events). Since you had no blue screen and it's just a complete shutdown (i.e; blackscreen), there is only one thing that can be the cause. Hardware.
When you say it shuts down, do you mean that the entire PC, fans, etc everytihng just immediately shuts off (fans will probably move while reducing in speed, but apart from that)?
If so, temperature is a possibility. Do a stress-test while monitoring the temperatures and see how this goes. This will be the best way to check temperature.
Assuming the temperature is fine, then the other potentional options are 1: issue with your outlet, 2: Issue with the power cable, 3: (mid stage signs of) dying components, specifically, the PSU or the motherboard.
Skimming your MB's manual, it seems it doesn't have any support for error-codes, so you're somewhat ♥♥♥♥ out of luck in getting any sort of guidance to what hardware is actually failing, without using a multi-meter (suggest not since you're posting here), or switching components to figure out exactly which one is failing.
This goes for you too.
--
Ultimately, it's not the game, if it was the game, you'd be getting a blue-screen pointing to the game, or something related to the game, triggering it. Situations as described by you two, is always hardware related.
This is underrated advice. I've had 7 clients since January with power issues with PCs that we built and once we got the boxes back in the shop, nothing was re-produceable, out of all 7. The causes came down to funny stuff like 20 year old, poorly wired outlets in one apartment to a guy trying to run his custom open loop OC'd 14900K 4090 rig on some busted ass 10 amp circuit that he knew couldn't even power a Dyson Vacuum without browning out his unit(he told us he knew that beforehand) and then thought it would be fine to power a PC with a 1600W PSU (that's 13.3 amps @120v at full load all by itself).
But it get's better: one client was using a pair of basic 6-plug pigtails (one plugged into each socket in the same outlet) and then plugged in their entire room, including their 1300W gaming PC, into those two pigtails and ignored the 3 other 15 amp circuits available around the room (because "that wasn't convenient to wire up") and then blamed our PC build for, and I quote, "It's trippin' my breakers, bro!". We have since made a sign that says that and hung it on the wall in the workshop for lulz.
If you have a high end PC, it gets one circuit. All by itself. No pigtail. Maybe plug a monitor into the second plug on the outlet, but even a single pigtail full of crap alongside a high-end PC, probably not, and absolutely not the PC with 11 other things plugged into 2x 6 plug pigtails on the same damn 15 amp circuit.
you might be a unicorn. As a unicorn, the most likely culprit are kernel, or bios level drivers (i.e; firmware) that's causing some issues, only fix here is complete BIOS reset and\or a system reset (a.k.a, reinstalling the OS, preferibly on a clean drive).
--
It is also possible you have incompatible hardware configuration, and just haven't noticed yet, because the incompatibilities haven't been used. This is extraodrinarily rare (unicorn) today to the point of basically unheard of, but it is theoretically possible.
--
In short; it is not the game, because it can't be the game. The game doesn't have kernel level access, therefore any shutdown request done by the game, will always go through the system event phase (this is the same for Unix based OS'es, and for NT based OS'es, i.e; Windows).
Yeah, though I do kinda get it. If the fault is the outlet\circuits, and you don't realistically have any other choice (without either redoing the entire wiring, or having extention cords everywhere), it's far easier to blame literally anything else, since it's cheaper\better than all of that.
Which is the same in situations like these. Easier to blame the game, than to face the reality the hardware (most likely) is giving initial warning signs. Said warning signs gets ignored, months later it died, and then the same people write on hardware forums how their computer stopped working out of nowhere with no warning....
Hell, I have personal anecdotal experience (when I was a teen) of the exact same thing, denial. When my GPU was trying to gently say it's dying (BSOD + graphical anomalities in a single game, no other game was an issue, so it couldn't be hardware, no, it MUST be the game!), then 3 months later it never booted up again, at all.