Asrock B560 - New SSDs unsafe shutdowns
Printed From: ASRock.com
Category: Technical Support
Forum Name: Intel Motherboards
Forum Description: Question about ASRock Intel Motherboards
URL: https://forum.asrock.com/forum_posts.asp?TID=25657
Printed Date: 06 May 2024 at 2:25pm
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com
Topic: Asrock B560 - New SSDs unsafe shutdowns
Posted By: EasySan2k
Subject: Asrock B560 - New SSDs unsafe shutdowns
Date Posted: 23 Mar 2023 at 11:00pm
Hi there,
I have a litte but strange problem with my new WD SN770 SSDs.
First of all after hours and hours of investigating i found out that the problem only exist with the SSD in the M2_1 slot. If i put the SSD in the M2_2 or M2_3 slot the problem doesnt exist.
The unsafe shutdowns counter goes up every second boot and is always "power cycles devided by 2". I know it sounds strange but i spend many hours testing it.
One week ago my new WD SN770 SSD had 10 power cycles and 5 unsafe shutdowns. Now im already at 22 power cycles and 11 unsafe shutdowns. I received a second SN770 yesterday, cloned the OS and did test the new on in the M2_1 slot, same behavior.
So that both SN770 having the same issue they cant be faulty at all.
Before the new SN770 SSDs i had 2x WD SN750 installed, they were running fine.
Does anyone have any idea where the problem could be?
OS: Win 10 Pro
MB: AsRock B560 Steel Legend (BIOS 2.20)
NVMe Driver: Standard MS AHCI Driver
Fast Boot on UEFI and Windows disabled
No errors on windows event viewer or reliability monitor
|
Replies:
Posted By: threadzipper1957
Date Posted: 24 Mar 2023 at 11:31pm
Yep.
This is a bit of a known issue, but is not ASRock related, it is on all brands.
What sometiems happens is that there is a compatibility issue between the boards PCIE lanes, and the controlelr on the M.2.
Sometimes M.2 intermittently stops working, sometimes it is not detected at all.
When You connect the M.2 to another baord, it is working fine, conlcusion, it is a board problem.
However when you use another brand M.2 on this "Defective" board, it works fine, so it's not the board but the M.2.
But this is difficult to solve, and usually it is better to go for another brand of M.2.
There is no standard solution for this, just sheer bad luck
-------------
Kind Regards
|
|