MPG X870E EDGE TI WIFI intermittently doesn't detect SATA SSD drives on restart

[russny]

Hello,

I've been dealing with this issue for several months now and multiple BIOS updates did not resolve the problem. Currently have the latest 7E59v1A82 BIOS installed.

The issue is intermittent, but frequently when I restart my computer, it will boot into BIOS instead of booting normally due to my SATA SSD drives (one of them is the boot drive) not being detected. This issue only happens when restaring the computer and never from cold boot. When this happens, both SATA SSD drives fail to get recognized. This does not effect my M2 drives, of which I have three isntalled.

Usually, turning off the PC and unplugging the power for about a minute resolves the issue and the PC boots normally, but this is only a temporary fix. Sometimes exiting BIOS and restarting the computer (often multiple times) without a full shutdown will also result in a successful boot.

Does anyone know what could be causing this issue? It seems like some kind of firmware problem, rather than a hardware defect, since I never have any issues with these drives being detected once the computer is booted into Windows.

Any help would be greatly appreciated!

 

[ericj159802e9]

That's a bit of an odd problem; I have the same board with four SATA disks (no NVME disks) and have never experienced this.

Usually, turning off the PC and unplugging the power for about a minute resolves the issue

To speed things up a bit hold down the power button for 30s after unplugging the power . This trick is typically used to resurrect lost Ethernet or WiFi adapters.

Do the Windows Event Logs (Event Viewer) give us a clue?

 

[russny]

Thanks for the reply. What would I look for in the Event Viewer? Would anything even show up there since the issue seems to manifest itself even before the OS is booted?

Once these SATA drives fail to get recognozied and I restart the computer by exiting the BIOS screen, more often than not, the drives don't reappear until I restart the PC (from the Click BIOS UI) multiple times or do a complete shutdown and drain the power.

 

[Tourica]

Thanks for the reply. What would I look for in the Event Viewer? Would anything even show up there since the issue seems to manifest itself even before the OS is booted?

Once these SATA drives fail to get recognozied and I restart the computer by exiting the BIOS screen, more often than not, the drives don't reappear until I restart the PC (from the Click BIOS UI) multiple times or do a complete shutdown and drain the power.

First, check if there is a hardware issue.
Download it for free, not for a fee.

Download NIUBI Partition Editor Product Editions | Download Center

NIUBI Partition Editor download center. Download NIUBI Partition Editor Free, Professional, Server, Enterprise and Technician Edition. 100% Clean and safe.

www.hdd-tool.com

 

[russny]

I'm not familiar with that softrware. Does it have utiities to detect SSD hardware faults?

Both of my SATA drives are Samsung SSD 860 EVO and the Samsung Magician software doesn't show any issues with the drives. Drive firmware is also up-to-date.

 

[Tourica]

I'm not familiar with that softrware. Does it have utiities to detect SSD hardware faults?

Both of my SATA drives are Samsung SSD 860 EVO and the Samsung Magician software doesn't show any issues with the drives. Drive firmware is also up-to-date.

Download this program and try installing the drivers.
It also includes a performance check.

Samsung Magician Software Download | Consumer Storage | Samsung Semiconductor Global

Samsung Magician software is designed to help you manage your Samsung SSD with a simple, intuitive user interface. Download files & find supported models.

semiconductor.samsung.com

 

[russny]

Download this program and try installing the drivers.
It also includes a performance check.

Samsung Magician Software Download | Consumer Storage | Samsung Semiconductor Global

Samsung Magician software is designed to help you manage your Samsung SSD with a simple, intuitive user interface. Download files & find supported models.

semiconductor.samsung.com

Not sure if you missed my previous reply, but I already have Samsung Magician installed. Firmware for all the drives is updated and there are no drive issues reported by the software.

 

[Tourica]

I'm not familiar with that softrware. Does it have utiities to detect SSD hardware faults?

Both of my SATA drives are Samsung SSD 860 EVO and the Samsung Magician software doesn't show any issues with the drives. Drive firmware is also up-to-date.

First, check if there is a hardware issue.
Download it for free, not for a fee.

You can inspect the surface here.
First, download the app.

Download NIUBI Partition Editor Product Editions | Download Center

NIUBI Partition Editor download center. Download NIUBI Partition Editor Free, Professional, Server, Enterprise and Technician Edition. 100% Clean and safe.

www.hdd-tool.com

First, select the hardware you want to test,
right-click and select “Surface Test,”
and then run the surface scan.

 

[ericj159802e9]

Thanks for the reply. What would I look for in the Event Viewer? Would anything even show up there since the issue seems to manifest itself even before the OS is booted?

The problem only happens after a restart so there is a (slight) chance it might be Windows related. Hence my question.

 

[russny]

The problem only happens after a restart so there is a (slight) chance it might be Windows related. Hence my question.

I see what you mean. While most of the time I encounter this error when restarting from Windows, it does also occur on occasion when restarting from the BIOS UI, even before the OS is booted. I just don't often restart my PC from the BIOS screen. So I'm inclined to believe this is some kind of SATA initialization issue.

 

[ericj159802e9]

From what you describe an initialization may be where the problem is. What SSDs are you using? Are they the same brand and version?

 

[Tourica]

I see what you mean. While most of the time I encounter this error when restarting from Windows, it does also occur on occasion when restarting from the BIOS UI, even before the OS is booted. I just don't often restart my PC from the BIOS screen. So I'm inclined to believe this is some kind of SATA initialization issue.

If it's a hardware issue, check the system status.
Go to the Control Panel and check the system status list.
Then, check to see if it's a software issue.
The issue has nothing to do with the SSD.
If it's a hardware problem, it's likely a software conflict.
First, check that the SSD is properly installed, then try again.
Next, try replacing the SSD cable and try again.
If the problem persists,
open Command Prompt as an administrator.
Run the command “Sfc /ScanNow”
to run a scan.
Then, create a bootable disk.

bcdedit /set disabledynamictick yes



bcdboot c:\windows /s c:



bootsect /nt60 C: /mbr



Then, for the disk check command,



type “chkdsk C: /f/r/x”, press Y, hit Enter,

and reboot.
If a prompt appears during boot asking you to press a key to cancel within a few seconds,
do not press any keys on the keyboard;
just wait.
The system will then run a disk check.
If you want to check a different disk,
you can modify the command from the C: drive to target the D: drive and run the check.

 

[russny]

From what you describe an initialization may be where the problem is. What SSDs are you using? Are they the same brand and version?

Both drives are Samsung SSD 860 EVO - one is 1TB and the other 2TB. Both are healthy drives since Samsung Magician is not reporting any problems with them and I never have issues while using the PC.

I've had these drives installed since my previous build (MEG X570 UNIFY) and never had this issue - it only started happening when I switched to AM5 about a year ago. When the issue does occur, both of these SSD drives (connected by separate SATA cables) fail to get recognized, so it's unlikely the cables.

It's also difficult to troubleshoot since the issue is intermittent and can't be reproduced reliably - sometimes the PC boots up fine after a restart, sometimes it doesn't. I've never seen it happen from cold boot though, so that's why I think it's some sort of SATA controller initialization or a power delivery issue.

I've been working with computers (building, fixing) for most of my adult life and also worked at Apple for 4 years as a tech (so I'm not a novice) and this doesn't "feel" like a hardware issue based on observed symptoms.

 

[Tourica]

Both drives are Samsung SSD 860 EVO - one is 1TB and the other 2TB. Both are healthy drives since Samsung Magician is not reporting any problems with them and I never have issues while using the PC.

I've had these drives installed since my previous build (MEG X570 UNIFY) and never had this issue - it only started happening when I switched to AM5 about a year ago. When the issue does occur, both of these SSD drives (connected by separate SATA cables) fail to get recognized, so it's unlikely the cables.

It's also difficult to troubleshoot since the issue is intermittent and can't be reproduced reliably - sometimes the PC boots up fine after a restart, sometimes it doesn't. I've never seen it happen from cold boot though, so that's why I think it's some sort of SATA controller initialization or a power delivery issue.

I've been working with computers (building, fixing) for most of my adult life and also worked at Apple for 4 years as a tech (so I'm not a novice) and this doesn't "feel" like a hardware issue based on observed symptoms.

What is the power rating in watts?
If you're asking about the power supply, I recommend an 800W unit.

 

[ericj159802e9]

What would I look for in the Event Viewer?

I see I didn't answer this question. Use the filter function to filter for Critical and Warning. Log entries of DistributedCom can be discarded. Check the log entries to see if there are references to problems with disks.

Could you post a screenshot of CrystalDiskInfo to see if it reports something?

I found the following solution at Samsung Forums that may be worth a try:

Change the AHCI driver to "Standard AHCI 1.0 Serial ATA Controller"

 

[russny]

I see I didn't answer this question. Use the filter function to filter for Critical and Warning. Log entries of DistributedCom can be discarded. Check the log entries to see if there are references to problems with disks.

Could you post a screenshot of CrystalDiskInfo to see if it reports something?

I found the following solution at Samsung Forums that may be worth a try:

Thanks for finding that! I got excited for a second, but when I checked the Device Manager I see that I'm already using the recommended SATA controller drivers.
I've attacched the CrystalDiskInfo screenshots for the drives in question.

 

[ericj159802e9]

My eye got drawn by the POR Count (Power On Recovery Count). According to Samsung support document POR Count is:

A count of the number of sudden power off cases. If there is a sudden power off, the firmware must recover all of the mapping and user data during the next power on. This is a count of the number of times this has happened.

It points to the PC switching off unexpectedly. From a hardware perspective the PSU becomes a suspect. Can you tell us what PSU you are using and how old it is?

 

[russny]

It's a Seasonic VERTEX PX-1200 and it's less than a year old. I can't say that I remember experiencing that many instances of sudden loss of power. Maybe a couple of times last year when the power went out in the apartment, but that's about it.

Also, I'm not sure if that value (99) is even accurate? Unless I'm misinterpreting that number. According to that table, the drive's Power On Hours is only 97, while it says 14174 hours in the details section above.

I'm curious, which drivers are you using for the SATA Controllers? Is it the "Standard SATA AHCI Controller" and is the Driver Date Wed 6/21/2006 and Version 10.0.26100.7920? Seems strange to be using a driver from 20 years ago.

Appreciatre all the help!

 

[ericj159802e9]

T

Also, I'm not sure if that value (99) is even accurate? Unless I'm misinterpreting that number. According to that table, the drive's Power On Hours is only 97, while it says 14174 hours in the details section above.

The numbers for Current and Worst are normalized numbers. It represents a percentage of full health for the parameter.

I have the same driver version and date.

Instead of looking at the normalized number we want to look at the raw numbers. They show 73 (Hexadecimal) which translates to 115 (Decimal: the numbers we use and understand) and 61 (HEX) which translates to 97 (DEC). Means there have been 115 shutdowns for the 1 TB SSD and 97 for the 2TB SSD. There is a setting in CrystalDiskInfo to show decimal numbers instead of hexadecimal.

According to Acronis:

Power-On Hours (POH) S.M.A.R.T. parameter indicates a count of hours in power-on state. The value of this attribute shows total count of hours (or minutes, or seconds, depending on manufacturer) in power-on state. A decrease of this attribute value to the critical level (threshold) indicates a decrease of the MTBF (Mean Time Between Failures).

Comments online that PowerOnHours is not a useful parameter for SSDs. Looking at Total Bytes Written is said to make more sense.

For both drives the TBW (Total Host Writes in the upper part of the screen) equals to 33594 GB (32.807TB) and 10032 GB (9.797 TB). The TBW for both drives are 600TB and 1200TB according to the specifications so both have years to go.

CDI says the overall health is good 96%. Power On Recovery Count still piques my interest. Do you have another PSU that you could test with? On a sidenote. How often does this happen? Once or a couple of times a week?

Does Windows report the Power On Recovery issue in Event Viewer? It may log it as Event ID 41. When using Event Viewer use the filter option and filter for critical events and warnings. Warnings about DistributedCom can be disregarded.