Actually, before I upgraded to Win10, I read on the ASUS ROG forums someone claimed Win10 was running their CPU at a lower speed than Win7. It starts at 83MB but with Win7, it keeps growing so within a day, it would be up to 1GB and the process will crash on it's own. I'm running Process Hacker so I just use it to restart the process. With Win 10, it stays at 83MB and doesn't grow.
Still a lot for a process you most likely do not need running even if you shut it down which kind of makes no sense with process hacker, mean run it when you need it ? As said i believe it just monitors it as the name states, you should google it more as i did before answering you before.
There isn't a way to run it manually as it's not even part of the Start Menu. Most other people find it annoying as usually it will just crash on it's own and they have no way to run it again as it's really called SignalIsland.exe as can be seen here:
Intel Turbo Boost Monitor is anoying | Intel Communities
I keep it run so I know when the system is actually running at full load for no reason and I always manage to restart it before it crashes since my systems are usually up 24x7x365. It's more important in Win10 since ASUS's Power4Gear no longer has OSD in Win10 and there are times like earlier today when the system was running at a slow profile that I didn't know about as Fn+space will toggle between the P4G profiles without any OSD indication.
A lot of the Asus stuff is unnecessary , there is a blog somewhere that explains whats worth having and what to get rid of regarding the Asus utilities.
I only keep what i think i really need and my computer seems naked compared to a lot of others i have seen , very few programs , very few extensions and this is after years of using it .
When i see other people post whats on their computer in the malware removal forums it just boggles my mind lol.
Yep, Gigabyte had Apps i first tried when i bought system and after upgrades to other OS determined they were just useless in ways, monitoring apps and things i could do in BIOS just made it more convenient in notification area, but used more resources, just eye candy. Read into things, too many opinions and should haves and should not haves and who is right and who is wrong.
Then when have new OS, scrambling around looking for a new version to work on it for reasons cause it was on site for your product then.
Well, I use HWINFO32/HWINFO64 to monitor my system. It monitors the turbo boost as well as temperatures, memory usage, fan speeds and almost all available information coming from sensors and devices. It is lightweight and customizable and is able to show graphs. http://www.hwinfo.com/download.php
Task manager is nice for the basics. And some Mainboard/PC manufacturer tools like A-Tuning from Asrock install other tools I do not wan't on my system without the option to remove them. If A-Tuning users are here, look what your CPU does when you lock the PC. And look at the power meter. It's caused by the built in USB-lock feature. The high power consumption is not a bug. It's feature to enable you to use an USB stick to unlock your PC.
Well, HWINFO is free of such hassles and it combines the heaps of monitoring apps into one.
The BSOD I reported here I get when trying to run the Inf updater is connected to the GPU drivers, Intel or Nvidia or both, or the DirectX subsysem by MS, I guess, and not necessarily to the Inf updater itself. Because I get the same BSOD when trying to update OR remove graphics drivers. I also get it sometimes trying to turn on ShadowPlay. I thought about it, and I think it happens during Intel Inf Updater because during the setup, Windows "disconnects" the GPU for a moment, or something like that, because of the new drivers for the PCIe lines. This is mostly the same event as removing or updating the GPU drivers, or a similar event.
I own a GTX970, and my friend a GTX770 and he has the exact same BSOD, same code, same cause, same event where it happens (updating the Nvidia drivers for example).
I have absolutely no idea how this BSOD is triggered, and why it seems to be so rare.
I have reported it several time at MS and Nvidia (got two other people in that thread who had the exact same BSOD + same time happening during update/remove of GPU drivers).
http://answers.microsoft.com/en-us/w...d-d47af1101296
MS Support Engineer said:
"This might occur if the program which you are trying run, not compatible with Windows 10.I suggest you to uninstall Nvidia and Intel driver and try installing it on Compatibility mode.
To run a program in compatibility mode, refer to the below link:
Make older programs compatible with this version of Windows - Windows Help
Note: Applies to Windows 10 as well."
But I don't think this can be true, which would mean the Nvidia Windows 10 drivers, or the Intel drivers, aren't Windows 10 compatible.
I know it's not a hardware fault, I thought at first my GPU or PSU could be broken, because at this state, I know of at least 4 other people, who have the same BSOD, same code, same dxgkrnl.sys, same time when it happens.
Quote