The Definitive Guide to Acer Aspire Gemstone Blue Throttling Issues

The Definitive Guide to Acer Aspire Gemstone Blue Throttling Issues v2.0
Credit Due to DarkSilver, ATG, Sgogeta4, and Unclewebb


This thread is specifically designed to put an end to the multitude of threads about people asking why their Aspire 6920G, 6930G, 6935G, 8920G, or 8930G is experiencing lackluster performance in gaming.

What Causes It

We’re not 100% certain, but through a process of elimination, we believe there are two possible causes:
• That a sensor on the motherboard is going haywire, reading internal temperatures entirely wrong. As a result, the system’s BIOS believes the CPU’s temperature is reaching dangerous levels when it’s really well within operating limits, and causes a thermal throttle to be activated. This halves the CPU’s performance until the temperatures are returned to what the system perceives as safe levels.
• It could also be potentially linked to a ridiculously low setting in the BIOS and not the fault of a motherboard sensor – this was refuted by my travel to Acer’s Canadian headquarters, where a stock 6920G was shown to operate just fine, with no throttling whatsoever. That being said, given the large number of users affected, it's still a possibility.

All we know for certain is that the chipset has reason to force the CPU to throttle, running it at a lower clock speed and thus ruining your performance.

“But TehSuigi!” I hear you say. “Why does my GPU downclock as well? Isn’t that the reason why my system slows down?” You’ve got the order of events mixed up if you think the GPU downclocking is the problem. Because the CPU can’t process the physics of the games as fast or send frames to the GPU as often, the GPU requires less power to render what frames manage to get to it. As a result, it drops into a lower power state using Nvidia’s PowerMizer or ATi’s PowerPlay technology. Even if you disable these power saving measures, game performance will still suffer because the CPU will still be throttling.

How to Diagnose It

Thankfully, diagnosing the problem is relatively easy to do. First off, download and run ThrottleStop. Unzip it and open it up, clicking OK on the rather frightening warning window (feel free to read it, but it's more concerned with Dells and Alienwares whose throttling issues are related to power supplies - Acers are unaffected). You'll be presented with the window below (minus the red box - I added that).

The next step is to try and trigger that throttling through normal use. Open up your favourite game (windowed, if possible) and begin playing. When the game performance drops, check the ThrottleStop window – if the numbers in the red boxes show less than 100, your system is throttling. If not, your performance issue lies elsewhere. If you want to see if your system throttles in a hurry, just run ORTHOS for a while – mine usually throttles in under 5 minutes.

How to <strike>Live With It</strike> FIX IT FOR GOOD

Thankfully, since the first edition of this post, an enterprising user named unclewebb has developed software to end this blight upon our systems. It's called ThrottleStop - if you didn't download it during the diagnosis step, do so now.
To not only stop your system from throttling, but prevent it from occurring again, simply tick the box I've marked in green in the screenshot below (and change the % number beside it to 100% if it's anything else).

And that's it! You should no longer be throttling, and your system can now be used to the fullest of its potential. This is the one-size-fits all solution we've been waiting for, until proven otherwise.
Some helpful options are detailed below:
• Minimize on Close means that it'll be sent to your notification area when you click Close on the window. It can then be restored or exited from there.
• Log File will write your CPU speed, load, and temperature to a file to be examined later.
• More Data will increase the frequency of data refreshing. This means that your monitoring data will be more accurate, but change rapidly.
• You can set up a Task through Windows Task Scheduler to automatically start ThrottleStop whenever you log in, or whenever a certain program/game opens up. Use Google for a guide, because it can be a little confusing.

For more discussion of ThrottleStop, check out its thread here on the Acer forum.

The Alternative - Undervolting
It still works to solve throttling issues, but by different means - dropping your CPU's temperature below the trigger point, instead of disabling the throttle altogether. There are better guides for undervolting elsewhere on NBR, so I won't duplicate their content here. Advanced users might want to give this a spin, especially since it will also result in a cooler-running CPU and longer battery life.
I personally use RMClock to undervolt (64-bit users will need the signed drivers from here).

There's one last thing I recommend - call Acer and tell them that you're experiencing this problem! The only way we can get them to release a patched BIOS (if that's the problem) or repair your motherboard's thermal sensors (if that's the problem) is by informing them in large numbers.
I know that I've got a commitment from Acer to diagnose and repair my system's thermal issue whenever I please, but then again, I'm still covered under warranty. Please call them before yours expires!

If you have any questions or concerns, feel free to post here.

 

Tehsuigi, STICKY is needed.
If not, I think multiple-similar threads would appear again.
By the way, my REGISTRY tweaks has been change to HARMLESS(which won't screw up the system).
All extreme tweaks has been taken out. Check it on here again, http://forum.notebookreview.com/showthread.php?t=393073

EDIT: Thanks for crediting me and included my FIX on this thread. As well as buying your time on reading my FIX again.

 

By the way, I've changed my mind. I won't be sending my laptop in to Acer's repair centre, if only because I've managed to get everything else on my laptop just so, and I'd rather not have it mucked up by some brainless techie.
That, and I don't want to swap my CPU back to the T5550 unless I absolutely have to.

The throttling issue is a nuisance, yes, but I'm willing to live with it for the time being. As well, I'll be trying to get in touch with someone at Acer Canada who can help me out without having my laptop on hand.
Stay tuned to this space for updates.

sneaky bump is sneaky

 

Even I really they release a BIOS(not 100% confirm is BIOS problem but might be) to fix this lame problem. However, I would still undervolt my laptop.
This is because I want lower the temperature of CPU and so GPU temperature could be lowered too.

 

UPDATE:

Another development in this ongoing story. I was bored tonight and figured I was due to clean out the mesh screen on my laptop's fan intake. So after removing the bottom access panel and cleaning it, I had an idea. I know that the system can run without the bottom plate - why not get an idea of how well it does?

Imagine my surprise when I was able to run ORTHOS for 5 minutes on my regular undervolt without a downclock!
And on top of that, the fan sped up around 59 degrees Celsius when testing on stock voltages (2:15, then downclock).
The times with the bottom plate back on were 2 minutes-then-downclock and 45 seconds-then-downclock, respectively.

I noticed that not having the bottom plate on allowed the fan to move a lot more air over the exhaust grille. Not sure how that ties into the ability of the fan to speed up when the CPU gets stressed (which rarely happened in my previous tests), but the speed-up point of 59 degrees explains why most throttling instances were just below then.

So this means that we can entertain the possibility that this whole problem is caused by that stupid mesh screen in front of the fan (as well as BIOS/fan/motherboard issues).

 

It is the same for my Aspire 4530 except I removed it before you did.
I notice I can feel Air moving across the intake so I figured I remove the stupid useless mesh.

Other more hardcore mods like cutting out bigger vents holes also help.
Originally I had 16 vent bars I cut away 8 so it looks proportional and helps airflow.

 

Yep! Take out the bottom part of the laptop casing of course would lowered the temperature.
Just like open your windows and let the air come into your house.

Still the problem lies on BIOS/Motherboard/Fan.
I hope it is the BIOS problem instead of Motherboard or Fan.
So, with easy flashing of BIOS, we can fix this THROTTLING problem easily and fast.

Tehsuigi, try put your laptop on a portable air-conditional. I mean where the part cold air blow out. It won't throttle even without undervolt. XD.

About the mesh screen, I love them. Because it helps me to block a lot of dust for me. I can see the mesh screen filled with dust after 1 month. It is effective for me.

 

Have you all considered overloading DSDT tables?
It is the Thermal Control table BIOS passes to Vista on Boot and stores it in the registry
Just install RW Everything and export the DSDT Table.
Modify the asl file (text)
Then install Microsoft ASL Compiler recompile the ASL to AML files and overload the table into BIOS.
Or you need me to provide a Guide for this?

 

Sounds complicated but INTERESTING.
Dear Weinter, please provide the guide. Thanks.
Tehsuigi, your bored night, this is your task. XD. I would follow if tehsuigi sucess with this.(sorry tehsuigi, this is not an order from me, I just hope if you can experiment on it since you have superior computer skill than me)

 

Wish I could spend the time on it, but I'm still studying for finals here.
Weinter, sounds interesting, but way too time-consuming. I don't know enough to mess around with DSDT tables and not muck something up.
DarkSilver, I was thinking of getting a laptop cooler sooner or later - the number of vents on the bottom will certainly promote good airflow.

 

Ok I checked the DSDT seems ok using the latest BIOS after
I dissembled the BIOS and extracted the DSDT.
What I want to suggest is go to the registry and delete the old DSDT table so Vista will attempt to acquire a new DSDT Table from the BIOS.
The location of the DSDT Table is as Follows:
[HKEY_LOCAL_MACHINE\HARDWARE\ACPI\DSDT]
My rationale is I am not sure if Vista "backup" DSDT or automatically acquire DSDT from BIOS on Boot.
If it "backup" DSDT in the registry the new patched BIOS DSDT settings will not get through.
Anyway deleting the DSDT will not cause BSOD or anything.
I have done it before.

 

Tehsuigi, you try it 1st FTW! Because my system is OK now. In addition, I am on final as well. LOL. Same same. XD I am planning for cooler too. If any model cheap and reliable(useful), please stay in touch with me. Thanks.

Weinter, you're using AS6920G? You seems really pro in computing. XD

Nevertheless, check my THROTTLING 6920G fix guide here, http://forum.notebookreview.com/showthread.php?t=393073&page=16
There is a person claims some BIOS stuffs and successfully fix the throttling using it.

 

I'll give it a spin later tonight, after I'm done studying.
It's entirely possible that since I never reinstalled my operating system after doing BIOS updates (unless the in-place upgrade from Vista to 7 counts), I'm still using the DSDT table from BIOS 1.06.

 

Is the restore to default factory from acer hidden partition counts as a re-installation of OS?

But so far I know your AS 6920G is basically from Windows Vista HP x86 then upgrade(reinstall OS?) to Vista Ultimate x64 and then upgrade again(reinstall OS?) to 7 x64. Are these counted as re-installation of OS?

 

No Factory Installed uses the Windows Registry from the time when the Image was created by some Acer tech so the BIOS could be ancient.

 

The Server BIOS trick sound fake.
BIOS has lots of specific customization to each laptop so you cannot just happily use any BIOS.
Even a predecessor model it is not possible because of different Chips and ACPI settings.

 

I had restore to default factory plenty of times. But restore to default factory doesn't change the BIOS right?
The BIOS in the CPU-Z shown I am using v1.14 even I have restore to default factory many times.

Now, the only question left is, is it the Windows Registry didn't know the changes of new BIOS? So, it still acts as the ancient BIOS setting?

About the server bios, it does sound fake of course.

 

BIOS is read only so default factory doesn't touch BIOS unless you flash it.
Problem is factory image backups everything that was created from factory image hence the DSDT Tables as well.
As I said I don't know if Vista will automatically request new ACPI info from the BIOS or it will use the old ACPI acquired from Factory Image.
I have seen some people with Wrong Processor Info in device manager due to factory image wrong configuration hence using this parallel I am assuming the same result.

 

If Vista acquired the ancient BIOS setting from factory image instead of ACPI(1.14 BIOS), then I think you guide/tweaks/theory might be true.
We can confirm this with Tehsuigi sooner or later.

 

First thing, 2000th post. Shweet.

Secondly, I tried Weinter's DSDT suggestion. Didn't fix the throttling issue, and I think it might have mucked up my wireless connection somehow. One System Restore later, though, and we're back and running.
However.
I think Weinter's on the right track. The DSDT in registry is the one used by Windows (not the one from BIOS), and it can be patched.
Therefore, I believe that a permanent fix is possible by changing the DSDT itself.
I found three patching guides online, but all of them deal with other makes and models. In theory, the thing should be the same.
If the DSDT controls the fan, we'll just make it spin faster.
But if it controls the thermal throttling temperatures, we can set them to sane levels and stop this whole sordid mess!

 

Ok. 3 guides there. I have no time to explore on it currently.
weinter have higher and superior skills on these stuffs. XD

I think this might be great too, http://tldp.org/HOWTO/ACPI-HOWTO/dsdt.html

 

I will give instruction how to get the DSDT Table, Modify it and Overload it in WINDOWS (Some people might not have Linux but ALL have Windows ).
1) There are a few ways to obtain the DSDT Table
a)Get Phoenix BIOS editor and dissemble the BIOS the DSDT is fully obtainable
Copy and paste the entire text into Notepad then save as xxxx.asl
b)Get from Windows Registry however it is in binary I didn't figure out how to convert to asl so ...
c)Download Install RW-EVERYTHING go to ACPI.
Copy and paste the entire text into Notepad then save as xxxx.asl

Go Download ACPI Specification 4.0 (google)
Open the text and try to read and understand the asl language

After you are happy download and install Microsoft ASL Compiler.
Compile the ASL to AML by
Command Prompt (admin permission), asl.exe xxxx.asl
You will get a DSDT.AML file
Then
asl.exe /loadtable DSDT.AML
If you are really happy with the new DSDT you can modify the BIOS DSDT to make it permanent or backup your DSDT to overload whenever you reformat.

If you don't want to try modding DSDT the only other thing you can do is lower the temperature as much as possible.

For those who do DSDT modding there is a pointer I wish to point out to.
First I already check out the DSDT, you cannot do fan control but there is this function you can modify
.
There is one line like this

It translate to this

So you can modify it to report temperature lower than it really is by modifying the formula
Note:There is no way to modify fan control directly as it is self regulated by a non-programmable controller.

 

tested it with rmclock, it shows that core clock at 995mhz and throttle clock 1995mhz, but then it becomes 1995 mhz for both.

is that fine? btw my cpu is 5750 @ 2ghz

 

If you really need my help I can help you modify DSDT for testing.

 

Weinter, I think you should help us to mod the DSDT table(when I am free I would send you those DSDT table of my laptop).
Right now, I have no intention to try or explore on it(mine got fixed).

 

hna, please read the original post. Your question is answered there.

Weinter, DarkSilver, the attachment is the DSDT I extracted from my BIOS. Have fun!

 

Is that a success? Or just some DSDT table which extraceted from v1.14BIOS?
I would like to confirm 1 thing that is the BIOS v1.14 DSDT table have the fix for the throttle issue?

 

That is the DSDT table from the 1.14 BIOS, and since I'm still throttling, it's obviously not fixing the issue.

 

I found something funny.
Guess what the ACPI FAILS Microsoft ASL Compiler...
OMG it couldn't even compile properly to generate a DSDT File.
WTH are those people doing?!

To further emphasize it is only the particular laptop problem, FYI my Acer Aspire 4530 ASL compiles properly to generate a DSDT.

 

So, did you mean AS 6920G ASL Compiler can't be used?
Tehsuigi claims that after using the ASL Compiler tweaks, the system become cranky and unstable. He told me via MSN.

 

I modded the ASL to report 10 degrees lower than the actual temp hopefully it will lower the threshold for throttling.
To use the DSDT
Install Microsoft ASL Compiler
Navigate to the directory place the file (rename to CRESTLINE.ASL)
then
type asl.exe CRESTLINE.ASL
You will get a DSDT.AML
Then overload it using the instruction I previously typed.
Reboot
DO TESTING FIRST
IF doesn't work or you sense something wrong
Revert to last working condition or delete the DSDT from Windows Registry.

 

So, I just need to copy and paste?
Actually, I have no idea about ASL Compiler because I haven't download it.
Anyway, Tehsuigi will test this out. But I heard he is studying very hard currently because his final is coming soon.

 

You need Microsoft ASL Compiler to overload the DSDT Tables
Anyway I did another new one with less error.
The mod is the same trick the DSDT into thinking 10 degrees cooler so it might throttle at a higher temperature instead.

What you need to do install Microsoft ASL Compiler
Open Command Prompt with Admin Rights
Put the asl file in the same directory
Change Directory to Microsoft ASL Compiler Folder
Run:
asl.exe Crestline.asl
It should create ACPI00.AML file
Rename to DSDT.AML
Run
asl /loadtable DSDT.AML
Reboot and do your throttling tests.

 

What you mean by put the asl file in the same directory?
Where am I getting the asl file?
Please state out all steps. It sounds like you're expecting me know a lot and already did some of the steps. However, to disappoint you, I did nothing at all.
So, explain all steps in details. Thanks.

 

I never said that - I said that deleting the DSDT/FADT/RSDT entries in my registry caused the instability, not using the ASL Compiler.
Weinter, might it be possible that some of the DSDT table is stored on the MXM vBIOS? Maybe that's why it's incomplete.

 

LOL! OMG I think these discussions are too advance to me.
I don't understand everything clearly, so, I thought you said that the ASL Compiler tweaks caused some problems. Sorry. My fault.
Beg for mercy.

 

No.
Ok the ASL Compiler is used to overload the new DSDT to the Windows Registry.
What I did to the Crestline ASL is to make it report 10 degrees lower than it actually is ,hopefully it will raise the throttling temperature.
Deleting the DSDT/FADT/RSDT in the Registry doesn't cause instability because Windows will automatically retrieve it from the BIOS's DSDT/FADT/RSDT and the BIOS is read only meaning you can never destroy DSDT/FADT/RSDT when you delete.
Windows Only holds a copy of it however using Microsoft ASL Compiler you can modify DSDT without having to modify BIOS's copy by modifying the copy Windows holds.

The actual DSDT is stored in the BIOS and pass on to Windows DSDT is not stored in the Graphics Card BIOS only stuff relevant to graphics card like voltage, frequency etc.

First Download and Install Microsoft ASL Compiler 3.0
Next download the attachment Crestline.ASL.txt and rename it to Crestline.ASL
Put it in C:\C:\Program Files\Microsoft ASL Compiler v3.0\
Open a Command Prompt with admin permission (Right Click Run as Admin)
Then
Type
cd "C:\Program Files\Microsoft ASL Compiler v3.0"
Type
asl Crestline.asl
It will generate a file in the same directory call ACPI00.AML
Rename it to DSDT.AML
Using the Commmand Prompt Windows earlier
Type
asl /loadtable DSDT.AML
Then reboot and do the testing.
If you find something wrong or it doesn't work, revert to last working condition or manually deleting the DSDT in the Windows Registry will force it to revert to the default BIOS DSDT.
Any simpler I have to write a batch file to automate everything.

 

OK, then I don't know exactly what caused the system to freak out when I deleted the DSDT registry key. It didn't fix the issue, so I'm not planning on doing it again.
Just thinking though, wouldn't it cause the fan to operate at slower speeds due to the artificially lower temperature readings? I could see that being a bit of an issue.

 

When you delete the key the system sort of freeze lag right?
Because Windows is trying to re-retrieve a new DSDT Table from the BIOS as it doesn't exist in the registry as normally.
After a reboot everything will be back to normal and you will find a new copy of a DSDT Table back in the registry.

 

It did indeed experience that - good call, weinter. Time to test it out.

EDIT: Deleted key and rebooted. Still throttled. Rebooted again. Still throttled.
So much for that.
I'm hesitant to use weinter's customized ASL file, but I think it could work with a little change.
Correct me if I'm wrong, but TZ00 is the one that controls fan speed yes? Why not crank that up 10 degrees to increase the fan speed?
If we can find the thermal zone that trips the thermal throttling and turn that down, even better.

 

I'll give the custom ASL a try later on but Tehsuigui's suggestion is more sensible.

 

I've also found a lot more success with a lower undervolt - dropped another 0.075V today to reach an even 1.0000V on my top multiplier. When testing for stability with ORTHOS, I only throttled ONCE for the entire 3 hour test. And even then, it was only for a minute and quickly resumed its normal speed.

 

OK the DSDT does not control the fan.
It only reports the temperatures so by increasing the actual value I was thinking it might increase the temperature of throttling.
By decreasing it it might decrease the throttle limits so you throttle much earlier.
When you undervolt you are also trying to decrease the temperature so it will not hit throttle temperatures.

 

Hi,
I've been trying to resolve a DPC spikes issue which causes a few clicks/pops to appear while using sound apps such as Native Instruments Traktor Pro (Acer Aspire 6930, T5800, Centrino 2 System)

What I've noticed is, with RMClock at Maximal Performance settings the CPU Core Clock displayed in the tray jumps between 2GHz, 1.99GHz and 1.20GHz. DPC Latency Checker shows the spikes to be around 1000μs.
Running StressPrime 2004 Orthos, the DPC Spikes disappear and the CPU Core Clock fluctuations also stabilise (1.99GHz & 2GHz)
I have updated to the latest BIOS version. Any thoughts and/or suggestions would be appreciated,
Thanks.

PS: Great thread!

 

Try disabling the CxE states on the Advanced tab of RightMark - that should prevent the clock from dipping when it's not supposed to.
Oh, and welcome to the forums, Cyberpunk! Make sure to stick around, and feel free to contribute.

 

Anyone one tried the modded DSDT?

 

i just made a post about upgrading the cpu on my 5920, and this issue is the heart of the reason for my upgrade. i have experienced this problem since i bought the laptop, and finally decided it was the cpu overheating.

i heard the newer .45nm processors run cooler than my old T5250, so i thought it might do the trick. very disappointed to see that the problem may still present itself after ther upgrade

glad to know there are people on it though. good luck working out a fix for this.

 

ildawg, the problem only occurs in Aspire Gemstone Blue models (69xx, 89xx) as far as we know, not regular ASpire Gemstones like the 5920.

 

interesting, well my whole system hiccups and downclocks durring long periods of gaming. i thought it was the video card for the longest time, but it does it even when the video card is severly underclocked. this lead me to the belief that it was a heat issue with my T5250. so maybe thats it after all and the cpu upgrade is all i need.

 

Could be - have you monitored the temperature of the CPU? Go get HWMonitor and have a gander.
Have you cleaned you vents? Undervolted?