As the title say, my computer shuts down every time i try to launch the game.

Config :
CPU - AMD Reyzen 7 5800x
GPU - Nvidia 3080 Founder Edition 10GO
RAM - Corsair VENGEANCE LPX DDR4 32 Go

GPU drivers are up to date, and other games runs just fine.
This is a computer i use dayly for work using software like the unreal engine 5, blender etc without any power supply issues.

Windows event log shows a Kernel-Power error 41 (63).

Any other report on the matter ?

Not really an expert on these things but did you check your pc temperature? Had the same problem back in the day it would suddenly shut off because it turned out that there was something wrong with my cpu cooler.

Also my first thought, check the temps of your components. Does the shutdown occur when the game is compiling the shaders?

Check Your Bios and Other Driver. Update it. Solved it for me.

I monitored my temps and everything was chilling. The game was crashing as soon as the exe fired not at the shader stage.

The only thing i did for it to reach the shader compilation stage is putting back the power management to default in windows.

Then got stuck at infinite shader compilation for two hours. Then, put power profile back to performence without issue (weird). I ran DDU to clean uninstall all my video drivers ... Didn't help.

30 minutes later launched the game thinking "one last try", the shader compiled fine ... Game launched.

Ok i guess ...

I suspect Nvidia users are experiencing a lot of issues.
My problem was the game would NEVER launch into the main menu (after 10-20 tries), and my desktop would crash and reboot during the "compiling shaders" stage, about half-way through the progress bar.

The solution for me:
Right-click desktop and select Nvidia Control Panel->Manage 3D settings->Program Settings
Click Add button and find your Stalker 2 exe file (Nvidia Control Panel might show it in the list or click Browse button and search for your exe file). Click Add Selected Program.

In the list of configurable options, scroll down to each of these settings and set it specifically to your GPU (graphics card).
1. CUDA - GPUs
2. OpenGL rendering GPU

My Specs: i5 10600k [OC to 5.0Ghz] / 16gb DDR4 RAM / 12gb Nvidia RTX 3060 / Win11 / SSD hard drive

*Side Note*
I have a feeling Windows and Nvidia are fighting. Telling Nvidia a specific GPU utilization in its Control Panel (even though it might be set Globally to prioritize GPU) seems to be what corrected my issue permanently. I also set the Max Frame Rate to 60 when making these changes where I found one of these changes caused the game to boot up as intended. I ended up turning this setting back to "Off" for Stalker 2, and the game still compiles shaders and gets me to the main menu where I can continue playing. Also to note, when the game launches and compiles shaders, I also noticed it compiles about twice as fast after changing whichever Nvidia setting corrected my issue.

Hope this info is helpful to others.
If anyone reading this has a Radeon card, maybe there is a similar solution for you in your driver settings.
Otherwise, this might be an "Nvidia/Intel" thang :)

I would recommend going through your event logs and looking to see what's going on around the time of the crash. You may have to enable dump file creation/collection and see exactly what's crashing to figure out the problem. I had an issue on my son's computer where it was shutting down because of a bug with LSASS.exe crashing after a game had started & would occur randomly. Ultimately leaving it up for 24 hours straight (not letting it sleep either) and resetting the BIOS to defaults allowed the computer to work properly. It was a PITA to say the least. I suspect the issue was with Windows 11 verifier, and the BIOS settings.

What's your PSU? and have you re-done your cable management recently?

3000 & 6000 series cards introduced so much noise on the 12V line that some games will trip the over current protections.

My TX Prime never crashed until I started playing Valheim after a cleaning of my PC, and after a deep dive I learned this was a issue that was fixed 2 months after the production date of my unit. Bought a new one & RMA'd the faulty one.