G73/53SW Owners - CPU Throttling to 798mhz and how to fix it

The HP Envy 17 had a similar throttling problem but I think it was mostly fixed with a bios update.

Try asking your question over in the HP thread and there will be more users there that are familiar with this issue that can help you out.

http://forum.notebookreview.com/hp-...ndy-bridge-2xxx-series-owners-lounge-603.html

 

Just want you all to know I filed a complaint to Asus using the quote on the last page, hopefully we all will. Let's rally together here! We shouldn't have to settle for less then what we paid for. I'll let you know when I receive a response and what the response says.

 

gah i just read about this after ordering the G53SW-XN1. hopefully it shouldn't be too much of a problem with the TS program. Any late info on what the progression is with a possible BIOS update?

 

I just downloaded throttlestop and used it because of issues I was having with choppiness/lag (throttling I guess? not a comp expert)... these problems ONLY started occurring after I did a reformat using the asus partition for reformatting that comes with the comp. Throttlestop got my FPS much higher and smoother but my confusion is why this is necessary if I reset the computer back to factory settings, and my concern is whether or not throttlestop is just removing the symptom of a bigger problem. My power adapter blew out recently when I began noticing the choppiness problem and I had to buy a temporary one from wal-mart to use instead. Since I saw mention of possible power issues this makes me think my issue has to do with hardware as opposed to random throttle settings. Any ideas? Help?

 

It's a known issue with the Sandys. Throttlestop would not fix any hardware issues, so I wouldn't go nuts over this. As for the power supply, how long have you had this laptop? The power brick is also covered under warranty if under a year IIRC.

 

the computer ended up blowing out like 6 hours after running throttle stop which made me think my throttling may have been legitimate and that by stopping it the computer blew out. blew out as in it wouldnt turn on or power up even when plugged in. it ended up working again the next day but by then I had already gotten my RMA to send back to asus and sent it anyway to get them to fix it since I still didn't know what was causing the choppiness/throttling. I'd had the computer for only about 6 months.

 

Hello,
I'm a G73SW owner and I face the same problem with Team Fortress 2

here it is the ReatTemp log

DATE TIME MHz CPU_0 CPU_1 CPU_2 CPU_3 LOAD%
11/21/11 22:59:35 3093.05 81 79 80 71 23.8
11/21/11 22:59:36 3093.05 79 82 82 72 34.6
11/21/11 22:59:37 3093.04 81 79 81 77 36.3
11/21/11 22:59:38 3093.05 79 81 83 78 31.9
11/21/11 22:59:39 3093.05 81 81 82 78 33.9
11/21/11 22:59:40 3093.05 79 79 82 75 32.2
11/21/11 22:59:41 1546.52 72 72 69 65 40.5
11/21/11 22:59:42 798.21 70 70 67 65 36.5
11/21/11 22:59:43 798.21 70 69 66 64 37.7
11/21/11 22:59:44 2344.73 81 80 80 71 34.6
11/21/11 22:59:45 3093.04 78 79 80 72 36.0
11/21/11 22:59:46 3073.09 79 80 80 75 35.5
11/21/11 22:59:47 3093.05 78 76 75 71 26.9
11/21/11 22:59:48 3093.05 77 76 74 71 19.0
11/21/11 22:59:49 3093.05 79 76 73 71 20.0
11/21/11 22:59:50 3103.02 82 78 75 71 25.5
11/21/11 22:59:51 3093.05 76 75 76 71 23.7
11/21/11 22:59:52 3093.05 79 75 72 69 19.3
11/21/11 22:59:53 3093.05 79 75 73 71 19.1
11/21/11 22:59:54 3093.05 77 77 75 70 19.2
11/21/11 22:59:55 3103.02 76 77 74 71 19.1
11/21/11 22:59:56 3083.07 83 83 84 80 35.0
11/21/11 22:59:57 2494.39 73 73 70 68 42.4
11/21/11 22:59:58 798.21 70 69 66 65 43.3
11/21/11 22:59:59 798.21 69 69 65 64 36.2
11/21/11 23:00:00 798.21 67 68 64 63 37.0
11/21/11 23:00:01 1446.75 78 76 77 70 39.1
11/21/11 23:00:02 3033.18 80 76 79 71 45.4
11/21/11 23:00:03 3083.07 78 75 71 70 23.4
11/21/11 23:00:04 3073.09 79 79 80 74 30.5
11/21/11 23:00:05 3093.05 74 74 77 71 29.4
11/21/11 23:00:06 3093.05 76 75 74 71 25.5
11/21/11 23:00:07 3093.04 75 74 75 70 19.9
11/21/11 23:00:08 3093.04 76 75 77 70 24.2
11/21/11 23:00:09 3093.05 76 77 76 72 20.2
11/21/11 23:00:10 3083.07 79 74 73 70 25.3
11/21/11 23:00:11 3093.05 76 75 76 69 24.6
11/21/11 23:00:12 3093.05 78 75 73 70 22.3
11/21/11 23:00:13 3093.04 76 75 74 70 19.5
11/21/11 23:00:14 3093.05 77 76 74 72 20.9
11/21/11 23:00:15 3093.05 76 75 74 69 23.3
11/21/11 23:00:16 3093.04 77 74 75 70 19.8
11/21/11 23:00:17 3093.04 75 76 72 71 21.0
11/21/11 23:00:18 3093.05 80 75 73 72 23.7
11/21/11 23:00:19 3093.04 77 76 72 70 20.1
11/21/11 23:00:20 3093.04 76 76 73 71 23.9
11/21/11 23:00:21 3093.05 79 76 73 70 26.8
11/21/11 23:00:22 1696.19 70 69 67 65 39.3
11/21/11 23:00:23 798.21 69 68 65 63 38.2
11/21/11 23:00:24 798.21 68 67 63 63 40.5
11/21/11 23:00:25 798.21 67 67 62 62 42.2
11/21/11 23:00:26 2384.64 79 80 74 73 43.0
11/21/11 23:00:27 3093.05 78 78 73 71 30.8
11/21/11 23:00:28 3093.05 77 79 76 72 29.6
11/21/11 23:00:29 3093.05 80 78 78 71 30.1
11/21/11 23:00:30 3093.04 80 76 79 70 30.4
11/21/11 23:00:31 3093.04 77 81 79 71 29.9

 

Nice find, I guess that makes sense as it does throttle in L4D2, same engine basically. I'll add it to the list, but for now best you can do is run throttlestop if you want to fix it. There doesnt seem any chance Asus will release a new BIOS for us. They won't even do it for their new G74 line up, so it's going to be even less likely for any us 73/53SW owners to get one.</log>

 

Yep! Throttlestop fixed that
So now I can heal my teammates without losing a frame!

Thanks for the precious thread

 

G53SW here.
I can confirm that ThrottleStop v4.00 fix the sudden framerate drop in the following games:

1. Just Cause 2
2. Skyrim (in 3D mode)
3. Sonic Generations
4. StarCraft II

Cheers. This issue was really killing me!
Much appreciated.

 

may i know you TS setting? Mine G53sw with TS started but does not resolve the FPS drop issue. IT's intermittently dropped to 800Mhz..

 

Sorry this is a late reply, maybe you have figured it out by now. But there really isn't any special settings for ThrottleStop. Just as long as the BD-PROCHOT option is not checked in TS, it should be working. PM me if you want to try a bios that disables BD-PROCHOT so you can test that way.

Also, thanks, I added those games to the list.

 

Will this also fix the throttling issue related to when you unplug the laptop from the charger and it throttles the cpu? I tested this with the diablo 3 demo and noticed while plugged in, everything was smooth. Once unplugged, the game was choppy.


Just saw this thread:

http://forum.notebookreview.com/asu...9-unofficial-bios-fix-throttling-g73sw-3.html

Would that be a better option to fix this? Flashing the bios?

Thanks!

 

I don't think it stops the throttle when on battery. AFAIK, its a hardwired "feature" to prevent too much power draw when not plugged in. So sorry, this or the bios shouldn't really change how the game runs on battery.

You're more than welcome to try and see if maybe it helps it become a little smoother, but in the end, it should still be running lower fps than if you were plugged in.

 

So I just bought a used G53Sw ... I'll test the issues with Need For Speed World and AutoClub Revolution when I get home from school.

Cheers. (BTW any word from Asus on fixing it?)

 

So ... does CPU-Z always lie or does Throttlestop lie?
My reason for asking is thus:

<param name="movie" value="http://www.youtube.com/v/03c9vSz8OZ8?version=3&amp;hl=en_US"></param><param name="allowFullScreen" value="true"></param><param name="allowscriptaccess" value="always"></param><embed src="http://www.youtube.com/v/03c9vSz8OZ8?version=3&amp;hl=en_US" type="application/x-shockwave-flash" width='640' height="360" allowscriptaccess="always" allowfullscreen="true"></embed></object>

 

Lie is kind of a strong word but you are not the first person to be confused when trying to compare CPU-Z vs ThrottleStop.

CPU-Z is a CPU validation tool. The programmer decided that a consistent MHz number when a CPU is lightly loaded is more important than accuracy.

In my opinion, this is one of the reasons why laptop throttling has become such a huge problem. The average Joe still has no idea what CPU throttling is all about. For some desktop CPUs like my QX9650, CPU-Z still ignores the two main types of clock modulation throttling so a user would have no idea why their CPU is running like a slug.

http://img845.imageshack.us/img845/1036/qx9650clockmodulation.png

The random looking multiplier data that ThrottleStop reports is an accurate look at what your CPU is really doing. Intel released a White Paper when the Core i processor family was first released in November 2008.

Intel® Turbo Boost Technology in Intel® Core™ Microarchitecture (Nehalem) Based Processors
http://download.intel.com/design/processor/applnots/320354.pdf

This white paper includes explicit instructions on how monitoring software can accurately determine the multiplier. At the hardware level in all Core 2 and Core i CPUs, Intel included two high performance timers for each thread that run at billions of cycles per second. By comparing these timers, the tiniest changes in the multiplier can be measured. ThrottleStop uses these timers and follows the Intel recommended method exactly.

The multiplier, especially when lightly loaded, can be changing hundreds of times a second as cores and threads rapidly enter and exit various C sleep states like C1, C3, C6, C7. ThrottleStop tells it like it is. If your CPU multiplier is jumping up and down, ThrottleStop will display a very accurate average of this. CPU-Z must have decided that this is "too much information" so when a mobile CPU is lightly loaded, it shows the minimum multiplier. I disagree.

The other problem I have with CPU-Z is that it rounds off the raw data.



All 8 threads are reporting that they are not maintaining the full 25 multiplier due to throttling but that's not what CPU-Z would lead you to believe.

In the next example, CPU-Z reports a far lower multiplier than what the CPU is actually using.

http://img818.imageshack.us/img818/7996/cpuzg.png

Based on CPU-Z data, the average user is going to conclude that there is a throttling problem when there might not be any problem at all.

Try using the Set Multiplier option in ThrottleStop and set that to 8 with ThrottleStop turned on. That might help you to see an honest 8 multiplier when your CPU is lightly loaded.

 

Thank you for the uber detailed explanation. So what you're saying is CPU-Z is being like Bill Clinton, asking us to define the meaning of multiplier? hehehehe (sorry had to!)

I may have to tell that to my hardware instructor! *LOL* Even HE couldn't tell me what was going on, and he's been working with computers since vacuum tubes! *LOL*

From this day forward, until Hell Freezes Over, or CPUID changes their way, I shall not use CPU-Z as a speed indicator.
(BTW on my old i3 350m, it never jumped like that! Than again, I didn't have turbo-boost...)

 

A statement like that needs repeating. I might have to add that to the ThrottleStop docs.

Even without Turbo Boost, if a Core i3 is using the deeper C sleep states, the multiplier ThrottleStop reports will jump around a lot when lightly loaded. You probably never noticed it jumping around because you were trusting CPU-Z.

 

I, Allan VanderSpek, do hearby give you full unilateral permission, to use my statement (and link back to this thread so I get credit...):