On my primary gaming build, the GPU radiator fan curve maxes out at 950 rpm, the GPU temperature at 63 ☌. It's a balance between heat dissipation and fan noise that you must decide. It's not my computer and I'm not in the same room so I don't care how you set your fan curves. If you're happy with your temperatures and fans reaching 100% speed then leave them that way. Personally, I never let any of my fans (whether they be radiator, case, or graphics card) run at 100% because I care about acoustics and I hate headphones. ![]() For my two custom loop builds, I also set the GPU radiator fans with the BIOS. With the exception of air-cooled graphics cards with the stock cooler, I set fan curves in the BIOS, not a Windows application. What's your ideal room temperature? 22 ☌? 25 ☌? 28 ☌? Plus each person has a different usage case, different applications they run, even during idle. plus different operating conditions (ambient temperature due to location, season, whatever). Everyone has a different idea of what is acceptable in terms of temperatures and fan noise.Įveryone's DIY build has different components: case, CPU, GPU, PSU, motherboard, chipset, RAM, drives, accessories, cooling solutions, etc. ![]() Additionally, you know approximately what date and time you create the version that introduces this new behavior, and you also know which version code it will have.The main thing is that you're happy with your fan curves. On first install, firstInstallTime and lastUpdateTime will have the same value (at least on my device they were the same) after an update, the values will be different because lastUpdateTime will change. The only solution I can see that doesn't involve an entity outside of the device would be to get the PackageInfo for your app and check the values of
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |