![]() ![]() Just be sure to check in every now and then even the best CPUs will suffer if they get to toasty.Ĭore Temp lets you see how individual CPU cores compare to others. They’re all free and easy to use, and are distinct enough that you can pick the one that best suits your preferences. ![]() This guide will focus on a few different software tools that you can use to keep an eye on CPU heat. Left unattended, an overheating CPU can cause system shutdowns, performance throttling – less than ideal for gaming – and even permanent damage to the processor itself. So while overheating is usually caused by an over-ambitious overlock or improperly installed cooler, rather than being part and parcel of computer ownership, it’s worth understanding how to monitor CPU temperatures so that you can spot potential issues quickly. Luckily this isn’t a common problem, but if you’ve just built a PC from scatch, have installed a new CPU in your existing setup, or are attempting to overclock, checking the CPU temperature is a quick step that can reassure you that all is well – just as much as it can warn you of an overly hot chip.Įxcess heat is a PC’s natural enemy, and gaming systems – with CPUs tending towards higher clock speeds, plus dedicated graphics cards producing extra warmth inside the case – are especially at risk. I'm on the Asus 圆70e Hero with Aida64 current beta and the temp does not read correctly gets stuck 61c cpu and 70c cpu pkg, once I put the PC in sleep mode and wakes it up the temp now reads 29c cpu and 36c cpu pkg matching HWiNFO.Once you know how to monitor your CPU temperature, you’ll be able to perform a vital health check on a PC component that you very, very much do not want to overheat and break. It can monitor the CPU package temp correctly without locking it. But it may not be limited to just CPU package temp either.ĮDIT: For the record, I tried the sensors on HWInfo64, and it is not causing this issue. Oh, incidentally, my GPU is a 1080TI and it doesn't seem to be locking that particular reading. This is on a 7950x and Crosshair 圆70e Extreme running on Windows 10. ![]() This is quite dangerous - if someone were to have their package temp locked at a low reading and then they ran something that drove the temps over 95c, I don't think it would increase the fans or throttle at all. I had it lock at 82c once, fans went full and stayed on full despite my going back to idle. CPU package temp gets locked as soon as Aida reads the sensors. Just adding that I am experiencing the same issue. At any rate, that temperature being displayed does not completely lock when I start the sensorpanel (unlike CPU package temp) but it does seem to be much less likely to change over time. So maybe it's just a single core temp? Or motherboard temp? Not sure. Not sure what temp it is honestly, I saw at one point that I had 70c package temp and only showed 38c on that led. However, it's also true that the temp being displayed where the POST codes normally go is *not* CPU package temp. I mention this because I don't think AIDA was causing this issue until I updated my BIOS to 0705, and the implementation of something directly tied to CPU temp monitoring seems to be a bit buggy, so it seems like it'd be worth investigating.ĮDIT: So I decided to experiment, and set that BIOS setting back to "Auto" so that it displays temp, and verified that Aida still locks the CPU package temp when sensors are turned on. No one knows what that means or why, but it's probably just a bug. This does not happen when running Ubuntu off a USB, it stays "AA" in that case, so it's definitely something in Windows triggering it. There does seem to currently be a bug in BIOS 0705 where, if you set it to "Show POST codes only", the LED shows the normal and expected "AA" code only briefly while Windows is loading, only to permanently change to "81" in the middle of the load. As I am already displaying CPU Temp both elsewhere on the motherboard and on my CPU cooler, I personally immediately changed that BIOS setting to "Show POST codes only", which was the default behavior before this latest BIOS version. On the latest BIOS version for my ASUS Crosshair X670e Extreme, BIOS 0705, they modified the BIOS such that the 2 character LED that normally displays Q-Codes (POST status) on Asus boards now displays CPU temperature by default instead. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |