Author: VUMeter
Subject: Idle CoreParking vCore // 1700x+X370TaiChi
Posted: 20 Aug 2019 at 4:47am
@cx5 Please don't take this the wrong way. But at this point I have no real interest in making anything run beyond spec.d parameters. It's probably easy and a 'free' overclock, but it's not something I am too fussed about at all for the time being.
Back to my original post:
Nope, setting the BCLK to a locked 100MHz does nothing to affect a change in this behaviour. It seems to stop it wandering so much when watching HWiNFO (is it correctly reported? Why would the BCLK not stick rigidly to 100MHz?), but doesn't cure my issue.
I have updated the chipset drivers, again no change.
Short of a CMOS reset, I am not sure why this is happening?
ZoneAlarm firewall/anti-virus is a known entity which does cause some strange behaviour. Could it be this that might be the culprit?
I wouldn't bother so much with a 3rd part firewall, except that the alerts are rather informative with ZA and non-existent with Windows own protections. I prefer to be alerted about every small thing happening rather than an overall program accessing the internet. ZA informs me of registry access as well, which is handy to stop startup programs being added.
But why would a Windows restart cure the issue so swiftly, and for it not to happen again after the first reboot?
I am very tempted to boot into Linux Mint Cinnamon 19.x from USB stick to see what happens on the next cold boot. A cleaner system which is up to date should give me some better indications of what is happening.
Sure, no Windows Core Parking, bit I might be able to read voltages with the applicable tools accessed.
Subject: Idle CoreParking vCore // 1700x+X370TaiChi
Posted: 20 Aug 2019 at 4:47am
@cx5 Please don't take this the wrong way. But at this point I have no real interest in making anything run beyond spec.d parameters. It's probably easy and a 'free' overclock, but it's not something I am too fussed about at all for the time being.
Back to my original post:
Nope, setting the BCLK to a locked 100MHz does nothing to affect a change in this behaviour. It seems to stop it wandering so much when watching HWiNFO (is it correctly reported? Why would the BCLK not stick rigidly to 100MHz?), but doesn't cure my issue.
I have updated the chipset drivers, again no change.
Short of a CMOS reset, I am not sure why this is happening?
ZoneAlarm firewall/anti-virus is a known entity which does cause some strange behaviour. Could it be this that might be the culprit?
I wouldn't bother so much with a 3rd part firewall, except that the alerts are rather informative with ZA and non-existent with Windows own protections. I prefer to be alerted about every small thing happening rather than an overall program accessing the internet. ZA informs me of registry access as well, which is handy to stop startup programs being added.
But why would a Windows restart cure the issue so swiftly, and for it not to happen again after the first reboot?
I am very tempted to boot into Linux Mint Cinnamon 19.x from USB stick to see what happens on the next cold boot. A cleaner system which is up to date should give me some better indications of what is happening.
Sure, no Windows Core Parking, bit I might be able to read voltages with the applicable tools accessed.