While playing the game?

Or just all the time? Because it's not going to cause anything when it's not running.

known and enduring bug with unreal engine. it causes intel CPUs to shut off, some kind of voltage problem.
its why i ♥♥♥♥♥♥♥ despise unreal engine and no one should use it.

Originally posted by Mystry:

known and enduring bug with unreal engine. it causes intel CPUs to shut off, some kind of voltage problem.
its why i ♥♥♥♥♥♥♥ despise unreal engine and no one should use it.

This is only if you have your bios set wrong for overclocking.

Originally posted by Kunovega:

Originally posted by Mystry:

known and enduring bug with unreal engine. it causes intel CPUs to shut off, some kind of voltage problem.
its why i ♥♥♥♥♥♥♥ despise unreal engine and no one should use it.

This is only if you have your bios set wrong for overclocking.

not true, this happens both with zero overclocking, and with overclocking enabled.

Originally posted by Mystry:

Originally posted by Kunovega:

This is only if you have your bios set wrong for overclocking.

not true, this happens both with zero overclocking, and with overclocking enabled.

You should try actually looking up the solution instead of just being wrong all the time. Those intel cpu's that had the issue were defaulting to unlimited turbo enabled, which lets a program define how much it overclocks instead of having the bios set to its actual expected range.

Unreal has a habit of just telling a program to "run as high it can" and then expects the hardware to limit itself. For many people who have no clue how to correctly set a bios, the defaults for many motherboard / cpu combos were not in a safe range.

Intel cpu's have had automatic overclocking for nearly 2 decades, if you don't set its cap in bios, it leaves them vulnerable to overheating.

Try actually looking at modern Intel CPU's they all have a range limit, they idle low and then overclock themselves on demand. If you don't set the bios correctly, they can easily go over their actual expected range.

Originally posted by Kunovega:

Originally posted by Mystry:

not true, this happens both with zero overclocking, and with overclocking enabled.

You should try actually looking up the solution instead of just being wrong all the time. Those intel cpu's that had the issue were defaulting to unlimited turbo enabled, which lets a program define how much it overclocks instead of having the bios set to its actual expected range.

Unreal has a habit of just telling a program to "run as high it can" and then expects the hardware to limit itself. For many people who have no clue how to correctly set a bios, the defaults for many motherboard / cpu combos were not in a safe range.

Intel cpu's have had automatic overclocking for nearly 2 decades, if you don't set its cap in bios, it leaves them vulnerable to overheating.

Try actually looking at modern Intel CPU's they all have a range limit, they idle low and then overclock themselves on demand. If you don't set the bios correctly, they can easily go over their actual expected range.

its funny you say that then when i can point out hundreds upon hundreds of people who had this same issue with unreal engine screwing over their CPUs even WITH bios properly set. id also argue that default settings should already be set to contain cpu speeds *and* that unreal shouldn't be making a 'run as fast as you can' call no matter the case too.
stop excusing incompetence and idiocy.

Originally posted by Mystry:

stop excusing incompetence and idiocy.

I didn't excuse you, you're just wrong and didn't understand what I said.

Originally posted by Mystry:

known and enduring bug with unreal engine. it causes intel CPUs to shut off, some kind of voltage problem.
its why i ♥♥♥♥♥♥♥ despise unreal engine and no one should use it.

Right off the bat you even blamed Unreal when the OP didn't even give enough clarifying information. If his system is rebooting even outside the game, it's not the game being installed that's causing it. His question is not well formed and he never responded to any further diagnosis. You just came in and made assumptions.

You aren't the OP, and you have no interest in actually understanding the issue, so there's no point in further responding to you.