The Speed of Processor 1 in Group 0 Is Being Limited by System Firmware Windows 10

The Windows log you lot posted shows a time of 23:27:27. That is xi:27:27 PM. The ThrottleStop log file you posted is from ii:sixteen AM to 2:35 AM. This time is completely dissimilar than the Windows messages that you posted.

The ThrottleStop log does bear witness the kind of throttling that you are talking near.

Lawmaking:

                  2016-11-04  02:32:09   8.00   52.2  100.0  100.0        0   63   0.6569    8.ii 2016-eleven-04  02:32:ten   8.00   61.9  100.0  100.0        0   64   0.6569    viii.half dozen 2016-xi-04  02:32:11   8.00   48.8  100.0  100.0        0   62   0.6561    8.0 2016-eleven-04  02:32:12   viii.00   40.ane  100.0  100.0        0   62   0.6569    7.7 2016-eleven-04  02:32:13   eight.00   54.7  100.0  100.0        0   62   0.6527    eight.3 2016-11-04  02:32:14   viii.00   39.3  100.0  100.0        0   62   0.6576    7.8 2016-11-04  02:32:15   eight.00   50.6  100.0  100.0        0   63   0.6561    viii.1 2016-xi-04  02:32:16   viii.00   43.1  100.0  100.0        0   62   0.6561    7.seven 2016-11-04  02:32:17   8.00   40.6  100.0  100.0        0   61   0.6569    7.6 2016-xi-04  02:32:eighteen   eight.00   67.0  100.0  100.0        0   63   0.6561    eight.7
                

The 8.00 is the multiplier and the number beside that is the load. This means your CPU has throttled down to the minimum multiplier. The temperatures are OK so with this kind of load, there is definitely a problem here.

I am still waiting to run across a picture show of how you have ThrottleStop setup. Also run the Limit Reasons program built into ThrottleStop and postal service a picture of that while your CPU is throttling. It volition probably show what is causing this throttling problem.

I did some searching last night and found another G751JY possessor with the exact aforementioned problem.

https://rog.asus.com/forum/showthrea…amp-frustrated

As soon as he used ThrottleStop to disable BD PROCHOT, his CPU immediately started running at full speed. Based on your testing and then far, I think your laptop has the same problem.

Your ThrottleStop screenshot does not bear witness whatsoever signs of throttling. Your CPU is running at 3400+ MHz similar it should be. Endeavour to get a screenshot of ThrottleStop with the Limit Reasons window open when your CPU is throttling and stuck at 798 MHz.

Limit Reasons shows what part of the CPU is causing the throttling. If a box lights up in red, that is the reason for the throttling that is soon happening. A yellow box ways that some throttling was previously recorded but the CPU is not presently throttling due to that reason. After y’all kicking upward, open Limit Reasons and click on the headings, CORE, GPU and RING. This clears the previous throttling reasons so the xanthous boxes should turn black. Some of these get set during the boot up phase. That is not important and so you want to clear those boxes earlier you start testing. Also open up upwards the ThrottleStop – Options window and cheque off, Add Limit Reasons to Log File. The log file volition then contain throttling reasons so this data can be direct compared to the CPU multiplier.

When monitoring, run ThrottleStop by itself. Other monitoring programs like HWiNFO automatically delete the Limit Reasons data that is stored within the processor. If the Windows system logs are random or not 100% reliable then ignore this data. It was prissy that Windows told you that there is a problem but now you need to ready it. Windows does not have any options available to gear up a throttling trouble like this.

Edit – It would also be a good thought to turn on GPU monitoring in the Options window then this information will be included in the log file besides.