Windows 10: Hard drive being active after recent TuesdayFebruary 3, 2021 update

Hello, I recently installed the update that had been sent out over the past few days and one of my hard drives is constantly showing as active in my Task Manager despite me not running a program or even accessing that drive to go thru the folders and files. Is this a known issue that Windows after this update wants to access a drive all the time that is not my primary drive where I have the OS installed? This has only happened after installing the recent update and has not been an issue before today.

:)

 

Hard drive/ OS issue

a guy suggested :

• shutdown
• unhooked HDD
• restarted
• yay !!
• reconnected HDD
• restarted
• yay !!

also , try method 3
How do I unlock the drive where Windows 10 is installed?

 

Overclock your hard drive!!!

Heres a much easier hack that I realized quite a few years ago that really does work!

REQUIREMENTS:

• Hard drive with molex power connection.
• PSU with more than 1 strand that has molex plugs on it.
• Wire strippers, soldering iron if you're fancy, electrical tape if you're not.

STEPS:

• Take the strand of connectors from your PSU, and decide which one will be the donator for this overclocking adventure.
• Cut the yellow and orange cables, then twist them together.
• Find the power connector you've chosen as the overclocking connector, and release the orange cable from the connector. Now use your preferred method to bind them together, then place it back together.
• Plug in a drive and feel the speed!

Congratulations! You've just overclocked your hard drive!

 

Gigabyte motherboard, pc won't bootup after recent hard drive change

So I've previously had this problem when I added new SATA hard drives to an old one, all I had to do was switch hard disk priority to the one I wanted to boot from. But that's not working right now.

Error message: AMD Data Change...Update New Data to DMI!
Specs:

• Motherboard: Gigabyte ma785gmt-ud2h
• Four SATA hard drives, three 2tb and one 1tb
• One IDE hard drive, 160gb
• 6gb RAM
• Everything else is the default

What happened: I had an Amahi home server running on this PC with Ubuntu 12.04LTS as the OS. It was using the four SATA hard drives and everything was running smoothly. Then I read that it's easiest to have a setup where the OS/Amahi is installed on one small hard drive while the large hard drives are used to keep the files on, this makes it easy to update the OS without worrying about the files. So today I installed Ubuntu 12.04LTS on an old IDE 160gb hard drive that I had laying around, which would be perfect to use since there is exactly one IDE port on the motherboard.

I disconnected all hard drives, connected the IDE, installed Ubuntu, and rebooted. I got a "AMD Data Change...Update New Data to DMI!" message.

What I tried:

• Have the IDE be given priority over other hard drives.
• Connecting all the hard drives back, with and without the IDE hard drive. Same message.
• Disconnect all hard drives, connect IDE, and set BIO to opimised defaults. Same message.
• Disconnect CD drive with only IDE attached, same message. Reconnect CD drive, same message.
• Disconnect CD drive with only SATA attached, same message. Reconnect CD drive, same message.
• Disconnect CD drive with SATA and IDE attached, same message. Reconnect CD drive, same message.
• Just IDE connected, mess with the peripheral settings by changing "OnChip SATA Type" to ATHCI, RAID, or IDE. Tried this with "As SATA Type" and with "IDE" set for the port4/5 type
• Just IDE connected, disable SATA controller
• Disconnect IDE, reconnect original hard drives. I still get the same DMI message.
• Attempt to boot from the SATA hard drive that has Ubuntu on it, using each of the SATA ports.
• Update BIOS to F10B, disabling the "Remember DMI" option. I reconnected all hard drives and the CD drive (the pdf said the 'system' will redetect all devices). Now I got the "AMD Data Change...Update New Data to DMI! Update Success" message, still hanging there. Rebooted, now it's the original message.

So I am at a loss. Any suggestions?

Edit: there were many suggestions to try clear the CMOS, however that didn't seem to help the posters. I haven't tried that, but if people suggest I should then I will do so tomorrow.