F5F Stay Refreshed Hardware Desktop Vivobook 15 experiencing slow performance at 0.40 GHz

Vivobook 15 experiencing slow performance at 0.40 GHz

Vivobook 15 experiencing slow performance at 0.40 GHz

Pages (2): 1 2 Next
R
ReptilianG09
Junior Member
43
01-02-2021, 05:29 AM
#1
Asus Vivobook 15 X512DA GPU paired with Radeon Vega 8 CPU. System runs AMD Ryzen 5 3500U with 12 GB RAM and Windows 11 Home OS. GPU drivers are installed, but troubleshooting steps have been tried. I restored the system ten days prior to the issue and it improved temporarily, though it reappeared after a day. Various power plans were tested without success. The BIOS was updated from version 317 to 318, yet the problem persisted. A new thermal paste was applied, but it didn’t resolve the issue. I reset the PC while preserving files, but the problem returned again. After disconnecting the battery and using wall power, no improvement occurred. I consulted forums and other communities, but no permanent solution was found. Recently, upon starting up, the processor reached full speed at 2.10 GHz (temporarily up to 3.10 GHz), then abruptly dropped to a low limit of 0.40 GHz. SpeedFan was used to test fan health, but RPM remained around 460 while operating at that frequency. I’m seeking help to identify the cause and find a lasting fix. Please note any details that could assist. Thank you in advance. Updated June 9, 2023 by TobyP
R
ReptilianG09
01-02-2021, 05:29 AM #1

Asus Vivobook 15 X512DA GPU paired with Radeon Vega 8 CPU. System runs AMD Ryzen 5 3500U with 12 GB RAM and Windows 11 Home OS. GPU drivers are installed, but troubleshooting steps have been tried. I restored the system ten days prior to the issue and it improved temporarily, though it reappeared after a day. Various power plans were tested without success. The BIOS was updated from version 317 to 318, yet the problem persisted. A new thermal paste was applied, but it didn’t resolve the issue. I reset the PC while preserving files, but the problem returned again. After disconnecting the battery and using wall power, no improvement occurred. I consulted forums and other communities, but no permanent solution was found. Recently, upon starting up, the processor reached full speed at 2.10 GHz (temporarily up to 3.10 GHz), then abruptly dropped to a low limit of 0.40 GHz. SpeedFan was used to test fan health, but RPM remained around 460 while operating at that frequency. I’m seeking help to identify the cause and find a lasting fix. Please note any details that could assist. Thank you in advance. Updated June 9, 2023 by TobyP

S
Stratin_OG
Member
232
01-02-2021, 11:03 AM
#2
I encountered a comparable problem on an Intel board. It seemed linked to a defective sensor triggering a throttle signal. On Ryzen systems this issue appears differently. See the Reddit discussion here: https://www.reddit.com/r/Amd/comments/mq...keep_your/. You likely don’t want to turn off that setting on Ryzen. If you still have coverage, I recommend sending it back via RMA promptly. Otherwise, the suggested fix might assist, though it could affect performance.
S
Stratin_OG
01-02-2021, 11:03 AM #2

I encountered a comparable problem on an Intel board. It seemed linked to a defective sensor triggering a throttle signal. On Ryzen systems this issue appears differently. See the Reddit discussion here: https://www.reddit.com/r/Amd/comments/mq...keep_your/. You likely don’t want to turn off that setting on Ryzen. If you still have coverage, I recommend sending it back via RMA promptly. Otherwise, the suggested fix might assist, though it could affect performance.

X
xGaminq
Junior Member
11
01-05-2021, 06:41 PM
#3
These low readings typically indicate the processor is operating in a protective state, usually due to heat constraints. Have you checked the temperatures? If you reprocessed the data, are you confident everything functioned correctly? Since you mentioned the issue existed prior to reprocessing, it’s unclear.
X
xGaminq
01-05-2021, 06:41 PM #3

These low readings typically indicate the processor is operating in a protective state, usually due to heat constraints. Have you checked the temperatures? If you reprocessed the data, are you confident everything functioned correctly? Since you mentioned the issue existed prior to reprocessing, it’s unclear.

A
206
01-06-2021, 08:27 PM
#4
Temperatures stay between 45 and 47 degrees Celsius frequently.
A
Anthony69edher
01-06-2021, 08:27 PM #4

Temperatures stay between 45 and 47 degrees Celsius frequently.

P
Prawnflakes
Member
204
01-11-2021, 06:32 AM
#5
It seems to be primarily a hardware concern rather than a software one.
P
Prawnflakes
01-11-2021, 06:32 AM #5

It seems to be primarily a hardware concern rather than a software one.

S
sniperwors
Junior Member
18
01-13-2021, 05:55 PM
#6
This situation involves a mix of factors. A signal may be causing your CPU to slow down, possibly due to a malfunctioning sensor or an incorrect implementation of the trigger. You might want to verify this using HWmonitor. (Refer back to the Reddit discussion)
S
sniperwors
01-13-2021, 05:55 PM #6

This situation involves a mix of factors. A signal may be causing your CPU to slow down, possibly due to a malfunctioning sensor or an incorrect implementation of the trigger. You might want to verify this using HWmonitor. (Refer back to the Reddit discussion)

D
davidspyro
Member
213
01-13-2021, 06:56 PM
#7
I've saved my homework monitor. I'll go over the post once more.
D
davidspyro
01-13-2021, 06:56 PM #7

I've saved my homework monitor. I'll go over the post once more.

I
IamRikyPT
Member
129
01-19-2021, 10:31 AM
#8
You're welcome! I understand you meant HWiNFO.
I
IamRikyPT
01-19-2021, 10:31 AM #8

You're welcome! I understand you meant HWiNFO.

J
JustAnApple
Junior Member
14
01-23-2021, 01:48 PM
#9
J
JustAnApple
01-23-2021, 01:48 PM #9

X
xLagx
Junior Member
7
01-23-2021, 08:02 PM
#10
This aligns with my incorrect sensor theories or another factor causing the signal, likely due to overheating.
X
xLagx
01-23-2021, 08:02 PM #10

This aligns with my incorrect sensor theories or another factor causing the signal, likely due to overheating.

Pages (2): 1 2 Next