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
Worked fine when i turned off FG... soo not hardware
Research suggests that hard crashes, like games causing PC reboots, are typically due to hardware issues rather than direct software faults.
It seems likely that games stress hardware, exposing problems like overheating or insufficient power, leading to reboots as a protective measure.
The evidence leans toward hardware-level errors, such as faulty power supplies or overheating, being the root cause, even if triggered by software activity.
When you play a game on your PC, it makes the computer's parts, like the graphics card and processor, work really hard. If these parts get too hot or if there's not enough power to keep them running properly, the computer might suddenly turn off and restart to protect itself from damage. So, even though it's the game that's making the computer work hard, the real reason for the restart is a problem with the hardware, like overheating or a weak power supply.
Why It’s Not Directly Software
Software, like games, usually can't cause the whole PC to reboot on its own. Instead, it might push the hardware too far, and if the hardware can't handle it, the system reboots to prevent damage. This is often due to hardware protections kicking in, not a direct software bug.
#1 diihk rider of sony/nixes
The current Nvidia drivers as of this year are known to cause various BSOD/reboots for all of the releases this year... Currently, developers are recommending rolling back to the December or earlier drivers from 2024 for the time being. Windows updates have also, at times, caused this issue but I haven't looked to see if any known instance right now (as it is usually Win11 and I'm on Win10 which is way more stable).
If rolling back drivers doesn't fix it, and assuming you aren't on a RTX 50xx series GPU which could have its own various issues, I would consider checking for any known Win11 update issues in recent months, otherwise double checking hardware issues. While disabling it might have fixed the issue it does not mean that this cannot be hardware related.
That said, your exact issue matches this report of Frame Generation from driver 572.16 causing this exact problem, and the others released this year have had sporadic reports as well: https://www.techradar.com/computing/gpu/nvidias-new-dlss-4-driver-might-be-appealing-but-you-might-want-to-avoid-it-for-now-its-reportedly-causing-crashes-across-several-games-potentially-even-bsods