Secondary HDD freezing and starting again

Geef

Distinguished
I have a 128GB SSD for main drive and a WD 10EZRX-00A3KB0 as my secondary drive. Everything was going great until I decided to plug in a USB Kingwin EZ-Connect to try and connect an older hard drive. Once I connected it I got the windows error "Your PC ran into a problem and needs to restart." I really didn't want to deal with errors so I disconnected the USB Kingwin thing. Ever since then once I start up my computer everything runs fine on my SSD drive but if I try to read any files from my secondary drive it will freeze for about 20 seconds or so then start going again for a little while then repeat. I double checked to make sure its not a power setting in windows turning off the drive or anything. I also ran WD DataLifeguard Diagnostics extended test and it didn't show any errors. I just can't figure out why it did that to me. Anyone have any ideas?
 
Solution
I managed to find the resolution to my own problem. My motherboard is an ASUS H170-PLUS D3 and there is a software program called Intel Rapid Storage Technology that runs on my machine for it. Inside the program it shows information and settings about the HDDs of the system. One of the settings is for LPM (Link Power Management) just like the BIOS setting. It has a ENABLE or DISABLE option. I found that mine happened to be on ENABLED in this program even though in the BIOS it was DISABLED. Once I put it on DISABLED in the program and restarted my machine everything started working again.

Geef

Distinguished
I managed to find the resolution to my own problem. My motherboard is an ASUS H170-PLUS D3 and there is a software program called Intel Rapid Storage Technology that runs on my machine for it. Inside the program it shows information and settings about the HDDs of the system. One of the settings is for LPM (Link Power Management) just like the BIOS setting. It has a ENABLE or DISABLE option. I found that mine happened to be on ENABLED in this program even though in the BIOS it was DISABLED. Once I put it on DISABLED in the program and restarted my machine everything started working again.
 
Solution