Question WD Blue 2TB SSD (Non-OS) Starting at 100% Active Time

OffensiveBias

Distinguished
Jul 31, 2015
19
0
18,510
I just completed a build on my new PC, and my secondary/storage SSD (OS is on a WD Black) for some reason always starts at 100% active time for about 5-10 minutes upon boot. I initially noticed this in the Performance tab of the Task Manager, then also looked into the disk portion of the Resource Monitor. When I did this, I noticed that there are usually several culprits, but most notably: NTFS File Logs and an MSI-related windows file (MSI in this case being message service interrupt). When I looked, these (and a couple of others) for some reason have approximately a 60,000ms (1 minute) response time. The drive and everything on it functions totally fine when this disappears, though I just can't seem to figure out how to make it work instantly.

Things I have done so far:
Tried different SATA Cables/SATA Ports
Completely Wiped the SSD and started over
Disabled MSI
Disabled Pre/Superfetch
Disabled Windows Defender/Downloaded Avira
Confirmed AHCI was active, ensured all AHCI-related items in the registry were set to the appropriate values.
Probably have done a few other things as well, but I have tried so much that it is difficult to remember everything.

If ANYONE has any insight to this issue whatsoever, I would be eternally grateful.

Let me know what logs/screenshots I need to provide.
 
What are the specs for this system (make/model of all components)? Also, what version of Windows?

Is Windows, your motherboard BIOS, and all of your major drivers (video, audio, motherboard chipset, and network) up to date?

All drivers are up to date 100%.

Specs:
EVGA NVIDIA RTX 2080Ti,
Intel i7-9700K
GSkill 32GB DDR4 3200MHz RAM
OS SSD: WD Black 500GB m.2
SSD in question: WD Blue 2TB SATA
HDD: Seagate 2TB SATA
MOBO: Gigabye Aorus Z390 Pro Wifi
PSU: EVGA 1000W 80 plus gold
 
Last edited by a moderator:
See page 20 of the manual. Make sure you aren't trying to use SATA ports that become unavailable when m.2 devices are installed.

https://download.gigabyte.com/FileList/Manual/mb_manual_z390-aorus-pro_wifi_1001_190708_e.pdf

Also, make sure your motherboard BIOS is updated to the most recent version, as well.

First off, thanks for providing a plausible solution. It did not help, but thank you anyway.

I checked to see which m.2 the OS was installed in, and it was the m.2A, which shares with SATA 1. I have nothing plugged into the SATA 1 port. The m.2M, which has nothing installed, is related to SATA 4/5, of which are my HDD and Disk Drive, respectively. Unfortunately this means the problem is not related to this.

All drivers for everything are up to date.
 
Please try the drive in another computer as a second drive, if it continues to have 100 percent usage, I think there is something wrong with the controller so your drive. Copy the contents of the drive and then ask for a change.
 
Please try the drive in another computer as a second drive, if it continues to have 100 percent usage, I think there is something wrong with the controller so your drive. Copy the contents of the drive and then ask for a change.

If I had a second computer to test it with, I would. It only really continues for 5-10 minutes at most after each boot, then is fine. Looking in the Resource Monitor, the NTFS log and master file table, along with some assorted random files on the drive (Halo MCC, Steam-related, even a War Thunder file I saw once) shoot up to a long response time. The NTFS ones are the ones that occur every single time, whereas the others are a bit more random.
 
First off, thanks for providing a plausible solution. It did not help, but thank you anyway.

I checked to see which m.2 the OS was installed in, and it was the m.2A, which shares with SATA 1. I have nothing plugged into the SATA 1 port. The m.2M, which has nothing installed, is related to SATA 4/5, of which are my HDD and Disk Drive, respectively. Unfortunately this means the problem is not related to this.

All drivers for everything are up to date.
Understood on the drivers. What about the motherboard BIOS? That is not the same as the aforementioned drivers.
 
That is certainly odd. Have you installed, changed, etc anything since the previous "fix"/change in performance?

I uninstalled a secondary antivirus because I thought it was causing the issue (was just super high disk use, not active time). Aside from that, all I have done is add mods for GTA V but according to the resource monitor those are not the items with issues. This time, aside from testing to open a specific program on the drive, the only delayed items in the resource monitor were NTFS-related.

Is there perhaps some file indexing/TRIM action occurring during the first several minutes after bootup? A large amount of 'rewrites' to new areas of the SSD (if needed) might indeed keep it busy for a few minutes...

Honestly, I don't know. I'm more of an expert with the hardware side than I am the actual processes. The drive is mostly empty (1.2TB free of 1.8TB formatted), so I wouldn't think it would be doing any indexing, but you probably know far more than I do.
 
Just another update,

I wiped the drive and restarted for a second time. This time, I ensured that I did not install any Windows Store games on the drive and kept them on the OS drive. I put a couple of files on the drive (Division 2, EVE Online, COD:MW, Dota 2, all utilize separate services). Wouldn't I know it, the problem still persisted.

HOWEVER, I did notice a couple of things this time in the Resource Monitor. While the file section was indeed in the various games on my SSD (F drive, now), the delays were actually only caused by 2 .exe files, which I will list below:

MsMpEng.exe
GameManagerService.exe

The first, as I understand it, is a file utilized by Windows Defender, which I THOUGHT I had disabled, but perhaps I did not do so completely and someone else may have some more insight on that.

The second is a function of Razer Synapse. To quote a Razer employee from Reddit "Game Manager Service is responsible for maintaining a list of all games installed on your PC and helps in determining when a game is launched/shut down, so that Synapse can switch your device/chroma profiles based on the active game/app."

So, I think the next step is going to be trying to completely disable Windows Defender and its processes, then see if I can figure out what is going on with Synapse.

EDIT: It seems this also occurs when the computer enters sleep mode then starts again. Upon this occurring, I am seeing that the System itself has a delay, not an .exe file as is mostly present in the 'image' category. It literally says System for the image, and the files were NTFS-related.
 
Last edited by a moderator:
Another update:

I was finally able to try the drive in my buddy's desktop... It works perfectly fine. We tried the same cable I used and everything. I once again tried a different SATA port in my computer (avoiding SATA port 1 as per the mobo manual) and still the same issue. This pretty much tells me that it is an OS issue. Our current next step is trying a different windows installation on a different drive and using it as the boot drive instead of my m.2. If that fixes it, it means we will just re-install Windows 10 and see what happens.