F5F Stay Refreshed Hardware Desktop Issue with power efficiency in NVMe SSDs Bug affecting energy consumption during operation

Issue with power efficiency in NVMe SSDs Bug affecting energy consumption during operation

Issue with power efficiency in NVMe SSDs Bug affecting energy consumption during operation

I
iLwRo
Member
130
10-01-2016, 05:06 PM
#1
I experienced some unusual behavior last year where Windows would unexpectedly restart when idle. This occurred even when I wasn’t using it and the event viewer was blank. After a while, I tried updating the BIOS, which seemed to resolve the problem—though it didn’t completely fix it. Now it happens less often, which eased my frustration. Meanwhile, my Linux setup began facing I/O issues with the main drive, so I decided to reinstall the OS. During the process, I found something strange: the disk would become unresponsive randomly. I reviewed the dmesg logs and saw a message about a faulty power-saving feature. I’m seeking advice from the community because I’m unsure how to proceed. I checked all NVMe-related BIOS settings, but every power-saving option was disabled. My machine runs a Ryzen 5600G on an Asus Prime B450M-A II with a Samsung 970 Evo Plus drive. If anyone knows a workaround or can point out which manufacturer might be involved, I’d really appreciate your help. Also, please note that my English is still developing.
I
iLwRo
10-01-2016, 05:06 PM #1

I experienced some unusual behavior last year where Windows would unexpectedly restart when idle. This occurred even when I wasn’t using it and the event viewer was blank. After a while, I tried updating the BIOS, which seemed to resolve the problem—though it didn’t completely fix it. Now it happens less often, which eased my frustration. Meanwhile, my Linux setup began facing I/O issues with the main drive, so I decided to reinstall the OS. During the process, I found something strange: the disk would become unresponsive randomly. I reviewed the dmesg logs and saw a message about a faulty power-saving feature. I’m seeking advice from the community because I’m unsure how to proceed. I checked all NVMe-related BIOS settings, but every power-saving option was disabled. My machine runs a Ryzen 5600G on an Asus Prime B450M-A II with a Samsung 970 Evo Plus drive. If anyone knows a workaround or can point out which manufacturer might be involved, I’d really appreciate your help. Also, please note that my English is still developing.

V
VinylGuarder
Member
153
10-02-2016, 03:13 PM
#2
You transitioned from a Windows reboot to using Linux, possibly during a BIOS update. Are you referring to dual-booting? Can both OSes still be accessed? The issue appears to involve the NVME drive consistently, no matter which system you're using.
V
VinylGuarder
10-02-2016, 03:13 PM #2

You transitioned from a Windows reboot to using Linux, possibly during a BIOS update. Are you referring to dual-booting? Can both OSes still be accessed? The issue appears to involve the NVME drive consistently, no matter which system you're using.

X
XDR_Hellfire
Junior Member
1
10-02-2016, 09:15 PM
#3
I haven’t changed the operating system, I use both according to my requirements over the past three years. Yes, the problem occurs no matter which OS I’m using. I need to turn off power-saving features in Windows—like sleep mode and screen off—to prevent crashes, and even after the last crash it didn’t save any data to the event viewer. On Linux, the message shows up after I perform an action on the drive and wait a short time.
X
XDR_Hellfire
10-02-2016, 09:15 PM #3

I haven’t changed the operating system, I use both according to my requirements over the past three years. Yes, the problem occurs no matter which OS I’m using. I need to turn off power-saving features in Windows—like sleep mode and screen off—to prevent crashes, and even after the last crash it didn’t save any data to the event viewer. On Linux, the message shows up after I perform an action on the drive and wait a short time.

R
142
10-03-2016, 11:37 AM
#4
Check for any available firmware updates for the drive.
R
RM_55_BlackRoi
10-03-2016, 11:37 AM #4

Check for any available firmware updates for the drive.

C
CharlieMcD14
Member
64
10-04-2016, 05:51 AM
#5
Confirmed, it isn't as expected.
C
CharlieMcD14
10-04-2016, 05:51 AM #5

Confirmed, it isn't as expected.

P
PersieO
Posting Freak
786
10-09-2016, 08:11 PM
#6
Followed your advice and encountered the same problem again. I captured a screenshot of the dmesg output from my phone and saw that it recommends reporting the issue. Should I try using kernel bugzilla, check arch bugs, or look up the AMD forums for possible platform-specific fixes?
P
PersieO
10-09-2016, 08:11 PM #6

Followed your advice and encountered the same problem again. I captured a screenshot of the dmesg output from my phone and saw that it recommends reporting the issue. Should I try using kernel bugzilla, check arch bugs, or look up the AMD forums for possible platform-specific fixes?

P
Peteechops25
Member
210
10-10-2016, 01:35 AM
#7
If it doesn't work on both Windows and Linux, the issue is likely hardware-related. You might want to reinsert the SSD, CPU, or RAM to check for a faulty connection.
P
Peteechops25
10-10-2016, 01:35 AM #7

If it doesn't work on both Windows and Linux, the issue is likely hardware-related. You might want to reinsert the SSD, CPU, or RAM to check for a faulty connection.

F
flyer78
Senior Member
425
10-28-2016, 07:14 PM
#8
That's actually a good idea, i will try that.
F
flyer78
10-28-2016, 07:14 PM #8

That's actually a good idea, i will try that.

C
cherryforce
Junior Member
8
10-28-2016, 09:51 PM
#9
I attempted this but it didn't work. Now I'm checking if it functions with fans running at full speed—possibly the SSD overheated due to being placed between the GPU and CPU. I'll share my update once I resolve it, so others looking for solutions can try too.
C
cherryforce
10-28-2016, 09:51 PM #9

I attempted this but it didn't work. Now I'm checking if it functions with fans running at full speed—possibly the SSD overheated due to being placed between the GPU and CPU. I'll share my update once I resolve it, so others looking for solutions can try too.

M
Mino995
Member
103
11-02-2016, 01:16 AM
#10
In the end, it seemed quite simple—it was just poor airflow, and increasing the ambient fan speed resolved the issue. I’m still amazed by how this turned out!
M
Mino995
11-02-2016, 01:16 AM #10

In the end, it seemed quite simple—it was just poor airflow, and increasing the ambient fan speed resolved the issue. I’m still amazed by how this turned out!