Silent Scone@ROG wrote:
What did you adjust in the BIOS prior the problem starting? Have you tried to reset the UEFI via the rear I/O panel?
Silent Scone@ROG wrote:
The iCUE uninstallation could be a red herring, hard to say. Reset the UEFI and go from there.
OK, finally I did it...I think I've nailed down the problem at least but not solve it...and it's not a good news either....
I believe the culprit is my W.D Black 2TB
Let me remind again that what drive my system have.
1X W.D Black 2TB ( It's partitioned into two partition, around 900GB each and this is an old drive from my previous system )
2X Curial MX500 1TB ( one is brand new, another is from previous system as well )
1X Crucial MX500 2TB ( brand new )
1X Corsair MP510 960GB ( brand new and it's my boot drive )
Ok methods I've tried and found out this is the drive causing issue.
1) Remove all SATA drives, Restart PC. PC Boot up fine reaches Desktop no drama.
2) Install my W.D Black 2TB first, startup PC, click Restart....bam instant hit with A2 error code when booting up. Just like usual.
3) Unplug my W.D Black 2TB, use a DIFFERENT SATA PORT on the Mobo, same thing...A2 error code
3) Unplug my W.D Black 2TB, connect one of my Crucial MX500 1TB drive. Boot up PC, reaches Desktop, click Restart, PC restarts instantly reaches Desktop no issue no drama....
4) At this point I was confident, I connect the rest of all my other SATA drives, EXCEPT my W.D Black 2TB, boot up, Restart. NO ISSUE !
So it's confirmed that my W.D Black 2TB is causing me Restart issue.
Nothing else, I've even re-install iCUE, disabled my RAM lighting and it's not the culprit.
I've updated one of my MX500 1TB drive Firmware too, it was outdated, that wasn't the culprit.
I've changed SATA port along with the cable ( basically I just switched my MX500 SATA connector with my W.D Black ), doesn't work so it's not the culprit.
I think we can be damn sure it's the W.D Black 2TB itself causinsg it....but biggest question is, WHY ONLY ON RESTART ???
Why it never happen during Cold Boot ??
Also prior to this, I notice another strange issue. My SSD would randomly disappear, I never notice it till I reach desktop and wanted to play my games.
STEAM show it's not downloaded that's when I found out, I thought maybe my SATA conneciton were loose. So I turn off my PC, check everything ( i didn't even bother unplug and replug them ) everything was fine.
So I just start up PC again, all my drives are there again.
Then today it happened again, this time I just shut down PC, turn it on again and it's fixed like before.
I wonder if it's the W.D Black 2TB causing this problem as well....??
Is this a Software / Hardware issue ?? This is weird as well...it feels like hardware, yet it feels like a software....
So what do I do at this point ?? Throw the W.D Black 2TB away ?? That's quite an important drive to me, since that's where I store all my videos etc....
Why not grab a WD Blue 2 TB SATA SSD and get rid of that old clunker? Yes it will set you back $200 but that drive will last a long time.
I have the same issue and symptoms, X299 Prime Deluxe II MoBo however and Win11 Pro. All NVMe drives. 4 x 1TB Mushkin in a RAID5 in an Asus Hyper M.2 PCIe card, Adata SX8200 500GB on the MoBo, and a Western Digital Black PC SN700 1TB as my Boot Drive in the other MoBo slot. Everything up-to-date. System is a rocket otherwise and no stability issues either. Green checkmarks and green lights everywhere I can run a test, benchmark or diagnostic BUT if I warm-boot.. I get the A2 Detect HDD code... it seems though IF I wait almost 10 minutes, it finally gets by the issue and Windows loads and everything is ok. Cold boots are fine. I'm a big fan of the WD NVMe line as I have several others but from the higher-end Black SN850X series. I THINK the problem might just be with this more-towards-the-bottom dweller in the product lineup. Performance tested it at 2-3 GB/s reads and writes but something about it isn't responding correctly when the BIOS says "ok guys, where's the OS?" ... and when called upon, my WD NVMe just sits there like an idiot. I also believe this began somewhere within the Win11 ecosystem and subsequent updates to it. I doubt I'll try to solve it other than just replacing the SN700 with a better NVMe.