Printable View
Yes, the warning about C&Q is only related to custom C&Q (both techniques interfere with each other, as the tooltip suggests). Otherwise it's no problem and you are encouraged to use C&Q unless you have good reason to, and then you should control it with the percental CPU speed settings for each power scheme in case you want to restrict it to a certain P-state range. It makes no difference for the tweaker's other functionalities.
That is normal if your AM2+ system was single-plane. AMD specs Deneb chips with a lower NB/HT speed for single-plane operation. 2GHz is only the default for dual-plane motherboards.Quote:
Originally Posted by RaV[666]
Thx for that info DedEmbryonicCe1,was thinking only am3 allowed 2ghz HT/NB on stock.
Kink, i have more input with verified data as today im sober and fully functional ;-).
I tried again carefully editining register lile you said, but error persists(reboot and no reboot)
I tried disabling and enabling CnQ in bios, no go.
I tried different power profiles in windows (as not all of them enable CnQ anyway), no go.
I tried startiing up Phenomsr, and with error window in background setting service/main window with correct settings.This works up to the next boot, when i have to do all the setting again, in the service window it displays previously set settings but it seems that for de error and CnQ only settings in main/start window are relevant.
Neither pure or phenomsr CnQ seem to use P4 on my cpu/mobo.
As i wasnt sure i was modifiying register correctly i set it through phenommsr (with error in background) and tried that too, bet error still persists.
When i start manually pheniomsr service it stops itself immedietaly, and doesnt seem to affect CnQ speeds,i think it errors too.
CnQ settings seem to be changable only through main window of phenommsr (with error in the background), but they are zeroed upon reboot.
So with this version, only way to use it is to fire it up,hide error (clicking ok in error window closes program),set manually all states, click apply ,exiting program, fireing it up again (this time no error) and it works only till the reboot :-/.
P4 state (when in error mode) is:
All multis 8x
Cpu Vid 1.3 (my max official vid,thats a non BE chip)
NB Vid 1.225 for some reason, maybe its my fault.
And when i set all this things at or below P3, it stops erroring.
I think that old Phmsr worked because i i recall correctly it had only 2 power states.
Are there any command line options which would bypess P4 altogether or disabled checking it ?
AM2+ is dual-plane, AM2 is single-plane. And AM2+ is officially rated for HT up to 2.6 GHz; AM2 is capped at 1 GHz.
Simply ignoring the exception is dangerous as the program's state may not be valid anymore. If the service stops immediately, there's probably something wrong with your registry entries. You may wanna start from scratch: delete the HKLM\Software\PhenomMsrTweaker key altogether. Then start the GUI, ignore the exception (since it seems to work for you nevertheless, but in general this is not a good idea), customize your P4 and apply. Then open the service dialog, check the 'make permanent' checkbox and make sure the settings below reflect your new P4 settings, otherwise click on the update button. Then apply here too. The PhenomMsrTweaker service should be running then, if it isn't, something else is wrong. After that, you may enable custom C&Q, which should make use of P4 if you set the P-state bounds accordingly.
OK I think I got the hang of it. Works great so far. Thx kink for the hard work.
You're welcome. New version 2.0.4 out, including some minor GUI bugfixes (including no more exceptions in case P4 has not been initialized by BIOS and defines an invalid voltage). I also switched to Visual Studio 2010.
Awesome job kink. Should I just uninstall the previous one? Thx.
Thank you. Works like a champ on Asus M4A785TD-V EVO and Phenom II X6 1090T with CnQ off in bios. :up:Quote:
Originally Posted by kink
I just added the FAN1 value to my registry and upon reboot, I am very pleased with how it's working. So, now, kink, do you know which other fans PMt can control? Because SpeedFan normally could only control the one plugged into the CPU header, even though 3 headers are actually PWM rated on my board (790XT-UD4P, with Phenom 940 Deneb).Quote:
Originally Posted by kink
I would love to have it controlling the 2 fans in the other 2 PWM spots (the so-called "PSU" header and the "Sys1"). I guess I could add the values for FAN2/3 and see if it makes a difference, I'm just skeptical it will.
But regardless, thank you so much for going back to work on PMT (if I can so-abbreviate it) -- I love it, and my temps have never been so low! You rock!!
:banana3:
Thanks for the roses ;) and glad to hear this feature has not been overlooked. :)
Which 3 fans can be managed depends upon how the headers are connected to the SuperIO controller, so the simplest option to find out is to experiment with it, e.g., set the fan to 1% ('FanX' = '0:1'), restart the service and check which fan slows down.
My Asus M3A78-T features an IT8720F controller, fan1 is the CPU fan (regular 4pin-header), fan3 is the first chassis fan (3pin only) and fan2 either the PSU or the second chassis fan (again 3pin; my fans attached to these headers do not support PWM, so I don't know and don't care). The interesting thing is that PWM still seems to works with the 3pin headers: my fan3 doesn't support PWM, but it is attached to a Zalman Fan Mate 2 rpm regulator, which in turn is connected to the mainboard's fan3 header. The regulator seems to translate the PWM signal to actual voltage changes and hence allows me to manage the fan. So I guess you may just as well be able to manage PWM-capable fans attached to 3pin-headers too.
Also note that the fan speed percentage is not really 0-100% - this range is mapped to actual 20-100%, e.g., 12.5% translate to actual 30%. 0% though should disable the fan. So the fan speeds may differ from SpeedFan's. I chose this mapping because the controller natively supports it and it allows more fine-grained control in the upper range.
/edit: Btw, the CPU temperature is the one from the CPU's internal thermal diode, i.e., the core temperature shown in AMD OverDrive and CoreTemp, not the one the SuperIO controller is supplied with. I chose to use this sensor as it's fairly easy to access and because the CPU temperature seems like a good criterion for overall fan management to me: in most cases, a GPU-intensive task also stresses the CPU at least somewhat, thereby preventing energy savings and leading to higher CPU temperatures and hence increasing fan speeds. The most obvious thermal hot spots besides CPU and GPU are the voltage regulators, but their load is proportional to the CPU load. So I think this justifies the restriction of a single temperature as criterion for the management of all 3 fans.
Kink, how to see what version is running? I'm not sure if i have latest version...
search the exe-file(s) in installation directory, select properties and there version ...
Version 2.0.3.0.
Is it valid version number? I doubt it.
Any clue? is it fresh or not?
What I ask Kink - it would be great to show version number in PhenomMSRTweaker window
deinstall your version (2.0.3) and install the current 2.0.4
;)
Hey kink, PhenomMsrTweaker is amazing, I've put it on every single K10 machine I've come into contact with.
I was looking at adding K8 support for a friend that's on an athlon 64 x2 6400+, and I'm not sure what to change to let phenommsrtweaker run on his system.
From what I can tell, I think what I need to do is add a check for a 6400+ (or any K8), using CPUID I think, then change all the Msr calls for K8 FIDVID and P-state stuff. I'm pretty sure 0xC0010042 is FIDVID_STATUS, and 0xC0010041 is FIDVID_CTL.
Does that seem correct?
I got this info from this pdf.
Also, the newest version of PhenomMsrTweaker broke MinVID for me. It's the default 0.0125V instead of the old 0.775V on my PII x2 550. Same goes for my Sempron 140. This isn't a bad thing, as min voltage on the sempron is higher than what I have it set at :D
On a side note, how do you figure out what fan controller the mobo has?
Thanks for the great software,
-Nodex
Hi nodex,
after a quick glance at the linked pdf, I see quite a big difference in both architectures - P-states themselves don't seem to be customizable, the only option seems to be the direct transition to a given voltage and frequency via 0xC0010041. To keep it simple, you should focus on the service as it is the core, the .NET stuff is just for the GUI (which isn't necessary if the user is able to configure the service directly via the registry). Then it depends on what your target is - you could simply add a hack when the service is started to transition to a given voltage and frequency. C&Q will probably need to be off to ensure the settings remain active - a common scenario if you're only interested in applying overclocked settings. If the target is custom C&Q for K8, you will need to replace the switch-P-state command (by writing to 0xC0010063 if I recall correctly) by a write access to FIDVID_CTL, applying the voltage and frequency of the new "P-state" directly instead. You may need to use 2 writes - increase the voltage before increasing the frequency / decrease the frequency before decreasing the voltage.
You will basically need to look at all code segments performing low-level stuff (using the WinRing0 API) as the code is clearly tailored for K10.
/edit: About the min voltage - the previous limit of 0.775V was a deliberate choice of mine to keep the range on the safe side, but I then decided that it's really up to the user, so 0.0125V as min voltage, even if probably noone will ever be able to confirm it works. ;)
About the fan controller: it's in IT87FanController's constructor. Information about the procedure can be found in IT87xxF references (I found a public one for IT8712F, newer ones aren't public anymore) and in the Linux codebase. :)
Regarding the fan controller, I installed SpeedFan and I have the same controller. Although, both of my fans are 3-pin and speed controlled using a trim pot, so I guess it won't make a difference.
For my cpu (phenom ii x2 550 unlocked to quad), i was able to put voltage at 0.725 with a 4x multi, but as soon as i did 0.7, it locked up. Right now, I'm at a comfortable 0.8V/6x underclock, and a 1.375V/17x overclock. I love this program.
I found this list of P-state VID/FID combinations for different K8 cpus. While my friend's 6400+ isn't listed, it's the same voltages + 200mhz for each state over the 6000+ (page 31). There's also this pdf for socket 939 and 754 cpus.
Anyway, so, how should I go about substituting P-state switching with P-state reading/FIDVID writing without removing support for K10? I think I'd also need a way of changing VID then FID when going up, and FID then VID when going down.
My coding skills are minimal, so I might need help putting the right funtions and function calls in the right places.
Right now, I'm using visual studio 2010 on my phenom ii x2 system (my main computer). I have direct access to two test machines (one with a sempron 140 (k10), and another with an athlon 64 3200+) and indirect access to a 6400+ (over rdp, or asking him to do something via chat while he's using the system).
Thanks,
-Nodex
Hey RaV[666],
Have you fixed your problem yet?
I had the same exact error on my brother's computer (phenom 9550). Followed Kink's directions but for all states, got it to work and then custom set my own states for the service. It's all working now.
I went ahead and made a .reg file for your 910. It sets all the p-states to have a 13x multi, 1.4 cpu vid, 1.225 nb vid for all 4 cores.
Delete the old phenom msr tweaker reg key, then add my attached one.
That may be true, as the fans need to either support PWM directly or be attached to a fan controller translating the PWM signal to voltage changes for the fan (via my Zalman Fan Mate 2, for example).Quote:
Although, both of my fans are 3-pin and speed controlled using a trim pot, so I guess it won't make a difference.
Sadly, if I could point out all the needed changes in a forum reply, it would probably take more time than including K8 support myself ;). If you know some C++ and are willing to learn a bit about some low-level stuff, here's a great opportunity to do so. :) The first reference would be the official AMD doc you linked earlier, everything you need to know is there - the limits are readable from FIDVID_STATUS (including the default multiplier, max multi and max voltage), the changes are performed via FIDVID_CTL (the encoding scheme of multis and voltages is listed in the table, the register description contains the offsets of each field, so that you know which bits to set/read; this involves some bitwise shifting and masking, so make sure you're settled in this topic). The WinRing0 API (OlsApi) is used to access the CPU's registers in kernel-mode (e.g., Rdmsr() to read from a register, Wrmsr() to write to it), so you'll need to scan the service code for primarily these 2 functions and dependencies. Use CpuId() (I think ;)) to distinguish between K8 and K10 (and please cache the result, as there's always a costly transition from user-mode to the kernel driver and back involved).Quote:
Anyway, so, how should I go about substituting P-state switching with P-state reading/FIDVID writing without removing support for K10? I think I'd also need a way of changing VID then FID when going up, and FID then VID when going down.
My coding skills are minimal, so I might need help putting the right funtions and function calls in the right places.
For custom C&Q, you'll need to modify the P-state settings format in the registry from K10 registers to a FIDVID_CTL register values (masked, so only the bits for VID and multi). During a transition, you then write these values (again masked, i.e., the other bits are copied from the current value) to each core's FIDVID_CTL (I assume there's a complete set of MSRs for each core as for K10). As noted earlier, you may need to do this in 2 steps, voltage then multi or the other way around if the CPU doesn't handle it in hardware. That would be my recommended starting point: implementing custom C&Q for K8 too. If there's a K8 CPU, you should skip appying custom P-state settings and unlocking P-states when the service is started. Then look in CustomCnQThread for necessary changes to include K8 support. K8 support would then be configurable via direct registry manipulation (due to different P-states format, e.g., you could use a human-friendly string format like "10|10@1.2" and parse it to FIDVID registers when initializing the service, then use them in CustomCnQThread).
So don't give up, good luck :)
Actually, it sounds like a good plan.
I'll stick to just service and registry support for now.
I think for now it'll be fine just to hack up your code and change all p-state stuff appropriately (using the status and ctl registers for K8 instead).
The bitwise shifting and masking looks easy enough from looking at your code (>> and <<, plus && with certain values).
I've tested reading from FIDVID_STATUS and writing to FIDVID_CTL using crystalcpuid, with success,
Using CPUID() seems easy enough to distinquish between K8 and K10.
I'll add checks for safe VID and FID switching anyway, just in case.
How do I cache results from a CPUID() call?
I'll hack together something hopefully soon. I aquired a new K8 system to test on, so this should be fun.
Afaik, there's just one set of MSRs. Writing to FIDVID_CTL changes both cores at the same time. Apparently, however it's done, if only one core has its VID or FID changes, it won't change if going lower, and both cores change if going higher.
Simply by keeping the result in a variable instead of using a CpuId() call for every check.Quote:
How do I cache results from a CPUID() call?
I think there are separate MSRs for each core, see section 10.5 in the AMD doc. Quote from 10.5.7.3:Quote:
Afaik, there's just one set of MSRs. Writing to FIDVID_CTL changes both cores at the same time. Apparently, however it's done, if only one core has its VID or FID changes, it won't change if going lower, and both cores change if going higher.
This seems to apply to your results as well, so it may actually be done by the hardware itself, not the CPU driver. Testing is easy: modify an MSR on the first core, then read it from the second, if they don't match, there are separate MSRs, and you'll need to write to all cores.Quote:
The processor driver enforces a “highest requested P-state” policy. Both cores will be in the highest P-state requested for either core. The processor driver keeps track of P-state transition requests and only reduces the P-state of either core after the operating system has requested that the P-state of both cores be reduced. When the operating system requests that the P-state of either core be increased, the processor driver increases the P-state of both cores.
Also have a look at tables 66 and 67 in section 10.5.7, as K8 doesn't seem to be able to transition from a given multi to an arbitrary other multi (only up to an absolute delta of 1, i.e., half and whole steps up and down, of this strange VCO multi, which is identical to the actual multi if >= 8 and the doubled multi if < 8; [nerd]explanation: this is the numerator of the actual multi, and they'll use a denominator of 2 for multis < 8, skipping every other clock cycle; the aim is to modify the clock generator's frequency in steps of half and whole reference clocks[/nerd]). It also looks as if you need to do the transition in 2 steps (and some iterations for a transition to an arbitrary other multi). Section 10.5 is very detailed and should contain all the necessary information.
Have fun and keep in touch :)
/edit: Note that you can debug the service. Start Visual Studio with admin rights (the service needs admin rights in order to load the driver) and select the right configuration (native platform, debug build). Then copy the WinRing0 binaries to the configuration's output folder. After setting the service as StartUp project and launching it with F5, you can debug it like any other app by placing breakpoints etc. Use Ctrl+C (in the console window) to stop the service and ignore the following exception by clicking on continue.
thread rez
this thing is great for the thulban, but since the thulban can use different voltage per core and this can only control the stated of up to 4 cores in unganged mode it would be nice if there was an update.
this is a life saver for the summer as my 1090 has a vid of 1.3 but it can do that at under 1.2V so cool and quiet was raising the voltage to throttle it to 800mhz @ 1.225V, now it dose 1V as it should and it dropped a good 30W idle
The unganged mode supports all cores, not just up to 4. Additionally, all K10 (incl. K10.5 etc.) CPUs support different voltage IDs per core, but all cores get the same actual voltage - corresponding to the currently highest voltage ID of all cores.
interesting, when i was testing it before i set it to ganged it would always have 2 cores at p0 but the other 4 at p4 without load. and with AOD and everest it showed with cool and quiet enabled (before using this and disabling cool and quiet) it would show the correct voltage for each core depending on its pstate, now they all have the same. am i doing something wrong or is AOD messing with me.Quote:
Originally Posted by kink
i think that u covered the voltage as amd was messing me, but i just want to be sure. the power output has gone way down though and its a god send when u have an old AC unit and its over 100f outside all the time to beable to use the computer
That's probably due to inappropriate custom C&Q settings - don't simply switch from ganged to unganged mode, you'll also need to adjust the other parameters (the thresholds are per core in unganged mode, for example, and you'll also need to lower either the interval or the number of samples to reduce the delay from load/idle detection to P-state transitions - of key importance when dealing with loads which do not affect all cores, otherwise the performance is notably decreased!).Quote:
when i was testing it before i set it to ganged it would always have 2 cores at p0 but the other 4 at p4 without load.
OverDrive shows the current voltage ID of every core, so it should show different voltages if the cores are in different P-states (and if the voltages of the P-states differ, of course). That's what it does on my machine, and I haven't heard otherwise from any other user. In ganged mode, all cores are in the same P-state at any time (well, apart from some milliseconds for all transitions), so that the voltages are the same.Quote:
now they all have the same.
Btw, if your default C&Q used a VID of 1.225V for 800 MHz, your BIOS is obviously buggy as the default is about 0.8V afaik.
here is what its doing
http://i47.tinypic.com/vr4jd1.png
and yes i figured that it was a bios bug, but i have a 790fx gd70 and msi sucks with distributing beta bioses and fixing problems that wont effect sales.
i do love the program im just a little confused. and when u said that AOD displays the VID of the core but each core gets the actual voltage, that would mean that since cool and quiet is disabled it would read the voltage to the cores so they would all have the same actual, so thats what it would display?
Well, this screenshot is confusing me too. :) All I can say is that there's definitely no issue concerning writing the desired VIDs to each core's P-states. Although I would have guessed that the BIOS cannot interfere here, I strongly suspect that the faulty BIOS is the cause of this phenomenon. But since the actual voltage is 1.1875V in this case anyway, it doesn't change anything.
I'd suggest reducing the number of samples further. For example: if there's a single-threaded load (and no other relevant loads) and the thread hasn't been manually bound to a single core, the Windows scheduler re-assigns it to different cores over time. Using your settings, a core in P4 (800 MHz) switches to P3 (1600 MHz) only if the thread has been assigned to it for about 4*50 = 200 ms. After another 200 ms of constant assignment, it switches to P2 (2200 MHz) and so on. Based on my experiments, the scheduler re-assigns the threads rather frequently, so I'd rather suggest something like 2*25 ms for up and down (and maybe even enabling "aggressive up" to switch directly to 3200 MHz after 50 ms of constant load). Just experiment with a single Prime95 thread (or the like) yourself and measure the performance decrease compared to ganged C&Q or no C&Q at all, it may be huge! Also note that you do not have to use custom C&Q as default C&Q is supposed to work pretty well on Phenom II and Windows >= Vista. PhenomMsrTweaker then simply applies your P-states and lets the driver switch between them.
well its working in ganged mode, and the bios ms has for the thulban is a little off so i guess its a wait and see
Thanks to kink for this beautiful utility!
I found that I can raise the NB frequency to 266 MHz without problems (so I can run all my 8 GB RAM at 1066 MHz avoiding the 4 DIMM modules limitation). Now I am at 2500 MHz. But the problem is: if I raise the clock the "original" C&Q ceases to operate, leaving my 940 BE at full 3.0 GHz.
I thought to use this program to solve this problem.
But I have a little doubt: as I have to raise the NB-CPU voltage a little more than stock voltage, I need to set the value in PhenomMsrTweaker, but if the value is set only in BIOS, when the program starts, the voltage (I suppose) will go back to default (in fact I tried, but always getting a BSOD).
I thought about a possible solution:
1) I leave the BIOS NB-VID and reference clock to default settings
2) I boot the system and set the NB-VID in PhenomMsrTweaker to the deisred (higher) value (to ensure stability with NB-CPU at 2600 MHz clock)
3) I reboot and set the voltage as above and raise ref. clock from 250 to 266 MHz in BIOS settings
4) I save the setting and reboot
Do you think it is the right procedure?
Thank you for your kind attention,
L.
Hi all.
Is there any possibility to change my NB VID with this tool or K10stats on my Phenom 9500 and Foxconn Destroyer?.. Which setting should i use in BIOS? Now it is ******* locked on 1,25V!
Hi Kink,
Is there any way you can change how much voltage is allowed to be applied in PMSRT?
It seems like 1.55 is great amount, BUT i think i need a lil bit more to push for the 4.6ghz mark.... LOL
Thanks kink! :D
Nope, 1.55V is the maximum VID. But if you additionally raise the Vcore in BIOS, the BIOS might apply the difference from the original Vcore to every VID. We've already had this VID => Vcore topic in this thread a couple of times.Quote:
Is there any way you can change how much voltage is allowed to be applied in PMSRT?
I can't tell you, just have a try. I suppose it's gonna work.Quote:
Is there any possibility to change my NB VID with this tool or K10stats on my Phenom 9500 and Foxconn Destroyer?
It doesn't really matter, but I'd suggest starting with the default one (the locked 1.25V if I understood correctly).Quote:
Which setting should i use in BIOS?
@fastleo:
The procedure you described seems a little too complicated to me. I suppose you can just set and apply your settings in full overclocked mode. When you first start PhenomMsrTweaker (the GUI) it displays your current multipliers and VIDs for every P-state. If the NB VID in P0 is not the same as the voltage you set in the BIOS, the BIOS probably applies the difference from the original voltage as fixed offset to every VID, so keep an eye out for that one. But anyway, I think you only need to make sure all P-states specify the same NB VID (most likely P0's VID pre-set by your BIOS). Since the effective NB voltage is governed by the maximum NB VID of all cores, it may drop to an unstable value as soon as no core is in P0 anymore (if your BIOS hasn't applied the higher VID to all P-states, which was my first guess). Distinti saluti :)
/edit: Btw, my setup is similar to yours (also due to the memory controller limitations) - my reference clock is at 250 MHz atm (used to be >260 MHz too), the NB is clocked at 9x250=2250 MHz. I increased the NB VID in BIOS to keep it stable until the tweaker service is started. The service then applies the higher NB VID to all P-states. The only difference is that I'm using a Phenom I, but I suppose this doesn't matter here.
kink, you will also be needed again in HLuxx
thanks for this great tweaker!
Works great with my 890GPA-UD3H and 95W 1055T! Thanks for saving me 25w at idle :-)
--Matt
Kink, thanks again for this awesome tool! :)
Yeah...thank you for the tool! :up:
bump and another thank you. Using a late 2010 week 955 X4 with -
P0 - 3.6GHz 1.3V
P1 - 1.6GHz 0.83V
2.6GHz CPU-NB with 1.34V, will try lowering to 1.31V.
Now P1 uses less power than stock CnQ at twice the frequency. DeltaT of 4C between idle and load :D
Hi
I cant make it work on the crosshair V formula..
It doesnt apply the settings.. maybe for the the new chipset unsopported yet?
Software isnt developed no more.It doesnt work for me either (properly) even though i have 790FX witx x6 (it worked on x4).Pity, as it was brilliant.
its a pity..Quote:
Originally Posted by XRL8
I used k10stat but it doesnt work on the CH V so I tryied this but same thing. I think chipset not supported yet.
i think someone needs to get on this asap, love this program and hope ones like it exist really soon for when BD is out
That's odd. It works fine with my X6 on 785G, 890GX, and 890FX boards. What is it complaining about?Quote:
Originally Posted by XRL8
--Matt
Works great on new Gigabyte UD7 w/ 955! Not a hiccup one. Great software, and I agree someone should jump on this like flies on :banana::banana::banana::banana::banana: to make it better and more user friendly with more features. I would but I don't have the knowledge needed.
EDIT: Only problem I am having is it won't keep my changes after a reboot. I haven't tried to run it as admin though. So, that may fix it. I will report back!
make sure that u have it set so it changes all the cores at the same time, aka ganged mode.Quote:
Originally Posted by XRL8
This great utility works pretty well for me on my Athlon II X4 630, except I can't work out what settings to use to keep my CPU in P3 when I'm not doing much.
At the moment it's constantly switching between P3 and P2, with some jumps to P0, when my cores are around 25-35% (Total CPU <40%). I've got PhenomMSRTweaker set to Ganged, Sampling Interval - 50, Load Thresholds 50 & 20, Consecutive Samples 2 & 8, Aggressive Up disabled.
Kink: Not sure if your still around, but a version of "BulldozerMsrTweaker" would be awesome! :D :yepp:
IMHO, this was one of the best and most useful progys for Phenom ever released...
I'm affraid to try the Phenom version on BD. I'm sure the registers have changed, hopefully that may make it easy to modify by a person with your skills!
Oh well, it's a shot in the dark, just thought I'd throw it out there.... :p:
+1
i even have a few ideas for improvements (it didnt like when you disable some cores and forgot to clean out the registry)
Hey, Kink,Quote:
now supports setting the max number of cores in the Turbo state when using custom C&Q (also allows you to disable the Turbo). Higher multis should be allowed now, e.g. for 1055T. Could someone owning a Thuban check whether the Turbo works as expected when using custom C&Q? I still have my Phenom I 9950, can't test it myself...
I've been reading up on the behavior of PHMSRTwkr wrt Turbo & CNQ, like what you wrote a while ago (came from late 2010 I think).
I have 1090T, and in bios:
FSB=230, Multi=Auto (16), Turbo=Enabled, multi auto (18), CNQ=Disabled
In PhenomMSRTweaker, P0 has 18 multi (that's Turbo, right?), P1 = 16x, etc. On Service page, have checked "Enable Turbo Cores", with 4 selected. Unfortunately, once I turn on PhenomMSRTweaker, the cores never go to PO. If I turn off the service, the turbo cores do get activated and run at 18x, the default on the 1090T.
I wonder my PMSRT profile is "stuck", cuz for a while ran with Custom CNQ, with Balanced only going from P1-P3. Thought I might try uninstalling/reinstalling and see if that fixes it.
But what do you mean about having both Turbo and Custom CNQ enabled? It seems like the UI makes them mutually exclusive, unless you mean running Custom CNQ with CNQ disabled in BIOS, and the OS handling Turbo.
perfectly works in Windows 8 with X6 1055T
Could someone please post an updated link to the hotfix that fixes the issue of "Powerreadfriendlyname()" error?
I was searching for a solution and found this thread. However, the link on #162 by kink is broken :/
I just want control of my speed again! haha