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
The real problem with laptops are the tiny fans that they use are not proper, especially for "gaming" laptops as a lot of heat generates; therefore, the viscosity and thermal breakdown of that thermal paste happens at increased levels as opposed to a desktop.
Perhaps best to ask how long have you owned the laptop and if this is a new issue?
Do you allow the cpu voltages to be left on Auto? Never so that. Manually lower them.
Your apps could be wrong. At around 95*C then it should be thermal throttling the cou clocks, is that happening at all?
As I had mentioned in the post, this isn't a cooling issue. It only happens on the first boot, fixes after restart. The thermal pastes are new. Fans are working well. After restarting, I see 70 celsius max once again. The laptop is able to cool itself. Still, thank you for your answer.
HWMonitor. I did consider it to be wrong but I didn't see the need to use another app after noticing that I was also having FPS drops due to high temperatures. So it /does/ spike, for sure. I don't manually control the voltages, but I don't see the need to do that either. It's all fine after the restart, after all. I just want to understand why this happens on the first boot.
I've recently sent my laptop to services due to another problem. The motherboard was changed and I made sure the BIOS was up-to-date because there is no way to manually update it, since updates aren't given by the manufacturer. Is there nothing else that might be causing this? Or any other solutions?