Nah, the same thing was fine under windows. The old linux ntfs driver was just horribly inefficient and 100%'ed the cpu for too long. The hardware worked as intended - it shut down to avoid thermal damage. Possibly there was some lower “speedstep” the OS could have told the CPU to use, but that didn’t seem to happen on this combination of OS and hardware.
Running at 100% CPU for any amount of time should be fully expected by the manufacturer and should ramp up fans and throttle the CPU if necessary. Those are hardware functions.
Just to add on to your comment: Hardware should not “shut down” due to software operations. Max fan speed and execution slow down, yes, but not a shut down, unless your computer has a function of shutting down when getting hot. Normal operation should just keep going.
Emergency thermal shut-off is a very common function in various pieces of computer hardware. And if throttling doesn’t help it should indeed shut down, rather than cause damage.
That sound more like a hardware issue, no?
Nah, the same thing was fine under windows. The old linux ntfs driver was just horribly inefficient and 100%'ed the cpu for too long. The hardware worked as intended - it shut down to avoid thermal damage. Possibly there was some lower “speedstep” the OS could have told the CPU to use, but that didn’t seem to happen on this combination of OS and hardware.
Running at 100% CPU for any amount of time should be fully expected by the manufacturer and should ramp up fans and throttle the CPU if necessary. Those are hardware functions.
Just to add on to your comment: Hardware should not “shut down” due to software operations. Max fan speed and execution slow down, yes, but not a shut down, unless your computer has a function of shutting down when getting hot. Normal operation should just keep going.
Emergency thermal shut-off is a very common function in various pieces of computer hardware. And if throttling doesn’t help it should indeed shut down, rather than cause damage.