F5F Stay Refreshed Hardware Desktop Unusual performance issues with the processor.

Unusual performance issues with the processor.

Unusual performance issues with the processor.

Pages (2): 1 2 Next
Z
Zentrela
Member
129
02-11-2019, 01:10 PM
#1
Hey, I have a ryzen 3600 (undervolted to 1.25v @ 4.025 Ghz ) for about a year now. Those settings were well stable with stress when I first set up. Never had an issue (and I always keep an eye on my task manager) until now that I caught the second time (in a week or so) doing this where Core#0 just "dies" randomly, where the usage (of that core) is between 0 and 3% from there until I restart it. I don't have a clue if this is a visual bug, some bug on windows, a driver, a CPU clock problem, or even an Application causing it, and I can't find anything online about this weird behaviour. I don't notice apps crashing nor much of a performance hit in real world, well, because it's "only" 9%. Task manager and HWMonitor shows that core between 0 and 5% when both idling and/or stressing. Weirdly, Core#0 still shows that is consuming some Watts as on HWMonitor (probably for the second thread). Like I said, a restart fixes it temporarily until it happens again (within a few days) until this happens out of nowhere and I need to restart it again. Please help. Specs: Windows 10 Pro 64 bit version 20H2 build 19042.928 Ryzen 5 3600 MSI X470 Gaming Plus Max (MS-7B79) 4x16GB Corsair Vengeance RAM Corsair CS650M Bronze 650 Watts (oldest component, almost 7 years, I thought it could be that but the restart fixing it, kinda makes me think not) GTX 1660 Super (stock clock) A few SSD's
Z
Zentrela
02-11-2019, 01:10 PM #1

Hey, I have a ryzen 3600 (undervolted to 1.25v @ 4.025 Ghz ) for about a year now. Those settings were well stable with stress when I first set up. Never had an issue (and I always keep an eye on my task manager) until now that I caught the second time (in a week or so) doing this where Core#0 just "dies" randomly, where the usage (of that core) is between 0 and 3% from there until I restart it. I don't have a clue if this is a visual bug, some bug on windows, a driver, a CPU clock problem, or even an Application causing it, and I can't find anything online about this weird behaviour. I don't notice apps crashing nor much of a performance hit in real world, well, because it's "only" 9%. Task manager and HWMonitor shows that core between 0 and 5% when both idling and/or stressing. Weirdly, Core#0 still shows that is consuming some Watts as on HWMonitor (probably for the second thread). Like I said, a restart fixes it temporarily until it happens again (within a few days) until this happens out of nowhere and I need to restart it again. Please help. Specs: Windows 10 Pro 64 bit version 20H2 build 19042.928 Ryzen 5 3600 MSI X470 Gaming Plus Max (MS-7B79) 4x16GB Corsair Vengeance RAM Corsair CS650M Bronze 650 Watts (oldest component, almost 7 years, I thought it could be that but the restart fixing it, kinda makes me think not) GTX 1660 Super (stock clock) A few SSD's

C
Charoonia
Member
134
02-11-2019, 05:18 PM
#2
It performs the same action when you clear the overclock and turn on Precision Boost.
C
Charoonia
02-11-2019, 05:18 PM #2

It performs the same action when you clear the overclock and turn on Precision Boost.

L
Lukapop04
Member
216
02-26-2019, 08:39 PM
#3
I'm planning to share this now, as I've noticed something unusual about this device after a year of using the clock. Given how unexpected this issue is, I might only provide updates for a week or a month until it recurs (if it does).
L
Lukapop04
02-26-2019, 08:39 PM #3

I'm planning to share this now, as I've noticed something unusual about this device after a year of using the clock. Given how unexpected this issue is, I might only provide updates for a week or a month until it recurs (if it does).

L
los_dos
Member
50
02-26-2019, 10:37 PM
#4
It seems the issue might be connected to voltage. Turning on PB will indicate whether the device is functioning. CPUs require specific voltages for optimal performance.
L
los_dos
02-26-2019, 10:37 PM #4

It seems the issue might be connected to voltage. Turning on PB will indicate whether the device is functioning. CPUs require specific voltages for optimal performance.

F
filcio1234
Member
211
02-26-2019, 11:30 PM
#5
The central processing unit remains unaffected during gaming sessions.
F
filcio1234
02-26-2019, 11:30 PM #5

The central processing unit remains unaffected during gaming sessions.

E
evogeli
Member
249
02-27-2019, 07:37 PM
#6
stays unchanged. isn't applied.
E
evogeli
02-27-2019, 07:37 PM #6

stays unchanged. isn't applied.

T
TheAction1224
Junior Member
26
03-03-2019, 03:59 AM
#7
The game operates correctly, and the PC does not crash. If it runs smoothly, it indicates no sensor issues.
T
TheAction1224
03-03-2019, 03:59 AM #7

The game operates correctly, and the PC does not crash. If it runs smoothly, it indicates no sensor issues.

X
xXSaltySeaDog
Member
52
03-20-2019, 04:49 PM
#8
Okay then its definitely a sensor fault then, my pet peeve of AMD CPU's is this type inconsistency happens with them is they are well made but the thing that seems to be consistently cheaped out on is sensors for them. AMD CPU's otherwise are 98%of the time almost perfect just QoL stuff seems to take a back seat for the pure performance. As to the issue of the sensor and issue with it not registering atm core #0 then is not knowing if its ACTUALLY died... But by the time that core actually dies hopefully you have saved up enough to replace or get a new CPU.
X
xXSaltySeaDog
03-20-2019, 04:49 PM #8

Okay then its definitely a sensor fault then, my pet peeve of AMD CPU's is this type inconsistency happens with them is they are well made but the thing that seems to be consistently cheaped out on is sensors for them. AMD CPU's otherwise are 98%of the time almost perfect just QoL stuff seems to take a back seat for the pure performance. As to the issue of the sensor and issue with it not registering atm core #0 then is not knowing if its ACTUALLY died... But by the time that core actually dies hopefully you have saved up enough to replace or get a new CPU.

R
Raidex20
Posting Freak
751
03-20-2019, 05:01 PM
#9
No VM is being run and the hypervisor isn't utilizing that core.
R
Raidex20
03-20-2019, 05:01 PM #9

No VM is being run and the hypervisor isn't utilizing that core.

I
iTzChubiYT
Junior Member
18
03-21-2019, 06:50 PM
#10
Dead sensor = CPU will die completely soon? Well, I still have 1 year left from warranty... If this is a hardware problem I will RMA it. RIP work until I get a new CPU though.... If I set up a 12 core VM, same thing happens on the examples above.
I
iTzChubiYT
03-21-2019, 06:50 PM #10

Dead sensor = CPU will die completely soon? Well, I still have 1 year left from warranty... If this is a hardware problem I will RMA it. RIP work until I get a new CPU though.... If I set up a 12 core VM, same thing happens on the examples above.

Pages (2): 1 2 Next