I don't know a lot about the subject, but I have got quite a few BSOD after undervolting. Most of them of course showing WHEA uncorrectable error. From my cases, it was because I undervolted too much the CPU. If this didn't happen before you started undervolting, then it is definitely because of undervolting. Reduce the amount of undervolt you are doing and check for a stable value. You can also try to undervolt GPU and CPU separately.
-
Add in iGPU Unslice voltage offset equal as for iGPU and your're good to go.
From your own example above...
iGPU Unslice -50mv
iGPU -50mv
Cpu Core and Cache need the same offset. -
Ok so pictures:
The rest of the options are the default ones. I enabled Speedshift by just ticking the option in the main window and ran the 3DMark test Time Spy where I see the loss of performance. Then again, I lost about 20% performance in the CPU test, and 5% in the GPU test (due to the CPU). If I disable the SpeedShift and disable the undervolt, I regain the performance but the CPU throttles a lot. I thought about undervolting it to alleviate the temperatures and get more performance.
Log link: https://pastebin.com/r9uKaNYj
I also tried to force the error I described in my original message minutes ago disabling the Speedshift and enabling the undervolt at -70mV. The image issues are relative to the Intel GPU as I finally got a blue screen specifying the issue. Maybe I could try installing the Intel official drivers and not the ones provided by Asus? Is that advisable? I am asking because Intel do not advise doing this if I don't need it. Question is, may I need it?
Thanks a LOT for your help
Your program is amazing, it's just me not understanding some stuff or my computer being difficult to configure :/
-
Speed Shift 101
Speed Shift is usually enabled by Windows 10 automatically. Once Speed Shift is enabled within the CPU, you cannot disable it. The only way to disable it is to reboot. When booting up if your bios or Windows 10 enables Speed Shift again, then there truly is no way to disable it. When ThrottleStop shows SST in green, that means Speed Shift is enabled within the CPU. All you can try to do is work with Speed Shift.
If Speed Shift is enabled, there is a setting called the Energy Performance Preference or EPP. In ThrottleStop this can be adjusted from 0 (max performance) to 255 (minimum performance). Open the FIVR window. Look at the monitoring table in the top right corner. This data is live. It tells you what Speed Shift EPP value your CPU is presently using. Your screenshots above shows Speed Shift EPP at 0 so it is set to maximum performance. That is a good thing when plugged in and gaming.
On the main screen of ThrottleStop, if you put a check mark in the Speed Shift EPP box, this will tell the CPU to set the Speed Shift EPP value to 128. You can click on the number 128 and change it to whatever you like. An EPP setting of 128 will reduce your CPU's maximum performance. I think your testing might have been comparing a Speed Shift EPP setting of 0 vs a Speed Shift EPP setting of 128. It was not comparing Speed Shift enabled vs Speed Shift disabled. I am not surprised if an EPP setting of 128 is reducing your performance. 80 is a better compromise if you want to slow your CPU down when lightly loaded. When plugged in, I would set EPP to 0 so the CPU can run at maximum performance.
The Turbo Ratio Limits for an 8750H should be set to 41, 41, 40, 40, 39, 39. The 8750H is locked by Intel. Setting these limits differently than the default values accomplishes nothing.
In the FIVR window, just below the monitoring table, click on the Install button and follow the directions to download and install the RwDrv.sys file into your ThrottleStop folder. After that you can click on and use the Disable and Lock Turbo Power Limits feature.
I prefer using the latest Intel drivers for the Intel GPU. Did the blue screen tell you what driver or what caused the problem? Most people with the 8750H can undervolt more than -65 mV. Maybe the problem is just your EPP setting.
Where is a picture of the Turbo Power Limits screen? You may not have changed anything in there but that does not mean that everything is OK. Default settings might be a problem.
Do you remember if Add Limit Reasons to Log File was checked in the Options window when you ran the attached log file? I do not see any Limit Reasons showing up in the log file. There is definitely some serious throttling going on. I am not yet sure why. Fix EPP and try again. When you run the TS Bench 1024M test, is the multiplier and CPU speed consistent or do you see severe throttling? Open up the Limit Reasons window and take a screenshot while that test is running if you are seeing throttling.
Edit - You might have something called the Intel Dynamic Platform and Thermal Framework driver installed. Look in your device manager for something similar to that. It too can cause severe throttling and if so, it should be permanently removed.
@Automatikjack - If you are undervolting and getting WHEA errors then your CPU probably needs more voltage. Every CPU is unique. There is no guide for your CPU. It is all test and tune. If you are getting errors at an offset of -100 mV then you will need to try -90 mV or -80 mV. I would use the same offset voltage for the core and cache and I would leave the iGPU and everything else alone until I had my CPU 100% stable. This is my unofficial guide for an 8th Gen U series CPU.Last edited: Aug 20, 2019Ernesto Cardoza and 4W4K3 like this. -
@unclewebb
Hello unclewebb,
Can I ask you for little help?
I just managed upgrade my old system H 61 from Pentium to i7-3770s which was very tough as I needed ask for help bios experts to modify my SPI image.
Now system is stable and I really enjoy 3 gen with Throttlestop.
Than I found something about possibly unlocking 4 turbo bins and I would like give it to try.
Do you think should I go for another bios mod to unlock advanced settings for core ratio (currently I can see at AMIBCP hidden setting for it), or em I stuck here without any chance whatsoever?
MSR register 0x194 shows 0x00190000 and cant be rewrite to 8. After reboot still shows same bit 9, also bit 1 cant be rewrite.
Maxmulti shows I am on max but TS shows same core ratio limits.
When I click on memory tab at RWE I got bluescreen....
Thanks very much for your reply sirLast edited: Aug 20, 2019 -
Is 90W for PL2 high enough? I've been getting PL2 limit reason is TS and I'm not sure if I should upped my PL2 power limit. Is there a limit of how high I should set my PL2 limit? According to TS my max temp reached 89, I assume that's when it actually draw the 90W. The highest I ever saw it draw on benchmark was 70s on cinebench. Does raising PL2 limit as long as it doesn't temp throttle make sense or is it not good for the components?
-
@unclewebb
Thank you for the advice, Current Limit is locked, so no go there ./sad. I'm game to try PowerCut but if you don't mind elaborating a bit -
why, "adjust the VccIn to approximately 1.80 V"? Is that a safe voltage across all Haswell Chips? Why not just enable PowerCut with 'default' set for the VCCIN? Lastly, provided I've got all my settings to default (not doing anything weird), is there any realistic chance this setting will 'fry' the board or chip?
Thank you again for the help. -
RwDrv.sys installed. Do I need those features for something specific in regards to the behaviour I am experiencing? About the iGPU, I installed the official Intel iGPU drivers over the manufacturer ones, and now using -65mv with SpeedShift of 128 makes my computer reboot when running the TS Benchmark. It did not happen before. I never tick the check for SpeedShift anymore since i want it to run on maximum performance, i.e., speedshift 0 which is like that by default as far as I understood
. The turbo ratio limits were those by default, I did not change them. And regarding the blue screen error, it was a bluescreen showing TDR Delay error (i have TDR enabled and set to 2 seconds, apparently it failed). Now, when the gpu gets stuck, with the new drivers, I don't get any bluescreen but an instant reboot. All of this without touching EPP setting.
Yes, I had the option for Limit Reasons checked. When running the TS Bench without touching EPP (i.e., epp = 0) the CPU throttles and gets stable at ~3.6GHz on all cores. The Limit Reasons window show "PL 1" as the reason for this throttling. If I enable the EPP to 128 and run the TS Benchmark @ 1024MB and 16 threads, throttlestop closes after 3-4 seconds withut giving any apparent error with the new iGPU drivers. It did not with the older, manufacturer ones.
I do have the Intel Dynamic Platform and Thermal Framework driver installed. May I remove it? Could it be responsible of these issues? -
That confirms that your CPU supports +4 bins of overclocking. As far as I know, the H61 chipset does not support overclocking. I do not know if there is any trick to make this work. If you had a Z series chipset, you should have no issues using those extra 4 bins of turbo boost.
If your temperatures are fine, you can set your power limits as high as you like. No one on any forum has done any long term testing so I cannot tell you if this will be good for your components or not. All I know is that there have not been a lot of CPU casualties during this 1042 page epic thread.
That does not sound good. I would go back to square 1. You need to make sure your CPU and GPU and your entire computer are 100% stable at default settings. That includes your memory. A properly functioning computer should be able to run any software including the TS Bench without reporting any errors or randomly crashing.
Depending on the manufacturer, this can cause throttling problems but I do not think that this is your main problem. You will need to do some Google research if you decide you want to try and remove this so you can do some testing.
A GPU should never get stuck. Something is wrong. Either a bad GPU or the driver you are using is not stable or your memory is causing errors.
PowerCut takes advantage of a bug within Haswell processors. This only works if VCCIN is set to a value. It does not work when VCCIN is set to Default. I am not sure what is safe or not safe for VCCIN. Much less than 1.80 V and my Haswell will lock up. Some are not as sensitive. Try some different values to see what your CPU likes. In the name of science, I tried this maxed out at 2.30 V. Probably not a good idea to be doing that in a laptop but my CPU still runs just fine even after all of the abuse.Last edited: Aug 21, 2019Porter and Samchanchan11 like this. -
Have you done anything else to the laptop? Used another undervolting software like XTU or undervolted Nvidia GPU? If the BSOD wasn't appearing before undervolting then it is highly the reason for it. Try reducing the undervolt and see if it is stable somewhere lower. -50, -40, etc. Although it is still weird that you are gettinb BSOD at -65 already. Just to be sure, you are clicking on the Turn On button right? I have seen guides where the OP doesn't say anything about it (My first time undervolting where I was so confused about him not turning it on lol). Are you sure the reason for BSOD is the Intel GPU? Because you aren't undervolting it. Another solution could be to reduce the Turbo Ratio Limits with throttlestop. It will of course reduce performance but it should help with temperature without messing with the undervolting part. In your first thread, you say your graphics was resetting. Try reducing the amount of undervolting in your GPU if you have any. I had an issue close to that and that's how I fixed it. I would enable the box of speedshift in throttlestop and set it to 80 to see if it changes anything. As unclewebb said before, do not just use undervolt values you have seen in a guide. These values are are not the same for everyone. Some people might get -200 undervolt and be fine with it.
-
You do not need to click on the Turn On button to have your undervolt applied. Watch the monitoring table in the top right corner of the FIVR window. Change voltages, hit Apply and your voltages will be applied immediately whether the Turn On button is used or not.Prototime likes this.
-
What is the turn on button for then?
-
Older CPU's were not as good at boosting and would drop back down quickly. TS was a huge help back then to get the most our of your CPU. Unclewebb will hopefully explain it much better than that with the actual reasons why.ihueco likes this.
-
To be able to change Set Multiplier etc on main page in ThrottleStop.
ihueco likes this. -
these guys will get icelake b4 us papusan we be stuck on 14nm for a while longer. hope intel ports tigerlake to 14nm so we dont have to wait for 10nmPapusan likes this.
-
Point is, whichever test I execute when the uv is not applied, the computer does not experience any errors nor problems of any kind. I did memtests, stress tests on both CPU and iGPU and stress tests on the Nvidia GPU. No errors. Then, I apply whatever uV value, even small as -30, and the computer ends up getting errors along the day. I've thought about doing the uv tests on a Linux environment to check if Windows is messing something up. Does this idea make any sense?
As far as I've seen, no one is experiencing thermal throttling issues in my laptop. I guess this is not causing any issues whatsoever.
Another idea that I have is installing a really old iGPU driver, but I doubt this is the issue.
Nope, appart from inserting a second 16GB RAM module acquired directly to ASUS or putting a new 1TB ssd. I tried to uv the Nvidia GPU but resetted it to normal values. That did not cause improper behaviours though. Reducing it even to -30 uv ends up giving me errors :\ I'll try again with this little uv values as I updated the BIOS yesterday, Asus released it in the morning. And yes, I know uv values are different per chip, but putting -45 uv and get random iGPU resets (when I did not uv the iGPU) makes me wonder what is going on. And yes, I'm quite sure the iGPU is the reason behind the BSODs and resets. However, as I am in a laptop, I am unable to disable the iGPU to test everything with that part offline. -
I have a peculiar problem... I just built a new gaming PC, with a 9700K CPU and an Asus ROG Maximus XI Hero Wifi motherboard, and the CPU is permanently throttled to 800 MHz, even in the UEFI/BIOS. ThrottleStop indicates BD PROCHOT, and toggling it off does restore the CPU back to its normal operating speeds. RealTemp and HWMonitor both indicate that temperatures are totally within normal and safe levels (~35C idle, ~75C under load). Disabling "Thermal Monitoring" in the CPU configuration in the BIOS has the same effect as toggling off BD PROCHOT in ThrottleStop, but I'm not sure it's safe to use long-term. Does anyone have any ideas what could be causing this, or if RMA'ing the motherboard would be the best course of action at this stage?
-
You can try to undervolt core and cache individually and see if only one of them is the problem. Maybe you can get the hardware checked for errors or something saying that it is throttling. Just make sure to reset the undervolt if you are going to to that. For last resort, you could as I said just reduce the turbo ratio limits or even disable turbo completely. I know it sucks to lose that performance, but depending on the game you are playing it might not matter that much anyway.
EDIT: Maybe your tests/games are for some reason using the iGPU instead of the GPU, and that is why the iGPU is having problems?
@unclewebb What are the chances of getting a non-undervoltable cpu.Last edited: Aug 24, 2019 -
As of today, I have undervolted iGPU and unslice to -200mv, and it does not seem to crash or reduce temps. I guess my iGPU is disabled after all.
-
None. The chips will degrade as the time go and Intel have added in voltage headroom for this scenario.Ashtrix, tilleroftheearth and ihueco like this.
-
I see. Does this mean as time go and chips degrade undervolting will start to crash even when it was stable before?
-
Some reading for you... https://www.overclockers.com/forums/showthread.php/723980-Truth-about-CPU-degradation
Last edited: Aug 24, 2019Ashtrix, c69k, joluke and 1 other person like this. -
I want to make sure I understood it properly. So conclusion is yes it will degrade to a point where it might not be stable because of not getting enough voltage, but since I am undervolting, it will degrade slower and possibly will not degrade enough before I change the laptop or other parts fail first.
-
Yeah, higher voltage+high temp will degrade the chips faster. With undervolt this will take longer time. But high heat will decrease the advantage. And no chips is equal and you won’t know when your chips go up into the hardware heaven. From the picture I added. Some will die faster and some will stay alive longer. None know before the time has come
Maybe you already have sold your laptop before the time has come
tilleroftheearth likes this. -
I manage to get the 8265U on my 13'' lenovo laptop to stay around 20W, with the Disable and Lock feature. With the test for 8 threads and size 1024MB, it says around 18 watts. I would like to try to reach higher Watts, but so far I fail. Can you share a picture of your settings for both TPL and FIVR ?
also, is there any way to increase the prochot temp to 95 deg, instead of 90. -
I'm trying to use MSI Afterburner to undervolt for the first time. I'm guessing for that I need enable voltage control/monitoring? But on the tooltip I shouldn't unlock it if I'm using other program that does similar thing (which I guess TS does). So... Is it safe to enable the voltage control/monitor with TS running?
-
When your CPU is loaded, open up Limit Reasons and see if anything is showing red. Is your CPU throttling? Post some screenshots so I can see what MHz it is running at when loaded. What did you set the power limits to in ThrottleStop? If PL1 or PL2 are lighting up in red, these power limits need to be increased.
There is no way yet. When I originally tried to do this, I did not have much success. I plan to look into this some more in the near future.
MSI Afterburner is for under volting your GPU and ThrottleStop is for under volting your CPU. You should have no problem running both programs at the same time.Papusan and Samchanchan11 like this. -
You have probably answeared this before, but are you working on a Version compatible With AMD Ryzen?
Hope so!
-
hi
I repasted my cpu with kryonaut. this time I applied more paste and the temperature decreases again. And now the power throttle happens very quickly (before the repasting, i could stay at 25Watts longer, but I got quickly in RED thermal limits, with the very restrictive 90 deg limit)
I tried to remove the PL1 and PL2 by increasing hugely the limits and also the IccMAX like i read in this thread, but clearly it does not work.
beginning of the stress
end of the stress
settings
-
@artic_squirrel - It looks like your Lenovo laptop is enforcing the 15W / 25W long and short power limits. The Lenovo C930 that I recently played with did not enforce these limits so it could go well beyond 15W with no throttling flags lighting up in Limit Reasons.
In your situation, it probably will not make a difference, but for maximum performance, try setting the Speed Shift EPP value to 0. I would also not check the TDP Level Control and I would not check the Intel Power Balance feature.
If this gets you nowhere, try setting the long and short power limits to 35 and set both of the time limits to the default 28 seconds. Last thing, try checking TDP Level Control and setting that to 1 or 2 if those are supported.
Kind of sad when the Disable and Lock Turbo Power Limits feature does wonderful things on my Lenovo C930 but does not do anything on yours. I have no magic solution for this problem. When a manufacturer aggressively locks things down, there is not much you can do besides buy a different laptop.
Edit - Also make sure you are using the Windows High Performance power profile. If that option is not listed, use the trick mentioned in this post.
http://forum.notebookreview.com/threads/the-throttlestop-guide.531329/page-1032#post-10935559
I recently heard that AMD's mobile CPUs could use a good under volting utility. Sadly, I have no time or money to start a new project like this. Thousands of people download ThrottleStop each and everyday but on average, only a couple of people per year have taken the time to financially contribute to this project. My wife went out picking bottles one day and pulled in way more in one day than I used to make in a year working on ThrottleStop. Conclusion: writing free software is a bust. It is free for users but it just costs me money so no more freeware projects for me.
I still like answering questions in the forums!
tilleroftheearth likes this. -
I never wanted to make an account but it's about time...
My Build
Alot of detail on before this particular problem can found in this thread on PCPP. This particular problem meanwhile is better described here.
If you just want a simple TLDR on the background then here it is. Problem is described at the very end.
I have a gaming desktop that runs off a super CPU hungry game that works off a voxel-based environment and utilizes the AVX instruction set quite heavily. Early last month I started having issues during gameplay where loading the environment was very slow. After realizing this wasn't a patch issue during the transition from Alpha 1 to 2, I noticed windows performance monitor showed my cpu as pegged under a gigahertz and was capped at 20% load. While trying to diagnose things, then not only was this slowdown an issue, now the desktop is suddenly restarting.
After some digging around, Throttlestop was suggested which revealed the issue to be BDPROCHOT was being triggered. Disabling the intel thermal protection in the BIOS solved this problem.
Still on edge as I usually am with hardware problems, I decided to get my stuff looked at. PSU was fine, no unstable voltages on the 5 and 12-volt rails. Tore everything down, no hardware detected issues as far as my eyeballs and a brightly lit room could tell.
Cleaned everything and reassembled, worked fine again for another few days, now we're back to sudden restarts.
Throttlestop indicates a PL1 under Core in the limits section with a yellow background. Not including any pictures yet because this is occurring even with TS under stock settings and stock up-to-date BIOS. Shall I describe some more, need TS pictures?tilleroftheearth likes this. -
tilleroftheearth Wisdom listens quietly...
-
Alright, well with that being said here are those images.
https://snipboard.io/tdFs0G.jpg
https://snipboard.io/yNLsri.jpg
https://snipboard.io/Z5OghE.jpg
After a bit of BIOS tinkering, I found that downclocking to 3.2 Ghz (and changing no other setting in the BIOS from stock) did eliminate the PL1 issue. Still having problems with sudden restarts though. -
@tilleroftheearth is correct. Lots of screenshots makes me a happy guy.
Some MSI desktop motherboards are having problems with BD PROCHOT throttling. BD PROCHOT is a signal path to the CPU that allows other components on the motherboard to send a throttling signal to the CPU. It tricks the CPU into thinking it is too hot so the CPU responds by slowing down to 800 MHz.
MSI motherboards have an LN2 switch which allows extreme overclockers using liquid nitrogen (LN2) to boot up with the CPU locked to the 8 multiplier for maximum stability. Once Windows boots up, then you can flick this switch and get the CPU to go up to max speed for a quick CPU-Z screenshot or whatever makes you happy. When this switch goes bad or gets dirty, suddenly the motherboard will be constantly sending a throttling signal to the CPU so your CPU will be stuck at 800 MHz regardless of load. Using ThrottleStop to disable BD PROCHOT tells the CPU to ignore these throttling signals. If your CPU ever gets too hot, it will still throttle to protect itself. Disabling BD PROCHOT only blocks throttling signals that are generated outside of the CPU.
Long story short, I would not hesitate to disable BD PROCHOT, especially on an MSI desktop board. Using ThrottleStop totally fixes this issue so there is no reason not to do this. If you find this switch on your motherboard, with your computer turned off, try cycling this switch back and forth rapidly 101 times to see if you can clean some of the dust and dirt out of the switch. You could also try using some electrical contact cleaner while doing this. If this does not work, use ThrottleStop.
A yellow box in Limit Reasons is simply a record of previous throttling since you pushed the power button. Many computers will trigger some of the internal throttling flags during boot up. Yellow boxes are not a problem. They can happen before the bios has a chance to setup the CPU properly. You should be able to click on the headings in Limit Reasons, CORE GPU RING, and this will clear this info out of the CPU. It is only a problem if one of these boxes is glowing red. That means some type of throttling is presently occurring.
With a desktop board I prefer using manual voltage for the CPU. It makes it easier when trying to find out why your computer is not stable. It could be the CPU, the memory or maybe just the program you are trying to run is not stable. I like testing with Prime95, both the Large and Small FFT tests. Start with ThrottleStop's built in TS Bench test. Can your CPU run this test without it reporting any errors and without your computer rebooting? When using manual voltage, if you get any errors when testing, you can easily reboot back into the bios and bump up the voltage and see if that helps.
Switch to the Windows High Performance power profile. I am not sure if your bios or Windows or maybe you used ThrottleStop to enable Speed Shift. When ThrottleStop shows SST in green on the main screen, that means Speed Shift technology is enabled within the CPU. Check the Speed Shift EPP box on the main screen and change the number 128 beside that to 0 for maximum performance. This can help improve stability if your CPU is not 100% stable.
Deliberately downclocking a CPU is like a dirty word in this forum thread. Don't do it. Get back up to full speed, add some voltage and tweak away until you find stability.Last edited: Sep 1, 2019Papusan and tilleroftheearth like this. -
This "slow mode switch" as they call it, hasn't been so much as physically touched by myself since I have no use, and no one in my family would know what they're looking at. Looking through my side pannel it's currently still in the off configuration. Call me a skeptic but I'll try.
Previously BDPROCHOT was red before I disabled it in TS and eventually in my BIOS. It did go away but mind you, it did come up randomly while I was playing one fine day. Think that might have just gone bad and my board will need replacing?
The tests run stable. I can run P95 for hours, no problem. I can even run Furmark (yes I know) for an hour and not have any issues aside from me being uncomfortable with the heat buildup since my GPU just never souds like that on a constant basis. I've even run these tests in tandem and still haven't had a problem. I've only done mixed and small tests, I'll add large ones into the mix and try out TS's solution.
High power profile has always been selected in windows. Yes, I did enable speedshift in TS, I'm not seeing anything like that in my BIOS, the only thing remotely close is intel turbo boost. I will boost that setting though.
I only downclocked because for whatever reason that is clearing up the PL1 issue. Any clock above that seems to bring up that limit reason. I'll poke around and do more testing, but it just doesn't feel right that the factory settings are no longer deemed stable after being such for almost four years now.
You also realize that it's almost midnight where I live and that I'll now probably be up way past my regular turn in time?
-
The slow mode switches on MSI boards slowly degrade over time. I am assuming it is dust / dirt related and they start to short out after that. It is a common problem. Before you even mentioned MSI motherboard, that was my first guess.
PL1 in yellow is not an issue. It is only an issue if it is red while your CPU is loaded. Is your CPU throttling when testing? Try running a 1 or 2 thread Prime95 or TS Bench test as well. Screen shots when loaded would be nice too.
Your screenshots show that Windows is not running a true high performance profile. When using Speed Shift, you must check the Speed Shift EPP box and deliberately set that to 0. After that, open up the FIVR window and look in the monitoring table in the top right corner and make sure that EPP is being reported as 0. That should get your multiplier much higher when your CPU is idle.
It is my bedtime too. I just wanted to fix one more throttling problem before calling it a day!
Edit - Almost forgot. It is common that a CPU will require slightly more voltage when using Speed Shift. That might be why many motherboards do not have that option in the bios.Last edited: Sep 2, 2019Papusan likes this. -
Huh, okay. Well windows says the profile is set but just to be sure I reset all power profiles through the command prompt and re-selected the high power option.
The CPU is not throttling while gaming. Unfortunately I can not post a picture of the game while it is running as that would be a breach of a previously agreed to NDA. The CPU does however run at full, or near full utilization across all four cores and all eight threads, RAM usage isn't anything too special, I think the game only consumes three or four gigs at max.
Haven't tested P95 yet but given my previous runs of it, I expect nothing special which I will do come tomorrow. In the meantime, here are those screenshots.
https://snipboard.io/dN0T5D.jpg
https://snipboard.io/oxTyZj.jpg
https://snipboard.io/ceQsl8.jpg
https://snipboard.io/W7J4Mz.jpg
https://snipboard.io/rV72yP.jpg <
https://snipboard.io/XlqaGn.jpg
Notice in the second to last test as indicated (<) I changed the speedstep to what you had specified for... some reason. Don't know if this would invalidate the results posted, but frankly, I'm not in the mood to retest those single and double threaded 1024M's.
Decided to restart after finishing the testing, sudden restart with the core voltage pegged at 1.250 and again at 1.240.
Got a ticket open with EVGA for a cross RMA, if it's the PSU then this should rear its head as the problem, the only issue is I have no other system to personally test it on. They're suggesting a firestrike test with a link to the results. I got that downloading in the background.
For now though, I'm calling it a night. -
@unclewebb This is kind of random, but do you know where to enable intel GPU? From what I have found, it is done in the BIOS. However, my ASUS laptop BIOS seems to be very limited. I can't find where to enable the intel GPU nor change the voltage.
-
should I undervolt both Intel GPU and iGPU?
-
The first screenshots you posted on the previous page showed this.
When the CPU was lightly loaded, the multipliers were dropping way down. This usually does not happen when using the Windows High Performance power profile. I had a look at the FIVR monitoring table you posted and I found out why.
The Speed Shift EPP value that the CPU was actually using was 84. When Speed Shift is enabled, the Energy Performance Preference value controls what the CPU does when it is lightly loaded. An EPP setting of 0 tells the CPU to use maximum speed so it can achieve maximum performance at all times. A setting of 84 lowers the multiplier when lightly loaded.
If you do not check the Speed Shift EPP value in ThrottleStop and specifically set this to 0, the CPU will use whatever value that Windows tells it to use. In your second set of pictures, after you reset your Windows High Performance power profile, when lightly loaded, your CPU is now using the correct 42 multiplier. No more down clocking at idle. That is how the Windows High Performance power profile is supposed to work.
Does this happen only when in game or does it happen when lightly loaded using the internet or while completely idle? If you left your computer on doing nothing for an hour, is it still running when you go back to it? If this only happens in game then it is either a problem with the game or perhaps the GPU or driver is causing these random restarts. Could be lack of power going to the GPU but this is not very likely if your GPU can handle some FurMark testing without crashing.
When trying to track down random problems like this it really helps if you have some spare parts handy. The GPU and memory are common suspects. Try some Prime95 Large FFT testing to give more of the memory a work out. Swapping parts is about all you can do.
Your screenshots show VID 1.2954. This is the voltage that the CPU is requesting. Run CPU-Z. If it correctly reports your actual voltage, what does CPU-Z show when the CPU is loaded? Actual voltage of 1.24V or 1.25V should be enough at your speed but I would keep bumping this up in the bios until CPU-Z actual voltage is up around 1.30V.
If a manufacturer has disabled the Intel GPU in the bios and there is no user option in the bios to turn it back on, I do not know how to enable it.
The Intel GPU and iGPU are the same thing. If your laptop is using a separate Nvidia GPU then under volting the Intel GPU is probably not going to help very much. Do some testing on your computer. Make a change. Does it show any advantage? Any disadvantage like maybe less stability or artifacts on screen? The only one that can answer your question is you. On most recent CPUs, you need to under volt the Intel GPU and iGPU Unslice equally when testing. -
Hello, would it be possible to add 0.5W or even 0.25W TDP steps for us Intel Y-Series users?
-
Thank you for your answer! much appreciate it
two more thing i'm a bit too embarrassed to ask...
1. about the "Turn Off/ Turn On" button. Should it show "Turn On" on the screen or the other way to make this work?
2. This Throttlestop app should keep open/minimize all the time right? If I close the app it will not undervolt anymore? -
Help with Limit Reasons. I have PL2 under CORE and EDP OTHER under RING constantly. When I clear them, they will just pop back again after I use any program. Sometimes when I am looking at the limit reasons with something running on the background, they will flash red and turn yellow again.
When I first opened throttlestop, Core and Cache where undervolted to 0.1250. Is that normal?
It is a Ace Predator Helios 300 (2019)
i7-7700 9750H -
I have never owned or had access to an Intel Y-Series CPU. I have no plans for any further development.
The Turn On / Turn Off button only controls 3 things; Set Multiplier and the two types of Clock Modulation. Your screenshot shows that Speed Shift is being used, SST in green. Set Multiplier does not work when Speed Shift is being used so no need to check that box. Your laptop CPU does not support Chipset Clock Modulation adjustment so need to check that box. It is grayed out and locked as far as I know. That means the only thing that the Turn On / Turn Off button controls is Clock Modulation. You are not using that feature and there is probably no need for you to ever use that feature so all in all, Turn On / Turn Off really does not matter.
For you, it will change the color of the system tray icon and that is about it. This button is a very old feature. It is barely used and is on the chopping block. I added it to ThrottleStop in the early days of development because some users were afraid of how powerful ThrottleStop was. It was like hopping in a Tesla and clicking on the ludicrous mode button.
Now look at the title bar. If it says monitoring in the title bar and Clock Modulation is checked, ThrottleStop will not adjust the Clock Modulation value. If you click on the Turn On button, the word Monitoring will disappear from the title bar and now in this mode, ThrottleStop will actively monitor and adjust the Clock Modulation value if the Clock Modulation box is checked.
Voltage control and pretty much everything else I can think of will work regardless of the state of the Turn On / Turn Off button. Most importantly, do some hands on testing. Click on things and see if things change in the monitoring tables. You do not need a forum or YouTube video to learn ThrottleStop. Play with the program for a few days and it will start to make sense.
Did you try increasing the long and short turbo power limits in the TPL window? In the FIVR window, did you click on the Install button and follow the directions? Try downloading and installing the RwDrv.sys file into your ThrottleStop folder and then check the Disable and Lock Turbo Power Limits feature and see if that helps out.
I seem to recall that someone had great success doing this to his Helios 500. The results were so good that I thought about buying a Helios 500 for myself. The Helios 300 might be locked by Acer so the suggested mods might not work. It doesn't cost anything to try though. -
What are reasonable numbers to increase too. I have never used this feature. Is there a risk in increasing it too much? Also regarding the other question I posted, is it normal to have core and cache undervolted already when I first opened throttlestop on this laptop? (Never did undervolt either with other program)
-
If it was my laptop, I would increase both turbo power limits up to at least 80. The only time I want my CPU throttling is if it is overheating. The power limits were designed by Intel to keep manufacturers happy. It allows them to build and sell laptops with inadequate cooling solutions. If the heatsink and fan in your laptop are properly engineered, there is no need for power limits. Why buy a performance CPU and then deliberately limit its performance?
That is not normal. When you first ran ThrottleStop, did you download it fresh from TechPowerUp or somewhere else or did you copy ThrottleStop from your old computer onto a USB stick and then copy it onto your new computer? If you copied it from somewhere else then you might have copied your previous settings too.
All of ThrottleStop's settings are stored in the ThrottleStop.INI configuration file. If you want to find out how your bios sets up your CPU, completely shutdown your computer. To properly do this, hold the Shift key down on your keyboard and then select Shut down in the Windows menu. When you start back up, before you run ThrottleStop, delete the ThrottleStop.INI configuration file with all of your settings in it. If you have the Task Scheduler starting up ThrottleStop then before you shut down, exit ThrottleStop and delete the ThrottleStop.INI configuration file. When you start back up and run ThrottleStop, it will read all of the voltages, etc., from your CPU. The values it gets from the CPU or the values that the bios set your CPU to.
It is possible that your bios does an automatic under volt but it is not very likely. No one has ever reported that in this forum that I can remember. Did you look in the Task Manager - Details tab to see to see if Intel XTU remnants are running in the background on your computer? Some manufacturers have this junk hiding within their fan control software. -
Intel XTU was installed when I bought it. I uninstalled it but I still see it in task manager. I guess we solved the mystery. Is it fine if I just let it use the previous XTU undervolt or should I just clean it and undervolt from zero. On the other hand, I increased the power limits. It is not showing in limit reasons now while using the PC
. But now it is getting hotter which i know is normal, but is just sad that the low temps I was getting was just faked by the low power limits.
Last edited: Sep 4, 2019 -
When you uninstall XTU, it tends to leave some files behind. I used to install XTU for comparison purposes but I got tired of tracking down its left overs. My system is clean and XTU free! It is OK for ThrottleStop to use the previous XTU undervolt. It just reads that info from the CPU. After that you can set ThrottleStop to whatever you like.
You might want to try using Autoruns to make sure that nothing XTU related is starting up and running in the background.
https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns
Yes, you should be smiling! More power going to the CPU = more performance = more heat. I mostly use my laptop on a desk so it is not a problem if it is a little hot. Maybe this winter I will get around to adding a new feature to TS so you can have different turbo power limits for each profile.
Getting beyond the 45 Watt TDP limit is good news. Some manufacturers lock things down so this is not possible. That's when you put it back in the box and tell the manufacturer that they can have it back.
Edit - Good news. ThrottleStop sort of works on Intel's new Ice Lake processors.
The BCLK is botched but the multiplier looks right during this single thread test. The Limits button needs to be unlocked so the Limit Reasons screen opens up. I am pretty sure that the FIVR voltage control stuff works OK. That is the most important thing.Last edited: Sep 4, 2019ihueco, t456, tilleroftheearth and 1 other person like this. -
@unclewebb Sorry to bother again
What is the max I should go for? I am at 85 right now and PL2 still pops sometimes. I guess that if I get it too high it might damage my laptop. Also should I change ICC Max? I know it is related to voltage, but I don't exactly understand it(like a lot of features in throttlestop tbh lol). Is there a limit reason related to ICC? I thought it would be better if I can reduce the ICC to a lower value without throttling. Rn, I have 128 in Core, 11 in Cache and 32 in iGPU.
Last edited: Sep 5, 2019 -
But should keep Throttlestop open/minimize all the time ? If I close the app it will not undervolt anymore?
The ThrottleStop Guide
Discussion in 'Hardware Components and Aftermarket Upgrades' started by unclewebb, Nov 7, 2010.