Started by BenYeeHua, August 08, 2013, 07:47:42 AM
QuoteBasically if you are using Processor Power Management in Windows 7 & 8 at any setting under 100% then you are using core parking.If you donâ€™t want to use core parking:via Control Panel > Power Options > Pick your Power scheme(s) > Change plan settings > Processor power management > set Minimum processor state to 100% > press Apply and OK buttons.orFrom Microsoft White Paper â€" Performance Tuning Guidelines for Windows Server 2012To turn off core parking, set the Processor Performance Core Parking Minimum Cores parameter to 100 percent by using the following commands:Powercfg -setacvalueindex scheme_current sub_processor CPMINCORES 100Powercfg -setactive scheme_current
Quote from: chris635 on May 02, 2014, 10:44:32 PMUpon checking my settings in the bios I noticed I neglected to turn off C6 State. Thats what was causing my freezes with certain flash games with core parking dis-abled. Once I turned off C6 state and unparked the cores everything ran fine. So it looks like depending on how your system is set up, unparking the cores can cause some problems with high overclocks. Something I didn't catch earlier. This can be a bad tweak if your system isn't set up right for it, as mine clearly was until I pulled my head out of my butt and fixed it.
Quote from: Idontcareurl=http://forums.anandtech.com/showthread.php?t=2318675#5]http://forums.anandtech.com/showthread.php?t=2318675#5[/url]]The problem with LLC, or any voltage tweaking for that matter, is that the voltage changes faster over time than any software app is going capture and report...but the CPU itself will crash the moment the voltage drops below a critical threshold value.Voltage readouts you are getting from your BIOS or from CPUz may seem like they are updating in realtime but they are only sampling the actual voltage in steps over time.CPUz is even worse because it doesn't even show you the observed voltage, it quantizes the voltage in 0.008V increments, and to make matters even more worse it rounds down the number when reporting to you.So if the BIOS is reporting "1.287V" for Vcore then CPUz will take that number and report to you that the voltage is "1.280V"...a full 0.007V lower than what it actually is.So let's say your CPU really does need 1.286V and not a drop lower, but CPUz is telling you it is running along just fine with 1.280V. (which is not true, because it would crash at 1.280V) So you are led to think your chip is fine at 1.280V.Now you start up prime95, and so long as LLC keeps the Vcore at a value between 1.280V and 1.288V then CPUz is going to keep telling you the Vcore is 1.280V.Well lets imagine the actual voltage is 1.287V, just a smidge above the 1.286V minimum threshold. CPUz is still saying it is 1.280V but the CPU is stable nevertheless. Now a momentarily change in the Prime95 load causes a transient voltage to drop that Vcore from 1.287V to 1.285V...boom, CPU is now unstable.But CPUz is going to keep on reporting to you that the voltage is still 1.280V.In short, CPUz sucks and in ways that fool people into thinking their system, or parts of it like LLC, are not acting rationally when infact they are. It is CPUz that is problem as it is generating crap data for you.
Quote from: Idontcareurl=http://forums.anandtech.com/showthread.php?t=2318675#16]http://forums.anandtech.com/showthread.php?t=2318675#16[/url]]You don't need perfect programs, you just have to know the limitations of the ones you are using.Take the statement of yours above which I quoted from your OP. The problem you are observing is not that the "average" voltage is high enough or too low, rather the problem is that you are blind to the transient voltage swings that are occurring during loading and unloading (which can happen on the timescale of micro-to-milliseconds).The "maximum negative undershoot" value during idle and during loading is what causes your processor to become unstable, not the average voltage over the long-run at idle or under load.PIC that I can't quote at here.^ those voltage oscillations are called "transients" and your BIOS and software-based voltage monitoring software are blind to them because they happen very very quickly (milliseconds) but when they happen they can still cause your processor to be borked.
Quote from: silkyseanurl=http://hardforum.com/showpost.php?p=1036997079&postcount=329]http://hardforum.com/showpost.php?p=1036997079&postcount=329[/url]]LLC on REGULAR and Offset @ +0.140 = 1.368v under load (1.088 on idle) PRIME STABLELLC on MEDIUM and Offset @ +0.095 = 1.368v under load (1.040 on idle) PRIME STABLELLC on HIGH and Offset @ + 0.060 = 1.368v under load (1.000 on idle) PRIME STABLELLC on ULTRA HIGH and Offset @ + 0.025 = 1.368v under load (0.982 on idle) - BSODLLC on EXTREME and Offset @ - 0.020 = 1.368v under load (INSTANT DEATH)
Quote from: chris635 on May 10, 2014, 07:30:34 PMI waiting on windows 9.