The iMac stays cold (60 degrees) for a period of time in sleep mode.
by Poster
Feb 28, 2020
7
When the iMac enters the state manually or automatically sleep.
It will start to gradually heat up to around 66 degrees (suspected fanless heat dissipation), and all hardware will be kept low, such as SSD.
Even when not in use.
There is no software that needs to be run (such as rendering software). Of course, some software (such as QQ, WeChat, 2 browsers, etc.) is hung up, but it is impossible to judge.
I thought about it for a long time and the only possibility seemed to be to bring your own photo software.
Last year, I pushed GoPro photos and videos when I took photos during my travel. Later, I learned that photos can start another library through Alt, and they don't occupy iCloud space. This is more practical for software that only needs to view photos.
So I put almost 10G or so (seems) in it.
These days, I touched the back shell of iMac and found it hot. All the temperatures of the checking software were around 60.
From the sleep state to the wake-up state, it will gradually change from 45 degrees to 66 degrees, and then drop to 45 degrees immediately after waking up.
It seems that it can only run at low temperature because the fan is not turned on.
I'd rather like to know how to find this problem.
Due to my lack of skills or experience, I can't immediately detect the related problems.
Simple keyword search Google didn't find it either.
I hope you can provide some pointers to help query, or provide relevant keywords to supplement the search.
Replies
-
Anonymous114 Feb 28, 2020Please ask you to answer the professional part of this question. I can only look at it from the actual use. How long has this machine been used? Does it have anything to do with the dust or the location of it? It also has something to do with the indoor temperature. The higher the indoor temperature, the higher the machine temperature. Take a look at the CPU usage to see if any process has a relatively high usage. Finally, uninstall the software for watching the temperature, out of sight and out of mind.
-
Anonymous2185 Feb 28, 2020I wonder if it's power nap?
-
Poster Feb 28, 2020@ Anonymous114 # 1 Less than a year, dust I have been cleaning + air purifier. The indoor temperature is now 20 degrees, and it should be at least less than 20 degrees in the early morning. It is estimated that 18 degrees. CPU usage plummeted after I woke up. So I took a screenshot at the first time, but I couldn't see what the problem was. Since it was cut off in the morning, there was no further study due to tight working hours. @ Anonymous2185 # 2 No, I'm by default. Even if it does, it shouldn't be 66 degrees for a long time
-
Poster Feb 28, 2020@ Anonymous114 # 1 And I only found it when I touched the shell (when adjusting the angle)... You don't know until you look at the temperature software.
-
Poster Mar 1, 2020@ Anonymous114 # 1 @ Anonymous2185 # 2 Case solved: QQ. I checked all kinds of records and still didn't find the problem. Then I opened the activity monitor and found that all QQ seemed to rank in the top three, and even the memory was in the top. If the virtual machine is not turned on. Doubts arose in his heart: Could it be … this guy? In addition, QQ usually gets stuck when typing, so before going to bed, I returned QQ. Then now waking up and looking at it, it's in the 30s. Oh... ———— iStat Menus records up to 30 days. So it has been there since February 5th, but it seems that I have been tossing the record of VHDX installing Windows in front of me, so it's a pity that I didn't write it down these four days.
-
Anonymous2185 Mar 9, 2020@ Poster Alas, rubbish created by Tencent. (Sorry I didn't receive your reply before, so I just came over to take a look after seeing your thanks. Been demoted?
-
Poster Mar 9, 2020@ Anonymous2185 # 6 Actually, I thank you because what you said is right, and it has nothing to do with QQ. I wronged it. At that time, the test may be short or unexpectedly correct. I returned QQ and then observed that the activity monitor was not there, so I went to sleep and waited to come back to have a look (maybe I only observed for 45 minutes, and it happened that this Bug was triggered 40 minutes later). When it cooled down, it was decided that it was a QQ problem. After a few days of tossing, I found out that it was a suspected Bug.