They really have… luckily that moronic “feature” can still be reverted… for now.
Got an Exos 2X18 that Windows 11 23H2 drops every few days when waking in the morning from overnight sleep. There’s no exact pattern here, so it looks like there’s a randomness (luck) component to it. Motherboard’s an ASRock B650 Steel Legend with current BIOS (3.08, AGESA 1.2.0.2) and all firmware, drivers, and OS patches are current other than the 24H2 feature update. Drive was used this way for months with Win 10 22H2 on a B550 board without issue.
Wondering if anyone might have ideas besides pinging ASRock support hoping maybe eventually they can make a fix. Stuff I’ve tried so far:
- Putting the 2X18 on a chipset SATA port. Drops after a few days.
- Putting the 2X18 on a chipset SATA port marked as removable in the BIOS. Drops after a few days. Rescanning drives from Windows Disk Management doesn’t find it again.
- Putting the 2X18 on an ASM1601 SATA port off the chipset. Drops after a few days. Might be less likely to drop after chipset direct, but hard to tell.
- Changing the SATA data cable. No effect. Didn’t think it was a cable problem as the drive runs fine when detected but it was easy to try.
Sometimes there’s a bunch of storachi resets in the system event log before the disk surprise removed event, sometimes it’s just surprise removed. Not seeing anything else storage related or that looks different in wakes where the drive doesn’t drop versus wakes where it does.
The two NVMes in the build are fine and the 2X18’s picked up by a restart after it drops. Got an IronWolf available I’m going to put in to see if it also drops.
Playing with AHCI link power management - HIPM/DIPM may be worth a try.
https://www.tenforums.com/tutorials/72971-add-ahci-link-power-management-power-options-windows.html
Wild and crazy shot - Have you tried changing the power cable too?
And in less/fewer Windows problem - now you can download the ISO without having to go through the Media Creation Tool: Download Windows 11
Thanks. Checked and it’s defaulted to HIPM only. Neither drive’s dropped in the past couple days, so might be a while to change it to HIPM+DIPM and then longer to see if that has an effect.
Have thought about it, but not yet. Since a drive only drops every few days each step of testing take can take a week or more. While changing a lot of things and just getting a fix’d be nice I’m also curious to pin down where the issue is.
I got an interesting one.
Out of nowhere it seems that ALL tasks in the Task Scheduler that trigger on Idle simply NEVER trigger anymore. Yes I am aware that what Windows considers idle is a little strange. I also know that it will only trigger the idle state if CPU usage is below 10%.
This is also true with Windows based tasks as well it would seem not just tasks that I have made.
For example I have a task that is set to trigger after 5 minutes of inactivity to restart the windows audio service because iCue broke something, More on this here iCue Forum And it has been working flawlessly, Until for whatever reason on Idle just does not trigger anymore?
Anyone got any ideas? I am a little worried about the fact that even Windows tasks are not triggering such as;
Windows 11 has been like that since day 1 if memory serves me.
Never understood the media creation tool. I mean why create the media for my pc when I’m not always going to be installing it on my computer? Who says the .iso is not for a friend or fellow tech? /end rant!
Me neither, especially when you just got the .iso when accessing from linux (as I learned a few months ago lol).
It was like that for non-windows browsers a while back.
I can think of the following reasons through the time I’ve used it:
- Limiting access to who can download the image, just like Apple does. You can only generate an image from a Windows machine. (I disagree with this being a good thing)
- Allows to customize the ISOs with the right serial key and edition for you to download through command flags. This was very handy for me as I no longer needed to care about the installation process, once it started and I selected the drive, I could forget about everything for as long as it took to install. However, this meant that the ISO would be generated just for you. Which would make understandable the fact that it should not be publicly available (downloads through this mode have a life of 24 hours).
- Auto-generating a USB with the right format/signature out of the box. I can imagine telling my mom to go and use Rufus, deactivate Secure Boot at the BIOS/UEFI and having her to install Windows. (I understand that Windows is the only OS that can be comfortably used with Secure Boot at an install stage, please do tell me if I’m wrong with this one) (ps: read comfortably as “a person that does not know what Secure Boot is”)
Minor update: neither drive dropped in two weeks with the IronWolf and, in not quite two weeks with an MX500, neither drive’s dropped either. Looks like a single SATA drive issue, though since the 2X18’s used every day no data on whether it’s Mach.2 specific or affects other drive types.
Kept getting microstutters while using my computer. This guide resolved my issue for now
Will need to check alter to see if this is fully resolved